Warden plan

28 - CR-11 (pending): Visibility rule decision

tier: hermetic requires: []

28 - CR-11 (pending): Visibility rule decision

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-11 — Visibility rule decision - Statement: Decide between the subset rule (§3.2) and the intersection rule with fitted penalty ν for Claim visibility under Initiatives. - Metric: Held-out nDCG@10 on Initiative-scoped queries, each rule run with attention on. - Dataset/inputs: Same as CR-08. - Threshold: Decision rule, not pass/fail: intersection adopted iff significantly higher; otherwise the subset rule stays as the conservative default. - Drop condition: n/a (either outcome keeps a rule). - Source: Anchor §10.4. - Tier: gated — requires Initiatives machinery.

Named precondition

Precondition: requires Initiatives machinery. 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 "'initiatives'" "$SCHEMA" || MISSING="$MISSING initiatives-tables"

if [ -n "$MISSING" ]; then
  warden_skip "CR-11 — Visibility rule decision" "pending: requires Initiatives machinery — gated criterion, precondition not built (probes missing:$MISSING)"
else
  warden_skip "CR-11 — Visibility rule decision" "schema probes now pass — upgrade this pending stub to a real plan before CR-11 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).