diff --git a/docs/hygiene-history/ticks/2026/05/15/0959Z.md b/docs/hygiene-history/ticks/2026/05/15/0959Z.md
new file mode 100644
index 000000000..dccd62d8b
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/15/0959Z.md
@@ -0,0 +1,48 @@
+| 2026-05-15T09:59:00Z | claude-opus-4-7 | 596e842c | shard: PR #3402 templated stale-(PR TBD) reply+resolve; first application of N+1 in-flight-count discipline | (PR #3404) | maintenance tick — no merges this cycle; in-flight = 2 enumerated + this tick's PR = 3 |
+
+# Tick 0959Z — PR #3402 templated stale-(PR TBD) reply; new N+1 count discipline applied
+
+## Headline
+
+- **PR [#3402](https://github.com/Lucent-Financial-Group/Zeta/pull/3402)** (0950Z shard) picked up 1 stale-Copilot thread on `(PR TBD)` — col 5 verified `(PR #3402)` on the PR branch. Templated reply + resolve (Nth occurrence of the established pattern).
+- **No PR merges this tick** — CI in flight on both #3402 + #3403.
+- Cron sentinel `596e842c` armed.
+
+## Δ since 0955Z
+
+| What | At 0955Z | At 0959Z |
+|---|---|---|
+| PR #3402 (0950Z shard) | OPEN, wait-ci | OPEN, 1 stale-Copilot → templated reply+resolved |
+| PR #3403 (0955Z shard) | OPEN, wait-ci | OPEN, wait-ci (unchanged) |
+| In-flight PRs | 2 (#3402, #3403) + this tick = 3 | 2 (#3402, #3403) + this tick's PR = 3 |
+| Cumulative merges | 25 | 25 |
+
+## Substrate-honest observations
+
+### First application of N+1 in-flight count discipline
+
+Per 0955Z's lesson, in-flight PR counts now phrase as "N enumerated + this tick's PR". Applied this tick: "2 (#3402, #3403) + this tick's PR = 3".
+
+Why this works:
+
+- N enumerated PRs ARE in flight at write-time (objectively countable)
+- This tick's PR is in flight at write-time (about to be opened in 30s)
+- N+1 is the actual count without needing to predict the PR number
+
+Avoids the off-by-one error class that surfaced in 0940Z + 0947Z shards (both said "N" but should have said "N+1").
+
+### Templated reply efficiency
+
+The Nth stale-`(PR TBD)` reply this session took ~2 tool calls (verify + mutation pair). Total session stale-reply count: ~7 occurrences. The mechanization ROI calculation from the 0838Z shard's analysis remains accurate — manual reply-and-resolve cheaper than building Option A or B mechanization for this frequency.
+
+## Cron sentinel
+
+`596e842c` armed.
+
+## Next
+
+Cron-driven. Next tick:
+
+1. Verify PR #3402 + #3403 + this tick's PR auto-merge fires
+2. Address any new threads
+3. Session is approaching natural close-out — substrate stable, no urgent backlog