Decisions

What counts as a decision

Only three things become a decision, and all three are acts by a person:

• A published interface. When a Task publishes the shape other Tasks build against, that shape is a decision, versioned so "which version did you build against" is always answerable.
• A rule. Project and Task rules are standing choices; changing one records the new choice and retires the old.
• An answer. When an engine asks and you answer, your answer is a decision. This is the one every Task produces.

An engine's own account of its work is not a decision. It is recorded as an accepted outcome — evidence a decision can derive from, never authority in its own right. Nothing an engine writes can quietly become project policy.

What a decision governs

A decision is anchored to the ground it covers: the files a Task wrote, the Task itself, its mission, a Design frame, a Project Map node. Anchors are how a Task about to touch src/features/checkout/ finds the choices that already govern it, without anyone tagging anything by hand.

How it reaches the next engine

Decisions are recalled structurally, not by keyword similarity: given the files a round is about to touch, Iterel walks the anchors and the links between decisions and returns the ones that govern them, with their citations and where they came from. They enter the round above continuity and below your instruction — policy, not history.

Because the Context Pack carries no engine or provider, a decision reached in a Claude Code round is read by a Codex round with no re-briefing.

Needs re-confirming

If a producer republishes an interface after another Task already built against the older version, that Task's decision is marked contested. Nothing is auto-restarted and nothing is blended: both sides are shown, to you and to the engine, and the engine is told explicitly not to merge them. Contested decisions appear in the Command center as Decisions to re-confirm.

Availability

Decisions are recorded today. Structural recall into runs is landing; until it is verified in your project, decisions are stored and shown but not yet walked into every round. Decisions are a collaborative-project capability and require the cloud store.