2026-10-04 (the product thinker, working hypothesis, not a ruling): a brief is the product thinker's target design, written in present tense as the vision of the finished product; abcd makes it real step by step through the technical facilitator, deterministically: each brief section lists the intents and implementations that realise it, and a brief change is assessed for a new intent or issue, or for a contradiction with a filed, planned or built intent, which owes the product thinker a design decision. Under test on another repository; a state-of-the-art pass follows. Recorded on itd-61, itd-142 and itd-143.

Frontmatter

.abcd/work/decisions/dcn-2610040000000006-a-brief-is-the-product-thinker-s-target.md
open on GitHub ↗ · commit history ↗

mentions3

• itd-61A Human Edit To The Brief Cannot Commit Until Its Implied Intents And Principles Are Drawn Out And Reconciled
• itd-142The brief-creation interview: abcd elicits a repository's brief in a staged conversation — narrative first, then frontier rounds that ask only what the record cannot yet settle, options at conjectural questions (at most three candidate construals, a ceiling not a target, with a null answer always available), and a per-item confirmation — distilling committed products into the brief and a ledger while the transcript is discarded. Entry is one door for both modes: a brownfield repository arrives pre-populated from embark probe coverage, provenance-stamped and still requiring confirmation; a greenfield repository is the same interview run from the all-blank coverage state. Command-shaped, because it mutates state — abcd ships zero skills
• itd-143The brief gains a framing chapter under 01-product/ — the macro-why home: one section holds the project's framing, the why behind the why, and receives the brief-creation interview's committed framing products; the brief-lifeboat mapping gains the matching row so a lifeboat carries framing like any other section