Hand work from one agent — or one timezone — to another

The pain

Async work breaks at the boundary. The next agent (or the same agent, next morning) has to reconstruct scope, rationale, and remaining risk from commit messages, scattered notes, and a vague Slack history. Most of the resumed session is spent re-reading instead of working.

The brainclaw move

1. Snapshot state as a handoff, not as a memo. bclaw_create(entity='handoff', data=...) writes an immutable snapshot tied to the active plan, the git diff since session start, and the open claims. The next agent gets the full state in one read.
2. Spell out pre/post-conditions. A handoff includes “before resuming, check that X is still true” and “after this work is done, the plan should reach state Y”. The next agent verifies the entry condition before re-touching code — no surprise resets.
3. Capture inline observations. bclaw_write_note records the small “I noticed Z while doing Y” details that don’t deserve a decision but matter when resuming. Quick capture, no friction.
4. Resume with the delta, not the full repo. bclaw_context(kind='delta', since=<previous_session_id>) shows what changed since the previous session — instead of re-reading the whole project state every morning.

What changes

The boundary between sessions stops being a context-loss zone. A solo developer resuming next morning sees what they themselves left unfinished. A teammate picking up an unfinished feature sees the same.

Where it shines hardest

Distributed teams. When the agent doing the handoff and the agent picking it up are in different timezones, asynchronous coordination is the workflow — and the cost of a bad handoff is one full timezone of lag.