The scoping unit for all memory — usually one repository or working directory, identified by a slug.
Capture
A raw record of completed work (memory remember, memory capture, watchers). Input to curation, never served directly.
Curation
The pipeline that distills captures into canonical memories: extracts durable claims, drops noise, deduplicates, and decides replacements.
Memory (canonical)
A short, citable durable fact with a summary, canonical text, type, tags, confidence, importance, and sources. Immutable per version; superseded rather than edited.
Memory type
One of 17 classifications (decision, convention, incident, insight, …) that sharpen search and curation. See memory types.
Query
Hybrid retrieval (lexical + semantic + graph) over canonical memories, synthesized into a cited answer — or an honest refusal.
Resume
A briefing built from checkpoints, recent activity, and memories that gets you back into flow after time away.
Where a memory came from: files, commits, notes, or other memories. Verified against the filesystem; missing sources decay a memory's rank.
Confidence
How likely a memory's claim is true (0–1). Set at curation, raised by re-observation, decayed by failed validation. Low-confidence memories are never stated as answers.
Importance
How much a memory matters to the project (1–5); a ranking weight.
Citation
The specific memories an answer drew from, numbered in the response. Citations feed reinforcement.
insufficient_evidence
The query response flag meaning "the evidence is too weak to answer" — the design prefers refusing over fabricating.
Replacement proposal
A queued, human-reviewed suggestion that a new memory supersede an old one. Nothing durable changes without approval.
Review queue
Where all proposals (replacements, corrections, merges, insights) wait for human approve/reject — in the TUI Review tab, web UI, or memory review.
A per-project daemon that observes repository activity and feeds captures.
Loop
A built-in background automation (hygiene, CI triage, context packs, consolidation, evals…) that produces reports and proposals, never silent mutations.
Skill
Repo-local instructions + helpers that teach a coding agent (Claude Code, Codex) to use Memory Layer well.
MCP
The built-in Model Context Protocol server exposing read-first memory tools to any MCP client.
Bundle
A shareable, privacy-safe export of a project's memories (memory bundle).
Checkpoint
A saved execution state for plan-backed work (memory checkpoint), used by resume and plan verification.
Eval / gate
The measurement harness: paired no-memory vs full-memory runs over reviewed suites, with release gates enforcing floors.
