mnemo-amp 0.5.29

AMP / memorywire JSON-Schema 2020-12 interop adapter (5 ops × 4 memory types) over a MnemoEngine.
docs.rs failed to build mnemo-amp-0.5.29
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: mnemo-amp-0.5.27

mnemo-amp

AMP / memorywire interop adapter for mnemo.

AMP models an agent's memory surface as 5 operations (remember / recall / forget / merge / expire) over 4 memory types (episodic / semantic / procedural / working), carried in a self-describing JSON envelope validated against a JSON-Schema 2020-12 document. This crate implements that wire format as a [MemoryStore]-conformant surface over a real MnemoEngine, so any AMP-speaking client can drive mnemo's embedded DuckDB backend unchanged.

What maps where

AMP op Engine call
remember MnemoEngine::remember
recall MnemoEngine::recall (top-k, default 5)
forget MnemoEngine::forget
merge thin composition: remember (consolidated record) + forget (Consolidate) — not the branch-timeline engine.merge
expire thin composition: set expires_at + run_ttl_sweep — there is no engine.expire

Pieces

  • [wire] — the AMP envelope, result, and JSON-Schema 2020-12.
  • [store] — the [MemoryStore] trait + [MnemoAmpStore] engine impl.
  • [router] — the fan-out [AmpRouter] + RRF / max fusion.
  • [approval] — the HITL diff-and-approve hook ([ApprovalHook]), which gates long-term writes and records approvals in mnemo's hash-chained audit log.

Honest scope

This is a wire-format + surface adapter. AMP transport binding (HTTP / stdio framing, .well-known schema discovery) is left to the embedding application; the crate provides the schema document and the typed envelope so that binding is mechanical.