recover: three-repo-split ADR (Zeta + Forge + ace) from closed PR #54#378
Merged
recover: three-repo-split ADR (Zeta + Forge + ace) from closed PR #54#378
Conversation
Recovers the ADR that was drafted on commit 41d2bb6 ("Round 44: ADR — three-repo split (Zeta + Forge + ace)") in the Round-44 speculative fork branch stack. That commit was part of PR #54's diff, which I closed-as-superseded earlier this session on the assumption that "content already shipped to main via other PRs." The assumption was wrong for this ADR — it never landed on main by any other path. Aaron called out the over-close pattern 2026-04-24: *"bet you can find it in one of your closed PRs"* and more broadly *"i knew you were over closing."* This PR recovers ONLY the ADR file. The original 41d2bb6 commit also modified `docs/BACKLOG.md` to add a "P2 — Factory repo architecture" section; that BACKLOG update is deferred per the HB-002 per-row-BACKLOG-split blocker (no new BACKLOG.md rows until the split lands). ## What the ADR locks in - Three-repo split: Zeta (database/SUT) + Forge (software factory, self-hosting, Claude-delegated) + ace (package manager, Aaron-owned) - Closed Ouroboros dependency cycle: ace → Zeta, ace ← Forge, Zeta ← Forge, Forge → Forge - All three repos public from day one - Four-stage reversible migration (Stage 0 = this ADR) - Forge name rationale: adopts established "code-forge" term (Sourcehut, Codeberg, Gitea, Forgejo) per no-invent- vocabulary rule ## Retractability-in-action Otto-238 (retractability as trust vector): this is a visible reversal event. I closed #54 too eagerly; Aaron flagged the over-close pattern; this PR reverses the ADR-specific loss. The close+recover trail is visible in git history — that's the factory's retractability principle at the PR layer. ## Follow-up audit Per Aaron 2026-04-24 directive: going through all closed PRs I authored to identify other over-close misses. Audit in progress. This PR addresses the most load-bearing loss (three-repo-split ADR); other misses land in follow-up PRs. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Pull request overview
Recovers and reintroduces the missing ADR documenting the intended three-repo split (Zeta + Forge + ace) and its migration plan, so the decision record exists on main.
Changes:
- Adds ADR
2026-04-22-three-repo-split-zeta-forge-ace.mdback todocs/DECISIONS/. - Documents the split rationale (including Ouroboros dependency topology) and a staged migration plan.
- Captures a repo-creation “best practices” checklist and cross-references related docs/memories.
… MD032 - Line 373, 379, 397, 453, 461, 611: add memory/ prefix per Copilot thread feedback (files exist under memory/, bare refs don't resolve) - Line 340: rewrite + prefix to plus to fix markdownlint MD032 (blanks-around-lists was flagged on the quoted-text lines) - Keep name attribution in Deciders list intact per Aaron 2026-04-24: "first names are not PII and allowed in history files not other type file" (ADRs under docs/DECISIONS/** are history files per GOVERNANCE §2) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Recovers the three-repo-split ADR I over-closed via PR #54 earlier this session.
The ADR was drafted on commit `41d2bb6` and never landed on main through any other path. I closed #54 as "superseded" on the assumption the content was already on main — the assumption was wrong for this file.
Aaron's call on the over-close pattern
This is the first recovery. Audit of other closed PRs in progress.
What the ADR locks in
Scope
ADR file only. The original commit also updated `docs/BACKLOG.md` to add a "P2 — Factory repo architecture" section; that part is deferred per the HB-002 per-row-BACKLOG-split blocker (no new BACKLOG.md rows until the split lands).
Retractability-in-action (Otto-238)
Close-then-recover is the trust-vector reversal principle at the PR layer. The trail is visible in git history — visible reversal preserves the glass-halo discipline.
Test plan
Follow-up
🤖 Generated with Claude Code