05 — Workflows and user stories

Summary

The pack as deliverables. Five users — the visitor at five grant positions, the librarian, the sharer and recipient, the run operator, the site agent — and twenty stories each carrying a test that can come out negative, tagged with its defining document and shipped status. The feature table's honest reading is the inverse of the registry pack's: the instrument is built, the programmes around it are not. The flat refusals list is repeated from the principles so a reviewer can disagree in one place: no risk acceptance, no scanning, no backend, no score, no A/B statistics at qualitative sample sizes, no preferences verdict from synthetic readers.

Key concepts

• A test that can fail — the sibling pack's standard, applied — a story that cannot fail is a description
• The acceptor is nobody — no user of this tool is ever asked to sign anything — P7 as a user model
• V8, the standing story — no request leaves the origin — re-run before every release

Key ideas

• V12 (the three sets) is the one story gated on an open decision rather than on effort.
• The librarian's stories become scripts in phase 1; at v2 they are conventions, and the column says so.
• Workflow 7 — test a page before building it — is a workflow of this product, not just of its development.

Read the document