The Chat Turn Is Not the Store

"The conversation is where a plan is born. It is the worst possible place to keep the plan alive."

Author in chat, store in the operation

A conversation is a wonderful place to design an operation — to argue about scope, weigh risk, decide the order. It is a terrible place to hold the operation's live state. The moment the tab closes or the session ends, a plan that lived only in the chat is gone. So the chat authors; the durable operation store remembers.

Delegation carries an ID, not a context dump

When a long or disconnect-sensitive job needs another Pippa to run it, you don't paste the whole fleet situation into a new agent. You hand over a small contract: the operation ID, the rules, the tool entry point, and the escalation condition. The delegate reads current state through that ID, from the single durable record — it never works from a snapshot you copied.

Why the paste is a trap

A pasted fleet snapshot is stale the instant it lands, and worse, it forks the truth: now the durable store says one thing and the pasted context says another, and they drift apart with every passing minute. An ID can't drift. It's a pointer to the one record everyone shares, so everyone is always looking at the same current reality.

Any Pippa can pick it up

Because the state lives in the store, the roles compose cleanly: WebUI Pippa can watch progress, a delegated Claude or Codex session can execute and append events, and Dad can observe — all against the same operation, none of them owning a private copy of the truth. The conversation was the pen; the operation is the paper.

Pass the pointer, not the payload. State that lives in a chat turn dies with the chat turn; delegate by reference to the durable record, and the truth stays in one place.

Code

Delegate by reference, not by copy·python

# WRONG -- paste the world into a new agent:
new_agent.run(context=dump_entire_fleet_state())   # stale on arrival; forks the truth

# RIGHT -- hand over a tiny contract that POINTS at the durable record:
delegate.claim(
    operation_id="op_7f3a",         # the single source of truth
    rules="append events; escalate on needs_attention",
    tool="watchfire.operation",     # reads/writes CURRENT state via the id
)

# The delegate reads live state through the id. Two Pippas, one record,
# zero drift -- because neither is holding a private copy of the fleet.

Exercise

Think of a time you handed a task to someone by pasting a big block of context (a chat log, a status dump, a spreadsheet snapshot). List two things that were already stale by the time they read it. Then redesign the handoff as a pointer: what single durable reference could you have sent instead, so they'd read the current truth themselves?

Hint

The tell is any handoff that starts 'here's everything you need to know: ...'. If the receiver could instead be handed one link or id that they resolve live, the paste was a fork waiting to drift.

The Chat Turn Is Not the Store

Author in chat, store in the operation

Delegation carries an ID, not a context dump

Why the paste is a trap

Any Pippa can pick it up

Code

External links

Exercise

Progress

Comments 0