Metadata Governance
Strict governance ensures every datum carries correct, complete metadata — machine, channel, calibration, quality, version — so nothing is orphaned.
No datum without metadata
A raw number with no context is dangerous in a control system: it could be from the wrong machine, an uncalibrated channel, or a dead sensor. Metadata governance is the policy and enforcement that no datum enters the fabric without complete, correct metadata: which machine, which channel, which calibration version, which quality score, which schema version.
The required metadata
- Machine and configuration: breeder (Hyperion) or burner, and the shot configuration.
- Channel identity and its registry version, tying the value to a calibrated sensor.
- Timestamp and clock domain, so cross-channel phase is defined.
- Data-quality score and validation verdict.
- Feature version and lineage handle for anything engineered.
Enforcement, not convention
Governance is enforced at ingest: a record missing required metadata is rejected or quarantined, never accepted by default. This is stricter than typical data engineering because the consumers are safety-relevant — a twin acting on a mislabeled channel could mis-actuate a 9.66 MA plasma or a 26.49 T plug.
Governance enables everything else
Lineage, reproducibility, retrieval, and the IT/OT audit trail all rest on complete metadata. Governance is what lets the fabric answer, for any prediction the twin ever made, exactly which bytes and definitions it rested on (see data lineage). It applies uniformly to both machines and is a design and operational discipline for a stack whose FOAK machine begins construction Q2 2027.