Show the chain.
Every answer links to sources, revisions, applicability, changes, and the records rejected as non-controlling.If you cannot trace it, you cannot defend it.
We are here.We are building.
Veldarium is an industrial technology company pursuing AI-native shipbuilding. It is building the systems required for that mission, beginning with VeldBuild.
The mission
Shipbuilding first.
Ships are strategic and economic infrastructure — and one of the hardest systems-engineering problems anyone can take on, reconciling engineering, structure, power, piping, controls, software, supply and human craft in one hull on one schedule. The United States has a well-documented capacity problem here, worth taking seriously over twenty years, not one quarter.
It is called the first mission on purpose. The capabilities being built here should generalise to other difficult physical systems — but proving them anywhere requires proving them somewhere first.
The company destination
Software → shipbuilding system → operations → automation → physical capability → shipbuilder.
Each rung is labeled with what it actually is today. That is what makes it possible to state the destination at full size without any single line becoming a claim.
- TodayWorking
Evidence-bound build state
- Authority — which record actually governs
- Evidence — the chain behind every answer
- Permission-aware retrieval
- Conflict and disagreement kept visible
- Revision and supersession
- Named human ownership of consequence
The bounded software foundation and deterministic readiness proof run on synthetic records, with each control listed and limited on /trust.
- BuildingBuilding
Shipbuilding system model
- Vessel hierarchy — program to operation
- Work packages and dependencies
- Material and supplier state
- Engineering and production state in one model
- Configuration across the whole vessel
The model is being built and demonstrated on VS-001, a synthetic concept vessel. No customer program runs on it.
- NextTarget
Shipbuilding operations
- Engineering system integrations
- Production coordination and sequencing
- Planning against real material readiness
- Supplier and procurement state
- Quality and inspection closure
Not started as delivered capability. This is the layer that requires working with a real yard, which requires earning it.
- LaterConcept
Machine integration
- Sensors and machine state
- CNC and fabrication systems
- Robotic welding and handling
- Scanning and automated inspection
- Autonomous material movement
A design position about where the architecture has to go. Veldarium operates no machinery and integrates none today.
- Long termLong-term
Physical capability
- Specialised production technology
- Production cells and tooling
- Manufacturing and yard partnerships
- Vessel construction
- Repeatable shipbuilding capacity
Company direction. Veldarium owns no facility, holds no vessel contract, and has built no ship.
The destination
Build ships.
That is the destination. Stating it is not the same as claiming it — every rung above has to be earned in order, and each one is labeled with where it actually stands.
Where this came from
Built from inside the work.
I do not want software to sound confident. I want the work to be accountable.
Before Veldarium was a company thesis, Christopher Azar-Brandes was the person reconstructing missing documents, wrong statuses, rejected shipments, vendor exceptions and dropped handoffs when the official system stopped matching reality — in operations where a bad record stopped physical work immediately.
That operating lens is the company: inspect the real work, find the hidden authority and information boundaries, and build only what makes the system clearer for another person to run. Shipbuilding is where that lens now points, because the gap between drawing and steel is the same gap at much higher stakes.
Operating principles
Four rules that survive contact with real work.
Surface the disagreement.
Conflicts are not averaged away. They are recorded, compared, and routed to the right owner.If disagreement is invisible, so is risk.
Name the owner.
Consequential decisions stay attached to a person with authority, not to a role label or a model response.If no one owns it, no one can answer for it.
Earn the right to automate.
Automation comes after the source boundary, exception path, review gate and failure behaviour survive real use.Automate too soon and you automate the wrong thing.
Sheet 01 · Method and standardHow this company intends to work, stated so it can be held to it
The method
Build. Test. Inspect. Publish proof. Advance one capability. Repeat.
There is no shortcut from here to a shipyard, and pretending otherwise would be the fastest way to lose the people whose help this needs. So the company moves the way an engineering organisation moves: one capability at a time, each one leaving behind something a stranger can inspect.
The standard
- No fabricated capability
- No fake traction
- No theatrical defense branding
- No invented metrics
- Synthetic work labelled as synthetic, every time
- The gap between today and the destination stated, not blurred
We do not know every bridge between here and a delivered vessel. We know the direction, and we know the next one to build. We will find people who are better than us at the disciplines this requires. We will keep moving from theory toward proof.
Veldarium is here. Veldarium is building. Veldarium intends to stay.
Who should join
This will not be built by software engineers alone. It cannot be.
A company that intends to end up building ships needs people who have built things. Veldarium is early and is not posting requisitions for openings that do not exist — but it is genuinely looking across all four of these.
Engineering
The people who decide what gets built and whether it can be built at all.
- Software
- AI
- Autonomy
- Systems engineering
- Naval architecture
- Mechanical
- Electrical
- Controls
Production
The people who turn it into steel, and who know what a drawing costs on the floor.
- Welders
- Machinists
- Electricians
- Pipefitters
- Fabrication
- Planners
- Inspectors
Operations
The people who make sure the material, the money and the schedule are real.
- Supply chain
- Procurement
- Manufacturing operations
- Program management
Machine systems
The people who make machinery carry load that people should not have to.
- Robotics
- Industrial controls
- Mechatronics
- Perception
- Automation
Company facts
What is true, and what is not.
- Legal entity
- Veldarium Technology Systems LLC
- Category
- AI-native shipbuilding
- Founder
- Christopher Azar-Brandes · Founder, Veldarium
- Base
- Connecticut, United States
- Working capability
- Governed information layer — bounded scope, deliberately narrow
- Contact
- chris@veldarium.com
Distinctions that get blurred
- A prototype is not a production deployment.
- A planned control is not a working control.
- A fluent answer is not a governed decision.
- Synthetic proof is not a customer result.
- A stated destination is not a delivered capability.
- A shipyard, a drydock, or any manufacturing facility
- A vessel under construction, delivered, or under contract
- A Navy, Department of Defense, or other government contract or program
- A defense customer, a commercial customer, or disclosed revenue
- Production robotics, CNC machinery, or automated production lines in operation
- Certifications, accreditations, or third-party audits
- An employee count, team size, or disclosed funding round
- Classified work, cleared facilities, or cleared personnel
- Shipbuilding customers, design partners under contract, or a backlog
The canonical registry, with evidence and owners, is on Trust.