The Component Labeling System
A consistent naming and tagging scheme lets every part in both machines be selected, cited, and cross-referenced.
Names that mean one thing
A model with hundreds of selectable parts needs disciplined naming or it becomes unusable. Every component in the Kronos model carries a stable name and a machine tag, so a reader can say exactly which part they mean: the Hyperion toroidal-field coil, not just the coil.
The tag structure
- A machine tag: Hyperion for the breeder, or the burner, with the housing noted where relevant (Aegis or MetroVolt).
- A system name: magnet, blanket, vessel, divertor, heating, and so on.
- A component name within that system, unique inside its machine.
Function-first naming
Components are named by function, following the Kronos convention of describing the breeder as Hyperion and the burner by its housings rather than folding the function into a parenthetical. A part is the breeding blanket because it breeds tritium, not merely because it sits at a radius. This keeps the label meaningful even out of context.
Cross-references
Because names are stable, the library can link directly to a component. A page about the neutron shield can point at the vessel it protects, and the model can highlight both when the link is followed. The labeling system is what makes the model and this library one connected reference rather than two separate resources.
Citing a part
A stable name plus a model version is enough to cite a component unambiguously in a design discussion. This is another way the model functions as a design record. For how versions are tracked, see Versioning and Provenance.