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 revision record.
Revision record
The machine-readable record Word preserves and never shows: parties, anchors, signed turns, approvals, and optional extension references.
Stored here
- parties and keys
- anchors
- signed turns
- human approvals
- extension refs
<agentrevisionmarkup:record
xmlns:agentrevisionmarkup=
"urn:agentrevisionmarkup:docx:record:0.1"
version="0.1">
<agentrevisionmarkup:payload
encoding="application/json">
{
"manifest": { "sessionId": "session_001" },
"ledger": [
{
"turnId": "turn_001",
"authorPartyId": "acme",
"authority": {
"kind": "human-approved-agent-draft"
}
}
],
"turnCount": 1
}
</agentrevisionmarkup:payload>
</agentrevisionmarkup:record>Check any file yourself: inspect a DOCX in your browser.
The split
Stored in the DOCX:
- parties and public signing keys
- document anchors
- signed revision turns
- human approval bindings
- optional extension references
Not stored in the DOCX:
- private keys
- raw private playbooks
- hidden strategy
- access tokens
- an agent runtime
The draft uses one custom XML record part. There is no separate cache in this version. A tool can build its own UI summaries from the record, but those summaries are not the standard.
The file carries the record and coordinates. The agent still lives in a runtime owned by the user or organization.