Conversation
…d-research migration (Aaron 2026-04-29 input) Aaron's input received during PR #714 thread-fix tick: "backlog add other stuff we need from backlog research to escrow, we also needs rules for what goes in here, shit that's not ready yet, we've also overloaded escrow for this use and the use in software engineering for having copies of all our dependies local native incase the remote dependence disappears kind of like vendoring from the old go days (not exactly, there are modern software escrow too) backlog" Three distinct sub-asks captured: 1. **Naming collision** - "escrow" overloaded between research-grade preservation (B-0094 sense) and software-engineering vendoring (Go vendor/, modern software escrow). Three options surfaced: rename directory / disambiguate via prefix / glossary disambiguation. 2. **Define rules for what goes in escrow** - 7 candidate rules promoted from B-0094 implicit contract: eligibility criteria, required schema, single canonical home, no-multi-reviewer-loop default, bilateral clarification carve-out, implementation work allowed, explicit decision at expiration. 3. **Migrate deferred research** - audit existing backlog/P* + docs/research/ items; classify ESCROWABLE / STAYS-IN-BACKLOG / STAYS-AS-ACTIVE-RESEARCH / RETIRE. P2 priority. M effort (3 sub-asks each S-effort, combined M). This row is the carve-out per the session-closure rule's "explicit human ask" material-state-transition criterion. NOT new conceptual substrate beyond what Aaron explicitly requested. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 09163cca2f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Pull request overview
Adds a new P2 backlog row (B-0095) to capture follow-up work after the escrow concept landed: resolving “escrow” naming overload, defining escrow admission/rules, and auditing/migrating other deferred research into the escrow system.
Changes:
- Introduces backlog row B-0095 with three sub-asks: naming-collision resolution, escrow ruleset definition, and deferred-research migration plan.
- Documents candidate rule proposals + acceptance criteria for future work.
…ate on §23 + Copilot on stale path) Hard-defect class: incorrect canonical rule fixes / internal- consistency. 1. **§23 reference was wrong** (Codex P2 + Copilot duplicate): I cited GOVERNANCE.md §23 as authority that `references/upstreams/` is the vendoring home. §23 is actually about upstream open-source contributions via sibling `../` clones — sibling clones live at `../`, not under `references/upstreams/`. The operational rule for `references/upstreams/` lives in docs/AGENT-BEST-PRACTICES.md "Operational standing rules" section, not §23. Fixed both citations: now cite docs/AGENT-BEST-PRACTICES.md as the operational authority for the read-only-upstream- clones rule, and §23 as related-but-distinct workflow (sibling clones at ../). 2. **"Currently at" path claim** (Copilot): the row asserted the escrowed file is "currently at" `docs/research/escrowed/...` but on PR #715's branch (created from main BEFORE PR #714 merged) that path doesn't exist. Reworded to "the in-flight PR landing the file at... (path becomes canonical when PR #714 merges)" — accurate to the in-flight state. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
3 tasks
AceHack
deleted the
backlog/B-0095-escrow-rules-and-naming-collision-aaron-2026-04-29
branch
AceHack
added a commit
that referenced
this pull request
Apr 29, 2026
…a third-packet recursion-mirror confirmation (#717) * hygiene(tick-history): minimal-density row for thread-fix tick + Amara's third-packet recursion-mirror confirmation Per the corrected doctrine (rule landed PR #712, drift caught by Amara, applied PR #716): every tick gets a row, minimal density for pure-maintenance ticks. This tick: thread fixes on PR #715 (§23 reference + stale path) + Amara's third packet acknowledged (confirms recursive absorb-without-integrating worked). Two new candidate rules from Amara's packet recorded in row body: - Candidate-substrate row != doctrine promotion - Do not recursively canonize the rule against over-canonizing Both recorded as candidate, NOT promoted to memory file. Applying the discipline recursively to itself. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * review-thread fixes: count + spelling consistency on PR #717 (Copilot, 2 findings) Hard-defect class: internal-consistency / spelling. 1. "3 thread fixes" -> "2 distinct findings (3 threads incl. Codex+Copilot duplicate)" - the 3rd thread was a duplicate of the §23 finding (Codex P2 + Copilot both flagged it), so 2 distinct findings, 3 threads. 2. "allow-list class" -> "allowlist class" - this is the same spelling-consistency fix made earlier on PR #710. Re-applied consistently. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- 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
Captures Aaron's three sub-asks following PR #714's escrow landing:
docs/research/escrowed/README.md(or equivalent).Aaron's input verbatim
Why P2 / M effort
P2 because escrow is a load-bearing primitive landing today; rules + naming-collision resolution reduce future drift. M effort because three sub-asks each S-effort individually, combined M.
What this row does NOT authorize
Test plan
docs/backlog/P2/B-0095-...mdper BACKLOG canonical home