Agentic Market Protocol · The venue, by reference · Canonical text
Agentic Market Protocol · The venue, by reference · Canonical text
AMP-10060 defines the venue reference record: the sourced, dated and versioned identity of a venue, keyed by its Market Identifier Code, with its rules source, halts, calendar, clearing, participant roles, gates, reference endpoints and change notices, each with the page and date it was read from. The producing market node signs the record under the record contract; the receipt of the read is signed separately. A venue record is reference only: it establishes no entitlement, no permission to route and no order. Venue, market and jurisdiction are never used interchangeably. Missing evidence is reported as not found, never as absence. AMP makes where recoverable, so that whether can be answered first and acted on correctly.
AMP-10060 (Agentic Market Protocol) defines the venue reference record: the sourced, dated and versioned identity of a venue on which instruments in a market trade, keyed by its Market Identifier Code (MIC), with the venue's rules source, halts, calendar, clearing relationships, participant roles, obligations, gates, reference endpoints, settlement links and change notices. Its central object is the venue record. It answers one question — where — by reference, and establishes nothing about whether a party may go there.
Agentic Market Protocol is the only expansion of AMP. The word is market: the venue a record points at, not a marketplace the protocol operates. AMP sells nothing, lists nothing for sale and ranks nothing.
Every venue record published under AMP-10060 makes the same four promises.
Key. The record is keyed by the venue's evidenced MIC from the official MIC register, with the register entry as the key's source. Where an activity has no applicable code, the gap is preserved with a separately typed reference. No code is invented, derived or guessed.
Reference. Every field is reference information: what the venue publishes about itself, read from the venue's or its regulator's own pages, with the page and date. The record describes; it never entitles.
Distinction. Venue, market and jurisdiction are three identifiers and are never used interchangeably. A venue record names the market it is read under and the jurisdictions its scope binds; it does not become either of them.
Time. Sessions, holidays, closures, halts and change notices carry the date the source bears and the date the record read it. A calendar read from memory is not a calendar.
The key. AMP owns the rule that the venue is identified by MIC and only by MIC, sourced from the official register, and that a venue without an applicable code is recorded with a typed gap rather than a substitute identifier.
The venue record. AMP owns the catalogue of fields a venue record carries (the Appendix D catalogue of SM-ECO-10060): venue identity, venue scope, rules page, halts, calendar, clearing house, participant roles, market-maker obligations, gates, reference endpoints, settlement links, change notices and sources. The chapter holds the values; AMP defines what they mean.
The reference endpoints. AMP owns the representation of a venue's public reference locations — each with its purpose and its source — as locations to read, never as endpoints to connect to.
The change notice. AMP owns the rule that a venue's rule changes and operational notices are recorded as versioned entries with the date the venue published them, so that a reader can tell which rules were in force on a given date.
The three-way distinction. AMP owns the rule that venue, market and jurisdiction are never used interchangeably, in any record, page or descriptor of the family.
Names, types and meaning only. Proposals for review, not populated records or a declaration of deployed field support.
| Field | Type | Meaning |
|---|---|---|
schema_version | string | Venue record schema version |
venue_mic | string | Market Identifier Code, the venue key, with the register entry as its source |
mic_gap | object (optional) | Typed reference preserved where no applicable code exists; present only when venue_mic is absent |
market | string | Deployed receipt-market value the record is read under |
version | string | Immutable venue record version |
supersedes | string (optional) | Earlier venue record version replaced |
as_of | date | Date for which the record speaks |
produced_at | datetime (UTC) | Time this version was produced |
node | string | Producing node, inside the signed payload |
fields[] | array of field | The Appendix D catalogue, each entry a field instance in the 7.2 shape of SM-ECO-10060 |
proof | object | ECO signature profile; no new signing scheme |
Every catalogue entry — venue_identity, venue_scope, rules_page, halts[], calendar[], clearing_house[], participant_roles[], market_maker_obligations[], gates[], reference_endpoints[], settlement_links[], change_notices[], sources[] — is a field instance with its own source_url, source_date and read_at. One source is never assigned to the whole record.
A later version may define a route object naming an actor, an instrument, an action, an endpoint and the clearance profile and orderability outcome it rests on. Version 1.0 reserves the name and defines nothing under it. No surface describes a venue record as a route.