The S.M.A.R.T. Generator Plant Interface
The boundary where the software stack meets steel: every layer terminates in a named subsystem, sensor, or actuator on the real machine.
Where software meets steel
The S.M.A.R.T. generator is the physical plant the architecture serves, and the plant interface is the contract between them. The blueprint's discipline is that no layer floats free: each terminates in a named subsystem — a magnet, a feedthrough, the divertor, the DEC train — so the software can always be traced to the hardware it controls or observes.
The interface surfaces
- Sensing — 60+ analog channels through cryo-rated vacuum feedthroughs from the diagnostics constellation.
- Actuation — FPGA-driven coils, gas and pellet injection, heating, and the DEC steering on the burner.
- Protection — deterministic vacuum interlocks and the autonomous quench dump.
- Structural — strain gauges and structural health monitoring on the vessel and cocoon.
The magnet and preload interface
The most demanding interface is the high-field REBCO magnet system and its cryogenic ice-piston preload cycle. Sensing REBCO strain, controlling coil currents, and coordinating the preload are all done across the plant interface, and all are safety-critical because a magnet fault is not recoverable in software.
Interface, not integration afterthought
Because the plant is AI-native, the interface is specified alongside the machine, not adapted to it later. Diagnostics are placed for both human and model observability; actuators are chosen for deterministic control. The physical plant wiring page enumerates each termination, and the subsystem pages cover the fuel cycle, magnets, and DEC train.