- Job
- Product intent only the product owner can supply
- Requirement
- Required
- States / rules
- One Q at a time: labeled DRAFT from known context, then wait. His response is the answer. Companion: standard Layer 1 hard stop (v1.4).
- Specified means
- Spec quotes his responses from this conversation; unanswered drafts stay UNCONFIRMED DRAFT
- Hardest context
- Agent about to write tokens/atoms with no sitting
Draft shown; he agrees or changes; spec updated after
Agent filled the Q table from a plan or from an unanswered draft and stamped confirmed
How this lives in Building Blocks
Representation: Product-local decision contract.
Building Blocks can provide the intake structure and hard stop. The product owner supplies and confirms the actual product intent; a prototype or plan cannot silently answer it.
Do not specify the easy case only.
The source checklist’s hardest-context test is part of what “specified” means: Agent about to write tokens/atoms with no sitting.
On-spec signal
Draft shown; he agrees or changes; spec updated after
Failure signal
Agent filled the Q table from a plan or from an unanswered draft and stamped confirmed
Catalog connection
The product-local Catalog should show this row’s actual state for that product using the Catalog contract. Building Blocks documentation can define the baseline, but it does not make a product’s row Specified, Designed, or In code by itself.