XCIM Network status
Managed implementation evidence through 10 November 2026 · No production trust network
Latest specification · draft-saez-xcim-04
Experimental individual Internet-Draft. A bounded C01/SR01 testnet pilot verified consent reuse and revocation on 26 October 2026; production readiness remains open.
Reference implementation evidence
Inventory updated 2026-11-10. Each row retains its own observation scope and date. The 26 October C01/SR01 pilot, Deploy to Agents receipt/CSV pilot and frozen reference fixtures are separate evidence. No production trust network or independent ESP interoperability is claimed.
| Capability | State | Evidence and scope |
|---|---|---|
| C01/SR01 consent lifecycle | Verified bounded testnet pilot · 26 Oct 2026 | One fresh MuMaps consent: CURRENT, cached CURRENT without renewal, incremental REVOKED and persisted REVOKED. Both anchors verified under admitted testnet trust. Same operator; pilot closed; production gates remain. |
| Company onboarding | Verified managed site setup · 6–10 Nov 2026 | Deploy to Agents: new Company workspace, verified site domain, application registration, signed consent configuration and bound return. A developer and operator-assisted setup were involved; not measured as a completely unaided integration. |
| Application backend key persistence | Verified restart · 6 Nov 2026; new receipt/CSV · 10 Nov | Deploy to Agents retained a non-exportable Cloud KMS Ed25519 key across a real backend restart, verified its earlier receipt, issued a new receipt and completed ESP CSV evaluation. Domain roles, application credentials and ESP authorization retain separate expiry dates. |
| Identity and hosted consent | Verified managed pilot | MuMaps and Deploy to Agents exercised OIDC-01 using Google, followed by a separate explicit consent decision. The protocol permits admitted identity methods; these observations do not verify every provider or EVP. |
| Receipts and revocation | Verified managed pilot | Signed receipt issuance, authenticated API revocation and subsequent list re-evaluation were exercised end to end. |
| Managed ESP list evaluation | Verified managed pilot | Deploy to Agents, 10 Nov 2026: scoped ESP access, two-row CSV, authenticated export and persisted job after page reload; one EMABLED_CONSENT_ACTIVE and one XCIM_NONE. Public proof unavailable for the matching row. MuMaps separately exercised CSV/ZIP and revocation. |
| Lifecycle webhooks | Deployed; external test pending | Signed delivery infrastructure, company delivery history and recovery controls are implemented; an external receiver test remains a release gate. |
| Draft implementation artifacts | Published draft | Working Draft 02 with Erratum E1 publishes 33 unchanged schemas and corrected Python/Node tools, with 12 new E1 regression tests. Original WD-01 and WD-02 releases remain unchanged; synthetic checks are not live proof verification. |
| Public proof verification | Verified test-network snapshot | First public batch finalized on a Polygon test network: 19 events and four MuMaps proofs, checked by separate verification implementations. Historical evidence only; the five-minute status window has expired. Not mainnet or independent sender/receiver interoperability. |
| Emabled SDK distribution | Private packages tested | .NET and TypeScript integration packages have consumer tests; public npm/NuGet releases are pending. |
Managed pilot report · Shared implementation status JSON
Earlier pilot evidence is preserved in the historical test-network report. It does not demonstrate operational C01/SR01 conformance.
Identity Evidence metadata
| Field | State | Meaning |
|---|---|---|
| Identity Evidence schema | WD-02 profiles published | Explicit wire dispatch: OIDC-01 receipt 0.1, experimental EVP-01 receipt 0.2 |
| EVP-01 profile | Experimental / not network-critical | Experimental vendor-origin handoff deployed; not a receiver-time dependency |
| OIDC-01 profile | Reference implementation active | Google OIDC exercised in the separately dated MuMaps and Deploy to Agents managed pilots; other providers require their own verification |
These fields distinguish a profile definition, a reference implementation, an external experiment and production recommendation. They are not interchangeable. The shared source is identity-evidence.json.
Shared component status and remaining gates
| Component | Status | Remaining operational gate |
|---|---|---|
| Multi-issuer registry | Not public | Independent operating authority, admission review and signed lifecycle |
| Event and current-state roots | Published Amoy testnet snapshot | First batch published; ongoing fresh status requires renewed batches |
| Polygon anchor | Finalized on Amoy testnet | Batch 1 in block 50191125; no mainnet or production trust claim |
| Reference resolver | Not released | Reviewed package distribution and verification against current public evidence |
Draft tree algorithms and vectors are published. Public batch 1 adds real anchored evidence, but its expired snapshot does not establish current permission or continuous network operation.
Failure semantics
Missing sufficiently fresh current evidence produces
XCIM_STATUS_INDETERMINATE. Managed list evaluation exposes
issuer permission separately from public-proof availability.
EMABLED_CONSENT_ACTIVE must not be presented as
XCIM_PASS without verified, sufficiently fresh public evidence.
The historical test observed XCIM_STATUS_STALE after actual
expiry and XCIM_STATUS_INDETERMINATE at the cache boundary.
status.json · network-status.json · Pilot evidence · Support