System variables
| Symbol | Meaning | Unit |
|---|---|---|
| one input event or task instance | declared by task | |
| task-quality measure | task-specific | |
| risk, error, or miscalibration measure | task-specific | |
| 95th-percentile end-to-end latency | seconds | |
| energy over a declared interval | joules | |
| average power over a declared interval | watts = joules/second | |
| measurement duration | seconds | |
| qualified events completed | count | |
| bytes transferred across a named boundary | bytes | |
| counted arithmetic or module work | declared operation | |
| gate for module on event | dimensionless | |
| cost proxy for module | operations, bytes, or joules | |
| latent state at time | dimensionless vector | |
| predicted uncertainty for | same scale as distance | |
| normalized surprise | dimensionless |
Symbol scope
The table above reserves unqualified project-wide symbols. A chapter may add subscripts or superscripts, but it must not reuse a reserved symbol for a different physical quantity. In particular, remains power and remains normalized surprise. Predictors use symbols such as , and an environment state uses a locally declared symbol such as .
Time durations use seconds. Discrete sequence horizons use an explicit count such as or rather than the unqualified duration . Every local objective must state the unit of its value and of every coefficient that makes unlike terms commensurable.
Required qualifiers
FLOP, operation, token, event, and sample are not interchangeable.
Every use must define:
- arithmetic precision;
- dense, effective-sparse, or executed count;
- training or inference;
- batch and sequence shape; and
- whether memory and communication are included.
Boundary labels
- : accelerator package only.
- : accelerator, CPU, memory, local storage, and node cooling.
- : nodes plus network and shared infrastructure.
- : cluster energy multiplied by a contemporaneous, attributable facility overhead.
Results must not move between boundaries by implication.