Implementation

This page records implementation evidence from earlier XCIM working drafts and managed pilots. Individual results must not be promoted to general implementation or interoperability of the corrected consent protocol. The current scope and publication status are linked below; each pilot has a separate report and observation date.

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: Emabled

This page describes one implementation, not a required issuer or product. The Working Draft and schemas record the earlier product-independent design. Working-draft publication does not upgrade a running implementation.

Emabled implements the managed XCIM Consent Issuer and operator surfaces used in earlier managed XCIM pilot tests. The deployed sandbox supports company and ESP workspaces, OIDC-based identity evidence, issuer-hosted consent, application and manifest publication, signed receipt issuance, revocation, authorized list evaluation, lifecycle webhooks and public signing keys. Its first public event/state roots and proof set are anchored on a Polygon test network. This historical snapshot does not provide continuously fresh status.

A profile-neutral Identity Evidence layer is implemented. An experimental EVP-01 adapter is deployed for vendor-origin handoff; EVP inside Emabled Hosted Consent remains unavailable. Public delivery-mode capabilities are available at the issuer capabilities endpoint. Profile status is driven by identity-evidence.json.

Surface Current implementation Boundary
Operator console OIDC authentication, hosted-consent onboarding, MFA and workspace controls Separate company and ESP roles; authorized pilot access
Identity evidence OIDC-01 managed pilot; experimental EVP-01 vendor-origin handoff Profile maturity is not external standards status
Consent issuer Issuer-hosted consent session using a versioned manifest Reference flow, not universal conformance
Receipts and revocation KMS-backed Ed25519 signatures and lifecycle worker Emabled issuer semantics
Application identity XCIM Application ID, application key, metadata and current domain bindings Independent of any one OAuth client
Public discovery Issuer key set and service health No public XCIM registry or resolver yet

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.

Choose your integration role

Company: your site to a signed receipt · ESP: client access to CSV results

The Company operates the product and collects decisions; the ESP evaluates lists within that application’s authorization. One organization may perform both roles in separate areas. A provider login verifies identity; it is not a consent grant. Google was used in these managed tests, not required by XCIM.

Deploy to Agents, 6–10 November 2026: durable backend signing, receipt continuity and managed CSV results. Public verification was unavailable for its matching row. The complete implementation report lives on xcim.net.

Company and ESP integration

  1. The company configures its application, signed manifest, sending domain and consent return.
  2. The recipient uses an admitted identity method and chooses optional purposes on the issuer-hosted consent page. Registration and marketing permission are separate decisions.
  3. Emabled signs the receipt and returns it through the bound application flow.
  4. The company authorizes an ESP for a specific application, purpose, domain, validity period and list budget.
  5. The ESP submits JSON jobs or uploads CSV/ZIP through its workspace, then downloads authenticated results.
  6. Authenticated revocation changes current permission state; a later evaluation reflects the revoked permission.

Managed list results report issuer permission. The pilot observed EMABLED_CONSENT_ACTIVE, XCIM_REVOKED and XCIM_NONE. An active issuer result is not a public proof XCIM_PASS. A separate receiver verified the first test-network snapshot within its signed freshness window; that is not a current result for every list row or a completed fresh CSV/ZIP public-proof replay. List evaluation does not establish mailbox existence or inbox placement.

Historical working-draft identity profiles

Maturity labels below describe XCIM profile maturity, not the standards status of the external protocol. They do not establish implementation of the corrected C01 profile.

ProfilePurposeMaturity
EVP-01Email-provider-backed address controlExperimental
OIDC-01Identity-provider-backed authenticationSupported draft profile

Protocol roles

Identity Issuer
Provides independently verifiable identity evidence, such as EVP or OIDC evidence.
XCIM Consent Issuer
Validates acceptable identity evidence, presents the Consent Manifest, records the decision, and signs the XCIM receipt.
Application
Requests consent for a defined application identity, manifest and purpose.
Sender
Attaches the XCIM reference and proof to a message.
Verifier
Validates evidence and applies local trust and delivery policy.

Application identity

The XCIM application identity is not defined by an OAuth client. It is anchored by the XCIM Application ID, application key, metadata, and current domain bindings. OIDC client IDs are profile-specific integration metadata.

Verification sequence

  1. Identify the sender, recipient and communication types being evaluated. Consent verification is independent of an individual email; a mail integration authenticates the sender separately.
  2. Resolve the issuer and select an explicitly trusted assurance profile.
  3. Validate proof signatures, application and domain bindings, time limits and anti-replay context.
  4. Resolve current permission state; stale or unavailable state remains indeterminate.
  5. Return a structured result to local receiver policy.

Interoperability boundary

The deployed Emabled flow demonstrates implementation feasibility. Draft schemas, serialization decisions and vectors are already published. Independent conformance still requires reviewed profile external review, ongoing fresh public proofs, resolver distribution and tests between independent implementations. No implementation should treat the sandbox as a production trust root or sole abuse control.