Concepts

You will be able to explain why Commission is shaped the way it is — what is derived rather than stored, what is refused rather than recorded, and which trade-offs were made on purpose — well enough to extend it or to argue with it.

Concepts pages explain. They do not instruct (that is Guides) and they do not enumerate (that is Reference). A concepts page that cannot state the alternative it rejected is not finished.

Pages

page	you will be able to	status	owner
architecture.md	Trace a command from the CLI through the core to SQLite, see why the HTTP API, web view, MCP server, and adapters are all thin consumers of one writer, and read each storage decision with the reason it was made.	written	relay-61
principles.md	State each design rule — one truth with derived views, refusals as prompts, one recursive task entity, gates as data, parallel by default — and what each one costs.	planned	relay-61
data-model.md	Describe tasks, dependencies, criteria, evidence, bindings, and the append-only event log, and say which facts are stored and which are computed.	planned	relay-61
decisions.md	Understand the deliberate omissions — no estimation, no settable blocked status, no configurable workflow, no silent automation — as decisions rather than gaps.	planned	relay-61

architecture.md states each principle with the alternative it rejected and the cost it carries, and ends with the deliberate omissions. The three planned pages go further into one area each; until they exist, the architecture page is the answer.

Vocabulary lives elsewhere

The definitions of task, task graph, ready frontier, blocked, claim, actor, gate, evidence, acceptance criterion, refusal, context bundle, note, event log, touches, divergence, binding, execution policy, approval, workspace, drift, inbox, and ask/answer are in positioning.md §6, and that is the only place they are defined.

Concepts pages use those words with exactly those meanings and link to the table. They do not restate it, because two definitions of gate in one repository is precisely the drift commission exists to make impossible.

The same applies to the arguments: the case against a general tracker, against a coding agent’s memory, and against a project management tool is made in positioning.md §3, and the objections are answered in §4. Concepts pages go deeper into the implementation of those claims; they never restate the claims in new words.

What is shipped

Anything a concepts page describes in the present tense must appear in the shipped list of positioning.md §8. Planned capabilities are described as planned, with their task id, or not at all.