Memory System
This skill's persistence layer for project-local memory, at <project_root>/memories/, via scripts/memory <cmd> (backed by references/memory_tool, the deterministic source of truth for this layer — never modify its output or reimplement it). It doesn't assume the host has no other memory mechanism; if one exists, treat this as an additional, file-based layer alongside it. Stdout is JSON; re-read to confirm on-disk state.
Since 1.1.0, init also creates a hidden <project_root>/.memsys-db (SQLite + FTS5, journal_mode=DELETE, one file, no -wal/-shm) — the regenerable index and search plane. Markdown stays the source of truth.
Start here, in order:
- references/protocol.md — the full ingest → retrieve → reason → reflect → execute → package workflow, plus commands and quick-start invocations.
- references/layout.md — store layout and what to load for a given query.
- references/when-to-save.md — classify: skill vs. index vs. topic vs. reject, and skills-vs-memory routing.
- references/constitution.md — hard rules (never skip secret-scan, never exceed 200 lines, never write outside
memories/, never enumerate via bash, never WAL the ledger). - references/memsys-db.md — the
.memsys-dbledger contract: schema,search/reindex/forget, and why the DB never outranks markdown. - references/examples.md — worked examples: happy path, secret rejection, overwrite recovery.
Verify the install with scripts/memory selftest before first use.