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-28 — The dial: auto-activation quality - Statement: Dimensions activated autonomously (five gates, no Useful screen, no human review) are not materially worse, as judged by people, than Dimensions a human reviewed before activation — the measurable statement of auto-activation quality, and the pre-registered result that would flip the shipped default. - Metric: Primary: autonomous arm's meaningfulness rate (anchor §10.6 protocol: two raters, both must say yes, κ reported). Secondary: non-inferiority of autonomous vs review arm. Both cluster-bootstrapped over Domains (the design randomizes Domains; Dimensions within a Domain share subject matter, Claim base, and rater context — an unclustered bound would declare non-inferiority more easily than the data license). Also reported: review-arm approval rate (approval ≥0.9 means review is latency, not a quality bar — itself evidence about the default); activation-projection spend per arm (gated count × c_π per activation at the arm's disposal rate); the §8 engagement-log line per arm. - Dataset/inputs: Domains cluster-randomized between the autonomous and review dial positions for an evaluation cycle; sample floor 40 Domains per arm with ≥150 activated Dimensions per arm, accumulated over as many cycles as needed, stated in advance; power conditional on assumed within-Domain correlation 0.3 at ~4 Dimensions per Domain (design effect ≈1.9, effective sample ≈79 per arm, half-width ≈0.13 at worst-case rates near 0.5); observed correlation reported and power recomputed. - Threshold: Autonomous meaningfulness ≥0.5 (the anchor's own §10.6 bar); non-inferiority within 0.20 absolute (one-sided 95% bound on the rate difference); ≈80% power for non-inferiority at equal true rates once the floor is met; below the floor the comparison is reported as underpowered and moves nothing. - Drop condition: Primary failure flips the shipped default from autonomous to review. Non-inferiority failure (scored only at the sample floor) also flips it — but only when the review arm's approval rate is below 0.9; at ≥0.9 the result is reported without moving the default. Either flip is the autonomy half of the thesis failing, by design: the AI still authors (there is no manual end), but a human approves each Dimension. - Source: Companion §11.6 (dial mechanism in §8). - Tier: gated — requires the discovery pipeline and the five gates.
Precondition: requires the discovery pipeline and the five gates. 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 discovery pipeline and the five gates have 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-28 — The dial: auto-activation quality" "pending: requires the discovery pipeline and the five gates — gated criterion, precondition not built (probes missing:$MISSING)"
else
warden_skip "CR-28 — The dial: auto-activation quality" "schema probes now pass — upgrade this pending stub to a real plan before CR-28 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).