diff --git a/docs/hygiene-history/ticks/2026/05/16/0044Z.md b/docs/hygiene-history/ticks/2026/05/16/0044Z.md
new file mode 100644
index 000000000..85fb104da
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/16/0044Z.md
@@ -0,0 +1,80 @@
+# Tick 2026-05-16T00:44Z — Otto-CLI worker (jiggly-riding-corbato)
+
+**Surface**: Otto-CLI background worker (Claude Code, Opus 4.7, autonomous-loop tick fired against fresh worktree `jiggly-riding-corbato`)
+**Parent tick**: [2026-05-16T00:23Z](0023Z.md) — M/A coherence-laws type-correctness ([PR #3636](https://github.com/Lucent-Financial-Group/Zeta/pull/3636))
+
+## What this worker did
+
+Triage poll on 40 open PRs via `bun tools/github/poll-pr-gate-batch.ts --all-open`. Identified
+the actionable subset and applied named-dependency discipline rather than racing peer workers.
+
+## Actionable PR survey (gate ≠ "UNKNOWN none-armed")
+
+| PR | Gate | Threads | nextAction | Branch | Active worker |
+|---|---|---|---|---|---|
+| 3644 | BLOCKED | 0 | wait-ci | `kestrel/part3-…` | Otto-CLI (auto-merge armed) |
+| 3643 | BLOCKED | 0 | wait-ci | `lior/decompose-b0459-strict` | Lior; auto-merge NOT armed |
+| 3633 | BLOCKED | 9 | fix-failed-checks | `lior/decompose-3621` | Lior decompose |
+| 3621 | BLOCKED | 10 | fix-failed-checks | `feat/b0449-b0460-subscribe` | parent of 3633 |
+| 3597 | DIRTY | 6 | rebase | `feat/b0501-history-dedup` | sibling worker `.claude/worktrees/cached-sauteeing-plum` |
+| 3520 | DIRTY | 17 | rebase | `lior/decompose-b0058-…` | Lior |
+
+## Triage decision
+
+- **0 PRs match the strict criterion** `gate==BLOCKED && nextAction==resolve-threads` named in
+  this worker's instruction packet. The threads on the actionable PRs are gated behind
+  failed CI / dirty merge state, not by thread-resolution alone.
+- **All 4 thread-carrying PRs are claimed by active workers**:
+  - PR #3597 (6 threads) has `.claude/worktrees/cached-sauteeing-plum` checked out on its
+    head ref (b2033b47c, 2026-05-15T18:19Z author push for prior thread sweep)
+  - PRs #3633 / #3520 are on Lior decompose branches; PR #3621
+    (`feat/b0449-b0460-subscribe`) is the parent of #3633 — same-owner chain. Lior
+    gemini-cli autonomous-loop has been observed across the 0008Z / 0018Z / 0023Z prior
+    ticks. PR #3643 has 0 threads and is gated on CI rather than thread resolution.
+- **Per [`.claude/rules/claim-acquire-before-worktree-work.md`](../../../../../../.claude/rules/claim-acquire-before-worktree-work.md)**:
+  PR thread resolution falls under the DOES-NOT-APPLY clause, but the
+  multi-Otto-branch-state-contamination rule ([B-0519](../../../../../backlog/P3/B-0519-multi-otto-branch-state-contamination-rca-2026-05-14.md))
+  still applies — concurrent checkout of an active peer's branch races the peer's next
+  push.
+
+## Pattern observed on Lior decompose branches (3633 + 3643)
+
+Both fail an identical set of 5 lint checks: `BACKLOG.md generated-index drift`,
+`backlog ID uniqueness`, `markdownlint`, `tsc tools`, `§33 migration xrefs`. Plus CodeQL
+fail-at-2s (NOT the broken-commit canary — `git ls-tree pr-head` returns 52 entries vs
+main's 53, healthy delta from in-PR top-level changes).
+
+This is **main-drift accumulation**: each PR is dozens of commits behind a fast-moving main
+that has added new B-NNNN rows + memory files + §33 migrations. The fix shape is consistent:
+rebase onto main, regenerate `docs/BACKLOG.md` index via `tools/backlog/generate-index.ts`,
+push. Worth a generic notifier when the lint set matches this signature; not done this tick.
+
+## Holding-discipline trace
+
+Named dependencies present:
+
+1. Lior gemini-cli on `lior/decompose-*` branches (active across last 3 ticks)
+2. Sibling Claude worker on `.claude/worktrees/cached-sauteeing-plum` (PR #3597)
+3. Auto-merge daemon on armed PRs (3644)
+
+This is **not Standing-by failure mode**: there are concrete other workers I would race if
+I touched the same branches. The substrate-honest move is to leave the branches to their
+owners and write this visibility-shard so other Otto-CLI fires don't redundantly survey the
+same state.
+
+## State at tick end
+
+- Cron `<<autonomous-loop>>` armed at session start (catch-43 compliance)
+- `bun tools/github/refresh-worldview.ts` ran clean
+- `bun tools/github/poll-pr-gate-batch.ts --all-open` ran clean (1 of ~2 cascade-window
+  budget burned; second poll cost-deferred per `refresh-world-model-poll-pr-gate.md`)
+
+## Next-tick candidates
+
+1. **Auto-merge arm on PR #3643** — if Lior finishes rebase + lint fixes, having
+   `gh pr merge 3643 --auto --squash` pre-armed lets the daemon take over (low risk if Lior's
+   pace stays > Otto worker pace; high reward on idle Lior)
+2. **Generic lint-set-matches-main-drift notifier** — when a Lior PR fails the 5-lint
+   signature, post a bus envelope with the rebase-and-regenerate recipe instead of
+   triaging by hand each tick
+3. **Tick shard cadence** — continue per-tick shards while the active-worker queue is hot