Version two
The reviewed read
The spec asks for the reading. Putting that reading in the hands of a real team asks for more: stops, recorded decisions, ownership, an audit trail. The reading is the substrate. The review is the product. That distinction is the argument of this version.
Spine built. Roles and persistence designed, not built.
Built and running
- The run stops when it cannot decide. A policy named in a schedule of underlying insurance that is not in the document set halts the reading. The person deciding is shown the page and the line that names it, because a page number is a promise they would otherwise have to take on faith.
- Every step names who performed it. Model or code, which instruction document governed it, and that document’s content hash. The interpret-and-execute split is visible in the run rather than asserted in a readme.
- Every value traces to a page and a quote, and the quote is verified in code against the text of the page it cites. A reading that says page thirteen reads a certain way is turned into page thirteen reading that way, or it is not used.
- Uncertainty has its own answer. Cannot determine is a first-class result, and a finding that depended on a missing document is marked degraded automatically. A clean result cannot be constructed without a declared scope.
Designed, not built
These are shaped and argued for in this engagement. They are not running, and this page does not imply that they are.
- The decision as a record. When a person resolves a halt, that resolution belongs in the review as evidence, with who and when, rather than in a log line.
- Documents belong to a client account, not to a browser session. Storage today is an interface with an in-memory implementation behind it, which is the right shape and the wrong lifetime.
- Roles and permissions. The person who reads is not always the person who accepts.
- Audit history. Readings of the same program over time, so a renewal can be compared against what was there before.
Done when
The operational parts are shown working live, and the parts that are designed rather than built are labeled as designed. Roles, permissions, and persistence are presented as design in this engagement.