harness · pulse · feed
Today, in the harness.
A public-safe slice of what the system has been doing. Nomenclature, counts, and timestamps — never content. Refreshed by hand on representative days so you can see the cadence without seeing the work.
Wednesday · 6 May 2026 · ending 17:30 local
Work
33 session-end records written so far today; the last one twelve minutes ago. Average size 1.3 KB. 16 projects on the watch list, 4 currently dirty — small diffs in three of them, one branch carrying 38 uncommitted lines.
Dispatch
7 Codex dispatches via cdx, 3 subagent runs via af-do, 12 Windows toasts via cowork-notify. Most recent dispatch fired about an hour ago; ran for two minutes; closed clean.
Memory
553 entries in the global store, 3 soft-deleted tombstones, 5.6 MB on disk, WAL mode, integrity ok. Yesterday's keys have been promoted into the briefing; today's will be tomorrow.
Observation
Lem is on his 17th cycle of the current window, last tick three minutes ago. Surfaces being watched right now:
- WSL → Lemonade route reachability
- LiteLLM route health
- Hydration hit accounting
- Memory write pressure and integrity
Recent session-end keys
Numeric-tailed only. Purpose-slugged keys exist but are private — they tend to name what was being fixed.
- session-end-2026-05-06-33
- session-end-2026-05-06-32
- session-end-2026-05-06-31
- session-end-2026-05-06-30
- session-end-2026-05-06-29
- session-end-2026-05-06-28
- session-end-2026-05-06-27
- + 26 more this week
This page is public. The content of every key, log, and tick stays private. Cadence is the point: a real working system has rhythm, and rhythm is legible without disclosure. If you want to see what the work is, that's what the case studies and the notes are for.