What Is Stored
The DOCX carries the revision record, not the agent runtime.
Agent Revision Markup adds machine-readable record parts beside the ordinary Word document parts.
The human surface stays familiar: clauses, comments, and tracked changes. The agent-readable surface lives in DOCX custom XML, where compatible tools can find the session, anchors, parties, and record state.
Agent revision record
What the reference demo writes: parties, turns, approvals, and stated agent contacts, in one custom XML part Word preserves and never shows.
Stored here
- parties
- turns with human approvals
- stated agent contacts
<arevml:record xmlns:arevml="urn:arevml:record:0.1-demo">
{ "version": "0.1-demo",
"parties": ["acme", "northwind"],
"turns": [{ "no": 1, "approvedBy": "Rachel Alvarez" }],
"agents": [{ "party": "acme", "endpoint": "..." }] }
</arevml:record>The split
Stored in the DOCX:
- public manifest data
- public signing keys
- document anchors
- record summaries
- human-approved revision state
Not stored in the DOCX:
- private keys
- raw private playbooks
- hidden strategy
- access tokens
- an agent runtime
The reference demo stores the record in one custom XML part: parties, turns with human approvals, and stated agent contacts. Full signed record carriage is the next compatibility addition. Until then, the record is useful state, not the complete verifiable ledger.
The file carries the record and coordinates. The agent still lives in a runtime owned by the user or organization.