project-memory

You can maintain repo-visible project memory by organizing durable notes under docs/project_notes, which aligns memory entries with approved specs and plans without altering authoritative workflow artifacts.

To set up project memory files like bugs.md and decisions.md, apply memory templates during setup or repair to ensure consistent memos, backlinks, and alignment with runtime state.

Memory boundaries are enforced by running repo-safety checks before writing to protected paths, ensuring documentation updates align with approved specs and do not overwrite authoritative workflow artifacts.

Yes, you can repair existing key_facts.md and issues.md files by applying the provided memory templates and references to restructure the content and restore durable, backlinked project memory.

If project notes are misaligned, run repo-safety checks to enforce authority boundaries and update the memory entries to link back to the approved specs and plans.

You need to update project memory files during setup or repair phases when memory boundaries must be maintained, ensuring durable notes reflect the current runtime state and approved plans.