Warden plan

28 - CR-03 (pending): Claims-in-index retrieval contribution

tier: hermetic requires: []

28 - CR-03 (pending): Claims-in-index retrieval contribution

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.

Criterion implemented (verbatim from the register)

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-03 — Claims-in-index retrieval contribution - Statement: Indexing Claims alongside Signals improves retrieval over a Signals-only index (arm (v), the retrieval half of the thesis alternative). - Metric: nDCG@10, arm (i) minus arm (v). - Dataset/inputs: Same query sets as CR-01; arm (v) is the hybrid baseline with Claims removed from the index. - Threshold: None stated as pass/fail; decision rule: if (v) matches (i) within the noise of the test, Claims are not contributing to retrieval and the quality half of the thesis rests entirely on §10.2 (CR-04). - Drop condition: Not a component drop; feeds CR-19's thesis verdict. - Source: Anchor §10.1. - Tier: gated — requires Claims layer.

Named precondition

Precondition: requires the Claims 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/).

Skip guard

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-03 — Claims-in-index retrieval contribution" "pending: requires the Claims layer — gated criterion, precondition not built (probes missing:$MISSING)"
else
  warden_skip "CR-03 — Claims-in-index retrieval contribution" "schema probes now pass — upgrade this pending stub to a real plan before CR-03 can bind (probes are heuristic, not proof)"
fi

Shape (note for the next author)

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 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).