How OCSS versions the spec.
The Open Child Safety Specification (OCSS) follows semantic versioning adapted for protocols. Patch versions are corrections. Minor versions add capabilities or rule categories. Major versions can break adopter contracts — and require a 90-day public review window.
Draft 4 · pre-release · Public review
Three kinds of release. One contract.
The version number tells adopters exactly how much work a release demands — from a no-op clarification to a breaking contract change.
Typo fixes, clarifications, additional examples. Adopters need not re-implement.
New capabilities, new rule categories, new jurisdictions. Backwards-compatible. Adopters opt in.
Breaking changes to capability contracts. 90-day public review. Charter Adopter sign-off required.
How rules retire.
- 01Deprecated rule categories remain enforceable for at least one minor version after announcement.
- 02Major-version removals require a 90-day public review and Charter Adopter sign-off.
- 03Every deprecation is announced in the changelog with a migration path and a sunset date.
- 04Adopters can pin to a spec version; the Receipt stamps every receipt with the active spec.
Every change, in one place.
The OCSS changelog records every patch, minor, and major release with the corresponding rule registry diffs.