Memory, tasks, and work receipts¶
Memory¶
Use note for durable facts, constraints, hypotheses, and open topics. Use
decision only for an explicitly accepted decision and include its rationale.
Tasks¶
A task is a bounded piece of requested work. Its status and handoff fields are the current operational state. Updates use an integer version for optimistic concurrency control.
Work receipts¶
A receipt answers: which harness/session worked, what it completed, which Git state it used, what tests ran, and what should happen next. It is evidence from one execution, not a substitute for the task description.
Classification rule¶
Keep these categories separate:
- Open Topic: unresolved discussion or alternatives;
- Proposal: suggested solution not yet accepted;
- Decision: explicitly accepted direction;
- Task: work requested within a defined scope.