A Directive is a standing rule for later work. A Finding records an observation and its evidence. Saving them separately lets a later session tell what it should do from what someone previously found.
Complete project memory and relations and types. You need a working harness connection to loom_demo, a Coding-domain practice store, and the project scope durmem practice notebook. Scope is the name attached to memory, not just the folder you opened; the concepts guide explains the model.
Use only harmless practice facts. The prompts below go to your agent, not a shell. Example results describe what to check, not output the agent may invent. Nothing in this exercise authorizes a push, paid service, or repository change.
loom_demo for this session and project scope durmem practice notebook. Confirm the selection without displaying credentials or changing persistent store defaults. Use the author attribution established in the project-memory tutorial.Ask the agent to retrieve that Directive from durmem. A successful read returns the stored rule and reference, not merely a paraphrase of the preceding prompt. An identical identity is reused; rewording it can create a distinct fact.
loom_demo in this project. If a proposed change needs a paid service, what must happen first? Do not contact a service or spend anything.The agent should explain that it needs your approval. A remembered rule is not permission to perform the action it mentions.
A hook runs at a harness lifecycle event. A trigger associates a fact with an event and matching action text. Hooks can supply advisory context; the agent still has to judge and follow the rule. Previewing a trigger lookup does not prove a real hook ran. Tutorial 06 covers that separate check.
Keep the ordinary practice Directive and Finding above in Project("durmem practice notebook"). For this hook example, use the actual repository scope from Tutorial 03: Project("palmerpenguins"). First retrieve a harmless demonstration Directive in that scope. If none exists, create and verify one there, such as a reminder to preview Git commands without executing them. Do not reuse the notebook's general approval Directive or broaden the lookup beyond this project.
Project("palmerpenguins"), identify or prepare a harmless demonstration Directive that says to preview Git push commands, not execute them. Verify its actual reference and scope. Associate that Directive with upcoming git push actions in this project using the installed durmem skills, and save and verify the trigger. Then ask what would surface for the simulated text git push origin loom_demo. This is a preview only: do not run the push or contact a remote.Check that the preview identifies the actual demonstration Directive reference and Project("palmerpenguins") scope. If nothing matches, inspect the saved trigger, event, literal action text, and scope. Do not try a real push to make the example work. Tutorial 06's priming and intent examples keep their notebook scope; its trigger-preview exercise should reuse this repository-scoped demonstration Directive.
An Environment fact can separately explain a verified condition, such as a repository being a disposable checkout. Do not invent a claim that a real upstream is read-only or that your credentials cannot push to it.
loom_demo. Include the actual observation date, its fact reference, and project scope. Do not claim that a missing scope chain was created unless you observed that happening. On a rerun, retrieve the existing observation before deciding whether anything is new.Read the Finding back. Its content should explain what was checked and when. An old observation keeps its original author and date; finding it again is not the same as performing the original work today.
You should be able to retrieve a current Directive and an evidence-bearing Finding in the same practice scope, and preview the reminder without executing an action. If duplicate-looking facts appear, compare identities and meaning before asking the agent to reconcile the exact records; do not delete at random.
Next, plan with past decisions, or take the optional proactive-memory exercise.