Platform
Make design intent explicit.
A LITHIC contract records the requirements that govern a construction decision.
Updated
What a contract establishes
A model can describe a wall without establishing what that wall must achieve. A contract connects the intended construction system to explicit project requirements, so a recipe and product selection can be assessed against a recorded basis.
A wall example
An internal partition may need a specified build-up, thickness and performance evidence. Record those requirements, identify the recipe that is intended to satisfy them, and keep missing evidence visible. A type name alone does not prove fire or acoustic performance.
How it connects
Identity establishes the element and exact model scope. System classification establishes its construction system. The contract sets the requirements; the recipe describes the build-up; material requirements and product selection connect that build-up to real products.
When something changes
A revised requirement needs a new decision basis. Review the affected recipe, products, price and carbon evidence before relying on a new result. A historical receipt should continue to describe the decision that was actually recorded.