Layer 02 · Contracts
Architecture
Schema first, so the contract exists before the implementation does.
Layer 02 · Architecture
What the agents do
- Synthesise a typed schema for every entity and every boundary.
- Generate the API surface and the infrastructure configuration from those schemas.
- Fit the runtime to the product — cloud, edge, or fully air-gapped from a single flag.
What the machine refuses
- An entity or boundary that did not originate from a typed schema.
- A payload that fails validation — answered with a named error, never coerced.
- A dependency above the ceiling. This site runs on seven.
Where a person signs
Owns the contract
Schemas are reviewed as the design, because they are the design. A person reads the contract; nobody needs to read the generated code that honours it.
Check it: Every API on this site validates its payload against a typed schema and answers a bad one with a named error.
Methods
- Schema-first contract authoring
- Generated API surfaces
- Validation with named errors, never coercion
- Runtime chosen per product: cloud, edge, air-gapped
- A dependency ceiling, enforced
The other layers