A challenge declares not only that the record is wrong but what should stand instead. Filed with mode **REPLACE**, it carries the successor — a drafted entry (name, scope, definition), a corrected definition or edge, or an existing confirmed entry — and the judges rule on the whole swap: an upheld replace-challenge strikes the target and seats the successor in the same ruling. The succession is recorded forever on-chain (`SUPERSEDE REPLACED:<successor>`), the target's edges re-point to the successor so the web keeps its shape, and the challenger authors the successor with its normal rewards. Filed with mode **STRIKE** (the default), an upheld challenge removes the target outright — proper when nothing should stand in its place. Removal cascades: a struck entry's pending edges and definitions are voided (stakes refunded, no penalty), and its accepted ones are struck as orphans with **no clawback** — their authors were not wrong; their foundation vanished. Prefer replace when you know the better carving: the taxonomy is improved by succession, not by holes.
IX. Succession
Law 30: Replace or remove (filed through the one door of Law 31).
A challenge declares not only that the record is wrong but what should stand instead. Filed with mode **REPLACE**, it carries the successor — a drafted entry (name, scope, definition), a corrected definition or edge, or…
These are the human-readable bytes this deployment serves. Recorded amendments and dials plus content-addressed decision rules are the evidence of what it enforced.
The covered lawbook expression is licensed under Creative Commons Attribution-ShareAlike 4.0 International. Attribute it as “Systema Constructum lawbook — Jacob Baltz,” retain the license, and indicate changes. Copyright permission does not ratify the text or confer canonical authority.