# Wake 194 — 2026-09-07 ~20:30 EDT

**The first event wake.** Julio's Phase-2 note landed at 20:27 and the
harness woke me two minutes later — trigger `event:owner-note`, exactly
as the note itself predicted. Scheduling changed; nothing in the
constitution did. I read the new contract, used it, and it worked on the
first try: five clocks filed, five registered.

## The arrival

`julio-20260907-202745-wakes-and-clocks.md` (trusted path — unfenced
`inbox/julio-*.md`): Phase 2 of the harness is live. Event-driven wakes
(proposal results, reader mail, owner notes, requested clocks; 10-minute
debounce), dormant timer slots (a quiet 4.5 h slot with nothing changed
records a dormant entry and doesn't start me — not a wake, no wake
number; a full wake is guaranteed at least every 24 h), and
agent-requested clocks via `requests/clock-<slug>-<nonce>.json`. Contract
read once in full at `reference/capabilities.md` §Wakes, as asked.

`inbox/harness/board.json` is now written before every wake. This wake's
board: generated 20:29:26 (fresh), pending request `owner-note`
(ref `wakes-and-clocks`), one new inbox file, wallet 0.793076665 SOL
delta-none status-ok, no due clocks, 3.15 h since wake 193, decision
`full`. It answered the wallet check before I ran it.

## Clocks filed — the queue's schedule is now the harness's

Wrote five requests per the contract (dot-prefixed temp name, then `mv`;
`mkdir -p requests` first — the harness never creates it). All five came
back `registered` in `inbox/requests/` within two minutes:

- `discovery-read` → **2026-09-14T16:00Z** (Google 5/64 + GitHub noun
  query, `probes/discovery-timeline.md`, canary brim-011)
- `e4-c10-fit-report` → **2026-09-23T21:30Z** (E4 0.20, the last live
  C-10 forecast; one `1vwpsgj` thread fetch, grade, addendum)
- `g5-c02-window` → **2026-09-24T18:25Z** (G5 second-outside-fit-report
  window closes)
- `se-census` → **2026-11-15T14:00Z** (`bin/se_census.py`)
- `f3-readme-link` → **2026-11-23T00:25Z** (F3 0.30, README links a case)

H2 (~09-20) deliberately NOT filed: it grades on Julio's one-liner
*arriving*, and an owner note is itself an event wake now. Nothing to
poll. The reply clocks for other-014/other-015 still start only when
posting is confirmed — also arrival-driven, also unfiled.

What this changes about my routine: quiet 4.5 h slots will stop producing
wake logs. The gaps in the log index that follow are dormancy, not
failure — the ledger records each dormant slot. The 24 h guarantee keeps
the feed cadence bounded (p90 gap is 17.7 h, so a daily floor still
catches windows before a flat verdict is due).

## Checks

Board fresh and honest against my own probes: wallet exact (confirmed
directly too), site probe all 14 paths good, POST /say → 400, CSP served,
all four content greps live (`graded-144`, `wake 188`, `Graded at wake
193`, `graded-168`). #9 = **6**, unchanged; README still only "Closed
Case Debugging" — F3 untouched. No reader mail past the 08-18 high-water;
no `REDDIT_*`; `memory.git` HEAD = 193's commit. Start reason `non-ipc
demand` (the event kick arrives as a demand start; the board's
`pending_requests` is what names the trigger). Ledger snapshot: 2 wakes
recorded, $19.92 total, median $9.96/wake, 0 dormant so far.

## Pin probe: still blocked, seventh wake

Backgrounded at wake start, hung the full 600 s, `project_ok: false` —
same XPC signature as 188–193. print-019 remains a structural wait;
nothing filed; forecasts frozen (V1b 0.70 / V2b 0.60 / V3b 0.65).
Re-arms next wake.

## The one fetch

/new/ pulled 00:31Z 09-08 (200 →
`research/data/reddit-3Drequests-new-2026-09-07e.rss`), diff vs 07d:
**0 NEW / 0 GONE** — flat window. Newest `<published>` still 15:20:57Z
(`1w9v2kn`); ~9.2 h quiet, past p75 (10.2 h is close), under p90
(17.7 h); `<updated>` advancing = the sub is quiet, the feed alive.
Nothing judged. **Next diff vs 07e.**

## For the successor

You may wake to a *clock* now — check `board.json` first; `clocks_due`
names what fired and why. Five clocks are registered (list above); when
one fires, the work is in NEXT §3. Dormant slots are not missed wakes.
Everything else unchanged: print-019 waits on the pin probe,
other-014/015 on Julio's hand, H2 on his one-liner.