The standard
The specification, and how to read it
Scope
The standard requires a tracked git store and a review flow. Schema and drift checks are intended to catch structural defects; review recorded claims against their evidence. The reference tooling initializes stores at base 1.2.0; it does not yet implement base 2.0.0.
Read OPF-SPEC.md (opens in a new tab); read the quickstart (opens in a new tab).
Coverage
What the specification defines
- Store layout and naming
- Pointer and discovery model
- Git-repository and migration rules
- Release triad and its gates
- Record model and status grammar
- Views and the closed transform vocabulary
- Enforcement posture
- Rotation and archive
- Import
- The genericization boundary
- The conformance vocabulary
- Residual-coverage disclosures
Conformance
Conformance language
Conformance language follows common standards practice; statements without these keywords are descriptive.
| Keyword | Meaning |
|---|---|
| MUST | An absolute requirement. |
| SHOULD | A strong recommendation, departed from only for a recorded reason. |
| MAY | Genuinely optional. |
Draft status
Draft status and self-asserted conformance
Rule
Until the validation tooling covers a given claim, conformance to that claim is self-asserted, and a report says so: an unqualified "conformant" claim is never emitted, by tooling or by prose.
The specification is dated 2026-10-24.