--- title: "About the Company | Veldarium" canonical: https://www.veldarium.com/company html: https://www.veldarium.com/company description: "The company being assembled: the mission, the functions a shipbuilder needs and which of them are filled, operating principles, and current facts." last_updated: 2026-10-12 representation: registry-derived Markdown --- # Company > The company being assembled: the mission, the functions a shipbuilder needs and which of them are filled, operating principles, and current facts. An American industrial company. The intent: build an American shipbuilder able to design, supply, build, inspect, integrate, and deliver difficult vessels reliably. The reason is national: skilled work, ships built right, and a fleet the country can build for itself. Earned in order: software, then physical capability, then vessels. ## Why it exists **The work stops where four departments meet.** Engineering releases the drawing, material receives the plate, production schedules the crew, inspection holds the weld. Each is right about its own fact; nobody holds the answer between them. A crew waits on a revision nobody sent, or welds to one that has moved. Veldarium starts there, on the floor. Software over yard data is already being bought. In December 2025 the Navy announced a 448 million dollar investment in ShipOS, a program that applies Palantir’s software to shipbuilding data, run by its Maritime Industrial Base program with Naval Sea Systems Command. (U.S. Navy, December 2025: https://www.navy.mil/DesktopModules/ArticleCS/Print.aspx?Article=4355823&ModuleId=4021&PortalId=1). Veldarium intends to go further: into the yard itself, its production cells and the automation that executes released work. ## Why software first **The unit of improvement is the build, not the screen.** Governed build state is the one layer that can be proven before there is a yard: one partner’s work area, read-only, no steel at risk. Everything after acts on it. VeldBuild keeps build state governed. Bounded reasoning may propose; named people authorize. ## Build the governing layer. Connect what already holds the facts. Defer the physical capacity until it is earned. Another authority over engineering, material or inspection data would deepen the problem. Veldarium builds the layer between those systems and earns the rest. Moving that line takes published proof from the rung beneath it; capital or intent alone does not move it. ## The company and its two systems Veldarium is an American industrial technology company building toward AI-native shipbuilding: governed build state first, then bounded reasoning over it, production cells that execute only released work, a yard, and in time vessels, each opened by evidence from the step before. - **VeldBuild:** VeldBuild is governed execution and production control: the deterministic, authoritative build-state system that preserves source authority, computes governed state, establishes whether work may start, and records approved transitions. It remains useful with no AI present. - **VeldMind:** VeldMind is orchestration and bounded reasoning operating over VeldBuild state. It works out what deserves attention, traces the consequence paths a change opens, identifies missing evidence, preserves disagreement, abstains where the records cannot settle a question, and returns a traceable recommendation to the named person who decides. - **Human authority:** Consequential industrial authority is assigned to a named person or role with an explicit scope. That person holds the decision. The software informs it and never makes it. - **Physical execution:** People, suppliers, equipment, automation, workcells and facilities execute approved work. Evidence from that work returns to governed state before later work relies on it. Today that means software: governance engines tested in Veldarium’s code, and public demonstrations on synthetic records. **Destination:** Build an American shipbuilder able to design, supply, build, inspect, integrate, and deliver difficult vessels reliably. ## Facts - **Legal entity:** Veldarium Technology Systems LLC - **Founder:** Christopher Azar-Brandes, Founder, Veldarium - **Base:** Connecticut, United States - **Contact:** chris@veldarium.com ## Who is building it 1 of 37 seats filled today: the founder’s. The founder came to this from operations work. The plan does not rest on one person: each rung names the seats and partners it needs. No openings are posted; the founder reads every introduction. ### How decisions are made The founder holds every decision today. Each needs written evidence, fails closed without it, and moves to a named seat once that seat is filled. - **Publishing a claim.** Requires: An entry in the ledger with evidence a reader can inspect, and a release gate that passes. Without it: No evidence, no claim. A status is derived, so it cannot be raised by hand. Held by: Founder today; moves to the quality seat. - **Opening the next rung.** Requires: The rung’s gate evidence, at the proof level the gate demands. Without it: Until then the rung keeps the status its weakest stage gives it, whatever has been spent on it. Held by: Founder today; moves to the program leadership seat. - **Committing capital to a phase.** Requires: The gate beneath the rungs that phase funds. Without it: A phase waits on its gate. No amount is published for any phase. Held by: Founder today; moves to the operations seat. - **Holding a function in-house.** Requires: An attempt on the rung from which the company has to hold that function itself. Without it: Until then the function is reached through a partner, and the seat count changes only when a real hire is made. Held by: Founder today; moves to the operations seat. - **Reading a partner’s records.** Requires: Written terms first: the work area, data rights, the baseline, and the success and stop conditions. Without it: No terms, no access. A reached stop condition ends the work, and stopping is a recorded result. Held by: Founder today; moves to the data and integration seat. ### The seats to fill, as functions Each seat with the rung from which the company has to hold it itself; until then it is reached through a partner who already holds it. - **Programs and engineering:** Configuration management (rung 0); Welding engineering (rung 3); Naval architecture (rung 5); Systems engineering (rung 5); Structural engineering (rung 5); Electrical engineering (rung 5); Vessel programs (rung 6) - **Production:** Production control and planning (rung 0); Manufacturing engineering (rung 3); Production engineering (rung 4); Industrial engineering (rung 4); Production supervision (rung 4); Commissioning (rung 6) - **Supply:** Supply chain (rung 2); Material and logistics (rung 4); Supplier development (rung 5) - **Quality:** Quality (rung 2); Inspection (rung 3); Metrology (rung 3); Nondestructive testing (rung 4) - **Skilled trades:** Machine operators (rung 3); Welders (rung 4); Fitters (rung 4); Pipefitters (rung 4); Robotics technicians (rung 4); Electricians (rung 5); Machinists (rung 5) - **Machines and facilities:** Controls (rung 3); Robotics (rung 3); Maintenance (rung 3); Facilities (rung 5) - **Software and reasoning:** Industrial software (rung 0); Data and integration (rung 0); AI and reasoning (rung 1) - **Leadership:** Safety (rung 3); Operations (rung 4); Program leadership (rung 5) ## Operating principles - **Evidence before claim.** In this company: Every status on this site is computed from the capability ledger. The site’s release gate fails if any rung reads stronger than its weakest stage or the rung beneath it. Enforced by one guard in code. - **A named person decides.** In this company: Every public claim, control and proof has one named owner: the founder, not departments that do not exist yet. The software holds the same line: it offers approval only when every consulted domain is clear. Enforced by two guards in code. - **Fail closed.** In this company: Readiness has a third answer, cannot establish, and it never reads as ready. The company holds itself to the same rule: no cycle-time figure until a physical unit is measured. Enforced by two guards in code. - **Say what would prove it wrong.** In this company: Every stage on Progress names the finding that would falsify it, and every reasoning recommendation names the gate that would overturn it. Enforced by two guards in code. ## Why this shape can get there - **The first gate tests the whole thesis, cheaply.** Rung 0 needs 4 of the 37 seats in-house and one partner’s work area, not a yard. If governed state cannot change a real release decision, the company learns it before buying any steel. - **No gate asks for less proof than the one beneath it.** The gates climb from proof level 4 (real records, live decision) to level 8 (vessel delivery), each above the level 3 reached today. Capital phases fund the rungs in the same order: money follows evidence, not the calendar. - **The team arrives with the rung that needs it.** 7 seats are held before the first physical rung and 30 after it. Until a rung needs a function in-house, a partner who already holds it supplies it. - **Nothing is thrown away between rungs.** 9 of the 20 things the rungs stand on come from more than one rung down. A decision record with named owners, left by rung 0, still carries weight at rung 6. - **What this does not show.** None of it is evidence that the plan will work. It is the order in which a wrong assumption is cheapest to find, with every gate published before it is attempted. ## What is proven, and what is not yet Today that means software: governance engines tested in Veldarium’s code, and public demonstrations on synthetic records. Nothing has run on a yard’s records; everything shown runs on one synthetic vessel. - **Demonstrated, on synthetic records:** Tested software for readiness, change impact, evidence and authority; A synthetic vessel and build hierarchy to run it on; Three answers only: ready, not ready, or cannot establish - **Not yet:** A run on a customer’s real records; A connector to any yard system; The standalone application; A team beyond the founder, a funding round, a customer or a facility ## Contact To discuss a first VeldBuild deployment, or the company: [chris@veldarium.com](mailto:chris@veldarium.com). Name the release decision your team rebuilds by hand. Do not send confidential information in the first message. ## Sitemap - [Full site map](https://www.veldarium.com/sitemap.md) - [Machine context](https://www.veldarium.com/llms.txt)