Why conformance exists
Open protocols need independent implementations. Independent implementations need shared tests. Accord's conformance levels give builders a way to check whether their objects, transports, rail adapters and registry metadata match the current v0 expectations.
This helps avoid silent drift between SDKs, gateways, MCP wrappers and rail packages.
What the levels mean
L0 means schema-compatible. L1 means transport-compatible. L2 means rail-compatible against reference rails. L3 means security-compatible guardrail checks are present. L4 means registry-certified shape and cross-reference checks.
These levels are about protocol compatibility. They are not a statement that a verifier is honest, a bridge is safe or a script has passed external audit.
How teams should use conformance
Teams should run conformance during development, CI and release review. They should treat failures as compatibility issues, and they should document any intentional deviations clearly.
For real value, conformance should be one input into a broader safety process that includes audits, policy caps, signer controls, testnet history and operational monitoring.
FAQ
Does L4 mean production-ready?
No. L4 means registry-certified shape and cross-reference checks, not production certification.
Should every implementation run conformance?
Yes, if it claims Accord compatibility.
Open the conformance package
Use L0-L4 checks as compatibility evidence, not audit evidence.