What does one system produce?
Output, request, force, signal?
One side presents something the other can consume or respond to.
Side 79 · Special
Interfaces
A study of what happens at boundaries. Interfaces define how two components, people, organizations or systems exchange matter, information, authority or action without needing full access to one another’s internals.
boundary→contract→exchange→mismatch→adaptation
06interface lenses
05mismatch modes
05design questions
79Side
An interface hides internals while exposing usable behavior.
Good boundaries reduce the amount each side must know about the other.
Where does responsibility switch?
Ownership line.
Ambiguous boundaries create duplicated or missing responsibility.
What must remain stable?
Format, dimensions, timing, semantics?
Contracts let internals evolve while preserving interoperability.
What assumptions does the receiver make?
Expected input.
Interfaces fail when assumptions differ silently.
How is failure or state communicated back?
Acknowledgment, error, resistance?
Feedback closes the interface loop.
Interfaces work because expectations are constrained.
A contract can be formal, physical, social or institutional.
Software contract.
Methods, schemas and error behavior let components interact without sharing implementation.
Physical contract.
Dimensions, tolerances and loads determine whether parts mate and function.
Sequence contract.
Communication systems agree on message order, timing and meaning.
Organizational contract.
Teams need clear inputs, outputs, ownership and escalation rules.
Shared contract across many parties.
Standards reduce bilateral negotiation and increase compatibility.
Biological selective boundary.
Cells regulate exchange rather than remaining open systems without control.
Interfaces often translate between incompatible representations.
Translation can change units, syntax, semantics, timing or physical form.
Format
Change representation.
Adapters convert one data or physical format into another.
Unit
Convert scale or dimension.
Unit mismatch can create catastrophic failure despite correct local calculations.
Semantic
Align meaning.
Two systems can use identical labels for different concepts.
Timing
Buffer asynchronous systems.
Queues and caches absorb timing mismatch between producer and consumer.
Impedance
Match physical transfer conditions.
Mechanical, electrical and acoustic interfaces lose energy when poorly matched.
Interface failures are often locally rational.
Each side can work correctly according to its own assumptions while the combined system fails.
| Mismatch | Example | System effect |
|---|---|---|
| Semantic | “Customer” means account on one side and person on another | Wrong aggregation |
| Temporal | Producer faster than consumer | Queue growth / dropped work |
| Dimensional | Parts within local tolerance but stack fails | Assembly failure |
| Authority | Both teams assume the other approves | Decision stall |
| Error handling | One side retries while other duplicates work | Repeated side effects |
Interfaces recur everywhere.
The concept becomes useful when the same boundary logic can be recognized across very different systems.
Component APIs.
Stable interfaces let services evolve independently.
Team handoffs.
Work crosses ownership boundaries through documents, meetings and systems.
Buyer–seller exchange.
Prices, contracts and standards coordinate parties with different information.
Cell membranes and receptors.
Selective exchange preserves internal state while responding to environment.
Mechanical and electrical connectors.
Interchangeability depends on dimensions, loads and signals being standardized.
User interface.
The interface translates human goals into machine actions and system state back into human-readable feedback.
Good interfaces reduce coupling without hiding critical state.
The design problem is deciding what must be stable, visible and negotiable across the boundary.
Minimize surface
Expose only what the other side truly needs.
Make assumptions explicit
Document units, timing, ownership, version and error behavior.
Validate at boundary
Catch malformed or incompatible input before it propagates.
Version deliberately
Preserve compatibility or coordinate breaking changes explicitly.
Observe failures
Instrument the boundary because cross-system problems concentrate there.
Design Rulesmodularity and interfaces
Software Architecturecontracts and boundaries
Systems Engineeringinterface control
The Design of Everyday Thingshuman-system interfaces