I3352 — The six proof tests are registered, each with the claim it settles and its instrument, and none carries a protocol yet

✕BLOCKED wave 1 · p0 · docs profile · parallel safe

Part of the-proof-tests-are-registered-before-they-run — The six proof tests are registered as validated protocols, each frozen by its own digest, and every trial is a typed record that publishes only what its basis permits.

Objective

Write .ai/repo/benchmarks/proof-plan.yaml with tests t1-external-onboarding, t2-ab-workflow, t3-delivery-economics, t4-mesh-value, t5-resilience and t6-first-intent, each with its question, dimension, value words and instrument: planned with the issues of this program that build it, and with I3133 (acceptance), I3298 (topology arm) and I3299 (own overhead) where those are reused. Add six planned claims to docs/CLAIMS.yaml, one per test, in plain future tense with no figure and no asserted advantage. Say in .ai/repo/benchmarks/README.md that the plan lives there and is validated by economics::proof.

Why

The owner's report of 2026-10-19 asks for T1 to T6 within 30 days. Registering six rows first makes every omission visible on every surface as not_run. Each experiment milestone registers its own protocol, so this issue guesses no corpus, arm or threshold, and reusing I3133, I3298 and I3299 avoids a second acceptance metric, arm declaration and overhead bench.

Current state

git ls-files .ai/repo/benchmarks lists README.md and the subdirectories economics, observatory, pages and rust; no proof-plan.yaml. docs/CLAIMS.yaml:20-28 declares the statuses and holds no proof-test claim.

Desired state

economics::proof::load over the tracked tree validates six tests with no protocol; docs/CLAIMS.yaml carries six planned claims accepted by scripts/ci/claim-proof-check.

Scope

• .ai/repo/benchmarks
• .ai/repo/benchmarks/README.md
• docs/CLAIMS.yaml
• apps/majordomus-cli/tests/economics.rs

Out of scope

• Any protocol, threshold, sample size or corpus
• Marking any claim guaranteed
• Editing the economics suites

Dependencies

• I3351○READY A proof plan is a validated record in which each protocol is frozen by its own digest, so registering one test never stales another's records

What waits on this

• I3358✕BLOCKED economics check refuses a guaranteed claim of value that no passed proof test backs, in the claims matrix only
• I3360✕BLOCKED The T1 protocol and its selection floors are registered before any candidate is measured, and a record without an admitted candidate is refused
• I3370✕BLOCKED The corpus suite is registered and committed before its first run, and the T2 protocol names its registration digest
• I3383✕BLOCKED The T3 delivery window is registered before it opens: its period, the work it admits, the definition of accepted and a bound on each field's not-observed share
• I3388✕BLOCKED The mesh suite is registered before its first run, and the T4 protocol names its registration digest
• I3391✕BLOCKED The T5 protocol registers three fault kinds, the trials each needs and what a trial must show, before any fault is injected
• I3398✕BLOCKED The T6 protocol says who counts as a newcomer, what each trial records and how many must reach a satisfied verdict unaided, before any trial runs

Acceptance criteria

• The plan validates with exactly six tests named for T1 to T6
• Each test settles one planned claim docs/CLAIMS.yaml holds, and no claim sentence names a figure or asserts an advantage
• Each planned instrument names at least one existing issue id or a key of this program
• A test in economics.rs loads the tracked plan and asserts six tests and no finding

Validation

• cargo test --manifest-path apps/majordomus-cli/Cargo.toml --test economics
• scripts/generate-site-data --check
• scripts/ci/claim-proof-check
• majordomus economics check
• majordomus plan validate

Evidence required

• test_tracked_proof_plan_has_six_tests

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3352.yaml. Read it back with majordomus plan show I3352.