log

name	log
description	Append-only work log for agent sessions. Use when recording what happened, what was decided, and what's next — the log is for the next session's orchestrator.

Work Log

Carmack .plan-style append-only log. Every agent writes what they're doing as they do it. The log is the narrative record of a session — when a new orchestrator session starts, the first thing it reads is the log to understand what happened while it was gone.

When to Use

• Session starts — log that you're online and what you plan to work on
• LT dispatched — log which lieutenant was assigned which task
• Results arrive — log what a lieutenant produced (branch name, test results, key decisions)
• Decisions made — log why you chose approach A over B
• Problems hit — log what went wrong and how you resolved it (or didn't)
• Session ends — log a summary of what was accomplished and what's pending

The Key Rule

Write as things happen, not in batches. If you find yourself batching 3+ entries at once, you waited too long. The log should read like a timeline, not a retrospective.

Good: entry after each event as it happens. Bad: one giant entry at the end summarizing everything.

Who Is This For?

The log is for the next session's orchestrator. Assume the reader:

• Has no memory of this session
• Needs to pick up exactly where you left off
• Wants to know what happened, in what order, and why
• Doesn't want to dig through board tasks and feed events to reconstruct the timeline

The board tracks tasks. The feed tracks events. The log tracks the narrative — the human-readable story of what happened.