The product thinker approves a goal's scope once

Press Release

The product thinker approves a goal's scope once and abcd builds just those ideas within a budget: the approval is a decision record naming the member intents, tagged on each as target_release is; a filtered build next runs them through the capped one-yes drive, each new draft still crossing to planned through its own sign-off, and the run ends when every member's acceptance is audited, one is handed back, or the budget is spent, reporting in plain language which acceptance criteria now hold.

Why This Matters

Why this matters to the user — replace before planning.

Mechanism

Prompted (the claim-recording gradient): why the authors expect this to work, as a falsifiable "we expect X because Y" — not the outcome restated. Replace this line with the claim, or with the exact token None stated. alone on its line to record the claim as considered and declined.

Scope Conditions

Required (the claim-recording gradient): the population, platform, scale, or assumptions this claim holds under, one per top-level bullet — abcd intent plan stamps each with a persistent identity. Replace this line with those bullets, or with the exact token None stated. alone on its line.

Acceptance Criteria

Required (the itd-1 discipline): add at least one Given-When-Then bullet describing the verifiable bar for "shipped" before this draft can be planned.

Decisions

Answered by the product thinker on 2026-11-01.

1. The budget counts ideas: the product thinker approves a goal with the most intents the run may build, the number they can judge; agent runs and a deadline are later additions if a count proves too coarse.
2. A stuck idea does not stop the goal. When one member is handed back for a decision, the run carries on with the members that do not need it; where a later member depends on the stuck one, abcd makes a provisional decision and records it with its grounds (abcd decide), so the run never builds on an unrecorded guess.
3. The product thinker reviews every provisional decision once the run ends, and each review is recorded: kept, or reverted with what reverting it took (the rework, the pull requests and the runs it cost), so how often abcd's provisional calls hold is measured rather than assumed.
4. A goal starts from the brief: the product thinker picks one of the outcomes abcd offers from the brief's unrealised sections (see the goal view on itd-2610070550516046); a new direction is a brief edit first.
5. What is computed and what is recorded. The goal view on itd-2610070550516046 stays computed and stores nothing about the goal; only the product thinker's approval is recorded, as a decision record and a tag on each member intent, the way target_release is.

Open Questions

None recorded yet.

Audit Notes

Empty. Populated by intent-auditor when intent moves to shipped/.