Distilled patterns, not prompts.

Playbooks are the reusable workflows hiding inside the Field Reports library — written up as step-by-step guides with the failure modes included. The first five are in production now; until each guide ships, its library trail is open below.

The read-only-first agent

Pattern · from the library

Start every agent in inspect-only mode. Write tools unlock for one approved change, then verification — and rollback — close the loop. The guardrail pattern that recurs across the strongest field reports. See the cases ↗

The 6 AM chief of staff

Pattern · from the library

A scheduled brief that reads calendar, inbox, and goals before you wake — with a hard rule that it drafts but never sends. Dozens of practitioners run some version of this; the library documents the variants. See the cases ↗

Plan → build → review → verify

Pattern · from the library

The coding workflow that keeps surviving contact with real codebases: one agent plans, another builds, a third — which did not write the code — reviews, and a verifier blocks a false “done.” See the cases ↗

Let the model read, not decide

Pattern · from the library

Models extract; deterministic code decides. The accounts-payable build that routes by confidence score instead of letting the model approve payments is the template. See the cases ↗

Count the rescues

Measurement · honesty series

Split agent-only success from human-rescued runs, and log every rescue as an incident. The measurement habit that separates operating an agent from botsitting one. See the cases ↗

Get the week in agents, in your inbox.

One email a week: the new field reports worth your time, the leaderboard moves that matter, and the failures everyone else leaves out. Written by a practitioner, checked before it sends.

Signup currently opens your email app with a pre-addressed subscribe note — one tap, no account, no tracking pixels. Prefer to write directly? Email [email protected] with “subscribe” in the subject.