The Color Grammar
Seven colors classify every block in the blueprint by role — so a glance tells you whether you are looking at governance, infrastructure, or a thermal path.
Color encodes role, not decoration
In the Master Blueprint every block is colored by its function. The grammar is fixed across all diagrams so that the breeder and burner blueprints read the same way, and so that a block's role is legible before you read its label.
- Purple — strategy and governance: plant intent, regulatory constraints, decision audit.
- Blue — infrastructure and data: compute, storage, telemetry transport, the data fabric.
- Green — operations and ecosystem: dispatch, scheduling, supply chain, maintenance.
- Yellow — AI-workflow and optimization: training, surrogates, MPC, optimization loops.
- Orange — thermal, reactor, and DEC: the plasma, magnets, divertor, direct energy conversion.
- Pink — feedback, alerts, and retraining: anomaly signals, drift detection, model updates.
- Gray — framing: legends, boundaries, and non-functional annotation.
Why a fixed grammar matters
A fusion plant blueprint mixes microsecond hardware with month-long strategy. Without a consistent visual code, a reader cannot tell a safety-critical thermal path (orange) from an offline optimization loop (yellow). The grammar makes role errors visible: a pink retraining block feeding directly into an orange reactor path would be an obvious mistake.
Color plus line
Color answers what a block does; the line semantics answer how fast a connection is. Together they let an engineer verify, without reading text, that a microsecond real-time line only ever connects the blocks that belong on the sub-10-microsecond path.
Each color has a dedicated page: purple, blue, green, yellow, orange, pink, and gray.