System Laws
Core laws that define whether a system remains stable in real space. Not style. Not preference. Not marketing language. Structural reality.
These laws are stable reference points, not essays and not advice. System Laws define structural reality. Writing expands reasoning. System Lexicon defines terms.
These laws are written as constraints, not recommendations. They exist to prevent late clarity — the moment when a system is already irreversible, but people still think everything is flexible.
Wording may be refined. Meaning must not drift.
Decision order determines outcome
Decision order is not a workflow preference. It is a physical property of the final system. When appearance is fixed first and construction is “solved later”, the system begins accumulating compensation: added elements, conflicting joints, visual noise, and late-stage excuses. A calm result appears only when constraints and geometry precede the image.
An image is not a system
Images show form without resistance: no tolerances, no load paths, no joints, no methods, no installation logic. This is why “make it like the reference” is not a system specification. An image may guide proportion or rhythm, but it cannot define a real construction.
Materials define honesty boundaries
Material is not a quality upgrade and not a decorative choice. It is a boundary condition. It defines what joints are possible, what tolerances are honest, which elements can be hidden, and where visual purity becomes impossible without structural compromise.
Tolerances are a design layer
Tolerances are not precision for pride. They define long-term behavior. Where tolerances are not designed, the project later depends on improvisation: shims, sealants, explanations, adjustments, and site heroics. A calm object is not gapless. It is tolerance-aware.
Installation reveals earlier decisions
Installation is not where quality is created. It is where hidden assumptions become visible. If a system constantly needs to be “saved” on site, that usually means the design phase lacked fixed joints, fixed tolerances, and a coherent geometry.
A product without documentation does not exist
A single successful object may be luck or extreme effort. A product is the ability to reproduce a result. Documentation fixes responsibility boundaries: what is guaranteed by the system, what depends on the site, and what is explicitly excluded.
Boundaries are behavior, not objects
A boundary is not just an object inserted into space. It is a designed limit that organizes behavior: privacy, light, passage, rhythm, and use. This is why complex decisions should not begin with a door catalog. The object is secondary to the boundary it serves.