Engineering
Every engineered object — from a paperclip to a spacecraft — is an arrangement of marks and enclosures designed to perform a function.
Engineering is the discipline of intentional pattern creation. You decide what marks go where. You decide which enclosures contain what. You decide how the patterns interact. And you test whether the resulting pattern does what you intended.
Complex engineering projects are trees of nested enclosures:
City block [ building [ floor [ room [ wall [ brick ] ... Each level is an enclosure. Each enclosure has properties (strength, conductivity, cost). The design is the arrangement of these nested enclosures.
Application [ module [ class [ function [ statement ] ... Each level is an enclosure. Each enclosure has an interface (what goes in and out). The architecture is the nesting structure.
System [ board [ chip [ gate [ transistor ] ... Each level is an enclosure. Signal flow is marks moving between enclosures.
When an engineered system fails, it's because a boundary broke:
| Failure Mode | Pattern Description |
|---|---|
| Structural failure | An enclosure could not contain its contents — the boundary broke |
| Leak | Contents escaped their enclosure — marks crossed a boundary they shouldn't |
| Overload | Too many marks in one enclosure — the pattern became unstable |
| Interference | Two patterns conflicted — juxtaposition created unwanted interaction |
| Cascading failure | One enclosure broke, destabilizing the enclosures that depended on it |
Engineers add redundancy — backup systems, duplicate components — to increase reliability. But redundancy has a cost. Calling tells us: two identical marks are equivalent to one in information, but they're not equivalent in reliability. A backup generator carries the same information as the primary, but having both means the system survives if one fails.
Good engineering is knowing when redundancy helps (safety systems) and when it hurts (bloated code, overbuilt structures). It's knowing when to nest deeper (more abstraction layers) and when to flatten (simpler interfaces). It's pattern intuition — developed through practice — about how marks and enclosures behave when they have to work in the real world.