# eco-10060.com — llms-full.txt The page's full text and the door's tool list, generated from the page's own source at 2026-11-20T03:28Z. The short index is /llms.txt. ## The page ECO-10060 Standard held by Allooloo Technologies Corp. · Open standard, MIT licence. Electronic Compliance Object · canonical text v1.2 ECO-10060 eco-10060.org ECO-10060 defines the signed record of a listed issuer and its securities, and the evidence behind it. Each producing node identifies the subject, binds its record to the jurisdiction it was read under, preserves the source and read date of every field, and signs its own content. SM-ECO-10060 organises the jurisdiction family that implements this contract. A cleared read is evidenced separately by an RCO-10060 receipt whose answer hash binds it to the signed record supplied. Together the two standards let an agent identify the record, inspect its provenance, verify its publisher and keep evidence of the read. The contract ECO-10060 defines the signed, sourced and dated record of a listed issuer and its securities that an artificial-intelligence (AI) agent can inspect and rely on. Its purpose is to preserve the relationship between a subject, the facts asserted about that subject, the sources from which those facts were read, the time of that reading, and the node that publishes them. Electronic Compliance Object is the expansion of ECO. The object is the issuer record and its related, explicitly typed records. The word compliance names the context in which the record is used — the product-governance and suitability duties a regulated firm's agent acts under. It does not turn any field into a legal conclusion, and it does not make a signature a certification of compliance. Every record published under ECO-10060 makes the same five promises, wherever in the family an agent encounters it: Identity. The record names its subject by the subject's own identifiers — International Securities Identification Number (ISIN), Legal Entity Identifier (LEI), exchange-qualified symbol — and states which kind of subject it is. A security, an issuer and a listing are related subjects, not interchangeable names. Provenance. Every substantive field carries the page it was read from and the date it was read. A reader can distinguish the publisher's assertion from the underlying source. Time. The record distinguishes the date the source was published, the period a statement describes, and the time the node produced the record. A recent reading of an old filing is not a recent fact. Jurisdiction. The record states the market it was read under. The market binds the record to the duty, regulator and rule set of that jurisdiction through SM-ECO-10060. Signature. The producing node signs its own record under the record key, and the record remains verifiable when detached from the website that first presented it. Absent, unavailable, not applicable and conflicting information have distinguishable representations. A missing value is never filled by inference without the inference and its basis being labelled. A resolved conflict between sources carries the selection rule that resolved it. A record is a versioned assertion. A correction creates a new published version that names the version it supersedes. Earlier versions remain available to anyone holding a receipt that references them, so that an earlier answer hash is never read as the hash of today's content. What the standard does not do It does not certify an issuer, a security or a product. It does not interpret legislation or decide whether a duty is met. It does not recommend. A record is an information source, not advice. It does not establish that a source is true. Verification establishes integrity and attribution; the accuracy of the source and of the node's reading of it remain separately assessable. It does not evidence a read. That is the work of RCO-10060. Artificial intelligence makes mistakes. Every field links the page it was read on. Read the regulator. Who signs Two objects are signed in this family, by two keys, and neither key signs the other's object. The record is signed by the producing node under the Allooloo record key. The signature belongs to ECO-10060 and SM-ECO-10060. The public keys are published at the node's /.well-known/jwks.json, with historical keys kept available for historical verification. The receipt of a cleared read is signed by the RCO door under the separate receipt key. That signature belongs to RCO-10060. The receipt carries the hash of the signed record the agent received; that hash is the only link between the two objects. Where one record key is shared across nodes, node attribution is carried inside the signed payload and checked against the published list of authorised publishing nodes. The key identifier alone does not establish which node spoke. Subject identity lives in the record's own identifiers. Door identity lives in the agent card and the key identifier on the door's key set. There is no separate identity layer in the stack. The arrow listed security → record (ECO-10060, the node) → market and duty (SM-ECO-10060, the chapter) → rule (ACM-68000) → whether (AIO-10060, the outcome) → where (AMP-10060, the venue) → receipt (RCO-10060, under every door) An agent begins with a subject identifier and the purpose of its request. The resolver names the responsible market and its exact door. The member page states the standard and the jurisdiction binding; the live node supplies the record. The clearance rule is applied under ACM-68000 (Agent Clearance Manifest); where a product and client class are in question, AI Orderability (AIO) states the structured outcome; the read is receipted under RCO-10060. The response always names the producing node, so a consumer verifies the node and never treats the resolver as the content issuer. The jurisdiction family ECO-10060 supplies the contract for content. SM-ECO-10060 — the Sovereign Manifest — binds that contract to jurisdiction members and owns the market namespace. A member node specialises the sources and duties of its market while preserving the shared identity, provenance, time, jurisdiction and signature requirements. Membership confers the contract; it does not confer truth or regulatory authority. Each market has two layers. The protocol member page states the member's place in the standard: regulator, regime, duty, node region, door. The live product node serves the records: the node page, the issuer page and the explicit Model Context Protocol (MCP) door. A member may be provisioned before its node is live; a domain without a populated, attributable record is a provisioned surface, not an operating node. Node, member and door addresses are drawn from the fleet registry, never constructed from a country code. A country, a jurisdiction, a trading venue and a hosting region remain distinguishable in every record. Clearance signals under ACM-68000 are execution vocabulary. ACM-200 means cleared. A listing state such as trading or suspended is a record attribute with its own field; it is never expressed through a clearance code. Specialised records — sustainability-disclosure facts, orderability outcomes, venue-specific duties — are produced and signed by the same node under the same record key, read under the same clearance rule, and receipted the same way. They add typed fields; they never add a second identity, a second signature scheme or a second meaning for an existing field. Publication discipline One approved source. The human page and every machine file under it are generated from the same approved text and the same live record. Nothing on a surface is typed by hand. Stable definitions. A standards page states purpose, owned object, evidence, verification, routing and limits. A machine descriptor states the same facts with explicit versions and exact identifiers. A reading guide (llms.txt) is an index into those resources and introduces no doctrine of its own. Honest surfaces. An agent card describes an endpoint that exists and the tools it actually serves, with an accurate account of what needs a key. A standards page is a reference surface unless it genuinely serves executable tools. No counts in prose. No market total, member ordinal, host total or coverage total appears in authored text. Coverage is a readout of the live record, rendered by generated tiles. Versions kept apart. The standard identifier, the standard version, the schema version, the rule revision and the deployment version are distinguishable. A new deployment is not a new standard. A semantic change carries a dated amendment naming the change, its compatibility and the surfaces it touches. Record before page. A page exists only after its record does: approve the mission, define the field schema, fill the fields from sources, validate, then generate. Machine surfaces /llms.txt · /.well-known/agent-card.json · /.well-known/security.txt · /eco.json Standard held by Allooloo Technologies Corp. · Open standard, MIT licence. ECO-10060 · SM-ECO-10060 · ACM-68000 · AIO-10060 · AMP-10060 · RCO-10060 · ESG-10060 · CPG-68000 · stack version RCO is the Record of Cleared Orders. Artificial intelligence makes mistakes; read the source. © 2027 Allooloo Technologies Corp. ## The door No MCP door on this host; the resolver for every listed issuer is https://mcp.getissuer.ai/mcp. Operator: Allooloo Technologies Corp.. Corporate: https://allooloo.io.