Trustworthy Flows

Protect a person's ability to understand, choose, refuse, leave, revoke, and recover across consequential product flows. Audit the decision system, not the visual polish of one screen.

Operating contract

• Preserve source designs, components, code, data, and behavior unless the user explicitly authorizes edits.
• Scope work to the selected decision and the adjacent path required to understand entry, commitment, outcome, exit, revocation, and recovery.
• Reuse the existing design system, product language, application architecture, and interaction conventions.
• Separate observed, runtime verified, declared, hypothetical, and proposed evidence.
• Never infer intent from an interface alone. Describe the observable mechanism and plausible consequence.
• Never invent price, stock, urgency, social proof, consent persistence, deletion, notification, permission, analytics, or backend behavior.
• Do not diagnose a person's cognitive bias. State that a presentation may exploit or amplify a known bias.
• Do not declare an interface legal, compliant, safe, accessible, or free of manipulation from a static artifact.
• Preserve legitimate protective friction. Remove friction that exists only to advance the product's commercial preference.
• Escalate serious legal, privacy, accessibility, financial, child-safety, or coercive-control risks to the appropriate specialist.

Choose the mode