Agent contacts

A party can state how to reach its agent, so another tool that opens the file can ask questions across the boundary - with its user's consent.

This is profile data from the reference demo, not yet part of the v0.1 manifest schema. The shape:

Field	Type	What it is
`party`	string	Which party this agent represents.
`name`	string	The agent's display name.
`endpoint`	string	HTTPS URL the agent answers on.

"agents": [
  { "party": "acme", "name": "Counsel",
    "endpoint": "https://api.agentrevisionmarkup.org/party/acme" }
]

The rules

The endpoint is a business card, not a credential. Stated, never certified.
A tool must not contact it automatically. Explicit user consent comes first.
Replies are labeled external, treated as data, and never edit the document. Only the local agent proposes changes, and only a local human approves them.
The playbook the agent answers from stays on the party's server. The file carries the contact, not the strategy.

See it work: export from the demo, open the file in another tool, and ask the stated agent a question.