A Decision records a settled direction, including an approach deliberately rejected. A Roadmap records intended work. Reading both before planning helps an agent avoid proposing work that conflicts with an earlier choice.
Complete project memory and directives and findings. Custom types and hooks are not prerequisites. Use store loom_demo and project durmem practice notebook. The palmerpenguins clone from Tutorial 00 is evidence only: these records belong to the practice project, not to palmerpenguins. This exercise writes practice memory but makes no repository or network changes.
loom_demo and project scope durmem practice notebook. Confirm the actual connection and scope without changing persistent defaults or displaying credentials. Load the installed loom-coding skill.durmem practice notebook, not palmerpenguins. Do not implement them.Ask for each actual record's reference and status. A rerun may find work already completed; it should not reopen it or invent three new open items. These are planning records, not Kanban tasks or authorization to start workers.
The Decision explains the design boundary. A Directive, as used in Tutorial 05, is instead a standing behavioral rule for doing work within such boundaries.
The agent should cite the stored Decision and explain the conflict before drafting the proposed change. Whether a hook supplied context or the agent read it explicitly, the evidence is the actual current record, not a convenient memory of the preceding chat turn.
Check that the plan retains bundled data and separates proposed work from work already done. A plan is not a delivery receipt. Practice verifying and closing work in audit and maintenance only when there is actual evidence of completion.
A useful result names the current Decision, explains why the network proposal conflicts, and produces a compatible plan without taking action. If the agent misses the Decision, verify store, project scope and current status before resaving it. A missing record and a record never read are different failures.
Changing direction requires an explicit authorized decision and reconciliation of the old record; a hypothetical planning request is not that approval.
Optional advanced track: when a repeatable calculation or read pattern emerges, the rule-promotion exercise shows how to preserve its method.