DMF: your memory, in a format you own.
The Dijin Memory Format is owner-signed, portable, and documented. Take your memory anywhere. There's no lock-in, and you can verify it offline.
Why DMF matters for agent memory
Agents need memory they can verify, not just text they can retrieve. DMF gives every claim a portable structure: source segment, extracted claim, evidence span, valid time, signature, and audit chain.
That means one agent can propose or recall memory, and another agent can verify where it came from — without the memory belonging to either agent.
DMF is the memory handoff format.
- Not agent-to-agent messages.
- Not app-specific exports.
- Not opaque vector-store rows.
- DMF is how memory stays portable when agents change.
Inside a DMF
Segment
The source text you saved. It's the raw material a memory is built from.
Claim
A structured fact extracted from the segment, with its provenance.
Evidence
The link from a claim back to the exact span it came from.
Signature
An Ed25519 owner signature that proves it's yours and unaltered.
An honest maturity ladder
We won't slap a "standard" badge on it. Here is exactly where DMF stands today.
Tier 1: Public-documented
TodayThe format is published with conformance vectors. Anyone can read and implement it.
Tier 2: Independent implementations
In progressBuilding toward implementations beyond Dijin's own.
Tier 3: Open standard
Target≥2 independent implementations + a ratified RFC. The goal, not yet the claim.
Mapped to recognized standards
DMF sits in the standards lineage, not off to the side.
Canonical JSON
Aligned with RFC 8785 (JCS) for deterministic serialization.
Provenance
Modeled on W3C PROV-O for source attribution.
Signed claims
Aligned with W3C Verifiable Credentials 2.0 + Data Integrity 1.0.
Verify a memory archive
Use the Dijin CLI to verify signatures and tamper evidence offline.