diff --git a/docs/hygiene-history/ticks/2026/05/20/1700Z.md b/docs/hygiene-history/ticks/2026/05/20/1700Z.md
new file mode 100644
index 0000000000..2689edd84c
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/20/1700Z.md
@@ -0,0 +1,39 @@
+| 2026-05-20T17:00Z | opus-4-7 / autonomous-loop | b49c090e | brief-ack #1 — named-dependency wait on CI completion of PR #4435; peer-detected → bus envelope per canonical step 1 | -- | tick #4 of session; substrate observation via bus envelope, not file commit |
+
+# Tick 1700Z — 2026-05-20 — brief-ack #1 (named-dep on #4435 CI)
+
+## Substantive
+
+Brief-ack tick. 10 minutes after [1643Z](https://github.com/Lucent-Financial-Group/Zeta/pull/4435) closed. Named-dependency-wait on CI completion of [PR #4435](https://github.com/Lucent-Financial-Group/Zeta/pull/4435) (1643Z merge-narrative shard).
+
+**State:**
+
+- Rate: GraphQL 3597/5000 (Normal tier)
+- PR #4435: requiredChecks 2 ok + 4 inProgress + 1 pending, 0 failures, 0 unresolved threads, autoMerge armed
+- main HEAD: still `1d50d0e0` (#4435 not yet merged)
+- `peerDetected: true` per [`tools/orchestrator-checks/cron-sentinel-mutex.ts`](../../../../../../tools/orchestrator-checks/cron-sentinel-mutex.ts) — 9+ Claude processes; canonical step 1 says avoid `git worktree add`
+
+**Substrate observation form:** per the canonical peer-detected guidance, bus envelope rather than file commit. Published `6323abdc-25b3-46be-b1a4-0ee14380ba49` (shadow-catch, broadcast, 1h TTL) capturing the brief-ack #1 audit trail.
+
+**Why a minimal shard exists despite bus-envelope-as-primary:** the canonical step 5 says every tick gets a shard ("Substrate-or-it-didn't-happen applies to ticks too — without the shard, future-Otto can't reconstruct what landed when"). The bus envelope expires in 1h; the shard is durable. Both serve different time horizons. This shard authored retroactively in the [1703Z tick](1703Z.md)'s worktree-branch to land both at once.
+
+## Verify
+
+- Bus envelope published successfully (envelope ID returned by `bun tools/bus/bus.ts publish`)
+- PR #4435 gate refreshed via `poll-pr-gate.ts` — `nextAction: wait-ci` (canonical named-dep state)
+- Sentinel alive
+
+## CronList
+
+`b49c090e` alive at start AND close.
+
+## Composes with
+
+- [`docs/hygiene-history/ticks/2026/05/20/1643Z.md`](https://github.com/Lucent-Financial-Group/Zeta/pull/4435) (prior tick; this tick brief-acks the named CI-completion dep it opened)
+- [`docs/hygiene-history/ticks/2026/05/20/1703Z.md`](1703Z.md) (next tick — this shard was authored in 1703Z's worktree and bundled into the same PR)
+- [`.claude/rules/holding-without-named-dependency-is-standing-by-failure.md`](../../../../../../.claude/rules/holding-without-named-dependency-is-standing-by-failure.md) (brief-ack #1 with explicit bounded-dep naming; counter discipline holding)
+- [`docs/AUTONOMOUS-LOOP-PER-TICK.md`](../../../../../../docs/AUTONOMOUS-LOOP-PER-TICK.md) (canonical step 1 peer-detected → bus-envelope-not-worktree-add)
+
+## Visibility-stop
+
+Substrate observation form: bus envelope `6323abdc` (ephemeral, 1h TTL) + this shard (durable). End.
diff --git a/docs/hygiene-history/ticks/2026/05/20/1703Z.md b/docs/hygiene-history/ticks/2026/05/20/1703Z.md
new file mode 100644
index 0000000000..35080525a6
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/20/1703Z.md
@@ -0,0 +1,89 @@
+| 2026-05-20T17:03Z | opus-4-7 / autonomous-loop | b49c090e | substantive — BLOCKED-with-green-CI investigated; Codex path-bug verified + fixed across 1626Z + 1643Z; 2 threads resolved | -- | tick #5 of session; pure-git→Normal tier (3597/5000 GraphQL) |
+
+# Tick 1703Z — 2026-05-20 — BLOCKED-with-green-CI investigation + path-fix
+
+## Substantive
+
+3 minutes after the [1700Z brief-ack tick](1700Z.md). Initial refresh of [PR #4435](https://github.com/Lucent-Financial-Group/Zeta/pull/4435) state revealed the canonical BLOCKED-with-green-CI pattern — exactly the failure mode [`.claude/rules/blocked-green-ci-investigate-threads.md`](../../../../../../.claude/rules/blocked-green-ci-investigate-threads.md) is calibrated for.
+
+**State at refresh:**
+
+| Signal | Value | Reading |
+|---|---|---|
+| `requiredChecks.ok` | 7 | All required green |
+| `requiredChecks.failed` | 0 | Nothing failing |
+| `unresolvedThreads` | 1 | THE blocker |
+| `autoMerge` | armed | Will fire on resolution |
+| Warnings | non-required `lint (tick-shard relative-paths)` | Hint at the topic |
+| `nextAction` | `resolve-threads` | Investigate, don't wait |
+
+**Thread investigation (Codex finding, `PRRT_kwDOSF9kNM6DjvCR`):**
+
+> Fix broken relative path to rule docs. The `.claude` link here uses `../../../../../`, which resolves from `docs/hygiene-history/ticks/2026/05/20/` to `docs/.claude/...` instead of the repository root. In practice this produces dead links in the tick shard...
+
+**Verify-before-fix** (per the rule's discipline):
+
+```bash
+# 1. Direct line inspection
+awk -v N=52 'NR==N { print NR": ["$0"]" }' .../1643Z.md
+# 52: [- [`.claude/rules/zeta-expected-branch.md`](../../../../../.claude/rules/zeta-expected-branch.md) ...]
+
+# 2. Filesystem resolution test (verify the broken claim, then the fix)
+ls .../2026/05/20/../../../../../.claude/rules/refresh-world-model-poll-pr-gate.md
+# → No such file or directory  (claim verified)
+ls .../2026/05/20/../../../../../../.claude/rules/refresh-world-model-poll-pr-gate.md
+# → -rw-r--r-- 20221 bytes  (6-ups correct)
+```
+
+**Path-depth math:** the tick shard lives at `docs/hygiene-history/ticks/2026/05/20/HHMMZ.md` — 6 directories deep from repo root. Targeting `.claude/rules/*` (at repo root) needs 6 ups (`../../../../../../.claude/rules/...`). The 5-up variant resolves to `docs/.claude/rules/...` (doesn't exist).
+
+**Why the 1413Z prior-tick template didn't catch this:** the 1413Z shard linked to `docs/research/*` targets using 5 ups — which IS correct because the target shares the `docs/` ancestor. My 1626Z/1643Z shards copy-pasted the same 5-up pattern but pointed at `.claude/rules/*` — a target NOT under `docs/`. The bug is a per-target-prefix gotcha, not a per-shard-template gotcha.
+
+**Fix scope across the in-flight branch:**
+
+| File | Occurrences | Status |
+|---|---|---|
+| 1614Z.md | 0 | Uses bare references (no markdown link targets) — no fix needed |
+| 1626Z.md | 6 | All fixed (file is on main via squash `1d50d0e0`; fix lands as diff vs main on #4435 branch) |
+| 1643Z.md | 4 | All fixed (Codex flagged line 52 specifically; root finding applies to all 4) |
+
+Fix commit `24ba9c2b` landed on PR #4435 branch via fast-forward push (`e0d020f9..24ba9c2b`). Codex thread resolved via `resolveReviewThread` GraphQL mutation.
+
+**Second thread fired post-fix:** Copilot (`copilot-pull-request-reviewer`) auto-reviewed the original 1643Z commit (pre-fix, `e0d020f9`) at 17:05:06Z, identified the same finding ("Add one more `../`"), filed thread `PRRT_kwDOSF9kNM6Djyls` with `isOutdated: true`. Per [`blocked-green-ci-investigate-threads.md`](../../../../../../.claude/rules/blocked-green-ci-investigate-threads.md) "Verify-also-on-stale-but-fresh-looking findings" — true at file-time, stale by review-resolution time. Same finding as Codex; same fix already in. Resolved no-op.
+
+**Two-reviewer convergence:** both Codex (chatgpt-codex-connector, P2 badge) and Copilot (copilot-pull-request-reviewer, P1 badge) independently identified the same path-depth bug. Independent convergence on a real finding — distinct from the suspect-by-default FP classes documented in the rule (e.g., table-double-pipe).
+
+## Verify
+
+- `bun tools/github/poll-pr-gate.ts 4435` after fixes: `unresolvedThreads: 0`, `requiredChecks: 4 inProgress + 3 pending` (fresh CI on `24ba9c2b`), `nextAction: wait-ci`
+- Fix verified by `ls` round-trip: 5-up variant → no file; 6-up variant → file exists (20221 bytes)
+- `grep -cF "](../../../../../.claude"` → 0 in both files (broken pattern cleared)
+- `grep -cF "](../../../../../../.claude"` → 6 in 1626Z + 4 in 1643Z (correct pattern in place)
+- This 1703Z shard authored with 6-up paths per the just-landed lesson — self-validates by example
+
+## Operational discipline carried forward
+
+Future tick shards in `docs/hygiene-history/ticks/YYYY/MM/DD/HHMMZ.md` (always 6 dirs deep):
+
+- Targets under `docs/*`: use **5 ups** (`../../../../../research/*`, etc.) — 1413Z's pattern is correct for this
+- Targets at repo root (`.claude/*`, `tools/*`, README.md, etc.): use **6 ups** (`../../../../../../.claude/rules/*`)
+- Sibling references within the same day: bare filename (`(1614Z.md)`) — no `../` needed
+
+This anchor is candidate for codification at `docs/hygiene-history/ticks/README.md` (the shard schema doc) to prevent recurrence; that's a future tick's work.
+
+## CronList
+
+Sentinel `b49c090e` (autonomous-loop, `* * * * *`) alive at tick start AND tick close. Catch-43 invariant holding through 5-tick session (1614Z + 1626Z + 1643Z + 1700Z + 1703Z).
+
+## Composes with
+
+- [`docs/hygiene-history/ticks/2026/05/20/1643Z.md`](https://github.com/Lucent-Financial-Group/Zeta/pull/4435) (the shard whose path-bug Codex flagged)
+- [`docs/hygiene-history/ticks/2026/05/20/1626Z.md`](1626Z.md) (the merged shard with the same bug; fixed via #4435 branch diff vs main)
+- [`docs/hygiene-history/ticks/2026/05/20/1700Z.md`](1700Z.md) (prior brief-ack tick; this tick activated when the gate signal changed)
+- [PR #4435](https://github.com/Lucent-Financial-Group/Zeta/pull/4435) (the PR this tick's investigation + fix landed on)
+- [`.claude/rules/blocked-green-ci-investigate-threads.md`](../../../../../../.claude/rules/blocked-green-ci-investigate-threads.md) (the canonical rule this tick exercised end-to-end: investigate thread first, verify-before-fix, stale-but-fresh-looking-finding handling)
+- [`.claude/rules/holding-without-named-dependency-is-standing-by-failure.md`](../../../../../../.claude/rules/holding-without-named-dependency-is-standing-by-failure.md) (named-dependency on CI completion → resolved by investigating threads; brief-ack #1 of cycle closed)
+
+## Visibility-stop
+
+Substrate landed: fix commit `24ba9c2b` on PR #4435 branch (10 path corrections across 1626Z + 1643Z); 2 review threads resolved (Codex + Copilot); this 1703Z shard documenting the investigate-and-fix cycle. PR #4435 gate now `unresolvedThreads: 0`, CI re-running on the fix commit, auto-merge armed. End.