Record index
block.index.toml
Blocks, namespace BL, at
.working/toml/block.index.toml.
About
A block records that named work cannot proceed. It scopes an enumerated list of
record IDs, is active until released or expired, and
feeds the actionability rule: a backlog item is actionable when it is open or active and no
unqualified active block scopes it.
Why
"Blocked" is one of the easiest states to abuse: it can park inconvenient work indefinitely.
The standard makes a block a scoped, auditable record rather than a mood, and gates its
creation: a block created by an assistant or automation is active/proposed, a
proposal that hides nothing and justifies no stop until a maintainer ratifies it. Moving work
to blocked is the maintainer's decision, structurally.
Description
The shared index shape with the standard envelope plus scopes, the enumerated
record IDs the block covers. States: active (initial, gated) to
released or expired (terminal). Blocked-ness is never stored on the
scoped records; it is derived at view time through the block join.
How it works
The block-actionability join is one of exactly two named joins in the closed transform vocabulary: an unqualified active block hides the records it scopes from actionable views; a proposed or terminal block hides nothing. Active blocks never rotate to the archive.
Generated view
BLOCKS.md, composed from this index, plus the block join rendered inside
TODO.md, BACKLOG.md, and PIPELINE.md; optional
BLOCK-INDEX.md mirror. All byte-drift-gated.
Value
Blocks that are visible, scoped, and ratified, which helps prevent manufactured stops: work reads as blocked only on a grant the record can show.
Usage
- Created by:
opf init(empty index); maintainers directly; assistants as gated proposals. - Updated by: ratification, release, or expiry transitions.
- Read by:
opf render(BLOCKS.md and the actionability join in the three backlog views);opf doctor(schema, gated-state legality, scoped-ID resolution).