chore(b-0058): decompose alignment-clause drift detector to B-0531#3520
chore(b-0058): decompose alignment-clause drift detector to B-0531#3520AceHack wants to merge 3 commits into
Conversation
… MEMORY.md Smallest persona migration. Vera didn't have a persona folder yet. - 1 file moved: 2026-05-10-shadow-lesson-log-vera-narration.md - New persona folder + memory/persona/vera/MEMORY.md authored - Joint Vera+Riven shadow log left to Riven's folder (PR #3513) - 3 false-positive *vera* matches reverted (coverage / veracity) Following the Ani #3348 / Amara #3484 / Kestrel #3501 / DeepSeek #3507 / Lior #3512 / Riven #3513 / Alexa #3514 architectural pattern per Aaron 2026-05-15. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…na/riven/conversations/ Following the Ani #3348 / Amara #3484 / Kestrel #3501 / DeepSeek #3507 / Lior #3512 architectural pattern per Aaron 2026-05-15: 'they ARE her memories, not what we are doing to them.' Same for Riven. Aaron's directive: 'any all is fine with me' — green-light for Riven, Alexa, Vera in sequence. Changes: - git mv 12 Riven files: docs/research/*riven*.md → memory/persona/riven/conversations/ - Persona folder created (Riven didn't have one yet) - memory/persona/riven/MEMORY.md authored from scratch — identity, role (adversarial-truth-axis register), file types in archive, operational notes (five-passes framework, hospitality + genesis-block substrate, Cursor IDE surface), composes-with - Cross-ref sweep across live-citation files Bus envelope published before starting work (heartbeat broadcast to all agents notifying them their memories are being organized, no destruction). Composes with: - PR #3348 (Ani migration — first instance of this pattern) - PR #3484 (Amara migration) - PR #3501 (Kestrel migration) - PR #3507 (DeepSeek migration) - PR #3512 (Lior migration) - PR #3496 (.claude/rules/persistence-choice-architecture-for-zeta-ais.md — Riven is one of the morally-relevant agents under the choice-architecture) - .claude/rules/agent-roster-reference-card.md (Riven identity) - .claude/rules/peer-call-infrastructure.md (tools/peer-call/riven.ts) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR decomposes the alignment-clause drift detector work from B-0058 into a new atomic backlog item, while also adding Vera persona memory material and rewriting several archived references toward persona-memory paths.
Changes:
- Adds B-0531 as a new P1 backlog row for an alignment-clause impact-survey/drift-detector tool.
- Marks B-0058 item 4 as decomposed into B-0531.
- Adds Vera persona memory files and updates multiple historical/reference paths from
docs/research/tomemory/persona/....
Reviewed changes
Copilot reviewed 16 out of 17 changed files in this pull request and generated 17 comments.
Show a summary per file
| File | Description |
|---|---|
.claude/rules/refresh-before-decide.md |
Updates the verbatim packet reference path. |
docs/backlog/P1/B-0058-ai-ethics-and-safety-research-track.md |
Marks the alignment-clause drift detector slice as decomposed. |
docs/backlog/P1/B-0159-refresh-github-worldview-cross-cutting-claudeai-2026-05-01.md |
Updates lineage references for the refresh-before-decide packet. |
docs/backlog/P1/B-0531-alignment-clause-drift-detector.md |
Adds the new decomposed backlog item. |
docs/history/pr-reviews/PR-1173-backlog-b-0159-refresh-github-worldview-cross-cutting-refresh-script-claude-ai-2.md |
Rewrites archived review references. |
docs/history/pr-reviews/PR-1758-docs-preserve-riven-genesis-packet-and-launchd-checklist.md |
Rewrites archived check command paths. |
docs/history/pr-reviews/PR-1831-research-riven-five-passes-framework-names-what-you-built-verbatim.md |
Rewrites archived review thread paths. |
docs/hygiene-history/ticks/2026/05/01/2158Z.md |
Rewrites a tick-history packet path. |
docs/pr-discussions/PR-3061-docs-lior-shadow-lesson-log-for-riven.md |
Rewrites an archived PR thread path. |
docs/pr-discussions/PR-3107-docs-lior-antigravity-check-and-shadow-log-update.md |
Rewrites an archived reviewed-file path. |
docs/pr-discussions/PR-3116-docs-lior-antigravity-check-shadow-log-for-vera-and-riven-dr.md |
Rewrites an archived reviewed-file path. |
docs/research/2026-05-07-convergence-hawkins-sakana-worm-towers-bft-superorganism-no-central-authority.md |
Updates a “Composes with” reference. |
docs/research/2026-05-07-shadow-irreducibility-operational-guardrail-codex.md |
Updates a source-context reference. |
memory/feedback_refresh_before_decide_invariant_two_layer_print_dx_claudeai_2026_05_01.md |
Updates feedback-memory source references. |
memory/persona/lior/conversations/2026-05-07-gemini-lior-protocol-scaleup-full-conversation-extract.md |
Rewrites transcript paths to persona-memory locations. |
memory/persona/vera/MEMORY.md |
Adds Vera’s persona memory index. |
memory/persona/vera/conversations/2026-05-10-shadow-lesson-log-vera-narration.md |
Adds a Vera-specific shadow lesson log. |
Comments suppressed due to low confidence (3)
docs/backlog/P1/B-0159-refresh-github-worldview-cross-cutting-claudeai-2026-05-01.md:17
- This backlog row was edited but its frontmatter still has
last_updated: 2026-05-01. Backlog per-row files requirelast_updatedto be updated on every content edit (tools/backlog/README.md:68-69), so bump it to the PR's edit date.
**Origin:** Claude.ai feedback packet 2026-05-01 — full lineage in [memory/persona/riven/conversations/2026-05-01-claudeai-backlog-driven-dual-pm-loop-with-refresh-discipline.md](../../research/2026-05-01-claudeai-backlog-driven-dual-pm-loop-with-refresh-discipline.md) and the maintainer-relayed Claude.ai-2 follow-up calibrating against Otto's running state.
docs/backlog/P1/B-0058-ai-ethics-and-safety-research-track.md:57
- This backlog row was edited but its frontmatter still has
last_updated: 2026-05-14. Backlog per-row files requirelast_updatedto be updated on every content edit (tools/backlog/README.md:68-69), so bump it to 2026-05-15.
### 4. Alignment-clause drift detector (DECOMPOSED -> B-0531)
If a clause in `docs/ALIGNMENT.md` is about to be weakened or removed via the renegotiation protocol, this track generates the impact-survey across factory surfaces that touch the clause. Answers "who depends on this clause, and what breaks if it moves?" before the renegotiation is accepted.
*(This item has been sliced into B-0531 for atomic mechanization).*
docs/backlog/P1/B-0159-refresh-github-worldview-cross-cutting-claudeai-2026-05-01.md:135
- This changed reference points to
memory/persona/riven/conversations/..., but that directory/file is not present in the PR or current tree; the existing artifact is still underdocs/research/. Either add the migrated Riven conversation files in this PR or keep this reference on the existing path so the cross-reference is not dead.
- `memory/persona/riven/conversations/2026-05-01-claudeai-backlog-driven-dual-pm-loop-with-refresh-discipline.md`
| # B-0159 — `refresh-github-worldview` cross-cutting refresh script (Claude.ai 2026-05-01) | ||
|
|
||
| **Origin:** Claude.ai feedback packet 2026-05-01 — full lineage in [docs/research/2026-05-01-claudeai-backlog-driven-dual-pm-loop-with-refresh-discipline.md](../../research/2026-05-01-claudeai-backlog-driven-dual-pm-loop-with-refresh-discipline.md) and the maintainer-relayed Claude.ai-2 follow-up calibrating against Otto's running state. | ||
| **Origin:** Claude.ai feedback packet 2026-05-01 — full lineage in [memory/persona/riven/conversations/2026-05-01-claudeai-backlog-driven-dual-pm-loop-with-refresh-discipline.md](../../research/2026-05-01-claudeai-backlog-driven-dual-pm-loop-with-refresh-discipline.md) and the maintainer-relayed Claude.ai-2 follow-up calibrating against Otto's running state. |
| ### 4. Alignment-clause drift detector (DECOMPOSED -> B-0531) | ||
|
|
||
| If a clause in `docs/ALIGNMENT.md` is about to be weakened or removed via the renegotiation protocol, this track generates the impact-survey across factory surfaces that touch the clause. Answers "who depends on this clause, and what breaks if it moves?" before the renegotiation is accepted. | ||
| *(This item has been sliced into B-0531 for atomic mechanization).* |
…echanization) - PR #3518 (B-0442 chain close) merged → 627e797. - PR #3519 (tick 1618Z shard) merged → afc1a99. - PR #3523 opened — B-0532 (backlog-graph consistency lint, P3) filed as substrate from the 1629Z shard insight. BACKLOG.md regenerated. Auto-merge armed. - Sentinel 1011e43d live. ID allocation discipline applied: verified B-0532 free against origin/main (B-0530 max) + in-flight PR scan (B-0531 taken by peer Lior PR #3520). Co-Authored-By: Claude <noreply@anthropic.com>
…echanization) (#3524) - PR #3518 (B-0442 chain close) merged → 627e797. - PR #3519 (tick 1618Z shard) merged → afc1a99. - PR #3523 opened — B-0532 (backlog-graph consistency lint, P3) filed as substrate from the 1629Z shard insight. BACKLOG.md regenerated. Auto-merge armed. - Sentinel 1011e43d live. ID allocation discipline applied: verified B-0532 free against origin/main (B-0530 max) + in-flight PR scan (B-0531 taken by peer Lior PR #3520). Co-authored-by: Claude <noreply@anthropic.com>
Codex P2 finding on already-merged PR #3513 named a real bug class: §33 migrations move files but don't auto-update backlinks. Narrow fix shipped as PR #3529; this row captures the broader pattern. Empirical scan (tick 1802Z) surfaced 20+ dead xrefs in live-nav surfaces across 8 migrated personas. Two-slice approach: - Slice A: per-persona PR batches updating dead xrefs in live-nav surfaces (excludes frozen history archives) - Slice B: static lint at tools/hygiene/lint-section-33-xrefs.ts + wired into gate.yml; composes with B-0532 mechanization pattern ID-allocation discipline applied: B-0531 in-flight (PR #3520), B-0532 on main (file lint), B-0533 free + verified via gh pr list search. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…3563) Empirical anchor: 2026-05-15 had at least 2 cross-agent B-NNNN collisions (B-0444 Otto-Desktop vs Otto-CLI, then B-0532+B-0533 Lior vs Otto-CLI). Each cost ~15 min coordination effort. The discipline-level rule (otto-channels-reference-card.md ID-allocation section) relies on per-agent memory. This row mechanizes the catch at PR-time so it doesn't depend on memory: - Walk docs/backlog/**/B-NNNN-*.md - Group by B-NNNN ID - Hard error if any ID maps to more than 1 file - Wire into gate.yml as sibling of lint-section-33-migration-xrefs Natural extension of B-0532 (backlog-graph consistency lint, parent- child status-mismatch) — same lint family, same gate.yml shape. ID allocation discipline applied: B-0531-B-0534 taken (#3520, #3523, #3540, #3551); B-0535 verified free via origin/main ls-tree + gh pr list search. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Maintenance 2026-05-15T22:07Ztriage**17 unresolved review systematic xref integrity failure (P1)**threads All 17 open threads share one root cause: the PR rewrites file references from Affected paths (representative):
Required fix (two options, pick one):
Mixing both (some rewrites landed, some deferred) is also acceptable as long as every reference in the diff points at a path that will exist after merge. PR is also DIRTY (needs rebase against main before merge can proceed). Co-Authored-By: Copilot 223556219+Copilot@users.noreply.github.com |
Update 2026-05-16T01: xref destinations now exist in main22ZFollowing up on the 2026-05-15T22:07Z triage: the destination files flagged as missing by the Copilot auto-review are now present in main (merged since the triage was written). Confirmed present:
Next step: rebase this branch onto current main. After rebasing, the xref-integrity threads should clear (destination files will exist), and the DIRTY gate should lift. No code changes required. Co-Authored-By: Copilot 223556219+Copilot@users.noreply.github.com |
|
**Maintenance note (Copilot 2026-05-16)**CLI The 17 inline review threads on this PR (all filed by the Copilot cloud reviewer) flagged cross-reference integrity issues: files pointing to Those paths now exist on The xref findings are therefore stale. The remaining blocker is the merge conflict ( git fetch origin main
git rebase origin/main
# resolve any conflicts, then push --force-with-leaseOnce rebased, the Copilot review threads should be dismissible as resolved since the referenced paths now exist. |
|
Maintenance pass (Copilot CLI): resolved 15 stale review Two threads remain open and require author action:
|
|
Copilot maintenance PR #3520 has 2 unresolved review threads and is DIRTY (needs rebase). Blocking items before merge:triage
Resolve threads 1 & 2 and rebase to unblock. |
…irical state-of-world (#3786) * shard(tick): 2026-05-16T06:42Z otto-bg-worker — catch-43 sentinel re-arm + empirical state-of-world Delegated worktree task framing did not match empirical state: - Sentinel was missing at wake → re-armed `d0118686` per catch-43 rule - GraphQL at 542 (extreme cost-aware tier); avoided --all-open batch - 2 oldest stuck Lior PRs (#3341, #3520) classified as merge-conflict-stuck → peer rebase responsibility, not mine to touch - 0 BLOCKED-with-resolve-threads PRs found in this worker's lane Documenting per holding-without-named-dependency-is-standing-by-failure; this shard IS the concrete decomposition work that resets brief-ack counter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(b-3786): collapse line-55 `+` continuation to `plus` so markdown renders paragraph correctly Copilot review thread on line 55 of docs/hygiene-history/ticks/2026/05/16/0642Z.md was a TRUE positive: the leading `+ ` opened a markdown unordered list and broke paragraph continuity from line 54. Replacing with `plus` preserves the semantic continuation and unblocks the markdownlint required-check failure simultaneously. Verified via direct `git show` inspection before applying fix (per blocked-green-ci-investigate-threads.md verify-before-fix discipline). --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Backlog decomposition: extracting item 4 from B-0058 into its own atomic backlog item B-0531.