- Job
- Honest scope
- Requirement
- must specify
- States / rules
- Defer names the job not needed and who decides
- Specified means
- Invalid: “Make had billing”
- Hardest context
- Promoting leftover because it existed
“Analytics leftover until a weekly job exists — Vincent”
“N/A because prototype”
How this lives in Building Blocks
Representation: Operating / governance contract.
Building Blocks should provide the operating rule, review path, and source-of-truth guidance. A consuming product still records its product-specific answer and does not treat central governance as operational unless it actually exists.
Do not specify the easy case only.
The source checklist’s hardest-context test is part of what “specified” means: Promoting leftover because it existed.
On-spec signal
“Analytics leftover until a weekly job exists — Vincent”
Failure signal
“N/A because prototype”
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.