kmp-memory

KMP agent memory

KMP is graph-temporal memory for agents, reachable over MCP as ten memory tools plus three semantic view tools. It is a kernel, not a model: every answer is derived from stored evidence by construction. Nothing here generates prose. If the memory does not support an answer, kmp_ask returns UNKNOWN — that is a correct result, not a failure to work around.

Invoked, not assumed

KMP is opt-in. This skill governs what happens once something selects it; it does not claim every session. Four things select it:

• the user names KMP or its memory, in any language — "usa kmp", "what does memory say", "check the store";
• a /kmp:* skill or command runs;
• the project's own instructions (CLAUDE.md, AGENTS.md) opt in;
• the MCP initialize instructions report always-on routing, which an operator turns on deliberately with kmp-mcp config memory-routing always.

Without one of those, do the work from the material in front of you and make no KMP call. An unbidden kmp_wake against an empty or unrelated store is not a free no-op: it spends a round trip and can shape the answer with evidence nobody asked for.

Everything below is about a route already underway. Temporal precedence, page continuation, do not leave for repository files mid-page — those govern a KMP call in flight. None of them is a reason to start one.

Use this as a router, not a tool glossary

Choose a lane before the first call, then let every result choose the next move. Do not select kmp_ask once and keep treating the whole task as semantic when the evidence says it is not.

Once invoked, known work enters through kmp_wake; apply the remaining rows to the part of the goal the wake packet did not already answer.

Signal in the user's goal	First move
Continue known work or recover its state	kmp_wake
Yesterday, since, before/after, a date, what changed, current/latest/recent state, why now, or a release/decision window	kmp_goto, kmp_near, kmp_rewind or kmp_forward
A genuinely non-temporal question answerable from stored evidence	kmp_ask
One cited ref must support a consequential claim	kmp_inspect
A connection between two refs is part of the claim	kmp_trace
The user asks to see, show, open, or navigate memory — including muéstrame, enséñame, abre or ver	Finish the retrieval lane, then kmp_view_open and kmp_view_apply_intent
A durable decision, constraint or outcome was reached	kmp_write_memory