Base120 · Composition

Interface Contracts

CO · Composition

Define explicit agreements about data structures and behavior between components

Model code
CO9
Transformation
CO (Composition) — Combine elements so the integrated value exceeds the sum of parts.
Priority
9 of 20
Framework
HUMMBL Base120 — 120 mental models across 6 transformations

When to use

"Use when components need to interact and you want to enable independent evolution. Define explicit contracts (data structures, behaviors, error modes) so that changes inside one component do not break others."

Example

"A REST API contract specifies that GET /users returns an array of user objects with id, name, email. The database schema can change, the internal caching can change, the programming language can change — as long as the contract is honored, clients do not break."

Common misuse

"Contracts that are too tight (overspecify implementation details) or too loose (underspecify error cases). A good contract specifies what clients depend on and nothing more."

Also known as

API ContractsInterface Agreements

Related models

CO8CO12P18