One checklist. Three different questions.
The checklist says what a consuming product must have an opinion about. Building Blocks can still make a reusable baseline component available before a product needs it, and the product-local Catalog remains the authority on what that product actually specified, designed, and implemented.
Product cannot ship the relevant UI without an explicit opinion.
May deferAllowed only by naming the job not needed and who decides.
ConditionalActivates when the product has the named job.
Baseline availability is not the same as product adoption.
Tabs can be a complete reusable Building Blocks component even when a particular product legitimately defers Tabs. Conversely, a product’s component does not become In code just because Building Blocks has an implementation elsewhere.
68 visible jobs
Foundation
Components by job
Patterns
Proposed baseline additions
External benchmark research surfaced recurring jobs that are not in the authoritative checklist. They remain proposals until explicitly approved.