XCIM interoperability
Public evidence for implementers testing the XCIM draft across sending, receiving, Identity Evidence and infrastructure roles.
Current evidence
| Capability | State | Evidence | Next gate |
|---|---|---|---|
| XCIM Consent Issuer | Operational sandbox | Emabled public issuer surface ↗ | Pair with an independent implementation |
| Hosted consent and receipts | Implemented by Emabled | Public keys ↗ | Pair with an independent implementation |
| Identity Evidence schema | Drafting | Profile-neutral status metadata | Freeze profile-neutral receipt fields |
| OIDC-01 adapter | Operational sandbox | Emabled reference implementation | Publish vectors and independent test |
| EVP-01 experimental adapter | External experiment / in development | No XCIM end-to-end result published | Complete cross-implementation test |
| Self-test suite | Published draft | Unified Python + Node runner with deterministic fixtures | Recruit independent sender and receiver |
| Independent sender | No public result yet | No implementation report published | First ESP cohort |
| Independent receiver | No public result yet | No implementation report published | First mailbox-provider cohort |
| Interop-tested pair | Not started | Two independent implementations required | Run a paired test window |
What qualifies as evidence
A public result must name the exact draft, implementation version, role, profile, test date, vectors exercised and known limitations. A logo, sandbox account or private demonstration is not an interoperability result. One EVP site working does not establish XCIM interoperability.
Receiver boundary
Receivers do not need to validate EVP or OIDC for every message. Identity Evidence is validated by the XCIM Consent Issuer at grant time; the receiver validates the signed receipt, current state, bindings and local trust policy.
Test windows
The schemas, positive and negative fixtures, and local runners are published for draft review. The first cohort and paired test dates will be announced as independent sender and receiver teams join; teams can request sandbox access and review the Implementers Program ↗.
Machine-readable interop status · Implementation matrix · Tools and access ↗