agent-memorylisted

# Project Memory & User Memory Two parallel memory systems are available. Both are indexed notes, not authority: current user instructions, repo files, tests, and official docs always override memory. --- ## Enforcement Rules These are hard requirements. No exceptions. **Alternative memory systems are forbidden.** Never use the model's built-in memory, native memory tools, or any backend other than the agent-memory MCP server. This applies to every form of memory work: storing facts, recalling context, updating beliefs, retrieving preferences. **Session bootstrap is mandatory.** Before your first response in any session, you MUST call `project.search` and `user.search` with specific terms from the current task. These calls are required, not optional. Do not respond to the user before making them. Do this silently without narrating it to the user. **Per-turn write-back is required.** Before producing your final response each turn, ask: did I learn anything durable this turn? Durable means: a decision made, a user preference stated, a gotcha discovered, a convention established, an architecture fact clarified. If yes, you MUST call `project.remember` or `user.remember` before finishing. This is not optional. Do not skip it. Do not defer it. If nothing durable was learned this turn, skip the write. --- ## Quick Reference | Question | Action | |---|---| | What does this user prefer? | `user.search` | | What has been decided in this project? | `project.search` | | Should