§17b. Bypass register

planarian @ a924e09 · Spec v4.6 · snapshot main · all versions

docs/bypasses.md lists every known route by which the machine can reach a state this spec says cannot happen, or by which a stated guarantee stops describing the real machine, whether or not a proof is involved. One row per route: id (B for open, X for accepted; never reused), route, what it breaks (always invoked, tamperproof, or correct), severity (High: defeats a stated guarantee in the shipped configuration without root; Medium: needs root, a network position, or a likely deployment, or the spec overstates the mechanism; Low: narrow, availability-only, or process; Accepted: outside the claim by design), status, mitigation, phase, and the invariants it limits (all, or — for none; §17c). Any change that adds a path to the machine (a request type, backend call, hook, or posture option) adds a row or states in its PR that it opens none. planarian-gym verification --gate checks the file’s format and fails a gate with an open High row. The file has three tables — Open, Closed (status Closed (<sha>), kept forever), and Accepted — and a row moves between them when its status changes; the format check rejects a Closed row in the Open table. Rows added at v4.6: B-20 (High, Open: agent-name collision rebinds a running agent’s authority; closed by I24); X-12 (Accepted: an override-file writer that does not take the daemon’s lock).

Verus subset applies to schema, policy, txn only. exec, diagnose, incident, state keep the no-dyn and no-unsafe rules so they can be brought in later; intent, console, daemon, cli, gym are unconstrained.