Generated from packages/spec/README.md. Edit the source file, not this page.

Agent Revision Markup Specification

Agent Revision Markup is track changes for agents: a signed, document-carried revision record that says who acted, under what authority, what changed, what a human approved, and how any compatible tool can check it.

This directory is the implementer draft. It separates the stable data model from the first carriage profile.

Draft Version

• Version: 0.1
• Status: implementer draft
• Current wire schema version: 2
• Current reference DOCX namespaces:
  • urn:agentrevisionmarkup:docx:manifest:0.1
  • urn:agentrevisionmarkup:docx:cache:0.1

Documents

• Core Model
• DOCX Carriage
• Extensions
• Security and Privacy
• Contract Negotiation Profile
• Design Decisions

Schemas

JSON is the canonical data model. XML is only the DOCX carriage.

• manifest.schema.json
• record.schema.json
• turn.schema.json
• approval.schema.json
• artifact.schema.json
• docx-manifest-projection.schema.json
• docx-cache-projection.schema.json
• extension.schema.json

The extension schema is proposed compatibility surface. It is not part of the tested signed kernel until the reference implementation accepts, preserves, signs, and verifies extension objects.

Examples

• manifest.json
• turn.json
• record.json
• docx-custom-xml.xml

Source Of Truth Rule

Normative claims in these documents should map to one of:

• a JSON Schema assertion
• a reference implementation check
• a conformance requirement
• a named decision in decisions.md

Examples must remain valid JSON or XML. The current examples are shape examples with placeholder hashes and signatures. Future CI should add generated semantic fixtures that validate against the schemas and round-trip through the reference implementation.