Constraints

• Memory operations must work without network access by default.
• Skill, plugin, and CLI installation or update flows may use network distribution.
• Must store project memory as local Markdown files under docs/, with docs/memory/ as the default managed directory.
• Must not introduce RAG, embeddings, vector databases, or cloud memory for the MVP unless explicitly requested.
• Must be reusable across Codex, Claude Code, Gemini, and other agents.
• Must keep startup context small.
• Must make memory easy to review, diff, commit, and roll back.
• Must keep default project initialization to six task-memory files plus the non-routed subjects.md protocol registry.
• Must keep workflow-specific rules out of the core protocol.
• Must keep Skill instructions concise and operational; detailed non-goals belong in README and references.
• Hard and purge forgetting must remove prior topic-bearing soft tombstones from managed memory.
• Forget apply must refuse before writing when a topic appears in a non-removable body or preamble that requires semantic rewriting.
• CLI inbox compaction must not infer semantic destinations from keywords; an Agent or user decides what memory means.
• Safe repair and optional enablement must not overwrite curated memory.
• Multi-file commands must precompute and validate mutation plans, then report any partial completion explicitly.
• Repair and migration must never downgrade a newer project protocol or accept an unparseable protocol version.
• Destructive bullet cleanup must operate on complete column-zero top-level units, including their nested and continuation content.