Purple — Strategy and Governance

Purple blocks carry plant-level intent, regulatory constraint, and the audit trail — the layer that decides what the machine should do and proves what it did.

What purple means

Purple marks the governance role: the parts of the architecture that set intent and hold accountability rather than execute physics. In the blueprint, purple concentrates at L7 Ecosystem & Strategy and threads down into the rules and audit functions of L4 Orchestration.

What lives in purple

• Plant intent — dispatch windows, campaign goals, availability targets.
• Regulatory and safety-case constraints that bound what any lower layer may attempt.
• The decision-audit lineage: every command, who or what issued it, and the twin state it was based on.
• Governance of model promotion — which trained models are allowed near the control loop.

Why governance is its own color

In a fusion plant the difference between a goal and an action is a safety boundary. Purple keeps intent visibly separate from execution so that a strategy decision can never be mistaken for, or wired directly to, an actuation. A purple block may request a breeder equilibrium change; it can never command the magnets.

Both machines

Purple governance is machine-agnostic. Whether the target is Hyperion's negative-triangularity shape or the burner's plug-density setpoint, intent and audit look the same at L7; only the constraints passed down differ. This is what lets one governance layer oversee a mixed breeder-and-burner fleet.

Purple's audit function is the backbone of data lineage and governance, and its constraints are enforced by the safety hierarchy.