Skip to content
autonym.dev
ContentsHide contents

Adoption records

AI agent memory interoperability

spec 1.0-draft-1
Field Value
Status Track and align shapes
Version pinned Community Group charter 1.0 (adopted 19 June 2026); draft-saihm-memory-protocol-01 (27 May 2026)
Source https://www.w3.org/community/ai-agent-memory-interop/
What is taken Nothing normative; receipt and erasure message shapes are compared for alignment
Why Avoids gratuitous divergence from emerging agent-memory work
What is extended or replaced Open Personal Context receipts are per read, not per memory write
Specification home A9, A10 notes

Version pinned

  • The W3C AI Agent Memory Interoperability Community Group (ai-agent-memory-interop), launched 3 June 2026, charter 1.0 adopted 19 June 2026. It has published no report or draft. A Community Group is not on the W3C standards track.
  • draft-saihm-memory-protocol-01, "The Sovereign AI Horizontal Memory (SAIHM) Protocol", 27 May 2026, an individual Internet-Draft intended as Informational, with no IETF standing. The group's charter treats it as a normative reference.

What is taken

Nothing normative. When receipt (A9) and erasure (A10) shapes are next revised, they are compared with these to avoid needless divergence.

Why

Open Personal Context tracks this work as prior art for receipts and erasure.

What is extended

Open Personal Context receipts record each disclosure to a recipient, not each memory write. Purge acknowledgements are recorded assertions, never proof of erasure (A10).

What is replaced or not used

The draft's post-quantum identity binding, public-chain audit anchoring and encrypted memory cells are not used.

Deviations

The group's post of 29 July 2026 and the IETF datatracker disagree on the draft's status (concluded independent-submission consideration, as against "In ISE Review"). This record cites the datatracker.

Conformance checks

None. LOG-01 and PURGE-01 cover the Open Personal Context receipt and purge shapes.

References to other standards and projects describe intended technical alignment only and do not imply endorsement or partnership.