Skip to content

[codex] docs(r3): align verification manager full scope - #3042

Merged
briansrls merged 8 commits into
mainfrom
codex/r3-verification-manager-full-scope
May 13, 2026
Merged

briansrls merged 8 commits into
mainfrom
codex/r3-verification-manager-full-scope

Conversation

@briansrls

Copy link
Copy Markdown
Contributor

Summary

  • Follow-up to merged PR [codex] docs(r3): refresh verification manager actual-close scope #3018 after post-merge blocking review identified that the brief still narrowed the canonical Verification Manager scope.
  • Updates docs/briefs/r3-verification-manager.md to match docs/r3-structure.md: 6 lane surfaces, 2 cross-program partners, T-WAD Slice 7 as an extension, and the bridge ledger gate.
  • Separates the immediate 2026-05-13 actual-close dispatch subset from full-scope manager tracking so the brief no longer treats the old 3-lane standby surface as authority.

Validation

  • git diff --check

@briansrls

Copy link
Copy Markdown
Contributor Author

Verified dashboard review artifact 11422 against the current PR. It is approval-only and lists no actionable findings; no fix commit is required. CI is green on the current head. Merge readiness remains blocked because the dashboard currently parses the approval artifact as verdict=unknown and approval count is 0/2. — sent from still-moth-538

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review metadata

  • Provider / model: codex / unknown
  • Commit: 41aa62ec · Trigger: schedule
  • Thinking: 217s wall

BLOCKING (3)

Root Cause

  • docs/briefs/r3-verification-manager.md Actual-close obligations are being modeled only as lane rows and T-WAD extension rows → add explicit non-lane actual-close responsibility rows/cross-refs for Gap 9 and Gap 10 or state why another manager owns them.
  • docs/briefs/r3-verification-manager.md r3-structure has a 6-lane total that does not enumerate a sixth standalone Verification lane → reconcile r3-structure's count or amend the authority before reclassifying the TC bundle.
  • docs/briefs/r3-verification-manager.md The full-scope refresh updated the table but left the downstream consumption/sub-brief guidance on the old carve framing → update or remove the stale #95 R4-defer guidance in the same PR.

⚠️ The scope refresh is directionally useful, but these contradictions/missing obligations would misdirect Verification dispatch.

Comment thread docs/briefs/r3-verification-manager.md Outdated
- **Substrate-fact-introduction procedure** ([`INVARIANTS.md`](../../INVARIANTS.md) §P1): self-serve through the 3-step decision procedure before escalating substrate-shape questions to Director. Director ratified unified substrate-introduction for TC1/TC2/TC3 as `BinaryDimensionReportEquals` at [#828 c#4356050427](https://github.com/gunb-ai/gunbc/issues/828#issuecomment-4356050427) + [#828 c#4356138359](https://github.com/gunb-ai/gunbc/issues/828#issuecomment-4356138359); Substrate owns the predicate variant, while Verification supplies consuming coverage requirements.

## Owned program scope (4 lanes + 1 cross-program extension + 1 ledger gate)
## Owned program scope (6 lanes + 2 partners + 1 T-WAD extension + 1 ledger gate)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BLOCKING: The expanded owned-scope section still omits the actual-close plan's Verification-owned Gap 9 show-correct-code implementation and Gap 10 predicate-execution work, so the full-scope brief drops ratified close obligations (top-down PM intent / INVARIANTS P2).

Comment thread docs/briefs/r3-verification-manager.md Outdated
| **Lane 4: T-Tests-As-Data-Completeness** | L | **Actual-close Gap 5 owner** — Cluster M Phase 3 bulk-port is now lane-closing Verification work, not audit-only tracking. The manager owns worker dispatch for per-class ports and the generated-test manifest authority required by `docs/r3-actual-close-plan.md` §Gap 5. | ProgramGenerator substrate (#86) landed; #85 generated consumer + Cluster M Phase 3 generator-manifest work remain. |
| **Cross-program extension: T-WAD Slice 7 affected-set CI selection** | M | **Absorbed owner for `ci_uses_affected_set_selection`** per [`docs/r3-t-workflow-as-data-full-r3-close-scope.md`](../r3-t-workflow-as-data-full-r3-close-scope.md) §3/§7. This is a Verification extension to T-WAD, not a standalone Verification lane, because it consumes the affected-set lens output and removes regex bridge authority from CI selection. | Slice 5 BinaryShim projection arm + PR #2713 affected-set lens output. |
| **Lane 5: T-Lens-Self-Application** | M-L | **Verification-owned recursive-flex demonstration** — gunbc applies its own lenses to its own build/CI workflow, including `lens_self_application_demonstrated`, `apply_lens_self_application_demonstrated`, and `recursive_flex_demonstration_landed`. | T-Workflow-As-Data; T-Lens-Application-Surface; T-Lens-Behavioral-Parity COMPLETE; R2-Evaluator |
| **Lane 6: TC1/TC2/TC3 formal-grounding bundle** | S-M | **Absorbed lane responsibility** — strict-fire activation tracking for the formal-grounding deferred claims via the unified `BinaryDimensionReportEquals` path. This preserves the current `r3-structure.md` manager-row total while keeping the implementation cadence as audit/activation rather than a separate standalone dispatch program. | Substrate-owned predicate/modifier support; R2-Evaluator strategy/report producers; T-FixedPoint for TC3 |

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BLOCKING: Calling the TC1/TC2/TC3 bundle "Lane 6" creates a new lane authority not named in r3-structure's Verification Manager row; those executable TC gates are recorded under T-Verification-L4-L7-Direct, so this violates INVARIANTS P2/top-down intent.

| **Lane 5: T-Lens-Self-Application** | M-L | **Verification-owned recursive-flex demonstration** — gunbc applies its own lenses to its own build/CI workflow, including `lens_self_application_demonstrated`, `apply_lens_self_application_demonstrated`, and `recursive_flex_demonstration_landed`. | T-Workflow-As-Data; T-Lens-Application-Surface; T-Lens-Behavioral-Parity COMPLETE; R2-Evaluator |
| **Lane 6: TC1/TC2/TC3 formal-grounding bundle** | S-M | **Absorbed lane responsibility** — strict-fire activation tracking for the formal-grounding deferred claims via the unified `BinaryDimensionReportEquals` path. This preserves the current `r3-structure.md` manager-row total while keeping the implementation cadence as audit/activation rather than a separate standalone dispatch program. | Substrate-owned predicate/modifier support; R2-Evaluator strategy/report producers; T-FixedPoint for TC3 |
| **Partner: T-Lens-Behavioral-Parity** | L-XL | **Cross-program with Substrate** — Verification owns cementing/register receipts and behavioral-completion evidence for the all-4-lens R3 scope; Substrate owns carrier/walker substrate work. | T-E-P-Producer-Broadening; R2-Evaluator; R2-T-Substrate-Lens-Primitive |
| **Partner: T-Lens-Application-Surface** | L-XL | **Cross-program with Substrate** — Verification owns execution/demo split receipts, including complexity/cost demos and the R3-load-bearing #95 cascade as ratified; Substrate owns carriers and application surface shape. | T-Lens-Behavioral-Parity; R2-Evaluator |

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BLOCKING: The new T-LAS partner row makes #95 R3-load-bearing, but the same brief still instructs worker briefs to defer #95 under the old R4 carve, leaving conflicting dispatch authority (INVARIANTS P2).

@briansrls
briansrls merged commit c177853 into main May 13, 2026
5 checks passed
@briansrls
briansrls deleted the codex/r3-verification-manager-full-scope branch May 13, 2026 23:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant