Brief / Foundations
From document search to controlled ship state
Search answers once and forgets. A shipbuilder needs a lasting record of what governs, what it affects, and who decided.
Search starts over every time
Search and chat produce answers, not a record. Neither preserves why one source governed, why another was rejected, what work was released, which material was affected, or who accepted the consequence.
That is why repeated industrial questions stay expensive after a search rollout: the organization keeps rebuilding authority and current state from fragments.
The durable primitives
An AI-native shipbuilding system needs a graph of controlled relationships: requirements to design objects, design objects to material, material to work packages, work packages to production state, production state to inspection, and every consequential transition to the people and evidence that authorized it.
- Identity and permission scope
- Requirement and configuration lineage
- Material and supplier state
- Work package and production state
- Inspection, exception, and rework state
- Named review and decision lineage
How the system compounds
Each reviewed decision should leave behind more than prose. It should update the controlled state of the ship: what changed, what evidence controlled, what downstream objects were affected, what remained unknown, who decided, and what has to be revalidated.
Veldarium has working evidence-bound control primitives and a synthetic vessel program that demonstrates the larger architecture. The deeper shipyard integrations, multi-discipline graph, and production control surfaces remain the next layers to earn.