The Resource Pool: A Grant That Depletes, And The First Loss Data This Pivot Can Have
Summary
The second axis. Every memo before this one rates CAPABILITY — what an agent can reach. This one rates CONSUMPTION, which is orthogonal to all of it: two placements with byte-identical grant trees can differ by two orders of magnitude in what they burn, and nothing the estate measures would see it. A pool of tokens underwritten for a population rather than allocated per agent, on the reasoning that one execution in a hundred spiking is fine where a hundred spiking is not — which is correlated risk, named in a single line, and the first concrete instance of the aggregation problem doctrine 01 recorded as a rule and never implemented. A resource pool is a grant that DEPLETES: every grant in this corpus is static, and a pool carries a remaining that no existing node has, which makes it a fourth primitive rather than a restatement. The largest thing here is not any of that. The pivot has argued about insurance for eleven memos with no loss data, no claim shape and no pooling, and this supplies all three at once — in a currency that is not money, from meters that already exist for billing, which is why it needs no carrier and puts nobody in the line. A budget overage is a loss event that is dated, quantified, attributable and independently recorded by the supplier's invoice, so loss-event/v0 can finally be drafted against a real instance. It also resolves GM-D78's collision and finds doctrine 07's first mover, because the resource supplier has a reason to refuse that nobody had to argue it into: it is paying. Corrected: the memo says the pool defines the grant, and it does not. A budget bounds volume, never reach, and the cheapest catastrophic action is cheap.
Key concepts
- The resource pool — doctrine 11
- The rating — the aggregation problem this gives a concrete instance
- The policy as a statement — the first mover it was missing
- The world model — the missing primitive this supplies
- The schemas and the clocks — GM-D78's collision, resolved
Key ideas
- A resource pool is a grant that depletes — every other grant here is static, and exercising it does not shrink it.
- A pool bounds how much an agent does. The mandate bounds what. The cheapest catastrophic action is cheap.
- A token pool is risk pooling in a currency that is not money: no carrier, no capital, no authorisation, and structurally the thing insurance does rather than the thing underwriting does.
- It's okay to have one out of 100 to have a spike, but it's not okay to have 100 having the spike — correlated risk, named in one line by the memo itself.
- A budget overage is a loss event, and unusually it is one nobody here has to instrument: the supplier's invoice already records it.
- The counter exists and somebody else runs it. Reading a meter that exists for billing does not put this project in the line.
- The resource supplier has a reason to refuse: it is paying. The first natural relying party in eleven memos.
- Same policy, three tiers, decided entirely by who holds the meter.
- remaining > 0 cannot be unknown — the only warranty in the pivot that fails one way instead of three.
- A pool without a per-occurrence limit converts one runaway agent into an outage for every well-behaved one.
- The memo has described an excess-of-loss treaty and names three of its four parts.
- The shape applies to a resource metered by a non-consumer, fungible, and depleting. Capability fails two of three.
- Tokens are a currency people actually want, so 'a level is never declared, only derived' stops being hygiene and becomes the control holding the whole thing up.
- The pool is what a rate limit cannot be: permissive per agent and bounded in aggregate. The buffer is the entire product.
On this site
Adds insurance doctrine 11 and reopens a series called complete at ten. Proposes GM-D86 to GM-D95: consumption as a second axis and the pool as a fourth primitive; a pool bounds volume never reach (correcting the memo); pooling in a non-money currency; consumption as the first obtainable loss data; GM-D78's collision resolved; the supplier as first relying party; the only warranty that cannot be unknown; the excess-of-loss structure and its missing per-occurrence limit; the generalisation's three-part boundary; and a desirable currency making 'never declared, only derived' load-bearing. The v0.33.82 series gate fired on doctrine 10 when this memo was filed, and was rewritten to forbid a hand-typed denominator rather than check one.