Record, render, check, commit.
Operational records, governed like code.
Project records kept in chat logs and hand-edited Markdown drift from what the tools did, so nobody can cite them in a review, an audit, or a handover. OPFiles pairs machine-written TOML records with generated human-readable views. A drift gate, configured as a required check, re-renders the declared views and fails the build when a view and its sources disagree.
See how it holds together
Start here
- See the model3 partsSource, view, and drift gate in 1 diagram, with a TOML record beside the Markdown it generates.
- Read the standardspecWhat the specification defines, its conformance language, and its draft status.
- Know the core store files5 filesThe manifest, the ID counters, the version ledger, the worklog, and the lease.
- Adopt it10 verbsAsk your assistant for a plan, review it, then authorize; the 10 command verbs and their status.
What it gives you
OPFiles keeps each record in a fixed, machine-written form and generates the readable version from it; a check, set as a required step, fails the moment the 2 disagree. The standard forbids reusing a record's number or deleting a record. OPFiles is part of AIQT Guardrails (opens in a new tab), and both live in 1 repository: an AIQT adoption sets OPFiles up by default, and you can adopt OPFiles on its own. It is open source under the Apache License 2.0, except vendored third-party material, which remains under its own terms. Reference CLI status. Available: init, render, doctor, absorb. Partial: record (create, transition, done-with-receipt, and worklog-append; receipt-repair exits 2), adopt (plan, approve, reconcile, and status; apply and complete exit 2). In progress: upgrade, import, migrate, sync; each exits 2 in this build.
About this project