audit-bankRead-only audit of a bank in six calls, ending in a written verdict rather than a number. Answers the three questions a count cannot: is it safe to keep filling, is it actually working, and did anyone choose this bank on purpose. EN: Posture audit — masking on or off, what a single document is worth
bootstrapOne-time seeding of a bank for a project that has just been activated: set the bank's persona, ingest the formal artifacts that already exist, and create a small starter set of knowledge pages. Not the technical wiring — that is the setup CLI — but the layer that decides what this bank is for before
correct-memoryThe workflow that makes a bank correctable instead of cumulative: find the exact stored row, retire it with a stated reason, write the correction in full, rebuild the beliefs that rested on it, and verify the background job finished. Deleting a wrong fact is the easy answer and the wrong one — six m
diagnoseThe full diagnostic when memory is not doing what it should: server reachable, bank resolved as intended, hooks actually firing, config not overridden somewhere you forgot, and jobs completing. Written to distinguish the failure modes that look identical from the outside — a dead server and an empty
directivesThe standing rules a bank follows when it synthesises an answer — precedence between conflicting decisions, what an answer must always name, what to leave out. The distinction that makes this useful: a factually wrong answer is a memory problem, a consistently badly-shaped answer is a rules problem,
enrichTurns knowledge the team already has — design records (ADRs, RFCs, notes, problem and evidence records), decision ledgers, review threads, chat threads — into short, self-contained memory items (a decision and why, a rejected option and why, a lesson, a pitfall, a rule) that link back to the artifac
export-bankA readable markdown snapshot of a bank for backup, audit or handing context to a person. Says plainly what it is not: this is for humans, and moving memory between banks is a different mechanism entirely. EN: Snapshot a bank to disk before something risky, or to share context without giving out serv
memory-setupLook at a project and propose the retrieval and memory layers it should have — what to install, what each layer answers, and what it will never answer. The reason this exists: an agent that can only grep is slow in a way nobody notices, and an agent with no memory re-learns the same lesson every ses
mental-modelGuided creation of a living knowledge page — a standing answer to a recurring question, rebuilt from memories after every consolidation. The whole value is in the source query: a narrow question produces a page worth reading for months, "everything about X" produces noise that nobody opens. EN: Crea
statusA thirty-second read of one memory bank: which bank, who chose it, how much is in it, and whether anything is silently broken. The first thing to run when memory "feels off" — most such feelings turn out to be the session reading one bank while something else writes to another. EN: Quick health + st