memory-custodianlisted

# MemoryCustodian MemoryCustodian stores durable project memory as local, human-readable Markdown files under `docs/memory/`. Use it to: - load the minimum relevant project memory for the current task - update project memory after meaningful decisions - compact unprocessed memory candidates - forget or tombstone memory the user no longer wants used - keep platform entry files such as `AGENTS.md`, `CLAUDE.md`, and `GEMINI.md` short ## Hard Gate In a project that contains MemoryCustodian memory, do not start substantial planning, implementation, debugging, or review until startup loading is complete: 1. Read `manifest.md` if present. If the memory directory exists but the file does not, stop as described below. 2. Read `brief.md` before substantial work. 3. Identify the task type. 4. Load only files allowed by the manifest and matched by the current task. 5. Respect `do-not-use.md` and tombstones before proposing plans or implementations. If no memory directory exists, continue normally and offer initialization only when useful. If the memory directory exists but `manifest.md` is missing, stop memory loading and report an incomplete or corrupted setup. Do not infer routes; restore the manifest, migrate, or carefully reinitialize the project first. ## Core Workflow 1. Locate memory at `docs/memory/manifest.md`, or another project-declared memory directory under `docs/`. 2. Read `manifest.md`; it is the sole authority for runtime task-to-file routing. 3. Read `brief.md` b