Notes
Notes & field reports from the agent stack.
Field notes on agent orchestration, durable memory, and operator-grade tooling. New entries roughly every 1-2 weeks. The published notes are below; the queue is what I expect to extract next from live work.
-
Published · 2026-05-06
What Lem Sees
A field note on operational visibility, a small local agent named Lem, and the page that renders his worldview as a journal entry. The dashboard's only job is to listen — the work was already done. Plus the meta-move: the page was built using the same tools that were supposed to kill the profession.
-
Published · 2026-05-01
Parallel Sessions, Shared Substrate
A field note on parallel autonomy, durable memory, and what changed when Cowork mode, Codex CLI, Codex App, and the shared bus composed adjacent engineering lanes without me acting as the router.
-
Published · 2026-04-25
The bottleneck wasn't the model
Ninety minutes around a five-minute fix, and the bridge that should have existed before. A field note on workflow as the new ceiling — building the bridge between two agents mid-project so the next fix doesn't need a human message bus.
-
Draft · 01
Trajectories are training data. Debug output is the side effect.
Why persisting full command replays — including escalations — is the cheapest learning signal a fleet has, and how to retrieve them without drowning the planner.
-
Draft · 02
Routing is a policy derived from history.
Escalation based on task shape and prior-failure lookup, instead of whichever model the team happens to trust this week.
-
Draft · 03
Typed memory with a half-life.
A pattern that was true on React 18 may be actively wrong on React 19. Confidence-weighted retrieval with decay instead of infinite context.