03 — The policy object
Summary
Four documents and one derivation. The policy carries its rules version, its issuer and policyholder, the mandate it prices pinned by hash, an interval with a timezone, a draw mode whose default is recorded and whose threshold makes a draw requested, one entry per unit with a named meter, and an exclusion with a reason wherever the loss is irreversible. The event is generic on unit, names the policyholder as acceptor on every draw, and carries tokens as four counters. The balance is never stored: derived by the maintainer from the four documents with the reserve subtracted first, and where the evaluator's arithmetic at the time disagrees with the derivation, the derivation wins and the disagreement is a finding. The git pilot policy is built; the token policy is measured and deliberately unbanded.
Key concepts
- Every unit names its meter — a unit without one is refused by the schema
- The reserve is subtracted first — the catastrophe layer no verdict may reach
- Four counters, no bands — the token policy as instrumentation
Key ideas
- A stored balance is stale the moment an event lands elsewhere, and a balance maintained inside the insured is the insured marking its own homework.
- A hard cap on bytes into history is not the top of the buffer; it is the boundary of insurability.
- The request threshold is two-thirds of the exclusion so that the requested-draw workflow is exercised on real commits.