Microsoft Azure · agents resident in 18 countries worldwide

Electronic Compliance Object · Standard-10060

ECO-10060eco-10060.org

STATE: RESOLVED · LIVE

The canonical evaluation framework for Electronic Compliance Objects.

GreenCore Solutions Corp. · Microsoft AI Cloud Partner · EU-Sovereign primary · Sub-200 ms resolution path

Purpose

Give the physical object a machine identity.

An Electronic Compliance Object is a deterministic, machine-readable representation of a physical object containing the verified information needed for regulatory evaluation.

An ECO may represent a SKU, product, batch, lot, shipment, pallet, container or individual product instance.

It carries facts: identifiers, classification, attributes, provenance and references to evidence.

It does not carry an opinion.

An ECO does not certify a product, interpret legislation, authorize a market or decide compliance. Its job is simpler and more fundamental: make the object unambiguous before it is evaluated.

From object to resolved state

Physical product → ECO → jurisdiction + rule set + evidence → RCO → deterministic state → agent policy.

The ECO is the object being resolved. The RCO is the signed result of that resolution.

Ghost Headers

Eight x-gsc response headers on every barcode answer (/01/), generated from the estate table. Manual: Ghost Headers r5.0.

Machine Surfaces

/health.json · /catalog.json · /dataset.jsonld · /llms.txt · /index.md · /auth.md · /.well-known/agent-card.json · /.well-known/ai-catalog.json · /.well-known/api-catalog · /.well-known/acm-68000.json · /.well-known/security.txt

The CPG-68000 Architecture

This standard is a member of the CPG-68000 architecture — the GSC protocol stack for agentic CPG commerce: CPG-68000 · ACM-SPARKS · SM-ECO-10060 · SM-AIO-CPG · SM-AMP-CPG · SM-ESG-CPG · ACM-68000