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.

PROTOCOLInternet-Draft -04
EMABLED CONSENT ISSUEROperational sandbox
COMPANY / ESP PILOTVerified
PUBLIC KEYSPublished
PUBLIC PROOF PATHAmoy testnet snapshot

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.

CapabilityStateEvidence and scope
C01/SR01 consent lifecycleVerified bounded testnet pilot · 26 Oct 2026One 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 onboardingVerified managed site setup · 6–10 Nov 2026Deploy 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 persistenceVerified restart · 6 Nov 2026; new receipt/CSV · 10 NovDeploy 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 consentVerified managed pilotMuMaps 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 revocationVerified managed pilotSigned receipt issuance, authenticated API revocation and subsequent list re-evaluation were exercised end to end.
Managed ESP list evaluationVerified managed pilotDeploy 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 webhooksDeployed; external test pendingSigned delivery infrastructure, company delivery history and recovery controls are implemented; an external receiver test remains a release gate.
Draft implementation artifactsPublished draftWorking 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 verificationVerified test-network snapshotFirst 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 distributionPrivate 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

FieldStateMeaning
Identity Evidence schemaWD-02 profiles publishedExplicit wire dispatch: OIDC-01 receipt 0.1, experimental EVP-01 receipt 0.2
EVP-01 profileExperimental / not network-criticalExperimental vendor-origin handoff deployed; not a receiver-time dependency
OIDC-01 profileReference implementation activeGoogle 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

ComponentStatusRemaining operational gate
Multi-issuer registryNot publicIndependent operating authority, admission review and signed lifecycle
Event and current-state rootsPublished Amoy testnet snapshotFirst batch published; ongoing fresh status requires renewed batches
Polygon anchorFinalized on Amoy testnetBatch 1 in block 50191125; no mainnet or production trust claim
Reference resolverNot releasedReviewed 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