Skip to content

docs: R2 transition step 1 — R1 Closure Manager declares R1 closed #1161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
briansrls merged 3 commits into from
Apr 29, 2026
Merged

docs: R2 transition step 1 — R1 Closure Manager declares R1 closed #1161

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
480f7bb
docs: align R1 close authority with R1 Closure Manager in r2-structure
briansrls Apr 29, 2026
e574c6a
docs: neutral r1-closure-manager pointer until brief refresh PR lands
briansrls Apr 29, 2026
c813b31
docs: address #1161 review — step 1 wording + line wrap
briansrls Apr 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/r2-structure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -299,7 +299,8 @@ Rationale: consistent with anti-deferral stance — tail-shaped work closes befo

## Transition mechanics

1. **R1 gates green** → Director declares R1 closed.
1. **R1 close** — **R1 Closure Manager** declares R1 closed when **release acceptance** and **lane receipts** per `ROADMAP.md §"Release R1 Program"` are satisfied.
Closure record: [`docs/briefs/r1-closure-manager.md`](briefs/r1-closure-manager.md) (completion section).
2. **R1 residual sweep** — every open R1 ledger row gets an R1-or-R2 assignment. No orphaning. Done in the R1 closure PR. Expected to be short under all-gates-green criterion.
3. **R1 manager dissolution** — all R1 standing managers (Surface, Substrate, Testgen, Self-hosting, Release) archive with closure banners. Their scopes are fully absorbed by R1's gate acceptance; no inheritance into R2 managers.
4. **R2 manager spin-up** — **seven standing managers** initialized per the revised manager structure above (count updated 2026-04-28 per R1 Closure Manager review — Evaluator Manager added as Goal 7). Each manager gets a dedicated brief (`docs/briefs/r2-grounding-manager.md`, `docs/briefs/r2-substrate-manager.md`, `docs/briefs/r2-modeling-manager.md`, `docs/briefs/r2-impossible-bugs-manager.md`, `docs/briefs/r2-pure-bootstrap-manager.md`, `docs/briefs/r2-release-manager.md`, `docs/briefs/r2-evaluator-manager.md`) naming program scope + owned deliverables + cross-program dependencies + autonomous dispatch authority + reporting cadence. **Pre-stage skeleton briefs before R1 closes** (Director authors skeletons during R1 final week; promotion PR fills in scope-final details) so the R1→R2 transition is not gated on seven fresh authoring cycles. Existing `docs/briefs/grounding-manager.md` migrates content into `r2-grounding-manager.md` and archives. Existing `docs/briefs/pure-bootstrap-zero-manager.md` migrates content into `r2-pure-bootstrap-manager.md` and archives.
Expand Down
Loading