Discover
GET /api/delivery to resolve the current public release, its manifest, acceptance record and verifier.
The public interface is intentionally narrow: read a delivery index, fetch the exact artifacts, verify package identity, then consume the descriptive market state inside its declared boundary.
Claim boundary · DESCRIPTIVE_STATE_EVIDENCE_ONLY · ACTION_GATE 0 · predictive_claim NONE
GET /api/delivery to resolve the current public release, its manifest, acceptance record and verifier.
Download RELEASE_MANIFEST.json and the referenced MARKET_STATE.json from the release path.
Run the delivered consumer verifier outside the CMM.X repository or reproduce the SHA-256 checks independently.
Use only fields and semantics declared by the release. No action permission or directional interpretation is implied.
GET /api/deliveryCurrent release index and claim boundaryGET /api/evaluation-kitCurrent D2 evaluation kit, release binding and validator referencesGET /api/healthRuntime freshness, chain and pipeline healthGET /api/coordinateCurrent descriptive structural coordinateGET /api/chainAppend-only chain stateGET /api/attestationPublic attestation materialGET /api/reproduceReproduction status exposed by the observerDo not trust a rendered card. Resolve the release, hash the delivered bytes, check the manifest, run the verifier and only then parse the market-state payload.
curl -fsS https://observer.cmmx.systems/api/delivery
curl -fsS https://observer.cmmx.systems/static/delivery/first_real_market_delivery_v1/releases/seq_75239_20260908T202900+0000/RELEASE_MANIFEST.json
# fetch the verifier from the release index, copy the release outside CMM.X
python3 verify_release_v1.py /path/to/copied/release
# accept only PASS; then consume MARKET_STATE.json inside its claim boundaryDefine your consumer, retention requirement and verification boundary before any pilot output is treated as operational evidence.