machine .toml source > generated view > drift gate

Roadmap and status

Roadmap

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

Now

  • The specification is a stable draft: the store layout, the release triad, the record model, the enforcement posture, and the residual disclosures are defined.
  • Adopt-by-hand is supported and first-class: you can conform with hand-maintained files and your own checks.
  • Part of the reference tooling has landed: opf init, opf render, opf doctor, and opf upgrade, plus opf import with its scan, plan, review, and apply modes.
  • Conformance is self-asserted and says so; no unqualified conformance claim is emitted.

Next

  • The schema release that follows this specification fixes the normative module schemas and the digest canonicalization the freeze gates depend on.
  • The remaining verbs: store relocation (opf migrate) and the surfaced sync step (opf sync).
  • The assistant-driven adoption flow: pointing an AI development assistant at the site to investigate, plan, and, on your yes, carry out and merge the adoption, with the .working/ store left for your review.
  • The machine-readable discovery entry point for assistants: an /llms.txt index plus a generated /adopt.md and a root-page link an assistant can follow.

Then

  • 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 "then" items is indicative; the standard fixes the posture each must honour, not a shipping date.