| # Core trace objects | |
| | Term | What it means | What it does in the runner | How to read it | | |
| | ------------- | --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | | |
| | **Lane** | An anonymous actuator channel: `L0`–`L7`. | Each lane has its own persistent trace state: energy, hold, inhibit, release, correct. | A lane is not a word. `L5` means “actuator channel 5 became involved.” | | |
| | **Operation** | A selector/control action such as `INHIBIT`, `MERGE`, `RELEASE`, `CORRECT`. | Each operation has a fixed neuron pool. Walker contact with that pool increases operation pressure. | Operation names tell us what kind of control pressure the UTD layer is reading. | | |
| | **Command** | A coactivation of one operation and one lane on the same tick. | Example: `INHIBIT + L5` updates `lane_inhibit[L5]`. | This is where “op touches lane” becomes trace physiology. | | |
| | **Trace** | The persistent UTD-side motor-control state. | Carries values forward tick to tick with decay. | This is the internal motor posture before public output. | | |
| | **Witness** | A released outward actuator mark. | Emitted only when release gate conditions are met. | A witness means the trace crossed from preparation into outward action. | |