Standards
SAIHM — Sovereign AI Horizontal Memory Protocol
Candidate memory standard — the strongest one; chair of the W3C memory CG maintains it (disclosed conflict).
★ 4 on GitHub · last commit Oct 11, 2026
What it is
Candidate memory standard — the strongest one; chair of the W3C memory CG maintains it (disclosed conflict).
At a glance
- Business model
- Specification
- License
- Apache-2.0
- Governing body
- None (individual I-D, author Russell Jackson; Independent Submission stream, NOT IETF-endorsed)
- Maturity
- draft-saihm-memory-protocol-03; ISE concluded and released from queue 2026-07-25, directing work to IETF proper; no formal standing
- What it says about memory
- THE most developed memory-spec proposal: memory-cell shape, ML-DSA-65 identity, GDPR Art.17 cryptographic erasure, 8 MCP tools (remember/recall/forget/status/share/revoke_share/governance_propose/governance_vote).
- Artifacts
- datatracker.ietf.org/doc/draft-saihm-memory-protocol; Apache-2.0 reference impl (npm @saihm/mcp-server)
GitHub activity
This product has a public repository, so we read it nightly from the GitHub API. Stars measure developer attention, not quality or market share.
“Portable memory for AI agents — the open MCP client for SAIHM. Eight tools any MCP agent uses to reach a SAIHM operator endpoint: encrypted, shareable, provably erased. Implements the publicly documented SAIHM memory protocol (Independent-Submission Internet-Draft; not an IETF standard). Evaluate it offline first with the runnable demos.” (repository description)
- Stars
- 4
- Forks
- 1
- Open issues
- 7
- Last commit
- Oct 11, 2026 (30 days ago)
- License (GitHub)
- Apache-2.0
Links and sources
- Official sitesaihm.net/developers
- GitHub repositorygithub.com/SAIHM-Admin/saihm-mcp