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-19 — Anchor thesis falsification (composite) - Statement: The thesis-level verdict over the component results. - Metric/threshold: Quality half fails if CR-01/CR-03 (Signals-only arm matches full system on retrieval) and CR-04 (per-request reasoning matches on artifacts) both fail against the alternative. Cost half fails if CR-14 finds N* above observed N̄·m or no break-even. Weak failure if CR-13 shows staleness rising with accumulated structure. Any single component failing its own drop condition removes that component and leaves the thesis judged on the rest. - Dataset/inputs: Aggregates CR-01 through CR-14. - Drop condition: Any of the three failures returns Robin to the alternative (no persisted Claims; hybrid retrieval over Signals; per-request reasoning for artifacts). - Source: Anchor §10.8. - Tier: gated — composite over gated criteria.
Precondition: requires component verdicts for CR-01 through CR-14 (composite over gated criteria; it adds no thresholds of its own). 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/). A composite binds only on component verdicts, so this stub skips unconditionally until the component plans exist and have run.
set -uo pipefail
source "$WARDEN_LIB/assert.sh"
cd "${PROJECT_ROOT:-$(git rev-parse --show-toplevel)}"
# No greppable code marker exists for this precondition yet — unconditional
# pending skip; the upgrade decision is human.
warden_skip "CR-19 — Anchor thesis falsification (composite)" "pending: requires component verdicts for CR-01 through CR-14 (composite over gated criteria; it adds no thresholds of its own) — gated criterion, precondition not built"Pending 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 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).