Placement 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. Amends
2026-08-11-rebalancer-v1-foundations.md:
its R1 is REVOKED (P1 below). Verbatim owner quotes carry the definitions.
| # | ruling | consequence |
|---|---|---|
| P1 | R1 is REVOKED: the swarm runtime is FIRST-CLASS. Owner: “why would swarm runtime be legacy. when using swarm runtime the default is to not have it pinned to a node (by not pinned of course it still is pinned to all nodes that have runtime set to swarm).” | Swarm apps float across swarm-pool nodes by design. Capability investment in swarm is allowed. Every “swarm is legacy/second-class” consequence in the 2026-08-11 proposals is void; the runtime-is-the-placement-contract proposal’s premise stands (runtime carries the placement posture), with P2’s data exception. |
| P2 | Stateful on swarm needs no pin, unless it uses LOCAL storage. Owner: “stateful on swarm doesn’t need to be pinned to a node unless it’s local storage that it’s using. i thought i’ve said this before.” | The landed ce derive-and-pin fix (first-render mobility from compose + backup.yaml) is the correct mechanism. The 7 live production swarm deployments on node-local volumes (bitspur dtrack/gitlab/ollama/penpot; promanager dtrack/gitlab/penpot) predate it and must be brought under it, pinned to the node holding their data. Stateless swarm apps stay floating. |
| P3 | Directed moves: SHC names the destination node when an operator applies a rebalance/evacuation; the placement pin persists as the record of that intent. | Bare force-updates (measured: 0/12 moved off an 83%-committed node, ~4.1 s blip each) are not the apply mechanism. Amends ruling D’s “swarm picks destinations” for the applied-plan case. |
| P4 | Drain-live + Group E campaign AUTHORIZED. Prove the merged drain fix (ce ead32ab7) live 0→N, then run E1–E10: full node replacement, never executed on any cloud. | Shares disposable infrastructure with the backup proof campaign (B7). |
| P5 | Wave deploy is FUNDED behind its six-item acceptance bar (topological waves, one-shots as replicated-jobs, daemon blocks on task state between waves; mutation control + midpoint/traefik/postgres proofs). | Consistent with P1. Unlocks the ~38 ordered packages currently refused the swarm runtime. The refusal stays until the bar is met, never weakened to ship. |
| P6 | requires.runtimes violations REFUSE at Phase 1: a 4xx before any row is written, coded error naming the fix. | Closes the F3 FAILED-row debris; makes the ruled ordered-preference list enforced instead of advisory; three doc pages stop lying. |
| P7 | Block volumes: budgeted shortlist, measure first. Run the du -sb sweep on both estates, then declare x-shc-volumes only where a move is a real outage, inside the 16-per-node cap. | No broad catalogue campaign. |
| P8 | drain KEEPS its evacuation meaning. Pool membership gets a different word entirely; docker’s availability: drain sense is never surfaced as “drain”. | No CLI break. The internal naming tangle is documentation work, not a rename. |
| P9 | protected means CANNOT DESTROY/UNINSTALL, nothing else. Owner verbatim: “there is no never move flag. things can always be moved. protected simply means you can’t destroy it aka uninstall it.” | The current clone.Move refusal of protected deployments is a DEFECT: move (and therefore drain) must always work on protected rows. Fix the refusal, fix the help text, test both directions (protected blocks uninstall/destroy; protected does NOT block move). |
| P10 | No legacy spellings. Owner: “no legacy please.” The top-level runtimes: spelling becomes a hard catalogue build failure; mailcow migrates to requires.runtimes in the same commit, and “mailcow only supports compose runtime” (owner), so its declaration is [compose] only. | One spelling forever; the tolerated-read fallback is removed. |
| P11 | Add the node.architecture column so requires.architectures stops being inert. | One column, existing writers extended, one Phase-1 check; ivatar’s measured amd64-only constraint becomes enforced and arm64 nodes become safely addable later. |
Deferred (not ruled): the shc placement report plan-only verb; the owner
did not find the framing understandable; re-present with a concrete example
before asking again. Nothing is blocked on it.
shc@docs:~$