The format moves to OKF v0.2
- Decided
- 15 August 2026
- State
- binding
The base contract is OKF v0.2, adopted in one change — profile, okf_version,
fixtures and tests together. No dual-version support, no migration framework.
With it, the format takes v0.2's vocabulary instead of keeping private
divergences: the reserved status lifecycle key belongs to OKF, so our
user-facing property is renamed (see
state, not status); timestamp gives way to
generated: {by, at} with OKF actor strings naming who wrote the file.