Room 01 · Idea Capture
Yesod notes are the factory's durable inbox.
A note preserves captured intent and keeps its identity as planning, execution, and outcomes accumulate around it.
The first durable object
A Yesod note is a unit of captured intent. It can begin as a feature request, a bug report, or a usage note, but it is more than the original paragraph: it has an identity, provenance, metadata, comments, and a status that can change without losing the history that came before.
That identity is the thread through the factory. Plans and Beads can be attached to it. Runs can act on it. Outcomes can point back to it. The deliverable changes; the reason the work began remains findable.
Capture-only lifecycle
Ordinary capture makes no promise that work starts immediately. The note waits in the backlog until a human or an authorized process decides it deserves factory time.
That separation is deliberate. Intake should be cheap and trustworthy enough that you record an idea instead of keeping it in your head, while dispatch remains an explicit decision.
Automatic lifecycle
An --auto-plan request authorizes the factory to move beyond capture. The note can proceed through planning, estimation, dispatch, and verification without requiring a person to push it across every boundary.
Automatic does not mean invisible or endless. The work should reach a completed outcome or become explicitly blocked with the reason still attached to the record.
What a note does not replace
The note is the durable “why” and lifecycle record. A Bead tree is the executable decomposition of one planned feature. They stay connected because they answer different questions:
- Note: Why does this work exist, and what has happened to it?
- Beads: What bounded units must be completed, and in what order?
Next: see how the Planning Agent turns a note into a build plan.