Status: Phase 1 stub. Matures in Phase 5 per §8.1. Audit references: patterns #28, #35.

Statement

Trust copy, explainer text, security disclosures, onboarding hints, and any content that establishes why-the-user-should-trust-this-app must appear at content parity across mobile and desktop. Desktop-only "side panels" of trust content are forbidden — if it matters enough to render on desktop, it matters enough to render on mobile.

Why

The audit caught two recurring patterns across the screen body:

Pattern #28: desktop layouts shipped trust callouts ("end-to-end encrypted", "your nsec never leaves your browser", "no recovery by design") in side panels that simply vanished on mobile. The mobile user got the same flow with none of the assurance.
Pattern #35: desktop hover-revealed help microcopy that, on mobile, had no analogue — neither tap-revealed nor inline.

The unstated assumption was that mobile is the primary surface and desktop the bonus, so cutting content for mobile was acceptable. Inverted: mobile is the canonical layout (P-1), and desktop is the responsive accommodation. Cutting content from the canonical layout in favour of the accommodation is the wrong direction.

How

Per-PR contract item #15 (added in v3, §3.1): every primitive PR with a mobile and desktop variant must show both in its Storybook and Playwright capture. If a piece of content appears on one and not the other, the PR cannot merge.

Trust content is rendered through <MetaRow variant="trust"> (Phase 1 Track B PR — <MetaRow> consolidation), which ships identically on mobile and desktop with only its container changing. Hover-only content patterns are converted to tap-revealed disclosures using <Popover> (Phase 1 Track B addition) which works equivalently on touch and pointer.

Phase 5 deepens this stub with audit-pattern counter-examples (screens that violated #28/#35), per-route citations, and the parity-check automation in the Playwright suite.