The Claim Is The Draw: Money As A Metric, And A Push Budget Claude Can Run Today
Summary
Two halves. The reframe: the money in a policy is a metric for what the claim buys, so pay the claim in the thing itself — tokens, access grants, bandwidth, bytes — with the amount pre-approved. Then a draw on the pool IS the claim, paid in the resource and settled by the check in milliseconds, because trigger, cover and payment are three fields of one document read by one function rather than three parties' documents reconciled by people; the speed is a property of the mapping, and it is also why this stage waits on nobody. The worked policy: pushes per day and bytes per push, each with a normal band, a per-occurrence limit and a daily pool — all four excess-of-loss parts, twice — with the pool shared per repository so that pooled fate is deliberate and the per-occurrence limit is what stops one agent spending it alone. 'Let Claude manage this' read honestly: a skill the agent runs on itself is a SETTING, the first rung of a ladder whose upper rungs — a required CI check, a host push rule — take the same policy.json. And the first MVP, built before the brief was written: insurance/push-policy, whose checker replayed the last twelve site releases and refused every one at ten to forty-three times the per-push maximum, because the release stamps the version into every page. The policy is not mis-calibrated; the estate is. The hook is shipped and not installed.
Key concepts
- The push policy — the first MVP — policy, checker, ledger, hook, skill
- The claim is the draw — doctrine 12
- The resource pool — doctrine 11, which this finishes
- Not in line — why the skill is a setting
- Change control — GM-D97 to GM-D103
Key ideas
- The money in a policy was always a metric for what the claim buys. Pay the claim in the thing itself and the proxy disappears.
- A draw on the pool is a claim, paid in the resource, settled by the check itself. The payment is the permission to proceed.
- A claim settles in milliseconds when trigger, cover and payment are fields of one document read by one function. The speed is a property of the mapping.
- The pool is per repository, shared by every agent pushing to it. When the pool is out, nobody pushes — and that is policy, not accident.
- A skill that runs the check on the agent itself is a setting, and it says so on its own face.
- The ledger is the loss data. The numbers are placeholders until it can re-fit them.
- Bytes measured before the push are a floor on what the agent is asking to send, never a bill.
- Twelve of twelve releases refused. A release that touches every page is a policy breach in slow motion; the policy is not mis-calibrated, the estate is.
On this site
Adds insurance doctrine 12 and the first MVP, insurance/push-policy — policy.json, check.py, an append-only ledger, a sample pre-push hook shipped and not installed, and a Claude skill at .claude/skills/push-policy. Proposes GM-D97 to GM-D103. gen_insurance gains an MVP gate (a README with a does-not-prove section) and an MVP page builder; llms.txt's second carry item now says one thing is built and what tier it is.