ContractObject / content model
- Job
- What the UI is about
- Requirement
- must specify
- States / rules
- Types, required fields for list/card/editor, relationships
- Specified means
- Objects named before components
- Hardest context
- Card with no object
Example
Article: title, status, updated
Counter-example
Pretty Button on an untagged sitemap
How this lives in Building Blocks
Representation: Product-local decision contract.
Building Blocks can provide the schema for documenting objects and required list/card/editor fields. The consuming product owns the actual objects and relationships.
Do not specify the easy case only.
The source checklist’s hardest-context test is part of what “specified” means: Card with no object.
On-spec signal
Article: title, status, updated
Failure signal
Pretty Button on an untagged sitemap
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.