The architect: source of personality

The machine is deterministic. Intent belongs to the baker.

Decima does not choose what to become. Its runtime is indifferent to markets, sound, or industrial sensors. Personality appears when an architect connects a particular world to tile physics.

Baker workflow

domain
  -> semantics of 8 VSB lanes
  -> target event and negative examples
  -> organs made of tiles
  -> thresholds, decay, topology, domains, reset
  -> replay and independent validation
  -> frozen .d8p + hash

The baker designs memory dynamics, not an answer to one frame: what accumulates, what cancels, when a corridor latches, how long a lock permits descendants, and which event clears a used organ.

Three forms of architecture

Mixing these layers is dangerous. Baking an order directly into a sensor destroys its portability. Silently changing press normalization gives the same .d8p a different world.

Authorship and responsibility

Determinism replaces “why did the model decide this?” with exact questions: who defined the input meanings, which tapes were used, what was rejected, which reset and initial state were applied, and whether the artifact hash matches.

The baker owns those decisions. The runtime owns exact execution.

The baker need not be human

Search may be performed by an optimizer or AI, but the architect role remains. Someone defines the objective, constraints, holdout tape, and acceptance criteria. An automatic bakery is an architect's tool, not a source of meaning.

Mature personality

A mature .d8p is reproducible or preserved as a golden artifact, stays silent outside its event, survives independent history, has explicit input/reset contracts, and remains separated from the applied director.

Baking is closer to designing a measuring instrument than training an ordinary classifier.