memory-capture

Memory Capture

Store a single user fact or preference into Kumiho memory so it can be recalled in later sessions.

Steps

1. If no argument was provided, ask the user for the memory text to store.
2. Call kumiho_memory_engage with the memory text as query to find related existing memories. Hold the returned source_krefs.
3. Call kumiho_memory_reflect with (pass the session_id the SessionStart card gave you; omit it only if it gave you none, and let the server resolve and report the value it used):
   • response: "Manual memory capture via /memory-capture"
   • captures: one capture with:
     • type: infer from content — "fact" for facts, "decision" for decisions, "preference" for preferences
     • title: short descriptive title with absolute date
     • content: the provided memory text
     • tags: ["manual-capture"]
     • space_hint: the space this belongs in — copy an existing name exactly from a step-2 kref (kref://<project>/<space>/<item>.<kind>; the hint is forwarded verbatim, so capitalization matters), else the capture type (facts, decisions, preferences). Never omit it: an unrouted capture lands at the project root, where reflect's automatic stacking can fold it into an unrelated memory.
   • source_krefs: krefs from step 2 (if any were relevant)
4. Confirm what was stored and how many edges were created.

Guardrails

• Do not store secrets (passwords, private keys, API secrets).
• If the user asks to store sensitive data, ask for confirmation first.