The first five minutes are proven on every release: a stranger goes from the link to a built change, timed, with nothing to copy and nothing to read twice #11158

Why. Owner: "the product experience should be something that would make steve jobs smile." Each step has its own issue; nobody owns the whole. A probe on 2026-11-10 found the seams: a claim link to copy, a passkey demanded before a password, "needs a subscription", a 503 on the first form, a repository page saying "nobody can change it" to its owner.

The journey, as one standard.

1. Open the forge's link. The first screen says what this is in one sentence and has one field and one button.
2. Type a name; press the button. One more screen: username and password (a passkey is offered afterwards, never required first).
3. You are in your forge, signed in. The first screen has exactly one next step: say what you want built (a text box), with one line beneath about the key or the included credit (#11154).
4. Write one sentence. Within a minute the crew is visibly working; within five the app's link shows the change.
5. At no point: a link or code to copy, a word the person has not been taught (subscription, autonomy, cell, child, claim), a 5xx, a dead end, or a page that says something untrue about them.

What.

• A browser journey test that does steps 1–4 against a real cell with a stub model, asserting the screens count (at most three before the forge), the time budgets (forge ready under 20 s; first crew activity under 60 s), no 5xx in the network log, and none of the banned words on any screen of the path.
• The same journey runs as a release proof against production with a real, tiny ask on a throwaway forge that is removed afterwards; its timings are kept and shown on the release card. A release whose journey fails is not called proven.
• Fix what the probe found on the path and is not already covered: the passkey-first "everyday account" prompt, the owner's own forge repository reading "nobody can change it", and any screen that fails the banned-words check.
• docs/DESIGN.md gains the journey as a short section: the five steps and the budgets, so later work is judged against it.

Acceptance. The journey test is green in the check and on the release card with its timings; a deliberate regression (re-adding a copy-the-link step) turns it red.