Warden plan

28 - CR-01 (pending): Dimension-aware reranking gain

tier: hermetic requires: []

28 - CR-01 (pending): Dimension-aware reranking gain

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-01 — Dimension-aware reranking gain - Statement: The Dimension term improves ranking over the hybrid retriever plus standing penalty, and the improvement is attributable to geometry (survives the permutation control), within the fast-path cost bound. - Metric: nDCG@10 on held-out split, arm (iii) minus arm (ii); secondary Recall@50, MRR. Permutation control: (iv) minus (ii). Cost: query-projection share of median fast-path cost. - Dataset/inputs: ≥150 general queries per workspace across 3 pilot workspaces (~270 pooled held-out), graded relevance over pooled top-20, 40/60 validation/test split; ≥30 validation queries per fitted Domain. - Threshold: Dimension gain positive and significant (paired bootstrap, one-sided), design effect 0.03 absolute nDCG@10; no workspace significantly degraded (secondary); permutation control retains at most half the gain; projection calls add ≤10% to median fast-path cost for ≤3-Domain scope (≤3K calls). - Drop condition: Dimension term dropped if the gain fails the shared success rule, or the permutation control retains more than half of it, or the cost bound is exceeded and the gain vanishes with query projection disabled. Dropping also parks all Dimensions active only by the Useful screen. - Source: Anchor §10.1. - Tier: gated — requires Claims layer, active Dimensions, projection machinery, fitted β_{D,d} and μ.

Named precondition

Precondition: requires the Claims layer, active Dimensions, projection machinery, and fitted β_{D,d} and μ. 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/). Fitted β_{D,d} and μ have no code marker to probe.

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"
grep -q "'dimensions'" "$SCHEMA" || MISSING="$MISSING dimensions-tables"

if [ -n "$MISSING" ]; then
  warden_skip "CR-01 — Dimension-aware reranking gain" "pending: requires the Claims layer, active Dimensions, projection machinery, and fitted β_{D,d} and μ — gated criterion, precondition not built (probes missing:$MISSING)"
else
  warden_skip "CR-01 — Dimension-aware reranking gain" "schema probes now pass — upgrade this pending stub to a real plan before CR-01 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).