XCIM interoperability
Public evidence for implementers testing the XCIM draft across sending, receiving and infrastructure roles.
Current evidence
| Capability | State | Evidence | Next gate |
|---|---|---|---|
| Emabled reference issuer | Operational sandbox | Public issuer surface ↗ | Pair with an independent implementation |
| Hosted consent and receipts | Implemented by Emabled | Public keys ↗ | Pair with an independent implementation |
| 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, test date, vectors exercised and known limitations. A logo, sandbox account or private demonstration is not an interoperability result.
Test windows
The schemas, positive and negative fixtures, and local runners are now 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 ↗