10 — User stories, features and workflows

Summary

The pack turned into something a reviewer can sign off and a builder can work from. Six users — verifier, agent, issuer, processor, policy owner and auditor, split out as its own seat because it is the only one that exercises effective_from. Twenty-four stories, each with a test that can fail and a tag naming its phase, its defining document and its screen. Fourteen features with a status column whose honest reading is that everything at phase 0–1 is designed and nothing is built. Six end-to-end workflows, the mandate lifecycle as states, a traceability table, and a flat list of what the pack does not deliver — enforcement, receipts, confidentiality, attestation, a graph browser, a trust score, and estimates.

Key concepts

• The auditor as a separate seat — a verifier asks about now and may stop early; only an auditor reads the log backwards
• WF-6 has no acceptance test — a finding against the build order, recorded as C12 rather than tidied away
• P2 pulls against A3 — a public processor log is the oracle the blind ack exists to withhold — unresolved, and named

Key ideas

• A story whose acceptance criterion cannot come out negative is a description wearing a story’s clothes.
• A3 is a story whose success is an absence — the easiest thing here to break by accident and the hardest to notice.
• Estimates are deliberately absent: a fabricated number in a delivery document outlives every caveat attached to it.

Read the document