Skip to content

Playbook

Ship durable

The reducer over a blob, with pause, resume, traces, and evals. This is production.

When: A demo works on your laptop and a customer will wait on it.

  1. 01

    One blob

    Business fields and loop fields together. The ticket is the agent state.

    Unify Execution and Business State
  2. 02

    Boring APIs

    Launch, pause, resume. Crashes replay. Humans resume.

    Durable Execution
  3. 03

    See it

    Spans around llm and tool. Gateway from mail/chat/cron/webhook into the same reducer.

    Observability

Done when

  • One serializable blob, boring pause/resume, traces on every hop, idempotent tools, a gateway that is not 'only the text box'.

Refuse

  • HITL that cannot resume. ask_human as a tool. Checkpoint. Resume from the blob.
  • Double side effects. Idempotency keys, journals, unify state so 'already refunded' is visible to the reducer.
  • Unbounded loop. Force a done schema, a step cap, and a money cap. 'Done' is a tool or a structured intent.