08 — The build record
Summary
The consolidated record of what moved from specified to built between site v0.1.25 and v0.1.29 — the register, the pack, the enforcement point and two measured library entries — with a fetchable artefact named for every claim. Written because a corpus that records its corrections but not its deliveries will misstate what it has built: three days after the register shipped, the registry pack still described its own subject as entirely unbuilt in three places. It carries the four findings that cost something to record, the table of what the readiness report's six blocking questions became (three closed by execution, three still the project lead's), and a flat list of what remains only written down — a real issuer key, a boundary-tier enforcement point, the capability vocabulary, the append-lane write path, and the entire risk-product half.
Key concepts
- The register, built — eleven records, twenty-three signed statements, sgit-compatible by round-trip
- What is still only written down — a build record that lists only deliveries is a sales document
- The readiness report's six questions — three answered by building, three still open
Key ideas
- The registry is built; the trustworthy registry is not — the root is a fixture and says so.
- Three of six blocking questions were answerable by building rather than by deciding.
- A build record written by the builder names fetchable artefacts, which is a mitigation and not an audit.