Architecture · Shared core
Shared core
Reactor-specific rules stay out of the shared core. Every project uses one common data model, with separate, versioned configurations for its reactor family.
Identity
What each item, lot and serial number is.
Provenance
Who made it, handled it and shipped it.
Requirements
What it must meet, and where each requirement comes from.
Evidence
Certificates, inspections, tests, nonconformances and revisions, each with a defined scope.
Workforce
People, their qualifications and validity dates.
Work packages
What is installed, where, by when and under which conditions.
Dependencies
Logical links between work packages, with lags.
Events
The append-only, hash-chained record of every change.
Forecasting
Readiness by date, expressed as a range with a confidence level.
02 / Licence-holder layer
How does it work in practice?
How the layers are linked, checked and kept consistent is part of the licensed software and is explained to licence holders. Tell us about your project and we will walk you through it.
Ask us how it works03
Have a licence file, a supplier or a work package you are worried about?
Send a short description. We reply within two working days and sign your NDA before any document changes hands.