RCO-10060 is the Record of Cleared Orders: a signed, machine-verifiable record of one cleared decision. The standard is owned by the Agentic Private Office (Agentic KG Holdings), MIT-licensed, and implemented by both companies’ doors (GreenCore Solutions Corp. and Allooloo Technologies Corp.), and by any licensed firm’s agent with a write key.
An agent that clears a decision — an issuer resolved, a product cleared under a rule, a signal returned — leaves one receipt. The receipt is the thing a compliance officer is asked for, and the thing a licensed participant’s agent must be able to produce.
The unit
One cleared decision. One schema for every object type; the object identifier says what kind of order it was.
The receipt
Field
What it holds
decision_id
the id the decision was given by the door that made it
object
what was cleared: a GTIN, an ISIN, a product id — typed by its identifier
actor_class
for which actor class (never a person)
rule
under which rule object and version
records_read
which records were read, each with its signature (kid) and hash
signal
ACM-200 trading / cleared · ACM-403 halted / restricted · ACM-404 not on the register · ACM-451 read the filing
decided_at
when
issuing_door
which door issued it
signature
the issuing door’s signature, verifiable against its published keyring
ledger
the Azure Confidential Ledger transaction id under which its hash was written
Who writes, who reads
Writers: authorised doors — the gates and resolvers that implement RCO (listed below) — and any licensed firm’s own agent through the write path with a key. Write keys are issued by the office.
Readers: anyone — the firm’s audit function, its regulator, its counterparty. Reads are free and need no account.
Scope
RCO-10060 does
Keep one signed receipt per cleared decision
Name the rule object and version a decision was made under
Name the records read, with their signatures
Write each receipt’s hash to a confidential ledger
Serve receipts by decision_id over MCP and as a page
RCO-10060 does not
Interpret law
Certify products or issuers
Assert regulatory authority
Hold caller data, personal data or amounts
Verification
The signature verifies the issuer: the receipt states which door issued it, and the signature verifies against that door’s public key. The ledger receipt proves the hash was written when the door says it was.
Verification proves what the issuer stated. It does not make the operator a regulator.
Live
RCO-A2A is the live door: mcp.rco-a2a.ai/mcp, two tools — get_receipt(decision_id) for anyone, no account; write_receipt for authorised doors. Receipt pages at rco-a2a.ai/receipts/{decision_id} (JSON at .json). Hashes on Azure Confidential Ledger gsc-rco-ledger. The five v1 tools of the retired reading are not on the wire.
Pricing: reads are free. Write keys are issued by the office at no charge to implementers; writes by a firm’s own agents become a per-receipt line under x402.