Agent Revision Markup
Reference

Turn

One signed revision event.

A turn is the unit of agent document work. The signed body says what happened; the wrapper makes it verifiable and chains it to everything before it.

FieldTypeWhat it is
bodyobjectThe event itself. Fields below.
bodyHashstringSHA-256 of the canonical body.
signatureobjectkeyId, algorithm, value, signedAt. The key must be in the manifest.
turnHashstringHash of body plus signature. The next turn chains to this.

Body fields

FieldTypeWhat it is
schemaVersionintegerWire schema version.
sessionIdstringMust match the manifest.
manifestHashstringHash of the manifest this turn was made under. Swap the manifest, verification fails.
turnIdstringUnique in the record. Duplicates are rejected.
sequenceintegerPosition in the ledger, starting at 0.
previousTurnHashstring | nullThe chain. null only on the first turn.
authorPartyIdstringWhich party acted.
createdAtstringISO 8601 timestamp.
anchorIdstringWhere in the document this applies.
clauseTopicstringWhat it is about, from the manifest's topic lists.
decisionobjectkind plus a one-line summary. Kinds: propose, counter, accept, reject, escalate.
authorityobjectWhy this was allowed. Below.
proposedText ·stringThe text being proposed, when there is one.
visibleArtifactsarrayWhat humans see. Below.

Authority

Two kinds in v0.1:

  • { "kind": "direct-party-signature" } - a party acting for itself.
  • { "kind": "human-approved-agent-draft", "mandateId": "...", "approval": {...} } - an agent's work, carrying the human approval that authorized it.

Visible artifacts

Each artifact maps the record back to something a human sees in the document: kind is comment, insert, delete, or replace, with the anchorId, authorPartyId, and the text itself. Native Word ids are optional hints, never required for verification.

On this page