Contracts¶
Contracts define the human-readable obligations for canonical objects. Machine enforcement is provided by the corresponding JSON Schemas.
Every object contract defines:
- an object type;
- its registered OID prefix;
- required base metadata;
- type-specific required fields;
- valid lifecycle behavior;
- provenance and relationship expectations.
The repository includes contracts for all initial canonical object types under /contracts.
A contract constrains representation and stewardship. It does not determine whether an object's claim is true.