Brief / AI-native shipbuilding
The newest drawing is not the governing drawing
File recency is easy to rank. Shipbuilding authority depends on release, revision, applicability, configuration, and approval.
The recency trap
A field upload lands on Friday afternoon. Its timestamp is newer than the released drawing in document control. The markup may even describe a real condition. None of that makes it the governing 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.