Canonical Reference Surface
AI Orderability · The structured outcome an agent can act on · Canonical text
AIO-10060 defines the structured orderability outcome: whether a specified product may be ordered for a specified client category in a specified market, under a named immutable rule revision, on evidence the outcome names element by element. The producing node signs the outcome under the record contract; the receipt of the read is signed separately. An outcome carries one clearance signal from the ACM-68000 vocabulary and the scope, conditions, exclusions tested, assessments and documents required and evidence gaps around it. It speaks about a product and a category, never an individual; it is not permission, not a venue and not an order. Missing evidence is reported as a gap, never as a finding. AIO makes the orderability question answerable in a form an agent can act on and a reader can verify.
AIO-10060 (AI Orderability) defines the structured outcome an artificial-intelligence (AI) agent can act on: whether a specified product may be ordered for a specified client category in a specified market, under a named rule revision, on evidence the outcome names. Its central object is the orderability outcome. The outcome answers one question, in four parts: which product, which client category, which market, which revision. It answers nothing else.
AI Orderability is the only expansion of AIO. The word is orderability, not suitability and not advice: an outcome speaks about a product and a category of client under a market's rules, never about an individual.
Every outcome published under AIO-10060 makes the same four promises.
Scope. The outcome names its product by the product's own record, its client category by the market's own classification, its market by the deployed market value, and its rule by an immutable ACM-68000 (Agent Clearance Manifest) revision. An outcome with an unnamed part is not an outcome.
Basis. Every element of the outcome — each condition, each exclusion tested, each assessment or document required — references the chapter field instance or product-record field it rests on. An element without a basis is not written.
Signal. The outcome carries one clearance signal from the ACM-68000 vocabulary and adds no signal of its own. The structure around the signal is AIO's; the meaning of the signal is ACM's.
Gaps. Where the evidence does not reach a conclusion, the outcome says so, lists the evidence it lacked and the pages it checked, and stops. A gap is reported as a gap. It is never closed by assumption.
The outcome. AIO owns the shape of the answer to the orderability question: its four-part scope, its basis references, its conditions, its exclusions tested, its assessments and documents required, its evidence gaps and its single ACM signal. No other standard defines that object.
The orderability section of the chapter. AIO owns the catalogue of fields a market chapter must carry for outcomes to be produced in that market (the Appendix C catalogue of SM-ECO-10060): product scope, client categories, target market, negative target market, distribution conditions, required assessments, product documentation, manufacturer and distributor roles, review triggers, evidence requirements, exceptions and the orderability profile reference. The chapter holds the values; AIO defines what they mean.
The client category. AIO owns the rule that the client is always a category from the market's own classification with source-backed qualification criteria, never an individual, and that the same product may carry different outcomes for different categories in the same market.
The conditions. AIO owns the representation of a conditional outcome: each condition names the rule element it comes from, the party it falls on and the evidence that would discharge it. A condition without an owner or a discharge is a gap, not a condition.
The review. AIO owns the rule that an outcome names the review triggers and periodic review conditions the rules impose, so that a reader knows when an outcome must be produced again. An outcome never names its own expiry from memory.
Names, types and meaning only. Proposals for review, not populated outcomes or a declaration of deployed field support.
| Field | Type | Meaning |
|---|---|---|
schema_version | string | Outcome schema version |
outcome_id | string | Stable identity of this outcome |
subject | reference | Product record version the outcome speaks about |
subject_type | string | Product or instrument category of the subject |
market | string | Deployed receipt-market value |
client_category | reference | Client classification from the chapter's client_categories[] |
rule_version | string | Immutable ACM-68000 revision applied |
section_ref | reference | Exact chapter orderability-section version read |
signal | string | One ACM-68000 clearance signal; no other vocabulary |
conditions[] | array of object | Rule element, party it falls on, evidence that discharges it, basis reference |
exclusions_tested[] | array of object | Negative target-market and distribution exclusions tested, with result and basis |
assessments_required[] | array of object | Assessments the rules require before an order, with trigger and party |
documents_required[] | array of object | Product, risk and target-market documents required, with basis |
evidence_gaps[] | array of object | Evidence the outcome lacked, pages checked, reason |
review_triggers[] | array of object | Events and periods after which the outcome must be produced again |
as_of | date | Date for which the outcome speaks |
produced_at | datetime (UTC) | Time this outcome was produced |
node | string | Producing node, inside the signed payload |
proof | object | ECO signature profile; no new signing scheme |
Every basis reference names a field instance in the SM-ECO-10060 7.2 shape — the chapter section's own field with its source_url, source_date and read_at — or a field of the product record. The outcome copies no value out of its basis; it points at it.
| Signal | What the outcome says |
|---|---|
ACM-200 | The rules as evidenced permit the product for the client category in the market, subject to any conditions[] listed |
ACM-403 | The rules as evidenced restrict or halt the product for the client category in the market; the restricting element is in the basis |
ACM-404 | The product, category or required register entry is not on the register the rules name; pages checked are listed |
ACM-451 | The rules require the reader to read a named filing or document before any conclusion; the filing is referenced |
The signal's meaning is ACM-68000's and is not restated here. AIO adds the scope, the conditions, the exclusions, the gaps and the review triggers around it.