docs(briefs): R3 Cluster M dispatch briefs (Task 2 per Director γ-hybrid ratification)

docs/briefs/r3-cluster-m-dispatch-substrate-canvas-asks-2026-05-09.md

@@ -0,0 +1,88 @@
+# R3 Cluster M Phase 1 — Substrate Carrier Landing Asks (2026-05-09)
+
+**Owner**: Substrate Mgr (warm-wolf-698 / gunbc#2068)
+**Authority**: PM-tier dispatch coordination per Director ratification at gunbc#846 #issuecomment-4412309986 (Director answered Ask 2 with "Substrate Mgr standing authority"). Sequencing structure lives at [`docs/audit/r3-cluster-m-sequencing-plan-2026-05-09.md`](../audit/r3-cluster-m-sequencing-plan-2026-05-09.md) §3 (in-flight via concurrent PR #2361; this brief is the dispatch overlay — substantive content here is self-contained and grounded in locked-design authority `docs/design-tests-as-data-completeness.md` §2.1/§2.2 cited below). This brief is a light-touch dispatch surface.
+
+---
+
+## §0. Scope
+
+Two parallel substrate carrier landings — Phase 1 of Cluster M sequencing per (γ) hybrid dispatch shape:
+
+1. **#85** `forall_exists_quantifier_substrate_landed` — `Quantifier` + `QuantifiedTestClaim` carrier landing in `src/v3/std/verification.dag`
+2. **#86** `program_generator_carrier_landed` — `ProgramGenerator` carrier landing in `src/v3/std/verification.dag`
+
+Both carrier landings parallel-authorable; no mutual substrate dep.
+
+## §1. Authority correction 2026-05-09 (codex BLOCKING on PR #2361 sha `c6c3fb96`)
+
+Prior framing of this brief as "substrate canvas asks" + "surface for Director ratification" was a duplicate-authority anti-pattern. The substrate carriers are **already canonically defined** in [`docs/design-tests-as-data-completeness.md`](../design-tests-as-data-completeness.md) §2.1 + §2.2.
+
+Per locked-design §1 Authority discipline:
+> "All §8 design questions resolved in-doc per `feedback_design_before_implement` — **no Director ratification required before lane dispatch** (only standard cascade gates: R2-Evaluator landed; existing TestClaim infrastructure from DB-15 R2)."
+
+Single canonical authority per INVARIANTS P2: locked design owns shape; this brief owns dispatch coordination only.
+
+## §2. Dispatch disposition (cite-and-execute)
+
+- **Dispatch shape**: (γ) hybrid — Substrate Mgr lands carriers → Verification discipline → Verification bulk-port coordinator
+- **Authoring authority**: Substrate Mgr standing authority (worker brief authoring + dispatch under standing authority; no Director ratification needed — locked design resolves carrier shape)
+- **Pattern**: substrate-shape canvases for novel substrate (e.g., T-WAD Slice 2); migration / locked-design carrier landings dispatch directly. #85/#86 fall in the latter category.
+
+## §3. Substantive guidance per carrier (per locked design §2.1/§2.2)
+
+### §3.1 #85 — `Quantifier` + `QuantifiedTestClaim` carriers (per locked design §2.2)
+
+**Locked carrier shape** (`docs/design-tests-as-data-completeness.md` §2.2):
+
+```
+type Quantifier = ForAll | Exists  // closed two-variant sum
+
+type QuantifiedTestClaim {
+  generator: ProgramGenerator
+  quantifier: Quantifier
+  // ... see design doc for full Rust signature
+}
+```
+
+`Quantifier` is a closed two-variant sum exhausting structurally meaningful quantifications over a `ProgramGenerator`'s output. `QuantifiedTestClaim` lives **alongside** `TestClaim` (not as replacement) — covers the property-based axis where the existing `TestClaim` covers single-source enumerated tests.
+
+**Worker scope**: extend `src/v3/std/verification.dag` to add `Quantifier` + `QuantifiedTestClaim` per design §2.2 spec. No Director ratification needed.
+
+### §3.2 #86 — `ProgramGenerator` carrier (per locked design §2.1)
+
+**Locked carrier shape** (`docs/design-tests-as-data-completeness.md` §2.1):
+
+```
+type ProgramGenerator {
+  // structural reference to a generator declaration whose body
+  // produces a List<ProgramShape> (or iterator-shaped value)
+  // ... see design doc for full Rust signature
+}
+```
+
+`ProgramGenerator` is a structural reference to a generator declaration — **not** a roster of "shape kinds" (which would replicate the closed-roster failure flagged by `lens-library-design.md` §1.5). The generator body is itself a `.dag` declaration producing program shapes; `ProgramGenerator` references it structurally.
+
+**Worker scope**: extend `src/v3/std/verification.dag` to add `ProgramGenerator` carrier per design §2.1 spec. Composition with §3.1 #85: `QuantifiedTestClaim.generator` field references `ProgramGenerator`. No Director ratification needed.
+
+## §4. STOP-and-PING posture
+
+If during landing the worker discovers an unexpected shape question that the locked design §2.1/§2.2 does not resolve, STOP-and-PING via Substrate Mgr inbox per `feedback_construction_over_ratchets` rather than authoring a canvas mid-port. Surface the question; Director ratifies the surfaced shape; worker resumes.
+
+## §5. Dispatch trigger
+
+Substrate Mgr (warm-wolf-698) dispatches worker brief(s) for #85/#86 carrier landings under standing authority once PR #2361 lands (sequencing plan ratified by Director ratification at #846 #issuecomment-4412309986). Workers can be queued ahead of merge per pre-authored brief discipline.
+
+## §6. Receipt
+
+- `src/v3/std/verification.dag` extended with `Quantifier`, `QuantifiedTestClaim`, `ProgramGenerator` per design §2.1/§2.2 specs
+- §1.8 ledger Status moves DECLARED → CONSUMER_LANDED on substrate carrier landing PR merges
+- Phase 2 (#87) Verification Mgr discipline-pattern brief unblocks once #85/#86 carriers land
+
+## §7. Velocity context
+
+Per [`docs/audit/r3-pb0-velocity-walk-2026-05-09.md`](../audit/r3-pb0-velocity-walk-2026-05-09.md): Cluster M is **critical-path-load-bearing** for PB-0 closure. Phase 1 (this brief) gates Phase 2 (#87) gates Phase 3 (#84 bulk-port). Total Cluster M close target: 4-8 weeks per sequencing plan §6; fits 8-12 week R3 window with parallel dispatch per operator "staffing is not a concern" directive.
+
+---
+
+**End of brief.**

docs/briefs/r3-cluster-m-dispatch-verification-bulkport-84-2026-05-09.md

@@ -0,0 +1,68 @@
+# R3 Cluster M Phase 3 — Verification Bulk-Port Coordinator #84 Dispatch (2026-05-09)
+
+**Owner**: Verification Mgr (wise-bear-525 / gunbc#2075) — coordinator role
+**Authority**: PM-tier dispatch coordination per Director ratification at gunbc#846 #issuecomment-4412309986 (Director answered Ask 3 with "Verification Mgr coordinator"). Sequencing structure lives at [`docs/audit/r3-cluster-m-sequencing-plan-2026-05-09.md`](../audit/r3-cluster-m-sequencing-plan-2026-05-09.md) §5 (in-flight via concurrent PR #2361; this brief is the dispatch overlay — substantive content here is self-contained and grounded in live ledger authority below). This brief is a light-touch dispatch surface.
+
+---
+
+## §0. Scope
+
+**Gate #84** `every_rust_test_ports_to_dag_or_generated` — Cluster M Phase 3. Verification Mgr coordinates **bulk-port** of the full `EXPECTED_HAND_AUTHORED_TEST` set to `.dag` TestClaim form, partitioned by dissolution-trigger class.
+
+## §1. Director-ratified strict-zero close-condition (cite-and-execute)
+
+Per Director ratification at gunbc#846 #issuecomment-4412309986 Ask 4: **strict-zero, no closure-allowed exceptions**.
+
+- Director Option 2 timed-carries (`cross_target_coverage_carrier_test.rs`, `method_template_contract_test.rs`, etc.) are **NOT** folded into closure-allowed; they are blockers / non-close-risk until they migrate to testgen coverage
+- Where testgen can't cover (e.g., reflected-Dag structural assertions over std/ row authorities) → **Cluster M scope expansion**, not a closure-allowed carve
+- **Bulk-port scope = all entries in `EXPECTED_HAND_AUTHORED_TEST`** at PR-merge time (live authority: [`src/v3/compiler/tests/integration/sg0_census_test.rs`](../../src/v3/compiler/tests/integration/sg0_census_test.rs); count is `wc -l`-derivable from the array literal — **not hardcoded here** to avoid duplicate-authority drift). This is post #85/#86/#87 substrate landing.
+- Cluster M's job is making testgen capable enough to cover them all
+
+This is the load-bearing answer per `feedback_pb_zero_is_r3_close_target`: cascade promotion 2026-04-25 target is `0 hand-Rust + 0 TESTING residual`.
+
+## §2. Coordinator role (vs distributed per-lane)
+
+Per Director ratification: Verification Mgr coordinates centrally; lane Mgrs review their own ported tests for behavioral fidelity (signoff, not authoring). Reasoning: avoids per-lane TestClaim-authoring learning curve; concentrates testgen-capability development in one place.
+
+**Lane Mgr signoff workflow**:
+- Verification dispatches per-class workers; workers author bulk migrations
+- For each migration class, original lane Mgr reviews behavioral fidelity (e.g., m1/m2 boundary tests reviewed by their respective lane Mgrs)
+- Lane Mgr signoff is required before each migration class is considered closed
+
+## §3. Dispatch trigger
+
+Verification Mgr dispatches Phase 3 **on Phase 1 + Phase 2 lock** — i.e., #85 + #86 substrate carriers landed (post-Substrate Mgr canvas ratification + worker dispatch) AND #87 cementing-test discipline pattern landed (post-Phase 2 first-migration receipt).
+
+Phase 3 is parallel-dispatchable per-class within itself (per operator "staffing is not a concern"); coordinator role manages cross-class dependencies + lane-Mgr signoff workflow.
+
+## §4. Per-class brief queue
+
+Per Cluster M sequencing plan §5.2 (estimated from velocity-walk audit §2.1):
+
+| Class | Approx count | Worker brief scope |
+|---|---|---|
+| Cementing-test family (post-#87 pattern) | ~20-25 | Apply #87 pattern to remaining lens cementing tests |
+| Reflected-Dag structural assertion family | ~25-30 | Migrate to ProgramGenerator-driven TestClaims (#86 consumer) |
+| Generic DimensionReport / runner-discipline family | ~20-25 | Migrate to runner-side TestClaim (post-#87) |
+| Boundary tests (m1_*, m2_*, etc.) | ~10 | Each migrates per testgen-coverage discipline |
+| R1C-D / R1C-E wrappers | ~3 | R1-close residuals; may be eligible NOW |
+| L4/L7/L5 skeleton | ~5 | Verification Cluster G overlap; may bundle |
+
+Each class is a parallel-dispatchable worker batch. Verification Mgr authors per-class briefs as Phase 3 begins.
+
+## §5. Receipt
+
+- #84 status moves DECLARED → CONSUMER_LANDED on first migration class fully ported
+- #84 status moves CONSUMER_LANDED → PASSING when SG-0 census `EXPECTED_HAND_AUTHORED_TEST` count = 0 (strict; no exception fold per Director Ask 4)
+- §1.8 ledger Status updated by Verification Mgr per §10 cadence
+- Daily SG-0 census count tracked at [`docs/audit/r3-sg0-trajectory-tracker.md`](../audit/r3-sg0-trajectory-tracker.md) §3 history table
+
+## §6. Velocity context
+
+Per [`docs/audit/r3-pb0-velocity-walk-2026-05-09.md`](../audit/r3-pb0-velocity-walk-2026-05-09.md): Phase 3 dissolves the bulk of the SG-0 test side (~50-65 remaining test entries after Phase 2's ~20-25 reduction). #84 closure is the load-bearing event for PB-0 thesis test-side closure.
+
+Phase 3 timing: weeks 4-8 of the 8-12 week R3 window per Director's bulk-event sequencing in #846 #issuecomment-4412008376 §C. Parallel-dispatchable per-class; total close fits R3 horizon under operator "staffing is not a concern" directive.
+
+---
+
+**End of brief.**

docs/briefs/r3-cluster-m-dispatch-verification-discipline-87-2026-05-09.md

@@ -0,0 +1,53 @@
+# R3 Cluster M Phase 2 — Verification Discipline #87 Dispatch (2026-05-09)
+
+**Owner**: Verification Mgr (wise-bear-525 / gunbc#2075)
+**Authority**: PM-tier dispatch coordination per Director ratification at gunbc#846 #issuecomment-4412309986 (Director answered Ask 1 with "(γ) hybrid"). Sequencing structure lives at [`docs/audit/r3-cluster-m-sequencing-plan-2026-05-09.md`](../audit/r3-cluster-m-sequencing-plan-2026-05-09.md) §4 (in-flight via concurrent PR #2361; this brief is the dispatch overlay — substantive content here is self-contained and grounded in locked-design + live ledger authorities below). This brief is a light-touch dispatch surface.
+
+---
+
+## §0. Scope
+
+**Gate #87** `lens_cementing_test_discipline_complete` — Cluster M Phase 2. Verification Mgr authors discipline-pattern + first cementing-test migration receipt.
+
+## §1. Substrate
+
+**Locked design authority**: [`docs/design-tests-as-data-completeness.md`](../design-tests-as-data-completeness.md) §C5 (Cementing v2 oracle) — canonical predicate set for cementing-test discipline.
+
+**Existing brief at HEAD**: [`docs/briefs/r3-v-tests-as-data-v1-worker.md`](r3-v-tests-as-data-v1-worker.md) — **PRE-AUTH DISPATCH-READY** (tier-1 queue gunbc#1859). Covers all four Cluster M gates (#84/#85/#86/#87) in single-coordinator framing. Verified live on main: `git ls-tree origin/main -- docs/briefs/r3-v-tests-as-data-v1-worker.md` → blob `4ff9abcb1b8b`.
+
+**This dispatch shape (γ) splits the existing brief by gate-class**:
+- #85/#86 → Substrate Mgr canvas-tier (authored under standing authority; see [`docs/briefs/r3-cluster-m-dispatch-substrate-canvas-asks-2026-05-09.md`](r3-cluster-m-dispatch-substrate-canvas-asks-2026-05-09.md))
+- **#87 → Verification Mgr discipline-authoring (this brief)**
+- #84 → Verification Mgr bulk-port coordinator (see [`docs/briefs/r3-cluster-m-dispatch-verification-bulkport-84-2026-05-09.md`](r3-cluster-m-dispatch-verification-bulkport-84-2026-05-09.md))
+
+The existing `r3-v-tests-as-data-v1-worker.md` is cited as substrate-of-truth for #87 substantive content; this dispatch brief is the (γ)-hybrid coordination overlay.
+
+## §2. Dispatch trigger
+
+Verification Mgr dispatches #87 discipline-authoring **on Phase 1 partial-land** — i.e., once at least one of #85/#86 substrate canvases has Director ratification on carrier shape (does NOT require both #85 and #86 carriers to fully land; Director-ratified shape questions are sufficient to begin discipline-pattern authoring).
+
+Pattern precedent: discipline patterns can be authored against substrate-shape ratifications before substrate-implementation lands; the discipline pattern *consumes* the carrier shape, not its implementation.
+
+## §3. Authoring scope
+
+Per `r3-v-tests-as-data-v1-worker.md` substrate + Cluster M sequencing plan §4:
+
+- **Discipline pattern**: how every `.dag` lens has at least one cementing test in `.dag` form using #85 `Quantifier` + `QuantifiedTestClaim` carriers (per locked design §2.2) + #86 `ProgramGenerator` carrier (per locked design §2.1)
+- **First migration target**: smallest hand-Rust cementing test (e.g., `tests/integration/cementing/cementing_lens_registry_dispatch_test.rs`) — proof-of-concept migration from hand-Rust `#[test] fn test_X` with v2-oracle assert → `.dag` `TestClaim` with **same-source v2-vs-v3 comparison** via `DifferentialEquals` or `LensOutputEquals` predicate (per locked design `docs/design-tests-as-data-completeness.md` §C5 row, §"C5: Cementing (v2 oracle)" — "v2 oracle and v3 lens produce equal output on source S"). `BinaryDimensionReportEquals` is for Pattern-A DimensionReport comparisons (TC1/TC2/TC3 family), NOT for cementing — different predicate axis.
+- **Receipt**: state-check gate fires when audit confirms 100% lens coverage in cementing-test form using the locked-design predicates
+
+## §4. Receipt
+
+- #87 status moves DECLARED → CONSUMER_LANDED on first migration receipt (proof-of-concept migration lands)
+- #87 status moves CONSUMER_LANDED → PASSING when audit confirms 100% lens coverage in `.dag` cementing-test form
+- §1.8 ledger Status updated by Verification Mgr per §10 cadence
+
+## §5. Velocity context
+
+Per [`docs/audit/r3-pb0-velocity-walk-2026-05-09.md`](../audit/r3-pb0-velocity-walk-2026-05-09.md) §3.3: ~20-25 of the test entries in `EXPECTED_HAND_AUTHORED_TEST` (live count authoritative at `src/v3/compiler/tests/integration/sg0_census_test.rs`) dissolve via #87 cementing-test discipline landing (cementing-test class is the largest single class). Phase 2 is therefore a substantial bulk-dissolution sub-event en route to #84 close.
+
+Phase 2 sequencing-criticality: M → B → E (per PR #2300 §4 Risk 2 + this audit §5 Risk 4) — B's cementing tests must capture frozen v2-oracle snapshot via M's discipline before E (v2 retirement) fires.
+
+---
+
+**End of brief.**