Line Semantics

Three line styles classify every connection by latency class — so the diagram proves that a microsecond command never rides a batch path.

Lines encode latency, not just connection

In the Master Blueprint the style of a line tells you its latency class. A connection is not merely present or absent; it is real-time, standard telemetry, or offline batch. This turns the diagram into a timing contract that can be checked by eye.

• Microsecond real-time — the hard deterministic path, sub-10 microseconds, L1 to actuator.
• Standard telemetry — sub-microsecond-sampled data streaming up the fabric at millisecond-to-second cadence for monitoring and the twin.
• Offline / batch retraining — high-latency, high-throughput links for training and multi-physics runs at L0.

Why three classes

A fusion plant operates across nine orders of magnitude in time, from microsecond magnet protection to multi-hour Monte Carlo neutronics. Collapsing that range into three named classes lets the architecture state, and enforce, which functions may share a path. The classes align with the latency gradient across the layers.

A checkable invariant

The line grammar makes one rule visible: only microsecond real-time lines may connect the blocks on the sub-10-microsecond command boundary. If a standard-telemetry or batch line were drawn into that path, it would be an obvious violation. Color says what a block is; line says how fast it must be — and the two together let an engineer verify the safety path without reading a word of text.

Each class has a dedicated page: microsecond real-time, standard telemetry, and offline batch retraining.