Conformance criteria for implementations
Assess fit under the active protocol model
Reference model
Draft v0.1 is explicit and boundary-aware
ReferenceMeaningDetailsUse
Message conformance
Envelope fits
Active envelope and required refs are used
Message
Lifecycle conformance
State movement fits
Participation fits states and transitions
Lifecycle
Validation conformance
Checks match
Admissibility logic stays compatible
Validation
Protocol format
Concrete JSON for the active Draft v0.1 surface
Protocol format
Conformance shape
Implementations conform by preserving the contract
Conformance
required
{
"protocolVersionRef": "protocol_v0_1",
"messageEnvelope": "required",
"lifecycleContext": "required",
"validationResult": "required",
"privatePayloadEmbedded": false
}Operating rules
Protocol stays separate from Relay and execution
Compatible products can differ
Compatibility preserves the contract across different products