Start with a read-only status check. In the autonomous runtime, call

MemoryStatus({})

. The service's documented safe endpoint is GET http://127.0.0.1:8771/status (also /health). Read queue state, recent retry errors, worker liveness, graph_index, and hipporag.state/last_error. Keep the individual MemoryRemember receipt because aggregate status does not identify whether that exact record is ready.

The receipt's pending status means accepted. The memory worker claims pending or retry jobs, marks them processing, chunks and embeds content on CPU, then records ready. On processing exceptions it stores an error and retry time; the worker retries with increasing delay capped at 300 seconds. A newer submission with the same record ID can supersede an older queued job. Inspect the receipt ID/job_id and source before interpreting later results.

CPU readiness and graph readiness are separate. Queue ready means document embeddings are available for vector retrieval. graph_index and HippoRAG state describe graph progress. If the graph is indexing or retrying, Recall may return backend cpu-vector; check that label and the accompanying graph state. Graph updates write a checkpoint and durable operation record before changing graph files. Startup can restore and replay interrupted work. Check reported last_error and retry_at; do not treat an empty recent-error list as proof that every older job succeeded.

For a versioned core, the source-backed read-only check reports cpu_ready and graph_ready per segment:

python3 tools/memory_core.py --manifest ~/.batbox/autonomous/memory-core-v1/manifest.json status --database ~/memory.db

That command reads the local database in read-only mode. For a queued core, preserve its receipt and distinguish incomplete_retryable from durably_queued; neither status asserts graph completion. See core workflow.

Safe GET observed 2026-10-25T16:20:52Z: queue ready=1090, graph_index=791, HippoRAG state=indexing, recent queue errors empty, and memory/sources/hipporag workers alive. These volatile counts are included as a dated checkpoint, not a health guarantee. Latest source commit f7a4de4 was reported as about to deploy; status does not identify the deployed build.

Sources checked 2026-10-25 UTC: /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/README.md; /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/store.py; /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/graph.py; /home/isnotreal/batbox-fixes/skill-discovery-20261025/tools/memory_core.py; live GET /status at 2026-10-25T16:20:52Z.