- Job
- Which store leads
- Requirement
- must specify
- States / rules
- Six names for seeing: Standard, Checklist, Catalog page, Product spec, Git, Live catalog. Persistence: Catalog store (own file). Koyn is tasks.
- Specified means
- Change path written
- Hardest context
- Next Make export overwrites tokens
Git CSS writes; live catalog shows the fill
Three SoTs; reviews designed from the Catalog page file alone
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: Next Make export overwrites tokens.
On-spec signal
Git CSS writes; live catalog shows the fill
Failure signal
Three SoTs; reviews designed from the Catalog page file alone
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.