CANON

System Lexicon

Core system terms that define how real systems behave. Not style language. Not marketing vocabulary. Operational meanings only.

Browse terms System Laws Writing
Decision order Constraints Responsibility Documentation logic
What this page does

This lexicon defines operational meanings used across planning, documentation, coordination, and execution. System Laws define structural laws. System Lexicon defines structural terms. Writing expands reasoning.

Lexicon framework

The terms below describe how systems become fixed: through decision sequence, irreversibility, responsibility boundaries, structural drift, representation logic, material limits, and documentation.

01
Decision mechanics
How constraints become real.
02
Irreversibility
Where flexibility actually ends.
03
Responsibility
Who decides and who carries consequence.
04
Representation
The difference between image and system.

The lexicon fixes meanings. These terms are not branding vocabulary. They are structural constraints.

Public version: core terms only. Extended vocabulary remains in the private canon.

Decision Order defines the sequence in which constraints, geometry, responsibility, and appearance are fixed. A system usually becomes irreversible before production begins.

When responsibility boundaries remain undefined, later decisions compensate for earlier vagueness. “We’ll decide later” is not flexibility. It is delayed commitment.

Use: explain why early clarity prevents structural drift. Anti-phrase: “we can adjust on site”.
A system is usually decided long before it is produced.

Irreversibility is the moment when a system becomes structurally fixed. It does not begin in production. It begins when geometry and responsibility harden.

Production does not create irreversibility. It reveals what has already been decided.

Use: identify where flexibility actually ends. Anti-phrase: “we’ll finalize it later”.
Production reveals structure. It does not create it.

A responsibility boundary defines who decides, who verifies, and who carries consequence. Without a clear boundary, geometry drifts and systems compensate silently.

Responsibility cannot be shared abstractly. It must be assigned at specific structural moments.

Use: clarify ownership before geometry is locked. Anti-phrase: “we’ll coordinate it later”.
Undefined responsibility is a structural risk.

Structural drift is the gradual shift of a system away from its original logic through small compensations, postponed decisions, and unclear responsibility.

Drift rarely appears as failure at first. It appears as adaptation.

Use: identify early compensations before they accumulate. Anti-phrase: “it’s a small adjustment”.
Systems rarely collapse. They drift.

An image presents form without resistance. A system contains load paths, joints, tolerances, sequencing, and responsibility.

Images suggest appearance. Systems define consequence.

Use: separate visual intent from structural feasibility. Anti-phrase: “just make it like the reference”.
A system cannot be reverse-engineered from an image.

Material is not a quality upgrade. It defines what can exist honestly: joints, tolerances, hidden elements, surface behavior, and long-term stability.

If material logic is ignored, the system compensates through visual noise and fragile detail.

Use: explain why some details are impossible in a given material. Anti-phrase: “we’ll make it look clean somehow”.
Material is a boundary condition, not a decoration choice.

Documentation is a structural layer. It fixes what is guaranteed by the system, what depends on site conditions, and what is explicitly excluded.

Without documentation, the “product” does not exist. Only individual outcomes exist.

Use: define responsibility boundaries before production. Anti-phrase: “we always do it like this”.
Documentation turns craft into a system.

A boundary is a designed limit that organizes behavior: privacy, light, passage, rhythm, and use. It is not “just a partition”.

This is why complex decisions should not begin with object catalogs. The object is secondary to the boundary.

Use: explain spatial logic before choosing door types. Anti-phrase: “just split the room”.
Space is organized by boundaries, not by objects.
Canonical note: These definitions are the public reference layer. Extended protocols and additional vocabulary remain in the internal canon.

Author: Oleksandr Uhliar