Status: RULED (R91, root `REVISION_REGISTER.md`, 2026-09-19). Nothing to build.
This file exists so that a future round cannot add settlement here by accident. It is a list of absences, and the absences are the enforcement — the same discipline as connect-model.md §3's TransportPeer, which has no create because the missing constructor is the rule.
`computedriven` owns the count format. `locu.systems` owns the money.
The contract lives at locu.systems/docs/spec/91_SETTLEMENT.md. It was drafted here on 2026-09-19 as settlement-model.md and moved by R91: a substrate that carries our billing model cannot be run by anyone who is not us, and billing policy is not reusable the way the count record is.
| Must never gain | Why |
|---|---|
a payment or balance field on PeerExpectation | it is the convenient place to put one, and it is the single most likely way the contract is lost |
any settlement type nameable from cd-connect or cd-rendezvous | connect-model.md §1: a connector that can NAME a rendezvous type can branch on provenance. One level up: a connector that can name a settlement type can branch on solvency |
a solvency branch in cd-core / cd-kernellet admission — R90 | it would qualify the third clause, only the lineage decides what they may do, with an asterisk for money. And a settlement round trip on an admission path costing ~10² cycles (floor-attribution.md) makes settlement the dominant cost by six or more orders of magnitude |
| a debt, arrears or balance kind in the lineage — R91 | a settlement failure is the host's receivable, not a fact about what the world did |
There is no `cd-settle` crate and there is not going to be one. R90 removes the floor-side component entirely, so nothing remains here for a crate to hold.
90_LOCUS_HOSTING.md §2a's count record — a class symbol per admitted transition, grouped by (transition class × epoch). It has to exist for the meter regardless, it is genuinely reusable, and it carries no billing policy. That is the whole interface.
DISCOVERY CHOOSES WHERE WE TRY. cd-rendezvous here
AUTHENTICATION DECIDES WHOM WE REACHED. cd-connect here
ONLY THE LINEAGE DECIDES WHAT THEY MAY DO. cd-core / cd-durable here
SETTLEMENT DECIDES HOW MUCH MAY BE SPENT. ───────────────────── NOT HERE