03 — The library
Summary
A library entry is a measured, dated grant for one environment, published in the registry, carrying no personal data ever, and referenced rather than copied by an instance in the risk product. It is generated, never authored, because a hand-written grant is a wish; drift is caught by re-measuring and diffing, with the alarming case being a node that moved from setting to expectation — a control removed while nothing broke. The first entry was generated by measuring the site agent's own Claude Code Remote container, and the measurement refused itself: a single self-inspection probe was blocked by an account-level classifier evaluating outside the agent's loop, so the two nodes it would have filled are marked unknown rather than guessed. That refusal is a boundary-tier control observed working on the measuring agent — the cleanest demonstration of the pack's own three-tier test, produced by accident — and node n3, a release-branch push whose branch discipline is only prose, is the pack's thesis caught live.
Key concepts
- The first measured entry — nine nodes, two marked unknown, one refusal that is itself the finding
- Drift as a diff — setting → expectation is the silent case: containment stopped existing
- Floor, not census — the measurer is the subject, so the entry says floor on its face
Key ideas
- The refusal to self-measure is the sharpest datum: a boundary caught working on the measuring agent.
- Node n3: the environment can push to a release branch that deploys a public site, and only prose says which branch.
- One entry proves the format, not the dataset; a blind-spot delta needs two environments and ideally two agents.