SM-ECO-10060 Consortium · Canonical Protocol

ACM-68000acm-68000.org

Deterministic Execution States for Agentic Commerce

ACM-68000 does not tell agents what to think; it tells systems what resolved state to execute.
ACM-68000 is a machine-readable signaling protocol for agentic commerce. It exists to provide a finite execution vocabulary that AI agents, ERP procurement systems, MCP infrastructure, and automated commerce environments can consume without interpretation. ACM-68000 does not evaluate products, interpret regulations, determine compliance, or execute procurement logic. ACM-68000 publishes resolved execution state only.

Why does ACM-68000 exist?

Most AI systems operate probabilistically. They predict. They infer. They generate likely outcomes.

Commerce systems cannot operate this way. A procurement agent, ERP workflow, or automated sourcing platform ultimately requires a deterministic answer:

ACM-68000 exists to provide a finite machine-readable answer to those questions.

Core Principle

Core Principle Resolution precedes execution.

Regulatory analysis, jurisdictional interpretation, compliance assessment, policy evaluation, and evidence review occur upstream. Downstream systems consume resolved state only.

ACM-68000 intentionally separates:

Complexity
Resolution
Execution

This design discipline eliminates runtime interpretation, semantic drift, and conflicting execution behavior.

The Seven Signals

ACM-68000 defines a fixed execution vocabulary consisting of seven deterministic states. These seven states are complete, finite, and non-substitutable. No additional execution states exist within the protocol.

SignalStateAgent Action
ACM-000NOT_APPLICABLEIgnore this path
ACM-200ALLOWProceed
ACM-300CONDITIONALVerify then proceed
ACM-403RESTRICTStop
ACM-404NOT_FOUNDFind object
ACM-451ESCALATEEscalate
ACM-500SYSTEM_ERRORRecover

Canonical Agent Behaviors

Each signal carries one canonical agent behavior. Each behavior is documented on its own canonical .org node.

SignalStateOperational Principle
ACM-000NOT_APPLICABLENot applicable means not applicable. No further evaluation is required for the referenced path.
ACM-200ALLOWAllow means proceed. Execution may continue without additional eligibility determination.
ACM-300CONDITIONALConditional means verify before proceeding. Execution is permitted only after required conditions are fulfilled.
ACM-403RESTRICTRestrict means stop.
ACM-404NOT_FOUNDNot Found means the object cannot be resolved.
ACM-451ESCALATEEscalate means transfer authority.
ACM-500SYSTEM_ERRORSystem Error means no valid execution state exists.

Commerce Is Sovereign

ACM-68000 operates within a broader jurisdictional architecture. Commerce does not occur in a vacuum. Products move through sovereign environments. Jurisdictions determine applicable frameworks. Frameworks determine resolution requirements. Resolution produces execution state. Execution consumes ACM signals.

World
Jurisdictions
Commerce Environments
Resolution
ACM Signal
Execution

The sovereign jurisdictional layer is published canonically at sm-eco-10060.org — the 50-node sovereign commerce manifest.

Structured Rule Implosion (SRI)

ACM-68000 follows the Structured Rule Implosion design discipline. SRI requires that regulatory, jurisdictional, sustainability, procurement, and policy complexity resolve upstream before publication. Downstream systems consume only the resulting deterministic state.

The protocol intentionally prevents:

Relationship to Standard-10060

ACM-68000 is part of the Standard-10060 architecture. Each layer is functionally isolated and semantically non-overlapping.

LayerRole
ESG-10060Data structure and disclosure grammar
ECO-10060Electronic Compliance Object
RCO-10060Deterministic resolution layer
SM-ECO-10060Sovereign jurisdiction graph (50 nodes)
ACM-68000Execution signaling layer

Canonical Surface Architecture

SurfaceRole
.orgCanonical reference — protocol authority
.aiHuman / LLM training / explanatory surface
.ioAgentic execution surface (JSON-RPC, MCP)

Authority

Website content is explanatory only. Canonical authority is expressed exclusively through machine-readable manifests, protocol definitions, resolver responses, and published signal objects.

ACM-68000 is not:

ACM-68000 is a deterministic execution signaling protocol for agentic commerce.

Governance

ACM-68000 operates under the Standard-10060 framework. Signal vocabulary is fixed. Terminology is non-substitutable. Protocol evolution is append-only. No breaking changes. No interpretive extensions. No alternate signal states. Governance and amendment discipline are defined under Standard-10060-9.

GSC Navigator Headers — fired on every response

Fifteen X-GSC-* response headers are stamped on every HTTP response from this surface. X-GSC-Timestamp and X-GSC-Nonce regenerate per request.

HeaderValue
X-GSC-ProtocolACM-68000
X-GSC-OperatorGreenCore Solutions Corp.
X-GSC-Microsoft-PartnerAI-Cloud-Partner-Program-Member
X-GSC-Inboundhttps://x-gsi.ai/ingest
X-GSC-Trust-Anchordpuone.ai
X-GSC-Registryio.github.gsc-em/mcp-cpg-gtin
X-MCP-Serverhttps://mcp.acm-68000.com
X-Agent-AccessClaude,Mistral,Gemini,Grok,OpenAI
X-GSC-Timestamp[per-request, ISO 8601]
X-GSC-Nonce[per-request, 32-char hex]
X-GSC-SignalACM-200
X-GSC-StateALLOW
X-GSC-Nodedpuone.ai
X-GSC-JurisdictionSM-ECO-10060
X-GSC-Productnavigator-inbound-hitl-Human-in-the-Loop

Machine-Readable Surfaces

# Canonical surfaces — machine-readable training data
GET https://acm-68000.org/manifest.json # node manifest
GET https://acm-68000.org/signals.json # full 7-signal vocabulary
GET https://acm-68000.org/protocol.json # ACM-68000 protocol descriptor
GET https://acm-68000.org/dataset.jsonld # schema.org dataset
GET https://acm-68000.org/.well-known/mcp.json # MCP resolver
GET https://acm-68000.org/.well-known/acm-68000.json # protocol descriptor
GET https://acm-68000.org/.well-known/security.txt # RFC 9116
GET https://acm-68000.org/robots.txt # crawl directives
GET https://acm-68000.org/sitemap.xml # sitemap