ACM-68000 (Agent Clearance Manifest) · 6. The clearance vocabulary
ACM-68000 defines the clearance rule reference and signal vocabulary for listed issuers' records. Its rule register binds every rule_version used in a receipt to an immutable revision of a duty, its jurisdiction, legal reference, sources and effective dates. Each family publishes how its evidence-backed outcomes map to the clearance signals for a specified read or action. The producing node signs rule and outcome records under the ECO-10060 contract; the RCO door separately signs the receipt of the cleared read. ACM makes the governing revision and the meaning of clearance recoverable, and keeps three distinctions: lookup is not permission, missing evidence is not a negative finding, and system failure is not a resolved restriction.
| Signal | Reading | Boundary |
|---|---|---|
| ACM-404 | Not on the register | The named lookup target is absent from the identified register. This establishes neither global absence nor prohibition. |
ACM-200 means cleared. It never means a listing state. A listing attribute — trading, suspended, delisted — belongs in its own field on the record. A sourced halt may be an input to a family's restriction rule; the raw listing attribute and the resolved signal remain distinct, including when both appear in one response.
ACM-404 names the register and the lookup target: an absent rule revision and an absent subject registration are different failures and never share an unexplained message. ACM-451 names the required filing or evidence when known, and never disguises a service outage as a request to read.
| Family | ACM-404 |
|---|---|
| Duty clearance (national and shared families) | Requested duty revision absent from the register |
| AIO orderability | Requested product or rule registration absent from its register |
| AMP route clearance | Requested venue, route or rule registration absent from its register |
| ESG duty family | Requested disclosure or rule registration absent from its register |
The bindings below are the common interpretation. Each immutable family revision supplies its own source-backed prerequisites, applicability and reason codes before a binding is applied. A listed duty name is a register seed, not a completed rule.
An ESG ACM-200 clears the named check; it is not a sustainability claim. An AMP ACM-200 requires route-gate evidence; it is never produced because an endpoint is discoverable. An unresolved prerequisite stays visible: no evaluation issues ACM-200 while hiding an unmet condition. Evidence gaps, operational errors and unresolved conflicts have explicit representations, and a family uses ACM-451 only where its published binding calls for the named source to be read.