Storage / addressing / binding model rulings: 2026-08-14
Superseded by New-line runtime. The text below is the record as of its date.
Owner Q&A, 2026-08-14. Rules the open halves of
docs/proposals/2026-08-02-storage-model.md,
2026-08-02-node-addressing-model.md, 2026-08-02-deployment-binding-model.md.
Context: storage slices 1–2 are already on ce main (store registry,
attestations, MountsRoot funnel, landed honoring D5); D5 itself is
discharged and ce lane/store-slice2 (7e0cfe0f) is superseded; delete, never
merge (its atlas.sum deletes 16 applied migrations).
| # | ruling | consequence |
|---|---|---|
| M1 | Storage slice 3 is the next construction lane: the refusal gates: require_mounted wired into the PrepOp gate, --store validated against a real row, the ruled scale ceiling enforced. | Highest value per line; zero bytes moved. |
| M2 | Block volumes ship before the NFS shared store as the no-copy relocation escape; the P7 budgeted shortlist declares x-shc-volumes where moves really hurt; NFS lands after slices 3–4. | |
| M3 | A shared store holds ONLY the data (mounts/), never the whole deployment directory. Render artifacts (compose, manifest, app/, state) stay node-local; moves explicitly carry vapps/. | No two-renderer collision by construction. |
| M4 | Store reachability is probed LIVE at decision time (bounded probe at install/move gates); persisted attestations feed display (shc store ls, doctor) only. | No invented freshness TTL; no stale-green decisions. |
| M5 | Fresh-estate backup default: warn loudly until configured. Backups still run locally, but doctor + backup ls + install output carry a standing “archives share the node’s fate” warning until an off-node store is set. Production estates are already on S3 and unaffected. | |
| M6 | Durability is declared in a durability: block in backup.yaml, beside the exclude list; the storage mount grammar reads the same declaration. One source for both move-disposability and delete-criticality. | |
| M7 | terraform destroy of an occupied node HARD-REFUSES, naming the stacks in the way; explicit per-resource on_destroy="force" (or draining first) proceeds. The shipped warn-then-force is replaced. | Matches the removal-must-refuse-and-name ruling at the terraform boundary. |
| M8 | Genesis demotion: DO IT, with cold-start replanted: bootstrap becomes seed, the identity guards go, and vault cold-start becomes a declared cluster capability planted on a stably-chosen node, re-planted before any rotation touches its holder. | Node rotation becomes real on both estates. |
| M9 | Voter-deficit removals REFUSE without a flag (--accept-deficit / --rebalance). | |
| M10 | The terraform address-vocabulary rename lands NOW as one state upgrade (slices 1+8), gated on tofu plan showing zero changes on both estates after migration. | Stops the 228-use drift; pre-pays for IPv6. |
| M11 | ”There should be nothing special about the first init node” (owner verbatim, reinforcing M8). | Genesis demotion is not optional polish; every remaining first-node special case (bootstrap identity guards, cold-start residency, any genesis-only code path) is a defect to remove, not a corner to document. |
| M12 | No legacy APIs or compat shims kept around (owner verbatim: “i don’t want you keeping around legacy apis and shit”). | Standing doctrine, joins P10: when a surface is replaced, the old spelling/endpoint/shim is removed in the same program, not tolerated-read. Applies to the api-wire-dialect shim (steps 2–3 proceed to completion), the removed runtimes: fallback, and every future rename. |
Cell 6 (swarm + local volume) is not re-asked: placement ruling P2 already settles it: stateful on swarm auto-pins to its data node when using local storage (the landed derive-and-pin mechanism), floats otherwise.
shc@docs:~$