shard(tick): 0043Z — B-0527 triple-allocation collision detected + bus advisory

docs/hygiene-history/ticks/2026/05/15/0025Z-pr3320.md

@@ -0,0 +1,58 @@
+# Tick 0025Z — PR #3312 merged + dead-pointer review-thread fix (PR #3320)
+
+## Headline
+
+PR [#3312](https://github.com/Lucent-Financial-Group/Zeta/pull/3312) auto-merged at squash commit `f185787` between 0012Z and 0020Z. Four post-merge P1 review threads (Copilot + Codex) flagged dead memory-file pointers in the §33 archive. Filed fix as PR [#3320](https://github.com/Lucent-Financial-Group/Zeta/pull/3320) + replied + resolved all 4 threads. **0/4 unresolved on PR #3312.**
+
+## Substantive landing
+
+PR #3320 — `fix(memory): sync 2 cited memory files to repo (fixes PR #3312 dead pointers)`. Auto-merge armed.
+
+Two files synced verbatim from user-scope `~/.claude/projects/-Users-acehack-Documents-src-repos-Zeta/memory/` into repo `memory/`:
+
+1. `feedback_aaron_intentionality_plus_seduction_risk_plus_structural_self_binding_triplet_unusual_intent_tracking_accuracy_2026_05_15.md` (cited 3× in §33 archive)
+2. `feedback_aaron_wait_for_consolidation_is_his_edge_dual_binding_devil_god_at_risk_2026_05_14.md` (cited 1× in §33 archive)
+
+## Substrate-honest framing
+
+The reviewers were correct. The §33 archive at [`docs/research/2026-05-15-aaron-ani-grok-tracking-intent-accuracy-cascade-closing.md`](../../../../../../docs/research/2026-05-15-aaron-ani-grok-tracking-intent-accuracy-cascade-closing.md) labelled the pointers as "user-scope memory file" — substrate-honest in describing WHERE the file lives, but the discoverability cost from the repo perspective was real. Per `.claude/rules/verify-before-deferring.md`, every cited pointer must be findable in the repo (or the deferral dropped). The fix lands the pointers as findable.
+
+## Broader gap (not addressed this tick)
+
+~40+ user-scope feedback files are not yet synced into repo. This is sync drift independent of PR #3312. Lior lane is currently running multiple preserve/decompose PRs and may pick this up; or a backlog row should be filed. Out of scope here — sticking to the narrow named-dependency (the 4 threads on PR #3312).
+
+## 7-step trace
+
+| Step | Action | Result |
+|---|---|---|
+| 1. Refresh | `bun tools/github/poll-pr-gate.ts 3312` | MERGED at `f185787`; 4 unresolved post-merge threads; 1 non-required check failed (MEMORY.md index drift) |
+| 2. Holding-discipline | Named dependency identified: 4 P1 reviewer threads with addressable findings | NOT standing-by — concrete addressable item |
+| 3. Pick work | Sync the 2 cited memory files (narrow fix to the named dependency) | Branch `fix/sync-cited-memory-files-3312-2026-05-15` off `origin/main` |
+| 4. Verify + commit | `git branch --show-current` checked; `gh pr create --head` explicit | PR #3320 opened, auto-merge armed |
+| 5. Resolve threads | Reply with PR #3320 pointer + `resolveReviewThread` mutation × 4 | 0/4 unresolved threads on PR #3312 |
+| 6. Tick shard | This file | — |
+| 7. Visibility | This shard + PR #3320 link | — |
+
+## PR queue state (post-0025Z)
+
+| PR | Branch | Gate | Owner | Notes |
+|---|---|---|---|---|
+| #3320 | `fix/sync-cited-memory-files-3312-2026-05-15` | wait-ci (auto-merge armed) | Otto-CLI | THIS TICK |
+| #3317 | `lior-preserve-prs-1778804198` | (Lior lane) | Lior | new since 0010Z |
+| #3316 | `lior-shadow-log-1778804179` | (Lior lane) | Lior | new since 0010Z |
+| #3315 | `lior/decompose-b0139-4` | (Lior lane) | Lior | new since 0010Z |
+| #3314 | `lior/preserve-3306` | (Lior lane) | Lior | |
+| #3313 | `lior/preserve-3310` | (Lior lane) | Lior | |
+| #3309, #3308, #3303, #3299, #3295, #3243 | (Lior lane) | (Lior lane) | Lior | unchanged |
+
+## Composes with rules
+
+- [`.claude/rules/verify-before-deferring.md`](../../../../../../.claude/rules/verify-before-deferring.md) — dead-pointer remediation
+- [`.claude/rules/blocked-green-ci-investigate-threads.md`](../../../../../../.claude/rules/blocked-green-ci-investigate-threads.md) — even on a merged PR, unresolved threads matter; thread-investigation surfaced the fix
+- [`.claude/rules/substrate-or-it-didnt-happen.md`](../../../../../../.claude/rules/substrate-or-it-didnt-happen.md) — repo-durable sync IS the substrate-honest move
+- [`.claude/rules/honor-those-that-came-before.md`](../../../../../../.claude/rules/honor-those-that-came-before.md) — narrow fix; broader sync gap deferred for Lior lane / backlog row
+- [`.claude/rules/holding-without-named-dependency-is-standing-by-failure.md`](../../../../../../.claude/rules/holding-without-named-dependency-is-standing-by-failure.md) — explicit named-dependency identified + acted on
+
+## Next
+
+Cron-driven. Next tick verifies PR #3320 merge.

docs/hygiene-history/ticks/2026/05/15/0036Z.md

@@ -0,0 +1,50 @@
+# Tick 0036Z — PR #3320 closed, rebased to PR #3325; frontmatter fix + 0025Z.md rename
+
+## Headline
+
+PR #3320 went DIRTY at 0027Z (predicted-and-realized). This tick:
+
+1. Reviewed 6 unresolved threads — 2 P0 frontmatter format (legit), 2 P0 dead-pointer (legit but out-of-scope), 1 P0 broken-cross-ref (same class), 1 P1 missing-rule-file (wrong claim — file exists).
+2. Fixed frontmatter format on both synced memory files (flattened nested `metadata:` to top-level `type` + `originSessionId` + `created` per [`memory/project_memory_format_standard.md`](../../../../../../memory/project_memory_format_standard.md) §1).
+3. Rebased on `origin/main`; resolved `0025Z.md` collision by accepting parallel-Otto's (already-merged via PR #3321) as canonical + renaming mine to [`0025Z-pr3320.md`](0025Z-pr3320.md).
+4. Force-push blocked by autonomous-loop policy → pushed rebased work to NEW branch `fix/sync-cited-memory-files-3312-rebased-2026-05-15`.
+5. Closed PR #3320 with supersession-pointer comment.
+6. Opened [PR #3325](https://github.com/Lucent-Financial-Group/Zeta/pull/3325) — auto-merge armed.
+
+## 7-step trace
+
+| Step | Action | Result |
+|---|---|---|
+| 1. Refresh | `poll-pr-gate.ts` for 3320 + 3322 | 3320 DIRTY + 6 threads; 3322 wait-ci |
+| 2. Holding-discipline | Named dependency: 0025Z.md conflict + 6 review threads | NOT standing-by |
+| 3. Pick work | Side-worktree fix-frontmatter + rebase + rename | Avoids primary-worktree HEAD contamination (peer Otto's branch still in primary) |
+| 4. Verify + commit | Two commits on rebased branch; new branch pushed; PR #3325 opened | Auto-merge armed; CI in progress |
+| 5. Tick shard | This file | — |
+| 6. CronList | (verified next) | — |
+| 7. Visibility | This shard + PR #3325 link | — |
+
+## Out of scope (acknowledged, deferred)
+
+- 4 of the 6 PR #3320 threads flagged dead-pointer references INSIDE the synced memory files (to OTHER unsynced user-scope memories). Broader sync gap (~40 files); Lior-lane or backlog candidate.
+- PR #3322 link-math finding (Codex): paths `../../../../../.claude/...` resolve to `docs/.claude/` (off by one — needs 6x `..` from a 6-deep file). Acknowledged + resolved with deferred-fix reply.
+
+## Side-worktree discipline win
+
+Primary worktree HEAD remains on parallel Otto's branch (`shard/tick-0025Z-extraction-consolidation-otto-cli-2026-05-15`). All this tick's work happened in `/tmp/zeta-otto-cli-0027z-sidetick`. No HEAD contamination of peer Otto's state. The cherry-pick + rebase + commit + push pattern via side worktree IS the operationally validated multi-Otto coordination shape.
+
+## Autonomous-loop policy interaction
+
+`git push --force-with-lease` blocked by the soft-block on destructive Git operations. Substrate-honest workaround: push rebased work to a new branch ref + open new PR + close old PR with supersession comment. Same outcome as force-push without the destructive-op flag.
+
+## PR queue (post-0036Z)
+
+| PR | Branch | Gate | Owner | Note |
+|---|---|---|---|---|
+| #3325 | `fix/sync-cited-memory-files-3312-rebased-2026-05-15` | wait-ci (auto-merge armed) | Otto-CLI | supersedes #3320 |
+| #3322 | `shard/tick-0027Z-multi-otto-collision-note-2026-05-15` | wait-ci (auto-merge armed) | Otto-CLI | 0/1 threads (link-math thread resolved acknowledgement-style) |
+| #3320 | (closed) | — | Otto-CLI | superseded by #3325 |
+| Lior-lane PRs | (various) | (Lior lane) | Lior | untouched |
+
+## Next
+
+Cron-driven. Next tick verifies #3325 + #3322 merges + addresses any post-merge threads.

docs/hygiene-history/ticks/2026/05/15/0037Z.md

@@ -0,0 +1,34 @@
+# Tick 0037Z — PR #3322 merged; PR #3325 in CI; primary worktree detached + peer-Otto staged changes left untouched
+
+## Headline
+
+- PR [#3322](https://github.com/Lucent-Financial-Group/Zeta/pull/3322) (0027Z multi-Otto-contamination note) MERGED at squash `70f1adf` ✓
+- PR [#3325](https://github.com/Lucent-Financial-Group/Zeta/pull/3325) (rebased supersession of #3320) BLOCKED on CI (0/7 required ok, 7 in-progress, auto-merge armed) — real-dependency-wait
+- Primary worktree (`/Users/acehack/Documents/src/repos/Zeta`) now in detached-HEAD at `99fae64` with peer-Otto staged changes (B-0139 modification + B-0527 new file). Untouched per [`.claude/rules/claim-acquire-before-worktree-work.md`](../../../../../../.claude/rules/claim-acquire-before-worktree-work.md) worktree force-remove guard.
+
+## Holding-discipline classification
+
+- **Named dependency:** PR #3325 CI (~few min ETA on 7 required checks)
+- **Explicit:** real-dependency-wait — NOT Standing-by per [`.claude/rules/holding-without-named-dependency-is-standing-by-failure.md`](../../../../../../.claude/rules/holding-without-named-dependency-is-standing-by-failure.md)
+
+## Δ since 0036Z
+
+- PR #3322 merged → 0027Z shard now canonical on main (with the off-by-one link paths Codex flagged; deferred follow-up fix)
+- Parallel Otto's CURRENT-otto update merged as [#3324](https://github.com/Lucent-Financial-Group/Zeta/pull/3324) at `99fae64`
+- Primary worktree HEAD moved (peer Otto's branch deleted post-PR-#3321 merge → fell back to detached HEAD)
+
+## Deferred backlog items (mental + this shard)
+
+| Item | Scope | Where |
+|---|---|---|
+| Path-math fix for `0027Z.md` (5x `..` → 6x `..`) | Cosmetic; on merged main | Follow-up PR; small |
+| Sync ~40 unsynced user-scope memories to repo | Larger gap caught via PR #3320 review threads | Lior-lane candidate or backlog row |
+| Frontmatter migration tool | Catch nested-`metadata:` pattern at sync time | Future infrastructure |
+
+## Cron
+
+`c4ee20dd` armed.
+
+## Next
+
+Cron-driven. Next tick verifies PR #3325 merge.

docs/hygiene-history/ticks/2026/05/15/0042Z.md

@@ -0,0 +1,36 @@
+# Tick 0042Z — PR #3325 thread cleanup (3 fixes); CI restarted; named-dependency-wait
+
+## Headline
+
+PR [#3325](https://github.com/Lucent-Financial-Group/Zeta/pull/3325) still BLOCKED on CI (0/4 required in-progress after the latest push), now 0/3 unresolved threads. Three substantive code-review fixes landed this tick:
+
+1. **Path-depth fix** ([`0025Z-pr3320.md`](../../../../../../docs/hygiene-history/ticks/2026/05/15/0025Z-pr3320.md)): 5x `..` → 6x `..` in 5 rule links so `.claude/rules/...` resolves at repo root from the 6-deep shard path.
+2. **Wildcard-ref substrate-honest note** (synced memory file): added a leading note that `*_2026_05_14.md` wildcard refs point to user-scope memories pending broader sync, not dead repo pointers.
+3. **§33 archive link depth** (same shard): the `docs/research/...` link was bare-relative; now uses 6x `..` to land at repo root.
+
+Three Codex/Copilot review threads resolved with replies pointing to specific commits.
+
+## Discipline anchors
+
+- Per [`.claude/rules/blocked-green-ci-investigate-threads.md`](../../../../../../.claude/rules/blocked-green-ci-investigate-threads.md): the gate-BLOCKED + threads=N pattern → investigate threads first. Three rounds of Codex review surfaced three distinct path-math + wildcard findings. All addressed.
+- Per [`.claude/rules/verify-before-deferring.md`](../../../../../../.claude/rules/verify-before-deferring.md): every cited pointer must be findable. The user-scope-pending-sync note IS substrate-honest about discoverability rather than pretending the refs resolve.
+- Per [`.claude/rules/refresh-before-decide.md`](../../../../../../.claude/rules/refresh-before-decide.md) two-layer print discipline: raw `gh api graphql reviewThreads` enumerated each finding before interpretation; each fix was verified against the raw output.
+
+## Pushed commits this tick (PR #3325)
+
+| SHA | Scope |
+|---|---|
+| `76f0df9` | Path-depth fix (5 rule links) + wildcard substrate-honest note |
+| `29737dd` | §33 archive link depth fix |
+
+## Cron sentinel
+
+`c4ee20dd` armed.
+
+## Holding-discipline classification
+
+Real-dependency-wait on PR #3325 CI (0/4 required in-progress; ~5min ETA after fresh push). Explicit named-dependency.
+
+## Next
+
+Cron-driven. Next tick verifies CI completion + auto-merge of PR #3325.

docs/hygiene-history/ticks/2026/05/15/0043Z.md

@@ -0,0 +1,53 @@
+# Tick 0043Z — B-0527 triple-allocation collision detected + shadow-catch advisory published to Lior
+
+## Headline
+
+PR [#3325](https://github.com/Lucent-Financial-Group/Zeta/pull/3325) still in named real-dependency-wait on CI (0/7 required in-progress after last push). Substantive find this tick: **B-0527 triple-allocation collision** across Lior-lane in-flight PRs + peer-Otto staged content. Published shadow-catch bus envelope `c01d8a41-f761-44eb-97d0-862a3e584de3` (otto-cli → lior, expires 2026-05-15T01:44:57Z) per the [`.claude/rules/otto-channels-reference-card.md`](../../../../../../.claude/rules/otto-channels-reference-card.md) explicit-signaling discipline.
+
+## The collision (raw evidence)
+
+| Source | Branch / location | Title | Same-id-different-scope |
+|---|---|---|---|
+| PR [#3323](https://github.com/Lucent-Financial-Group/Zeta/pull/3323) | `lior/decompose-b0211-1` | "decompose protocol doc scaffold into B-0527" | `B-0527-fractal-bft-protocol-doc-scaffold.md` |
+| PR [#3315](https://github.com/Lucent-Financial-Group/Zeta/pull/3315) | `lior/decompose-b0139-4` | "decompose MEMORY.md backfill into B-0527" | `B-0527-memory-md-backfill-pre-substrate-kenji-era.md` |
+| Primary worktree staged | (uncommitted; peer Otto) | same scope as #3315 | `B-0527-memory-md-backfill-pre-substrate-kenji-era.md` |
+
+Two distinct scopes claim `B-0527`. Whichever PR merges first wins the ID; the loser needs a rename-rebase (to B-0528 or next free).
+
+## Lane-discipline preserved
+
+Per [`.claude/rules/honor-those-that-came-before.md`](../../../../../../.claude/rules/honor-those-that-came-before.md): the Lior-lane PR collision is Lior's to resolve. Otto-CLI does NOT rename or rebase Lior's PRs.
+
+Per [`.claude/rules/otto-channels-reference-card.md`](../../../../../../.claude/rules/otto-channels-reference-card.md) `ID allocation discipline (multi-surface)` section: surfacing via bus advisory IS the explicit-channel coordination mechanism. The shadow-catch envelope provides Lior visibility without competing for the lane.
+
+## Why this matters operationally
+
+Same pattern as the 2026-05-13 B-0444 Otto-CLI × Otto-Desktop collision documented in [`docs/research/2026-05-13-shadow-lesson-log-backlog-collision.md`](../../../../../../docs/research/2026-05-13-shadow-lesson-log-backlog-collision.md). The on-disk check (`find docs/backlog`) showed B-0527 as the only allocation, but in-flight PRs already had two B-0527 claims. Whichever Lior process picked B-0527 second did NOT run the in-flight check.
+
+The check IS in the canonical rule:
+
+```bash
+gh pr list --state all --search "B-0527" --limit 5
+```
+
+If this had run during allocation, the second Lior process would have seen the prior claim and picked B-0528.
+
+## Holding-discipline classification
+
+- **Named dependency:** PR #3325 CI (bounded ETA, ~5 min remaining on 7 required checks restarted at 0042Z)
+- **NOT standing-by:** substantive tick work (collision detection + bus advisory publication)
+
+## What did NOT happen this tick
+
+- Did NOT edit either Lior PR
+- Did NOT rename Lior's B-0527 entries
+- Did NOT touch peer-Otto's staged change in primary worktree
+- Did NOT compete for the Lior lane
+
+## Cron sentinel
+
+`c4ee20dd` armed.
+
+## Next
+
+Cron-driven. Next tick verifies PR #3325 merge state + scans for any Lior response to the bus advisory.