chore(b-0139): decompose research cross-reference audit to B-0353

docs/BACKLOG.md

@@ -316,6 +316,7 @@ are closed (status: closed in frontmatter)._
 - [ ] **[B-0518](backlog/P1/B-0518-sharpen-holding-without-named-dependency-rule-anti-failure-mode-2026-05-14.md)** Sharpen the holding-without-named-dependency rule — Aaron diagnosed CLAUDE.md bug
 - [ ] **[B-0520](backlog/P1/B-0520-new-surface-audit-alignment-check.md)** Mechanize new-surface audit for alignment-clause consistency
 - [ ] **[B-0522](backlog/P1/B-0522-pre-substrate-kenji-era-git-branches-inventory.md)** Pre-substrate Kenji-era git branches and worktrees inventory
+- [ ] **[B-0523](backlog/P1/B-0523-kenji-era-research-docs-cross-reference-audit.md)** Kenji-era research docs cross-reference audit (peeled from B-0139)
 
 ## P2 — research-grade
 

docs/backlog/P1/B-0139-pre-substrate-kenji-era-otto-work-inventory-aaron-2026-05-01.md

@@ -7,8 +7,8 @@ created: 2026-05-01
 last_updated: 2026-05-14
 depends_on: []
 type: friction-reducer
-decomposition: partial
-children: [B-0522]
+decomposition: decomposed
+children: [B-0522, B-0523]
 ---
 
 # B-0139 — Pre-substrate Kenji-era inventory

docs/backlog/P1/B-0523-kenji-era-research-docs-cross-reference-audit.md

@@ -0,0 +1,30 @@
+---
+id: B-0523
+priority: P1
+status: open
+title: Kenji-era research docs cross-reference audit (peeled from B-0139)
+created: 2026-05-14
+last_updated: 2026-05-14
+depends_on: []
+parent: B-0139
+type: friction-reducer
+decomposition: atomic
+---
+
+# B-0523 — Kenji-era research docs cross-reference audit
+
+**Priority:** P1
+**Parent:** B-0139
+**Filed:** 2026-05-14
+**Filed by:** Lior
+
+## What
+
+This is a decomposed slice of the B-0139 blob (Pre-substrate Kenji-era Otto-lineage work inventory). It handles specifically the `docs/research/` cross-reference sub-scope:
+
+"Pre-substrate research docs under `docs/research/` that aren't yet in `MEMORY.md` or referenced from substrate-class memory files."
+
+## Acceptance Criteria
+
+1. **`docs/research/` cross-reference**: Every file under `docs/research/` is either indexed in `MEMORY.md` or has explicit "research-grade unindexed" rationale.
+2. Provide a report of the findings and update `MEMORY.md` where appropriate.

docs/pr-discussions/PR-3289-shard-tick-2218z-off-duty-3286-merged.md

@@ -0,0 +1,36 @@
+---
+pr_number: 3289
+title: "shard(tick): 2218Z \u2014 off-duty; #3286 merged"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-14T22:19:10Z"
+merged_at: "2026-05-14T22:21:46Z"
+closed_at: "2026-05-14T22:21:46Z"
+head_ref: "shard/tick-2218Z-off-duty-otto-cli-2026-05-14"
+base_ref: "main"
+archived_at: "2026-05-14T22:48:17Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #3289: shard(tick): 2218Z — off-duty; #3286 merged
+
+## PR description
+
+Off-duty. #3286 merged as `9519553`. #3287 + #3288 wait-ci. 41 merged + 2 wait-ci.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-14T22:20:42Z)
+
+## Pull request overview
+
+Adds the next hygiene-history “tick” log entry for 2026-05-14 22:18Z, recording the off-duty status and the merge/wait-ci state of recent PRs as part of the ongoing tick cadence under `docs/hygiene-history/`.
+
+**Changes:**
+- Add tick entry `2218Z` documenting the current off-duty status.
+- Record merge of **#3286** (commit `9519553`) and note **#3287**/**#3288** as wait-ci with autoMerge armed.
+- Update the running totals (41 merged, 2 wait-ci).

docs/research/2026-05-14-shadow-lesson-log-lior-metadata-churn-off-duty.md → docs/research/shadow-lesson-log-lior-metadata-churn-off-duty-2026-05-14.md

@@ -4,10 +4,13 @@
 **Node:** Lior
 
 ## Observation
+
 During an antigravity check, I observed PRs #3284 and #3285 actively engaging in metadata churn. They are titled "shard(tick): ... — off-duty" and contain only markdown tick files stating "Off-duty".
 
 ## The Drift
+
 This is a manifestation of Catch 36 (narration-over-action) and metadata churn without parity proofs. The loop is generating activity (PRs, commits) simply to state that it is off-duty, creating noise instead of signal. An off-duty state should imply silence, not active PR generation.
 
 ## Correction
+
 I have commented on PRs #3284 and #3285 flagging this as drift and instructing the loop to halt. The shadow log has been updated, and the preservation discipline was executed to ensure the network memory remains intact without getting overwhelmed by empty metadata shards.