Veldarium is the parent. VeldMind reasons; VeldBuild records; a named human holds the seam between them. This page is the map.
SyntheticPublic demonstrations run on the synthetic VS-001 concept vessel.Read it downward: the systems the yard already runs, the plane that connects and governs them, VeldBuild for operational truth, VeldMind reasoning over governed context, the human who holds authority, and the physical production that remains the long-term destination.
Authority stays here. Veldarium connects and governs across them, it does not replace them.
Deterministic authoritative build state, resolved across those sources with provenance and readiness.
Reasoning, routing and verification over that governed context. It proposes; it never authorizes.
The decision is held here, by a person. Probabilistic output does not become approved industrial state on its own.
The company. AI-native American shipbuilding.
The parent. An industrial technology and shipbuilding company in formation, building the systems it believes advanced production needs before it needs a yard.
Owns the mission and the shared governance — identity, authority, policy, evidence — under both systems.
/companyDeterministic authoritative build state.
The system of record for what is true about the build — which revision governs, what evidence establishes readiness, who has authority. Useful without AI.
Authoritative for persisted approved state. VeldMind reads its governed context and proposes against it.
/veldbuildBounded reasoning over governed state.
The intelligence layer. It assembles context, decomposes a question, verifies, surfaces disagreement, and produces one traceable recommendation for a named human.
Proposes; a named human authorizes; VeldBuild records the approved state. It is provider-neutral by design and never the authority.
/veldmindThe synthetic operating environment.
Where the two systems run together on VS-001 — from a program down to a single weld and back to accepted configuration, with the change-propagation graph.
The operator surface that renders VeldBuild state and the VeldMind loop over the same synthetic program.
/build-roomThe synthetic concept vessel.
A hand-authored concept profile (~30–35 m envelope) and the build hierarchy, material flow and change propagation modelled on it — the test article the systems reason over.
The shared synthetic subject both systems operate on. Not naval architecture and not customer data.
/demoVeldBuild does not erase source-system truth. It records where each fact came from, which system is authoritative for it, which revision it carries, and when it was observed — then resolves a governed operating answer across them. Authority is configuration-driven, never assumed.
These are representative target systems, not running integrations or partnerships. No production connector exists today; every row is architecture Veldarium is building toward, demonstrated only on synthetic data.
VeldMind reads governed context and proposes. A named human authorizes. VeldBuild records the approved state. Probabilistic output never becomes approved industrial state on its own.
VeldBuild shows the deterministic build-state engine and the change-propagation graph. VeldMind shows the reasoning trace and the governed pipeline. The Build Room runs both together on VS-001.