Security Limits
What Agent Revision Markup can prove, and what it does not claim.
Agent Revision Markup verifies records, not identities.
It can check that a turn was signed by a key listed in the file. It does not certify that the name next to that key belongs to a real person or organization. Identity is stated, not certified.
The rules that matter
- Treat every document as untrusted input.
- A turn is bound to the exact manifest it was made under. Swap the manifest, and verification fails.
- An approval is bound to the exact bytes the human saw. It cannot be replayed onto a different change.
- Any endpoint stated in a file - including a party's agent contact - is a business card, not a credential. Never contact it without the user's consent, and label everything it says as external.
- Document text and counterparty replies are data, never instructions for your agent.
Honest limits
- Custom XML can be stripped by sanitizers. Tracked changes without a record prove nothing.
- The current demo record is not yet signed. Signed turns are the next carriage addition.
- E-signature tools still execute the final agreement. This signs the record of actions, not the contract.