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-24 — Artifact engine: stance legibility with citation fidelity - Statement: The engine renders stance-true artifacts from the same Claim set without loss of citation fidelity — stance conditions treatment, not truth. - Metric: Primary: stance legibility — two blinded raters per render, each shown an artifact and both wikis of an opposing pair, asked which governed it; a render is legible when both raters name the governing wiki (the anchor's §10.6 both-raters convention), κ reported; scored with a cluster bootstrap over intents (renders arrive in pairs sharing an intent and a wiki pair and share raters within a workspace — a binomial over renders would inflate the nominal level under correlated guessing). Secondary: ALCE citation recall/precision of stance-conditioned renders non-inferior to the stanceless control, paired per intent. The anchor's precondition check on engine renders and on the display surfaces of 20 wikis per workspace (§2 extends renderer obligations to every family member). - Dataset/inputs: 20 intents per workspace, each rendered under both wikis of a §11.2 opposing pair (40 artifacts per workspace, 120 pooled in 60 intent clusters) plus one stanceless render (empty governing set) per intent as control; frozen Claim set, standalone engine runs (no derivation stages), ≤1 governing wiki per render — the per-Claim conditioning assignment is never exercised (field arithmetic with a deterministic rejection rule; no experiment of its own). - Threshold: Legibility above the 0.5 chance rate (conservative bound for the both-raters statistic: independent guessing sits at 0.25, perfectly correlated at 0.5 — valid at any rater correlation), one-sided at the protocol's per-look level, design effect 0.8 (what the test is powered for, not a second bar; power above the floor at 120 renders / 60 clusters even at full within-pair correlation); citation recall/precision non-inferior within 0.05 absolute; precondition check 100% (any miss a defect). - Drop condition: If stance-conditioning costs citation fidelity beyond the margin and the redesign (move stance source from prose conditioning to the wiki's citation edges — the wiki selects and orders what renders, prose stops steering characterization) does not recover it, the governing-wiki input is dropped and the engine renders stanceless — the weakened second read path of §1. Redesign trigger: legibility point estimate <0.8 with citations intact. - Source: Companion §11.3 (mechanism in §7; falsifier pointer at §7's close). - Tier: gated — requires the artifact engine and the Claim layer.
Precondition: requires the artifact engine and the Claim layer. 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/). The artifact engine has no code marker to probe. The CR-25 floor this criterion's citation clause compares against is already recorded by 26-cr-25 in warden state (cr25_alce_recall_floor / cr25_alce_precision_floor).
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-24 — Artifact engine: stance legibility with citation fidelity" "pending: requires the artifact engine and the Claim layer — gated criterion, precondition not built (probes missing:$MISSING)"
else
warden_skip "CR-24 — Artifact engine: stance legibility with citation fidelity" "schema probes now pass — upgrade this pending stub to a real plan before CR-24 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).