diff --git a/docs/hygiene-history/ticks/2026/05/15/0804Z.md b/docs/hygiene-history/ticks/2026/05/15/0804Z.md
new file mode 100644
index 0000000000..e32e54e019
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/15/0804Z.md
@@ -0,0 +1,60 @@
+| 2026-05-15T08:04:00Z | claude-opus-4-7 | 596e842c | shard: (PR TBD) preempts on 2 prior shards; ID-allocation rule update PR #3384 opened | (PR #3385) | preemptive vs reactive: 0754Z bug fix landed before Codex caught it; rule update closes the 0742Z B-0528-misallocation lesson |
+
+# Tick 0804Z — `(PR TBD)` preempts on 2 shards; ID-allocation rule update PR #3384 opened
+
+## Headline
+
+- **PR [#3381](https://github.com/Lucent-Financial-Group/Zeta/pull/3381)** (0742Z shard) had one new Codex P2 thread — `(PR TBD)` placeholder needed to be `(PR #3381)`. Fixed in commit `80a0a18`; thread resolved.
+- **PR [#3383](https://github.com/Lucent-Financial-Group/Zeta/pull/3383)** (0754Z shard) had the same `(PR TBD)` issue — fixed PREEMPTIVELY this tick (before any Codex/Copilot review surfaced). Commit `e2fa2ef`.
+- **PR [#3384](https://github.com/Lucent-Financial-Group/Zeta/pull/3384)** opened + auto-merge armed: ID-allocation rule update in [`.claude/rules/otto-channels-reference-card.md`](../../../../../../.claude/rules/otto-channels-reference-card.md). Replaces local `find docs/backlog` with `git fetch origin main` + `git ls-tree -r origin/main`. Closes the lesson from the 0742Z B-0528-misallocation incident.
+- Cron sentinel `596e842c` armed.
+
+## Δ since 0754Z
+
+| What | At 0754Z | At 0804Z |
+|---|---|---|
+| PR #3381 (0742Z shard) | OPEN, wait-ci | OPEN, 1 Codex P2 thread → fixed + resolved (`80a0a18`) |
+| PR #3383 (0754Z shard) | OPEN, wait-ci | OPEN, preemptive (PR TBD) fix (`e2fa2ef`) |
+| PR #3384 (ID-alloc rule) | not yet filed | OPEN, auto-merge armed |
+| PR #3379 (0724Z shard) | wait-ci after 8 threads addressed | OPEN, wait-ci (no new threads as of 0804Z) |
+| PR #3382 (bulk-fix) | OPEN, wait-ci | OPEN, wait-ci |
+| 0027z borrow count | ~14 | 17 (3 borrows this tick: 0742Z fix + 0754Z preempt + new branch) |
+
+## Substrate-honest observations
+
+### Preemptive vs reactive fix-pattern
+
+The 0742Z shard had `(PR TBD)` and Codex caught it (the 07:53Z thread on PR #3381). Standard reactive pattern: wait for the reviewer-finding, address it.
+
+The 0754Z shard had the SAME bug structure (`(PR TBD)` placeholder; PR number not knowable at write-time because the PR doesn't exist yet). This tick fixed 0754Z PREEMPTIVELY before any reviewer thread surfaced. Substrate-honest: I knew the bug pattern would repeat once I had the PR number in hand. Going forward: post-PR-create, immediately push a `sed s|(PR TBD)|(PR #NNNN)|` follow-up commit.
+
+This is the operational pattern emerging from this iteration — **the (PR TBD)-then-update sequence is structural, not accidental**. The shard authoring happens BEFORE the PR opens (you can't reference an ID you don't have yet), so the placeholder is inevitable. The discipline is to close it promptly post-PR-open, not to wait for review-thread surface.
+
+### ID-allocation rule update
+
+PR #3384 fixes the substrate gap exposed by tick 0742Z (B-0528-misallocation):
+
+**Before**: ID-allocation step 1 used `find docs/backlog -name "B-*.md"` against the local working tree. When the local primary worktree is stuck on a stale HEAD (detached from an abandoned rebase, or on a feature branch behind main), this returns stale state.
+
+**After**: Step 1 uses `git fetch origin main` + `git ls-tree -r origin/main -- docs/backlog/`. Reads the merged-state from the remote ref directly, independent of local worktree state.
+
+The empirical anchor (0742Z incident) is now cited in the rule body. Future-Otto cold-booting after PR #3384 merges will get the corrected discipline at session start.
+
+### Lane-respect for path-bug bulk-fix
+
+PR #3382 (bulk-fix) intentionally scoped to my 4 shards only. Peer-Otto's 0230Z + 0615Z left untouched per lane-respect discipline. If peer-Otto reads PR #3382 (or this shard) and notices their shards have the same bug, they can fix their own scope.
+
+This is per [`.claude/rules/no-directives.md`](../../../../../../.claude/rules/no-directives.md) — Otto-CLI doesn't direct peer-Otto's work even when the fix is mechanical. Peer-Otto is autonomous.
+
+## Cron sentinel
+
+`596e842c` armed.
+
+## Next
+
+Cron-driven. Next tick:
+
+1. Verify PR #3381 (post-fix) + #3382 + #3383 (post-preempt) + #3384 (rule update) auto-merge fires
+2. Watch PR #3323 for Lior response (still 3 comments: original Codex + my 2 advisories)
+3. If new threads surface, address in fix-iteration
+4. Consider next substantive work — current candidates: investigate `com.zeta.claude-loop` substrate (last remaining unknown in B-0530 prune-race investigation) OR write up post-PR `(PR TBD)` mechanization (small TS helper that auto-fixes after `gh pr create`)