Tools and access
The implementers program will publish the shortest path from a sample message to a reproducible interoperability result.
This inventory is deliberately honest about maturity. A planned tool is a tracked deliverable, not a downloadable placeholder.
| Resource | Status | Use |
|---|---|---|
| Protocol documents | Available | Read scope, roles and publication status |
| Emabled reference sandbox | Available by request | Run the managed issuer flow ↗ |
| Implementer source repository | Draft published | Review source and contribution policy ↗ |
| Issuer public keys | Published | Verify reference signatures ↗ |
| Schemas and canonical bytes | Published draft | Review JSON schemas and serialization notes |
| Test vectors | Published draft | Run positive and negative fixtures locally |
| Conformance runner | Unified Python + Node | Run every check locally or in CI |
| Shadow-mode header adapter | Published draft | Parse D-001 headers without changing delivery policy |
| Public artifact security scan | Automated in CI | Review checks and remaining manual gates |
| Reference resolver | Not released | Independent verification profile remains under review |
| Identity Evidence profile status | Published metadata | Review EVP-01 and OIDC-01 maturity; no public EVP fixtures are claimed yet |
| Implementation reports | Opening with cohort | Versioned evidence from independent implementers |
Repository plan
The public source keeps specification, schemas, fixtures, examples and implementation reports together so changes remain traceable. The draft source drop is available on GitHub ↗; schemas, vectors, registries and local runners are published for review. Standalone SDKs and a resolver repository will split out only when their interfaces are stable enough to support independently.
The source drop contains XCIM artifacts and OIDC-related draft vectors. EVP-01 fixtures will be published only when they are real, reviewable and safe to share; this page does not imply an EVP implementation is available in Emabled.
xcim/
├── spec/
├── schemas/
├── test-vectors/
├── examples/
├── implementation-reports/
└── tools/Request access
Tell us whether you are an ESP, mailbox provider, ISP, gateway, issuer, SDK or research team, what you want to test, and who owns the integration. Early Partners are paired across sending and receiving roles for a focused shadow-mode window. Sandbox access is non-production and subject to a short technical review. Use the intake template to make the scope and evidence plan explicit.