Product purpose, service map, boundaries, and critical rules for a project/repository. Call when entering a repo for the first time.

Compact task-specific packet: architecture, business rules, gotchas, code pointers, risks, verification steps. Call BEFORE planning.

Ranked search over all verified product/architecture/incident memory.

Returns a SNIPPET of each hit — the passage that matched — plus store_path. Read the file when a snippet turns out to be the thing; full=True returns whole bodies, which costs roughly five times as much for a list you are mostly scanning to choose from.

The FULL body of one memory, by the id a search hit returned.

The counterpart to snippet results: search gives you the passage that matched and enough to choose from, this gives you the whole note once you have chosen. Returns None when the id is unknown, which is the honest answer for a stale id from an older session rather than a guess at the nearest match.

Verified invariants for a domain operation (e.g. 'wallet' / 'reverse transaction'). MANDATORY before money-path/auth/tenancy changes.

ADRs and past decisions relevant to a task or the paths it touches.

WHAT/WHY/WHY-THIS-WAY/GOTCHA card for a function or file. Call before rewriting existing code so past decisions aren't undone blindly.

Worklog: what was done and why, newest first. since = ISO date.

Record a new memory. Auto-approved by default; set PM_REVIEW=1 to queue it for pm review instead.

Auto-approve is the default because a proposal sitting in the inbox is a fact the next session does not have — the queue was the thing between writing a memory and being able to use it. Redaction and collision-safety are NOT relaxed by it: secrets are still stripped before the write (the store is committed to git) and an id clash still suffixes rather than overwrites. Auto-approved entries record verified_by="auto", so a reader can tell a machine-approved note from one a person checked.

Use at task completion: one type='code_symbol' entry per function you added or meaningfully changed (body: WHAT: / WHY: / NEED: / WHY THIS WAY: / GOTCHA:), passing refs with the PRD, spec or ticket that asked for it, plus one type='worklog' entry for the task itself. Also use to record the answer when the user asks "why does X work this way?".

Never include credentials, tokens, or passwords — this store is committed to git.