Roadmap and status

Roadmap

Where OPFiles is today and the direction it is heading, as a slim, forward-looking view of the standard and its reference tooling. Ordering beyond what has landed is indicative, not a commitment.

Available nowWhat comes next

Landed

Available now

The specification is a draft: the store layout, the release triad, the record model, the enforcement posture, and the residual disclosures are defined.
The specification permits adoption with hand-maintained files and your own checks. Assistant-driven adoption is the recommended path; adopt-by-hand is the fallback.
The reference tooling: opf init opf render opf doctor opf absorb opf record (absorb with read-only changelog drafting and freeze-digest output; record with create, transition, done-with-receipt, and worklog-append). The ordinary opf import modes are retired and refuse with exit 2, and opf upgrade refuses with exit 2, since the reference tooling defines no store upgrade.
Conformance is self-asserted and says so; no unqualified conformance claim is emitted.

What comes next

opf migrate and opf sync, two of the standard's ten command verbs, are planned and currently exit 2 (not yet implemented) in the reference CLI.
Full module record schemas remain planned. Digest canonicalization is already implemented in the reference release and changelog helpers.

Later

Conformance tooling and the conformance-report vocabulary in action, so a claim can be reported against the base and each evaluated profile rather than self-asserted.
A rendered, drift-gated web version of the specification and quickstart (see the standard).

Ordering among the "next" and "later" items is indicative; the standard fixes the posture each must honour, not a shipping date.