Skilled trades
Welders, pipefitters, electricians, machinists, fitters and the supervisors who run the deck. The system exists to make their work possible, not to route around it.
Veldarium intends tobuild ships.
Not shipbuilding software for someone else — a shipbuilder. It starts with the engineering and production intelligence a modern yard runs on, then earns physical capability in order. Software is the first layer, not the destination.
How software becomes steel Open the Build Room SyntheticVS-001 · ~30–35 m (about 100–115 ft) concept envelope · not engineered or classed
Why this is hard
Every stage depends on the truth of the one before it.
A build runs downstream — design, supply, material, work, inspection, as-built — and each stage inherits the truth of the one before it.
- 01Design
- 02Supply
- 03Material
- 04Work
- 05Build
- 06Inspect
- 07As-built
Fragment that state across systems, spreadsheets and memory, and coordination degrades — slipped schedules, missed revisions, rework at the work face. A systems problem, not a people problem.
What Veldarium changes
From a chain of handoffs to one governed build state.
Instead of state thrown over a wall between disciplines, one governed model holds what is true — and an intelligence layer reasons over it while a named human keeps authority.
Conventional · fragmented
State handed off, then lost.
- Engineering hands off to planning
- Planning hands off to supply
- Supply hands off to production
- Production hands off to inspection
Each handoff loses context. The real state lives in someone’s head.
Veldarium · governed
One connected build-state model.
- Engineering, configuration and supply share one state
- Material, work and production read it continuously
- Quality, inspection and as-built write evidence back
- VeldMind reasons over it; a named human authorizes
The relationship, in full, on Systems.
The work this is for
In the end, this is about steel and the people who shape it.
The architecture exists to serve physical work: fabrication, welding, block construction, outfitting, inspection and delivery. Veldarium performs none of this today — it is the operating domain the systems are being built toward.
VS-001 · schematic production decomposition
Seven visual segments expose connected readiness and joining state.
Synthetic
B30 · ST-06 → ST-08
Rev D pendingMachinery block, forward — auxiliary & cooling
WP-019: Kit short: 2 of 9 spools held at receipt; Route not yet re-released at Rev D (CFG-029 open).
- Structure96%
- Material58%
- Piping34%
- Electrical41%
- Outfit22%
- Inspection30%
Holding this blockWP-019: Kit short: 2 of 9 spools held at receipt · Route not yet re-released at Rev D (CFG-029 open)
Synthetic percentages on a synthetic programThe value is the information architecture, not the numbers
VS-001 separates into seven schematic segments to examine how access and sequence change when a build uses blocks. It is a teaching visualization, not an engineered production breakdown.
Fabrication
Cutting, forming, and welding steel into panels, spools and sub-assemblies — the point where accepted tolerances become physical and measurable.
Block construction
Building the ship as modules that are outfitted while still open, then joined — so access and sequence are designed, not discovered at the work face.
Material handling
Every plate, spool and component moved to the work that needs it, when the opening to carry it in still exists.
Metrology & inspection
Dimensional verification, scanning, and acceptance resolved at the governing revision — with a qualified person signing where a signature means something.
Integration & delivery
Outfitting, commissioning, test and the as-built record that the delivered vessel — and everyone who maintains it — depends on.
Sheet 01 · Software to steelDirection · each phase carries one maturity
How a software company becomes a shipbuilder
The path from a foundation to a hull.
Software is not the company — it is the leverage that earns the next phase. Vertical integration attempted too early kills industrial companies, so the order is deliberate. Veldarium is at the beginning of it.
- NowSoftware foundationWorking + building
- BuildingShipbuilding systemBuilding
- TargetReal program integrationTarget
- ThenProduction cellsLong-term
- ThenPhysical infrastructureLong-term
- DestinationVessel constructionLong-term
Where to see it working
The mission is here. The proof is one click away.
This page explains the mission. Three surfaces let you inspect what exists — deterministic state, reasoning over it, and the two running together on a synthetic program.
VeldBuild
The deterministic system of record for build state — what governs, what is ready, what evidence establishes it.
Explore VeldBuildVeldMind
The intelligence layer that reasons, plans and verifies over governed state — and stops at a named human.
Explore VeldMindBuild Room
Both systems running together on the synthetic VS-001 program — inspectable evidence, not marketing.
Open the Build RoomWhere we actually are
Early, and exact about it.
Veldarium operates no shipyard, has delivered no vessel, and holds no shipbuilding contract or customer program. What exists is the software architecture, working governance elements, and synthetic demonstrations on the VS-001 concept vessel. Any future vessel would be developed and reviewed against the requirements applicable to its design, service and flag; VS-001 claims no class, plan approval, or regulatory authorization.
Long-termPhysical capability is company direction, earned in orderInspect every claim on Progress Scope & limits on Trust
Where to go now
Bring the hardest bottleneck in your build.
Shipyards, fabricators and suppliers: the first engagement is bounded — one consequential question, one record set, one owner, one reviewer. Naval architects, engineers, planners and trades: this mission needs people who know how hard things actually get built.