SYSTEM CANON

System Lexicon

Core terms that define how systems become coherent, constrained, and physically real. Not style language. Not marketing vocabulary. Structural meanings only.

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

This lexicon fixes the meanings used across the author method. System Laws defines stable structural principles. System Lexicon defines the terms through which those principles can be described. Writing expands the reasoning. Applied shows how the method enters concrete fields of practice.

Lexicon framework

The terms below describe how systems become defined: through decision sequence, diminishing reversibility, responsibility boundaries, structural drift, representation, material limits, documentation, and continuity across interfaces.

01
Decision mechanics
How constraints become fixed.
02
Irreversibility
Where flexibility begins to end.
03
Responsibility
Where decisions and consequences remain owned.
04
Representation
The difference between an image and a system.

The lexicon fixes meanings. These terms are not branding vocabulary and not commercial service descriptions. They are structural reference points.

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

Decision Order defines the sequence in which requirements, constraints, geometry, responsibility, and appearance become fixed. The sequence matters because each decision changes the range of decisions that remain possible afterward.

When early boundaries remain undefined, later decisions are forced to compensate for earlier ambiguity. Delaying commitment does not preserve unlimited flexibility. It transfers the decision into a less controlled stage.

Use: explain why early clarity reduces later contradiction. Anti-phrase: “We can solve everything later.”
A system is shaped by the order in which decisions become fixed.

Irreversibility is the progressive reduction of available alternatives as a system moves from intention into geometry and physical reality.

It is rarely one isolated moment. Different parts of a system become difficult to change at different stages. A decision may remain technically changeable while already carrying major consequences for cost, appearance, sequence, or surrounding interfaces.

Use: identify where apparent flexibility has already become conditional. Anti-phrase: “Nothing has been decided yet.”
A system becomes less reversible before it becomes visibly finished.

A Responsibility Boundary defines where ownership of a decision begins, where it ends, and which consequence remains attached to it.

Responsibility does not become clear merely because several people are aware of the same issue. It becomes clear when the decision, verification, and consequence have an explicit location within the system.

Use: clarify ownership before a decision becomes difficult to reverse. Anti-phrase: “Everyone is responsible.”
Undefined responsibility is a structural risk.

Structural Drift is the gradual movement of a system away from its original logic through small compensations, postponed decisions, altered interfaces, and unresolved contradictions.

Drift rarely appears as failure at first. It appears as adaptation. Each adjustment may seem local, while the accumulated result changes the system as a whole.

Use: identify local compensations before they accumulate. Anti-phrase: “It is only a small adjustment.”
Systems rarely fail all at once. They drift.

An image presents form without resistance. A system contains geometry, material behaviour, joints, tolerances, movement, interfaces, sequence, and consequence.

An image can communicate visual intention. It cannot, by itself, define how that intention becomes physically coherent.

Use: separate visual intention from structural definition. Anti-phrase: “Just make it like the reference.”
An image suggests appearance. A system defines consequence.

Material is not automatically a quality upgrade and not merely a visual choice. It defines what can exist coherently: joints, spans, tolerances, movement, hidden elements, surface behaviour, and long-term stability.

When material logic is ignored, the system compensates through fragile details, visual masking, or unrealistic expectations.

Use: explain why each material creates different structural limits. Anti-phrase: “The material does not change anything.”
Material is a boundary condition, not a decorative label.

Documentation Logic is the principle that a repeatable system must exist in a form that can be read, checked, transferred, and compared with physical reality.

Documentation fixes what is defined, what remains conditional, which assumptions are active, and where interpretation must end. Without documentation, individual outcomes may still exist, but a repeatable system does not.

Use: distinguish a repeatable method from personal memory. Anti-phrase: “We always know how it is done.”
Documentation makes a system transferable beyond memory.

A Boundary is a designed limit that organises behaviour: visibility, privacy, light, movement, passage, airflow, acoustic expectation, rhythm, and use.

It is not identical to the object through which it is physically expressed. A door, wall, partition, opening, curtain, or change of level may each create a different form of boundary.

Use: describe spatial function before selecting an object. Anti-phrase: “Just divide the room.”
Space is organised by boundaries, not by isolated objects.

Interface Responsibility is the ownership of clarity at the point where one decision, stage, component, or field of knowledge meets another.

An interface remains stable when it is clear what enters it, what leaves it, what has already been fixed, what remains conditional, and who owns the next decision. Responsibility cannot disappear merely because the system has crossed from one stage into another.

Use: prevent continuity from disappearing between decisions. Anti-phrase: “That belongs somewhere between the stages.”
An undefined interface becomes an unowned responsibility.
Canonical note: These definitions form the public reference layer. Extended protocols and additional vocabulary remain in the internal canon.

Author: Oleksandr Uhliar