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-27 — Label-free eviction: engagement as salience proxy - Statement: Query engagement predicts the Useful screen's verdict well enough to order provisional Dimensions for eviction until β exists. - Metric: Primary: Spearman rank agreement between trailing engagement at fit time and mean out-of-fold β_{D,d} from the first Useful screen, across Dimensions, bootstrap interval over Dimensions. Secondary (Holm-corrected): engagement's agreement exceeds the recency ordering's (age since activation, the naive baseline) — paired one-sided bootstrap of the coefficient difference, both computed on each resample (respects the correlation the orderings inherit from sharing the β ranking). - Dataset/inputs: Every Dimension crossing the anchor's fitting minimum during the pilot with a full engagement window (90 days initially) before first fit; floor of 28 Dimensions pooled (below it: reported as underpowered, cap-hit human escalation remains the only eviction path — stated in advance so an underpowered result cannot read as a pass). - Threshold: One-sided 97% bootstrap lower bound on the Spearman coefficient above zero (the protocol's nominal 0.03 per look under the two-look extension; the second look pools further evaluation cycles until they contribute as many Dimensions again as the first look, since the extension is by the same size and the per-look boundary assumes equally sized looks); design effect 0.5 (≈80% power at the 28-Dimension floor, Fisher-z approximation). - Drop condition: Lower bound at or below zero → engagement is uninformative or anti-informative; eviction reverts to cap-hit human escalation only; the engagement log is kept only if §6's shadow-suggestion machinery wants it. Redesign: significant but weak (bound >0, point estimate <0.5) → rule demoted to tie-breaking beneath human escalation, reported as such. - Source: Companion §11.5 (mechanism in §8, replacing the anchor's §5.5 β-ranked eviction, which breaks under autonomous creation; falsifier pointer in §8). - Tier: gated — requires active Dimensions, the query-projection log, and ≥1 Domain at the fitting minimum.
Precondition: requires active Dimensions, the query-projection log, and ≥1 Domain at the fitting minimum. 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 query-projection log has 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 "'dimensions'" "$SCHEMA" || MISSING="$MISSING dimensions-tables"
if [ -n "$MISSING" ]; then
warden_skip "CR-27 — Label-free eviction: engagement as salience proxy" "pending: requires active Dimensions, the query-projection log, and ≥1 Domain at the fitting minimum — gated criterion, precondition not built (probes missing:$MISSING)"
else
warden_skip "CR-27 — Label-free eviction: engagement as salience proxy" "schema probes now pass — upgrade this pending stub to a real plan before CR-27 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).