00 — The leading brief
Summary
The pack scoped by the specification's own test — a session that has read only the pack builds the vaults, wires the hooks, authors a policy, runs a working day and produces a room showing a refusal, a recorded draw and a waiting request, asking nobody a question — and by the project lead's instruction of 3 September that for the pilot one session with the vault key may run any role in any vault, integrity deferred and detected rather than prevented. The inventory the specification demanded was done first and changed the design in three places: there is no board application, so the room is a vault app; the platform fails open when a hook times out, so the git hooks are the enforcement point and the Claude hooks are instrumentation; and the eighteen June briefs were read, and only the naming brief collides. The four inherited findings are each re-checked here, including the four token counters measured again on this session's own transcript: sixty-eight thousand on the obvious counter, seven hundred and fifty-seven million in all.
Key concepts
- The pilot relaxation — one key, one session, every role — and every file shape unchanged
- The platform fails open — why the git hooks refuse and the Claude hooks do not
- The four findings, re-measured — lane, http, four counters, and the word that meant two things
Key ideas
- Every question the implementing session has to ask is a gap in the pack, and is filed as an amendment rather than answered in chat.
- Turning integrity on is a change of where things run, not what they say.
- A session that moved 757 million tokens reads as 68 thousand on the obvious counter.