The model
Source, view, and drift gate
Model
In 1 file
Edit the source. Run the renderer. Check the view.
.working/toml/backlog_item.index.toml
schema = 1
[[record]]
id = "BI-1"
type = "backlog_item"
status = "active"
title = "Add the drift gate to CI"
created_at = "2026-09-01T14:02:11Z"
updated_at = "2026-09-04T09:37:48Z"
actor = { kind = "assistant" }.working/BACKLOG.md
Generated by opf render --write from backlog_item.index.toml and block.index.toml. Do not edit; edit the store and regenerate.
BACKLOG
BI-1activeAdd the drift gate to CIactionable
Illustrative excerpt. You edit the TOML. The Markdown is generated. When configured as a required check, the gate compares the view with a fresh render of its sources.
In the box
What is in the box
The specification defines 12 baseline record types and 10 command verbs; the reference scaffold declares 13 generated views. The record types are 11 typed indexes plus the worklog ledger, each with a closed schema that refuses what does not fit. The scaffold declares 12 Markdown views and 1 TOML projection. The verbs: init, adopt, import, doctor, render, migrate, sync, upgrade, absorb, record.
Limits
What the checks establish
Schema validation and drift checks are intended to catch structural defects; they do not establish that a record's claims are true. Review recorded claims against their evidence.
Next
Next, read the manifest that declares every pair and the 4 files beside it.
The 5 core store files