Brief / Operations
The newest drawing does not govern
Authority over a drawing comes from release, revision, applicability, and approval. A timestamp confers none of it.
The recency trap
Release, not recency, decides which drawing governs. A field markup uploaded on Friday afternoon may postdate the released drawing and describe a real condition; it still does not control the configuration.
An AI-native shipbuilding system has to know more than what text looks relevant. It has to know what kind of record it is, whether it was released, where it applies, which revision it supersedes, what work package depends on it, and who approved the change.
Why this becomes a production problem
A bad revision decision does not stay inside document control. It can release the wrong material, change a weld sequence, invalidate inspection work, trigger rework, and move schedule risk downstream before anyone notices.
- Approval state before timestamp
- Ship, zone, system, and block applicability before broad similarity
- Revision lineage before filename convention
- Effective date before upload date
- Named decision authority before work release
What the operating system must show
The useful interface shows both sides: the released record selected as governing and the newer record rejected as non-controlling. Hiding the rejected file makes the screen cleaner and the operating decision weaker.
Veldarium’s current public proof demonstrates a narrower control contract with synthetic VS-001 records: readiness is computed from explicit gates, unknown evidence remains unknown, and a named person retains release authority. Live shipyard integrations and broad engineering-drawing intelligence remain work to earn.