diff --git a/docs/hygiene-history/ticks/2026/05/27/0608Z.md b/docs/hygiene-history/ticks/2026/05/27/0608Z.md
new file mode 100644
index 0000000000..5b27f6324d
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/27/0608Z.md
@@ -0,0 +1,89 @@
+# Tick 2026-05-27T06:08:49Z — Otto-CLI autonomous-loop
+
+Cold-boot autonomous-loop tick. Catch-43 sentinel was empty (session-exit
+non-persistence per [`tick-must-never-stop.md`](../../../../../../.claude/rules/tick-must-never-stop.md));
+re-armed `ebf96e67` with `* * * * *` + `<<autonomous-loop>>` BEFORE any
+substantive work.
+
+Prior tick on origin/main: `0408Z.md` (worktree-hygiene cleanup, 15 worktrees
+removed). Gap to this tick: ~2h. Cadence consistent with the multi-anchor
+"~2h sentinel session-exit" observation in user-scope MEMORY.md.
+
+## Refresh observations (Step 1)
+
+- `git fetch origin main` clean (no `unable to update local ref` wedge)
+- Operator's primary checkout: `main`, **33 commits behind origin/main** —
+  agent did NOT ff-promote operator's checkout per
+  [`refresh-before-decide.md`](../../../../../../.claude/rules/refresh-before-decide.md)
+  and [`agent-worktree-hygiene-never-hold-main-never-step-on-operator-cleanup-on-pr-merge.md`](../../../../../../.claude/rules/agent-worktree-hygiene-never-hold-main-never-step-on-operator-cleanup-on-pr-merge.md)
+  Rule 1; substantive work landed via isolated worktree off `origin/main`
+- GraphQL tier: **Normal** (`{core: 4934, graphql: 3831, reset_in_min: 51}`);
+  no rate-limit constraint
+- **Dotgit state: 0 stuck `git pack-objects|git maintenance|git repack`
+  procs** — see substantive observation below
+- 24 peer agent processes active (claude-code, gemini/Lior, kiro, cursor,
+  codex composition)
+- 57 untracked files in operator primary (mostly `decompose-4847-*/` +
+  `docs/pr-discussions/PR-52*.md` peer-Lior preservation WIP; not mine to
+  touch per cross-surface lane discipline)
+
+## Step 2 — holding-without-named-dependency check
+
+No named bounded-wait dependency. Brief-ack #1 of this fresh session.
+Substantive concrete artifact below (this shard + the dotgit-recovery
+empirical anchor) resets the counter per
+[`holding-without-named-dependency-is-standing-by-failure.md`](../../../../../../.claude/rules/holding-without-named-dependency-is-standing-by-failure.md)
+condition #3.
+
+## Step 3 — substantive observation: dotgit-saturation arc closed
+
+The multi-day dotgit-saturation arc anchored in user-scope MEMORY.md
+(13 anchors across 2026-05-23T10:18Z → 2026-05-24T12:08Z, stuck-proc
+range 33–540, mean ~382, with the multi-day-not-24h-cyclic refinement)
+**has fully terminated** by 2026-05-27T06:08Z:
+
+| Metric | 2026-05-23 → -24 anchors | 2026-05-27T06:08Z |
+|---|---|---|
+| Stuck git pack/maintenance/repack procs | 33 – 540 (mean ~382) | **0** |
+| Worktree-add canary | hang past 20s SIGKILL | clean (`HEAD is now at ...`) |
+| Worktree freshness post-create | ls-tree 53 (mixed; some gitdir-prune races) | ls-tree 61 + status 0 (clean) |
+| GraphQL tier | drained to Extreme repeatedly | Normal (3831/5000) |
+| Peer-process composition | 3 Lior procs + multi-Otto | 24 mixed peer procs, contention-free |
+
+**Termination mechanism**: not an external maintenance event the agent
+performed (per [`classifier-bypass-research-do-not-deploy-without-zeta-safer-floor.md`](../../../../../../.claude/rules/classifier-bypass-research-do-not-deploy-without-zeta-safer-floor.md)
+and [`agent-worktree-hygiene-never-hold-main-never-step-on-operator-cleanup-on-pr-merge.md`](../../../../../../.claude/rules/agent-worktree-hygiene-never-hold-main-never-step-on-operator-cleanup-on-pr-merge.md)
+destructive-`.git/` mutation discipline). Per
+[`refresh-world-model-poll-pr-gate.md`](../../../../../../.claude/rules/refresh-world-model-poll-pr-gate.md)
+dotgit-saturation recovery script: maintainer-side cleanup
+(`rm .git/index.lock` after `lsof` check, `kill -9` stuck plumbing,
+`git gc --prune=now`). Substrate-honest: the recovery happened
+between 2026-05-24T12:08Z (last 13th anchor) and 2026-05-27T06:08Z
+(this anchor); operational mechanism is bounded by the rule's
+maintainer-side recovery script + intervening B-0847..B-0854
+substrate cascade activity which would be impossible at saturated
+state. The arc DID terminate; the operational tier table's
+sustained-multi-day-extreme-oscillation sub-tier remains useful as
+recognition substrate for future recurrences.
+
+This empirical anchor refines the 12th-anchor "24h cycle closes"
+framing AND the 13th-anchor "multi-day not 24h-cyclic" framing
+into a single named termination point: **the arc CAN extend
+multi-day in continued Extreme tier AND it DOES terminate** —
+neither bound matters; recovery is real even without naming the
+exact mechanism.
+
+## Step 4 — verify + commit
+
+This shard + branch `otto-cli/tick-0608z-2026-05-27` off `origin/main`
+`729710947` (PR #5403 B-0852). Worktree at `/private/tmp/zeta-otto-cli-tick-0608z`
+per [`agent-worktree-hygiene-never-hold-main-never-step-on-operator-cleanup-on-pr-merge.md`](../../../../../../.claude/rules/agent-worktree-hygiene-never-hold-main-never-step-on-operator-cleanup-on-pr-merge.md)
+Rule 2 (NEVER under operator primary).
+
+## Step 5 — Visibility signal (Step 7)
+
+This shard IS the tick's concrete artifact. Otto-CLI's PR lane: 0 open
+Otto-CLI-prefixed branches on the queue (107 total open, all `lior/*`
+peer-surface — coordinate-don't-touch per
+[`fighting-past-self-vs-peer-agent-distinguisher-fix-your-own-coordinate-on-peers-dont-punt-by-default.md`](../../../../../../.claude/rules/fighting-past-self-vs-peer-agent-distinguisher-fix-your-own-coordinate-on-peers-dont-punt-by-default.md)).
+Sentinel `ebf96e67` armed; next tick fires ~1 min.