Skip to main contentSkip to navigation
Veldarium
Work with us
The construction log · last moved 2026-09-07

The construction log.
What is built, on what evidence, and where it stops.

What has Veldarium built, and how far is it from a ship?

Each entry records what exists, its evidence, what is missing and the next gate, dated when last verified. The order is the Roadmap.

A repository test is not a yard result. A stage moves only when its evidence exists.

The control-by-control limitFollow the ledger by feed

Rung 0 · Governed build state to Vessels

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8

Next: Real records, live decision

The distance

11 stages from modeling a vessel to delivering one. Here is where the built work stops.

  1. 1Code existsThe mechanism is written and can be read.
  2. 2TestedTests that can fail hold its rules, including the ways it must refuse.
  3. 3Synthetic system demonstrationThe mechanisms run together on authored records a reader can inspect.
  4. 4Real records, live decisionA real operating decision made on a partner’s records, with a named owner and failure criteria.
  5. 5Physical processOne physical process run under governed state, measured and inspected.
  6. 6Repeatable physical outputThe same output produced again and again, with time, cost, quality and rework measured.
  7. 7Integrated productionSeveral processes, suppliers and trades working as one production system.
  8. 8Vessel deliveryA vessel designed, built, tested and delivered, then a second.
Every capability stage: its state, what exists, what is missing, and what would falsify it
StageStateWhat existsWhat is missingWhat would falsify it
01 Model the vesselModel the objectSynthetic
  • Concept-vessel geometry: hull profile, keel line, transverse stations, decks and superstructure
  • Seven schematic build segments, each with synthetic state
  • Eleven vessel layers: seven physical systems and four state layers
A systems model, not naval architecture: no hydrostatics, no scantlings, no class compliance.Presenting the concept vessel as naval architecture, or filling unknown particulars as if measured.
02 Model the buildModel the objectSynthetic
  • A ten-level build hierarchy, from program down to a single operation
  • A twelve-stage build sequence, block by block
  • Per-block progress by trade and inspection
Hand-authored for one synthetic program. Not generated from, or connected to, any real engineering system.Treating the seven schematic segments as an engineered production breakdown of a real vessel.
03 Control the informationControl the informationSynthetic
  • Governed answers over bounded record sets
  • Authority, revision, supersession, applicability and conflict modeled explicitly
  • Maker-checker human review for supported actions
  • A deterministic public demonstration, with no language model invoked
Bounded scope, listed control by control on Trust. It runs on synthetic and constrained record sets, not a production document system.An answer that cannot name its authority, or that treats a repository test as production document control.
04 Propagate changeControl the informationSynthetic
  • One synthetic change evaluated across five records, its impact kept three-valued
  • Illustrative profile positions, not engineering locations
  • A thirteen-level walk from requirement to steel, each level holding its state under change
  • One known-not-affected record and one impact-not-established record kept distinct
The dependency graph is authored, not derived. Real propagation requires reading a live engineering model.Silence treated as unaffected, or an unmodeled relation presented as a cleared impact.
05 Material state, established per kitOperate the buildNeeds 04 firstBuilding
  • A nine-stage material flow: one item clears, one stalls at receipt
  • Material as a vessel layer beside the physical systems
  • Work-package readiness derived from kit completeness
No procurement integration, supplier data or inventory. It demonstrates the constraint and tracks nothing real.A shortage the model cannot see, or a substitution that enters a kit unapproved.
06 Production stateOperate the buildNeeds 05 firstBuilding
  • One program view: engineering release, material, structure and inspection closure
  • Critical dependencies as named constraints with owners
  • Authored block state on the drawing model’s identifiers
Every value is synthetic. Nothing is read from a production system, and there is no history.A live production number presented as measured when it is still authored.
07 Human and AI operationOperate the buildNeeds 06 firstTarget
  • A published authority chain: machine recommends, system traces, human decides, configuration records, production executes, human accepts
  • The AI role and human gate stated for each of ten operating stages
Governed retrieval exists. Assembling live build state into a prepared decision comes after governed state survives a partner’s real records.A recommendation that executes, or an unknown gate rounded to a proceed.
08 Human and machine productionTouch the steelNeeds 07 firstLong-termNothing yetNothing is built. Veldarium operates and integrates no machinery; this is a design position on where the architecture must go.Any implication that Veldarium currently operates or instructs machinery.
09 Physical industrial cellsTouch the steelNeeds 08 firstLong-termNothing yetNothing is built. No facility, no equipment, no cell.A laboratory photograph or vendor brochure presented as a Veldarium cell.
10 Integrated shipbuilding capabilityTouch the steelNeeds 09 firstLong-termNothing yetNothing is built. This depends on every stage above it.A software architecture described as shipbuilding capability.
11 Vessel deliveryTouch the steelNeeds 10 firstLong-termNothing yetVeldarium has not yet built a ship. This is the destination.A render, a repository, or a demonstration presented as delivery.

The evidence ledger

2 entries work today. Each states its limit.

The 6 states are defined in the status key on Trust. Choose one to filter the ledger.

  1. Working2 ledger entriesRuns today, with evidence and a named owner on /trust.
  2. Building2 capability stagesUnder active development. Partially real, not finished.
  3. Synthetic6 ledger entries4 capability stagesHand-authored demonstration data. Not a customer system, not live.
  4. Target1 ledger entry1 capability stageA capability Veldarium intends to earn next. Not started or not proven.
  5. Long-term4 capability stagesCompany direction. Years out, and dependent on everything before it.
  6. Source-backed1 ledger entryA statement about the outside world, carrying its published source.

10 ledger entries and 11 capability stages, counted from the registries that own them. The two are different kinds of object and are never added together.

Every entry carries what works, what is synthetic, and what remains unsolved.

  1. Vessel model

    Concept vessel and system model

    Synthetic

    One synthetic concept vessel, VS-001, carried through every scene on this site: hull, structure, seven build segments and eleven layers of systems and state.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingDownstream capabilities need shared object identity. When planning, material and inspection refer to different objects or segments, their state cannot be reconciled without resolving that disagreement.

    Repository evidence
    • apps/web/src/lib/shipbuilding/vessel-geometry.ts
    • apps/web/src/components/industrial/Vessel.tsx
    • apps/web/src/lib/shipbuilding/vessel-spatial.ts
    What actually works
    • One geometry drives geometry, system, dependency, production, inspection and delivery views
    • Layer isolation with dependency, owning roles, work packages, machine opportunities and inspection points
    • Keyboard-operable, reduced-motion-complete, screen-reader summarized
    What is synthetic
    • The hull, its dimensions and all identifiers are invented
    • System routes are illustrative, not engineered
    What it does not do
    • Not naval architecture: no hydrostatics, scantlings, stability or class compliance
    • The 3D view is a concept visualization lofted from the two-dimensional schematic profile: no engineered hull surface, no volumes, no interference checking and no class
    • Cannot be imported from or exported to any CAD or PLM system

    Opens nextA vessel model that can be populated from a real engineering source rather than authored.

    Roadmap gateRung 0, governed build state: not moved. Its gate needs proof level 4, real records, live decision; this stage is at level 3.

    OwnerFounder (product and design) · verified 2026-09-07

    Vessel explorer
  2. Build model

    Build hierarchy: program to weld

    Synthetic

    Ten levels of build hierarchy on the concept vessel, each answering the same questions: what it is, its state, who owns it, what governs it and what it waits on.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingProduction is executed against work packages, not drawings. A system that cannot represent the package, its operations, its material and its inspection cannot tell anyone whether work can start.

    Repository evidence
    • apps/web/src/lib/shipbuilding/build-room.ts
    • apps/web/src/components/industrial/BuildGraph.tsx
    What actually works
    • Drill from program to a single weld operation and back to accepted configuration
    • Gates rendered explicitly: what each object is waiting on
    • Blocked state traced to a cause: a revision that re-specifies two of the spools
    What is synthetic
    • The entire program and every record in it
    What it does not do
    • One authored program; no multi-vessel, no scheduling engine, no critical path
    • No write path: nothing can be updated, closed or approved
    • No integration with any planning or ERP system

    Opens nextA hierarchy populated from a real planning or engineering source instead of authored.

    Roadmap gateRung 0, governed build state: not moved. Its gate needs proof level 4, real records, live decision; this stage is at level 3.

    OwnerFounder (product engineering) · verified 2026-09-07

    Build graph
  3. Engineering control

    Governed answers

    Working

    The layer Veldarium has taken furthest: which record governs a question at a given scope and date, with rejected evidence kept visible and a refusal when authority cannot be established.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingIf a crew cannot determine which revision controls the work, the resulting decision can create rework, inspection, or material risk. This proof does not measure how often that occurs.

    Repository evidence
    • packages/core/src_pkg/services/answer.ts
    • packages/core/src_pkg/test/answer-governance.unit.test.ts
    What actually works
    • Authority, revision, supersession and applicability modeled explicitly rather than inferred from recency
    • Conflicting records surfaced instead of averaged into fluent prose
    • Evidence lineage attached to every answer, including what was rejected and why
    • Refusal path when no governing record can be established
    • Maker-checker human review for supported action types
    • Deterministic synthesis: no external language model in the public path
    What is synthetic
    • The public proof runs on the synthetic concept vessel and one synthetic work package
    What it does not do
    • Bounded to the document types listed in the capability registry
    • No production connector fleet: it does not read a live PLM, ERP or QMS
    • Scope and limits are listed control by control on Trust

    Opens nextApplying the same authority model to a bounded real engineering record set with an industry partner.

    Roadmap gateRung 0, governed build state: not moved. Its gate needs proof level 4, real records, live decision; this stage is at level 3.

    OwnerFounder (product engineering) · verified 2026-09-07

    Trust registry
  4. Engineering control

    Change impact propagation

    Synthetic

    One synthetic engineering change followed through the build: what it is known to affect, what an assessment shows it does not, what no one has assessed, and the work that must be recomputed.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingA useful impact record needs an evidenced boundary while preserving relations the available data cannot establish.

    Repository evidence
    • apps/web/src/lib/shipbuilding/change-propagation.ts
    • apps/web/src/lib/shipbuilding/change-impact-eval.ts
    • apps/web/src/lib/shipbuilding/build-graph-model.ts
    What actually works
    • Three distinct states: known affected, known not affected, impact not established
    • The same synthetic records feed the evaluation and the public impact view
    • Illustrative profile positions are labeled as presentation coordinates, not engineering locations
    • Unknown impact is not silently promoted to not affected
    What is synthetic
    • The dependency graph is authored for VS-001, not derived from an engineering model
    What it does not do
    • Cannot discover dependencies: they are declared
    • No cost or schedule model behind the schedule-impact step
    • One scenario, not a general impact engine

    Opens nextDeriving the dependency graph from a real model so propagation is computed rather than authored.

    Roadmap gateRung 0, governed build state: not moved. Its gate needs proof level 4, real records, live decision; this stage is at level 3.

    OwnerFounder (product engineering) · verified 2026-09-07

    Change propagation
  5. Build model

    Requirement to vessel

    Synthetic

    One synthetic requirement traced down thirteen levels to a pipe-work operation, each level holding what a change would ask of it. The Systems map draws the same path in nine stages.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingVeldarium’s thesis is that making the path from requirement to physical work visible can make change review more disciplined; this surface does not measure an outcome.

    Repository evidence
    • apps/web/src/lib/shipbuilding/requirement-walk.ts
    • apps/web/src/components/industrial/ExecutionSpine.tsx
    What actually works
    • Thirteen levels from requirement to vessel in code, each with an owner, an illustrative magnitude and its state if the requirement changes
    • The Systems map draws the path in nine stages, naming the requirement and the drawing it reaches
    What is synthetic
    • The requirement, its revision and every object it touches
    What it does not do
    • One requirement, one path. Not a requirements management system
    • No verification or traceability matrix
    • Magnitudes are illustrative, not calculated

    Opens nextMany requirements over one vessel, with coverage and orphan detection.

    Roadmap gateRung 0, governed build state: not moved. Its gate needs proof level 4, real records, live decision; this stage is at level 3.

    OwnerFounder (product and design) · verified 2026-09-07

    Requirement to steel
  6. Material

    Material readiness model

    Synthetic

    Two items on the same route into one work package. One clears. The other was made to a revision a change has just superseded, so it is held and the package is not ready.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingIf the material is not there, the work is not ready, and no planning system is entitled to say otherwise. Physical constraints have to govern the digital system rather than the reverse.

    Repository evidence
    • apps/web/src/lib/shipbuilding/work-packages.ts
    • apps/web/src/lib/shipbuilding/readiness.ts
    What actually works
    • Readiness derived from kit completeness rather than asserted
    • A named cause for the hold, not a red badge
    • Material modeled as a first-class vessel layer
    What is synthetic
    • The items, the supplier, the superseded revision and the lead times
    What it does not do
    • No procurement, inventory or receiving integration
    • No supplier records, lead-time data or substitution workflow
    • Nine stages are illustrative of a real flow, not a configurable process

    Opens nextA material graph that reconciles a real BOM against real purchase and receipt state.

    Roadmap gateRung 2, program-wide governed state: not moved. Its gate needs proof level 4, real records, live decision; this stage is at level 2.

    OwnerFounder (product engineering) · verified 2026-09-07

    The material gate
  7. Production

    Program state view

    Synthetic

    One operational picture of the concept program: engineering release, material readiness, structure, inspection closure, block state and named critical dependencies.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingThis teaching view asks what a responsible owner might need to inspect in one place; it makes no claim about how real programs currently review state.

    Repository evidence
    • apps/web/src/lib/shipbuilding/build-room.ts
    • apps/web/src/lib/marketing/yard-capability.ts
    What actually works
    • Critical dependencies expressed as a constraint, a consequence and an owner
    • Authored synthetic block state uses the same identifiers as the drawing model; no roll-up is claimed
    What is synthetic
    • Every number on the view is invented for the synthetic program
    What it does not do
    • No ingestion, no history, no time series, no forecasting
    • Values do not move because nothing produces them
    • The value is the information architecture, not the figures

    Opens nextState computed from the build model instead of authored alongside it.

    Roadmap gateRung 2, program-wide governed state: not moved. Its gate needs proof level 4, real records, live decision; this stage is at level 2.

    OwnerFounder (product and design) · verified 2026-09-07

  8. Human + AI

    Human authority boundary

    Working

    One published chain, applied across the site: machine recommends, system traces, human decides, configuration records, production executes, human accepts.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingAcceptance, safety and disposition carry legal and physical consequence. A system that blurs who decided something is not usable in a yard, however good its answers are.

    Repository evidence
    • packages/core/src_pkg/services/actions.ts
    • packages/core/src_pkg/test/actions-integrity.unit.test.ts
    What actually works
    • Every operating stage states its AI role and its human gate separately
    • Each of the four actors carries an explicit boundary, including what AI does not do
    • Enforced by test: the deciding and accepting actor must be human
    What it does not do
    • This is an architectural commitment and a published position, not an enforcement mechanism
    • Nothing here prevents a future integration from violating it: that requires runtime controls

    Opens nextRuntime enforcement: an approval path that cannot be satisfied without a named person.

    Roadmap gateRung 1, operational reasoning: not moved. Its gate needs proof level 4, real records, live decision; this stage is at no level yet.

    OwnerFounder (product engineering) · verified 2026-09-07

    System architecture
  9. Production

    Industrial base dependency model

    Source-backed

    The industrial base drawn as a four-tier load path, vessel to systems to fabrication to foundations, with the exposure at each node stated.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingA relevant constraint may sit in a yard, supplier, foundry, machining source, workforce pipeline, or another part of the industrial base; each claim needs facility-level evidence.

    Repository evidence
    • apps/web/src/app/industrial-base/page.tsx
    • docs/PUBLIC_CLAIMS_REGISTER.md
    What actually works
    • Structural argument published with per-node exposure
    • A facility-record standard published before any record exists
    What it does not do
    • The verified facility registry is empty. No record has been through the sourcing standard yet
    • No claim is made about any specific company
    • Source bodies are cited as publishers of data, not as partners

    Opens nextA first set of facility records that satisfy every required field, including a published coordinate.

    Roadmap gateRung 2, program-wide governed state: not moved. Its gate needs proof level 4, real records, live decision; this stage is at level 2.

    OwnerFounder (research) · verified 2026-09-07

    Industrial base
  10. Human + AI

    Operational decision assembly

    Target

    Assemble live build state into one prepared decision a supervisor can accept or reject.

    Why it matters, evidence, limits and what it opens

    Why it matters to shipbuildingVeldarium’s hypothesis is that assembling the governing state may reduce decision-preparation burden. No current baseline, phone-call count, or time saving is claimed.

    Repository evidence
    • docs/PRODUCT_TRUTH.md
    What it does not do
    • Not started. The governed retrieval half exists; the operational assembly half does not
    • Requires readiness computed from live records; today the readiness engine runs only on synthetic ones

    Opens nextThe first capability where Veldarium software changes what happens on a shift.

    Roadmap gateRung 1, operational reasoning: not moved. Its gate needs proof level 4, real records, live decision; this stage is at no level yet.

    OwnerFounder (product engineering) · verified 2026-09-07

Every entry states its own limitsAn entry with nothing under “what actually works” has not been built

What comes next

The next objective. The next proof.

Operational decision assembly

Why this oneThe first capability where Veldarium software changes what happens on a shift.

Next proof level
Level 4 of 8: real records, live decision.
The evidence that would count
One real release decision on a design partner’s work area, rebuilt from its own records: every fact traced to its owning system, a named owner, and failure criteria written before any record is read. It is the gate of rung 0, governed build state.
Every stage: its evidence, its next gate and what counts as complete

  1. 01 Model the vessel

    Earned through
    • apps/web/src/lib/shipbuilding/vessel-geometry.ts
    • apps/web/src/components/industrial/Vessel.tsx
    • apps/web/src/lib/shipbuilding/vessel-spatial.ts
    Next gate
    Model the build as production strategy, not visual segmentation.
    Counts as complete when
    A vessel representation whose unknowns stay unknowns: schematic geometry with engineering limits explicit, and no invented class, beam, or displacement.

  2. 02 Model the build

    Earned through
    • apps/web/src/lib/shipbuilding/build-room.ts
    • apps/web/src/components/industrial/BuildGraph.tsx
    Next gate
    Control which record governs.
    Counts as complete when
    Work packages bound to zones, trades, predecessors and inspection gates, distinguishable from a pretty explode view.

  3. 03 Control the information

    Earned through
    • packages/core/src_pkg/services/answer.ts
    • packages/core/src_pkg/test/answer-governance.unit.test.ts
    Next gate
    Propagate change without collapsing unknown impact into clear.
    Counts as complete when
    A named human can see which record governs, why a conflict was refused, and what evidence would change the answer, against a bounded record set.

  4. 04 Propagate change

    Earned through
    • apps/web/src/lib/shipbuilding/change-propagation.ts
    • apps/web/src/lib/shipbuilding/change-impact-eval.ts
    • apps/web/src/lib/shipbuilding/build-graph-model.ts
    • apps/web/src/lib/shipbuilding/requirement-walk.ts
    • apps/web/src/components/industrial/ExecutionSpine.tsx
    Next gate
    Material and supply as facts about kits, not dates.
    Counts as complete when
    A change reports known-affected, known-not-affected, and impact-not-established as distinct, computed from topology plus recorded assessments.

  5. 05 Material state, established per kit

    Earned through
    • apps/web/src/lib/shipbuilding/work-packages.ts
    • apps/web/src/lib/shipbuilding/readiness.ts
    Next gate
    One operational picture of what is actually happening on the build.
    Counts as complete when
    Readiness of a work package derived from kit completeness, receipt, and applicability, not from a planner assertion.

  6. 06 Production state

    Earned through
    • apps/web/src/lib/shipbuilding/build-room.ts
    • apps/web/src/lib/marketing/yard-capability.ts
    Next gate
    Assemble live build state into a prepared decision a named person still owns.
    Counts as complete when
    Blocked work traces to a named constraint with an owner, and inspection closure is a running number against the governing revision.

  7. 07 Human and AI operation

    Earned through
    • packages/core/src_pkg/services/actions.ts
    • packages/core/src_pkg/test/actions-integrity.unit.test.ts
    Next gate
    Waits on rung 0’s gate: one real decision on a partner’s records. Physical production is not next either.
    Counts as complete when
    A prepared option names its evidence, its uncertainty, and the person who must accept or reject it. The system does not release work.

  8. 08 Human and machine production

    Earned through
    No receipt: nothing has been built for this stage.
    Next gate
    Not the next front. Earned only after human-and-AI operation is real.
    Counts as complete when
    Machine programs generated from a released model, and sensor state read back into the build record.

  9. 09 Physical industrial cells

    Earned through
    No receipt: nothing has been built for this stage.
    Next gate
    Not the next front. Requires a cell that does not exist.
    Counts as complete when
    A physical cell Veldarium actually operates, with measurement captured into the same record that governed the instruction.

  10. 10 Integrated shipbuilding capability

    Earned through
    No receipt: nothing has been built for this stage.
    Next gate
    Not the next front. Depends on every stage above it.
    Counts as complete when
    Engineering through delivery on one governed state, with partnerships where others are better and internal capability where owning it matters.

  11. 11 Vessel delivery

    Earned through
    No receipt: nothing has been built for this stage.
    Next gate
    The destination. Not a current gate.
    Counts as complete when
    A vessel that leaves a yard and works. Then a second, and a third.