Warden plan
tier: hermetic requires: []
Pending stub — GATED criterion. The precondition below is not built; this plan reports the criterion as pending (skip, never fail) until it lands. When it does, replace this stub with a real plan in the shape of
25-cr-18/26-cr-25/27-cr-20.
Register: ~/.studio/master.withrobin.ai/project/rfc.one/criteria-register.md (status there: PENDING OWNER ACCEPTANCE; accepted by the 2026-08-31 proxy screen).
### CR-22 — Revision succession: survival and removal retraction - Statement: Accepted judgment formalized from a wiki survives edits that preserve the stance and dies with edits that remove it (§3.2's succession clauses). - Metric: Survival — fraction of accepted stance Claims whose stance the revision preserved that are not retracted after the revision batch (a contested transition is not a survival failure; what succession prevents is retraction through the withdrawn revision Entry). Removal retraction — fraction whose stance the revision removed that are retracted within Δ plus the batch's processing time. - Dataset/inputs: For 10 authored wikis per workspace (exclusion-on arm; succession is orthogonal to the exclusion), three drafted stance Claims per wiki accepted through claim adjudication; two revisions each through ordinary capture — one stance-preserving edit (wording, ordering, a fixed typo), then one edit removing one stated stance and keeping the rest. - Threshold: Survival ≥0.95; removal retraction ≥0.95 (both Holm-corrected secondaries of §11.2's family). A survival miss is a succession false negative (the entailment judge failed to match a successor to prose still asserting the stance); a removal-retraction miss is a false positive (prose no longer asserting the stance was matched anyway, laundering the removal). - Drop condition: Redesign: survival <0.95 → stronger succession matcher, or fall back to the alternative rule considered and not chosen (acceptance pins the justifying revision Entry, exempt from succession-withdrawal, drift stamp carrying the divergence); removal retraction <0.95 → tighten the entailment bar. - Source: Companion §11.2 (mechanism in §3.2). - Tier: gated — requires the Claim layer, claim adjudication, and wiki revision machinery.
Precondition: requires the Claim layer, claim adjudication, and wiki revision machinery. Not built at HEAD 7f379974 (verified 2026-08-31: no 'claims', 'dimensions', or 'initiatives' tables in server/src/db/schema.ts, and no conflicts_with edges anywhere in server/src or packages/). Claim adjudication and wiki revision machinery have no code marker to probe.
set -uo pipefail
source "$WARDEN_LIB/assert.sh"
cd "${PROJECT_ROOT:-$(git rev-parse --show-toplevel)}"
SCHEMA=server/src/db/schema.ts
MISSING=""
grep -q "'claims'" "$SCHEMA" || MISSING="$MISSING claims-tables"
if [ -n "$MISSING" ]; then
warden_skip "CR-22 — Revision succession: survival and removal retraction" "pending: requires the Claim layer, claim adjudication, and wiki revision machinery — gated criterion, precondition not built (probes missing:$MISSING)"
else
warden_skip "CR-22 — Revision succession: survival and removal retraction" "schema probes now pass — upgrade this pending stub to a real plan before CR-22 can bind (probes are heuristic, not proof)"
fiPending stub, hermetic on purpose: the guard reads the checkout only and emits skip in every branch, so this plan can never red a run — the criterion surfaces in every summary as pending with its precondition named. The probes are heuristic activation bells, not proof: quoted table names (and conflicts_with where the contradiction check is a precondition) flip the detail text when the machinery lands. The real plan must quote the criterion verbatim, turn its thresholds into warden_pass/warden_fail gates, and follow the conventions the three runnable plans set: machine-local fixtures (25-cr-18), NLI probe and versioned judge prompts (26-cr-25), data-keyed guard activation (27-cr-20).