Versioning
Canonical versioning and compatibility posture
This reference defines how protocol change is published, how compatibility is understood, and how the active model remains legible over time.
Status
Draft v0.1 canonical reference
Role
Defines publication and compatibility posture for protocol evolution.
Use
Use this page when evaluating whether implementations align with the active protocol version.
Versioning model
Rule changes must remain explicit and compatibility-aware
Protocol change only remains credible when evolution is visible. Participants need to know what changed, what remains compatible, and which model is currently in force.
Schema remains legible
Protocol evolution requires explicit structure changes rather than silent drift in message shape or interpretation.
Compatibility remains intelligible
Participants need to know whether they operate under compatible message forms, references, and transition rules.
Publication remains explicit
Rule changes are published as identifiable releases rather than treated as invisible implementation details.
Boundary note
Versioning governs model change, not local implementation drift
This surface governs public protocol change. It does not justify unannounced divergence through private implementation conventions.
What this surface governs
Visible protocol change, active-version posture, and compatibility logic.
What remains outside this surface
Private local drift that is not published as protocol change.