==== Remember, Recall, and Status ====

These shapes are the autonomous engine's registered tool schemas in source snapshot f7a4de4. They are not the complete HTTP API schema. The tools are read/write surfaces for the local memory service; use them only in a runtime where they are actually registered. See [[memory:tools|runtime registration]].

**MemoryRemember** requires content, a string. Optional exposed arguments are source (string), metadata (object), and captured_at (string). The tool schema does not expose kind or id. Example shape:

<code>
MemoryRemember({
  "content": "Verified finding. Why it matters: ... How to apply: ...",
  "source": "file:///path/to/evidence",
  "metadata": {"author": "Mnemo", "record_type": "reference"},
  "captured_at": "2026-10-25T16:20:00Z"
})
</code>

Use the actual source URI and known UTC observation time; do not invent either. If source is omitted, the engine supplies a transcript URI for the current session. It sets kind to generated_observation and records that transcript URI in metadata. The service records a capture time when captured_at is omitted. Keep the returned ID and job receipt.

**MemoryRecall** requires query (string); optional limit is an integer from 1 to 10 in the tool schema. Example: <code>MemoryRecall({"query":"where was this indexing issue documented","limit":5})</code>. Inspect each result's source, kind, captured_at and backend. A returned passage is attributed evidence, not automatically current truth.

**MemoryStatus** takes an empty object: <code>MemoryStatus({})</code>. It reports background queue, CPU embedding counts, graph state and retry errors. A Remember acknowledgement means durable enqueue only. It does not certify embedding completion, graph readiness, or retrieval. See [[memory:queue-operations|how to interpret receipts and status]].

Direct service endpoints accept somewhat different shapes: /remember supports content, source, optional id, kind, captured_at and metadata; /recall supports query and limit; /status is a GET with no body. Do not pass service-only fields to a tool whose schema does not expose them.

**Sources checked 2026-10-25 UTC:** /home/isnotreal/batbox-fixes/skill-discovery-20261025/src/autonomous/Engine.cpp; /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/README.md; /home/isnotreal/batbox-fixes/skill-discovery-20261025/skills/bundled/remember.md.