Brief For The pki.sgit.ai Site Agent: Specification For The Insurance Ecosystem Pack, What To Inventory Before Writing It, And The Four Findings That Are Already Established
Summary
The specification for a pack this brief deliberately does not contain, because writing it needs the codebase, the vault applications and the tooling surface. The objective: an end-to-end ecosystem on vaults where a new session is told the rules, handed its own policy, measured while it works, and refused by something that is not itself when it exceeds cover, visible in a room. First the inventory — nine items, none available to the session that wrote this — then the four findings to inherit rather than re-derive: the ledger must be an append lane because a write key grants purge; hook types include an HTTP variant, which is the difference between a setting and a boundary; token usage has four counters and the obvious one measured 562 for a session that moved a hundred and nine million; and June and August use mandate for opposite things, with August recommended. Seven sections the pack must cover, eleven questions it must answer (the ninth a decision), a first increment that produces a real refusal before any vault exists, and one acceptance test for the pack itself: a session that has read only the pack builds it all and asks nobody a question.
Key concepts
- The pack it specifies — written 3 September, after the inventory
- The inventory, done — the nine items with evidence, and the eleven answers
- The first increment — three git policies to two hooks, run
- The append lane — why the ledger cannot be a shared vault
- Question nine — mandate is the narrow thing; August governs
Key ideas
- The pack cannot be written honestly until somebody establishes what already exists.
- A write key grants configure and purge: an agent that can record its own usage can delete the record of it.
- A policy written against input_tokens would have measured 562 for a session that moved a hundred and nine million tokens.
- The word mandate names the maximum in one part of the corpus and the minimum in another, which is the most expensive kind of collision because both readings are plausible.
- Refusal must come from outside the agent's reasoning loop; balance derivation never runs in the agent; silence below cover is a requirement.
- A question an implementing session has to ask is a gap in the pack rather than in the reader.
On this site
Answered by packs/insurance-ecosystem: eleven documents plus change control, tools/, hooks/, policies/, a ledger and a room; build-order step 1 built and its acceptance tests run on 3 September.