Closed operating loop
One requirement.
One accepted hull.
Concept visualization. The region from above, each domain joined to the one governed build. Synthetic model; not a Veldarium facility.
A shipbuilder runs on one question: may this work start now? The answer sits in four systems (the drawing in PLM, the plate in ERP, the work in MES, the inspection in QMS) and is rebuilt by hand. Here one requirement is followed to accepted steel: who holds each fact, where software stops, and which person decides.
Synthetic records · no production connector · no machine operated
The operating architecture
Who may do what, between a requirement and accepted steel?
Records settle every gate. A named person makes every consequential call.
Who holds what, then one requirement carried through nine stations to the accepted as-built, each marked where software stops and a named person takes over.
- 01Source systemsPLM, ERP, MES and QMS keep owning their records.
- 02VeldBuildComposes them into governed build state.
- 03VeldMindReasons over that state and proposes.
- Reasoning stops04A named personAuthorizes the step, or holds it. Nothing else can.
- Steel changes05Physical executionA cell works inside the authorized envelope; machine safety answers separately.
- 06EvidenceMeasurements return, and an inspector accepts them or not.
- 07VeldBuild againRecords the result; downstream readiness is recomputed.
Evidence returns to the record. The next step starts from what was accepted, never from what was recommended.
Station by station, to the as-built
The execution line · one synthetic work package
VeldMind proposes · never authorizesField joining · 2 qualified welders · block B30WP-019 · Seawater cooling spool setREQ-1847 · DWG-SW-114RevisionRev CRev DConfigurationMaterialPredecessorAccessQualityResourceNot ready · 2 of 9 spools shortReady · every gate establishedReleased work area · bounded, revocableEnvelope ±1.5 mm0.4 mm ±0.3 · laser0.5 mm · visionAccepted · dimensional acceptance2 of 2 independent · R. Vancepressure test · no evidenceSystems engineeringOwns the requirement · REQ-1847Traces the requirementEngineering / configuration controlReleases the configurationRev D governsM. OkaforProduction release authority · B30Releases field joining to 2 qualified weldersReceiving / material controlReceives the materialKit 9 of 9 acceptedHot-work permitYard safety, separate from VeldariumZone released · may stop the workR. VanceQA inspector · B30Closes the dimensional acceptance hold point DIM-B30-019VeldBuild · record · append-only
- Requirement traced · REQ-1847 Rev A
- Configuration released · Rev D
- Readiness · Not ready
- Material received · kit 9/9
- Readiness · Ready
- Welder qualification for the process · established
- Field joining released · 2 welders
- Field joining started · by hand
- Weld record per joint · 2.4 h each
- Complete · 9 joints · 22 welder-hours
- Dimensional laser scan · 0.4 mm ±0.3
- Machine-vision inspection · 0.5 mm
- Accepted · R. Vance
- As-built · Rev D
- pressure test outstanding
Scroll to run the requirement through to accepted steel, or choose a station.
01 Requirement What the vessel has to do. Every downstream commitment traces back to it.
- Systems engineering Traces the requirement
- Requirement traced · REQ-1847 Rev A
- VeldBuild · owns
- Resolves the governing requirement and keeps its source: the originating system stays authoritative, and every object downstream traces back to it.
- VeldMind · proposes
- Retrieves the governing requirement, compares revisions, and surfaces where a newer revision is not yet effective.
- Named authority
- Requirement owner · whether a requirement is satisfied
02 Configuration Which revision governs each object, and what deviation was approved.
- Engineering / configuration control Rev D governs
- Configuration released · Rev D
- VeldBuild · owns
- Resolves the governing configuration and effectivity. The newest revision is not automatically effective for this hull, zone, or package.
- VeldMind · proposes
- Detects superseded references and traces change impact across the graph, marking impact-not-established rather than guessing.
- Named authority
- Configuration authority · acceptance of a baseline or approved deviation
03 Work package A bounded unit of physical work: scope, governing configuration, dependencies, gates, and a responsible owner.
- Readiness · Not ready
- VeldBuild · owns
- Computes readiness over the required gates (READY, NOT_READY, or CANNOT_ESTABLISH) and never counts an unknown as ready.
- VeldMind · proposes
- Identifies genuinely ready work, reasons over dependencies, and proposes a sequence. A proposal, never a release.
- Named authority
- Release authority · what work is released to the floor
04 Material Physical items with certificates, lead times, and a location.
- Receiving / material control Kit 9 of 9 accepted
- Material received · kit 9/9
- Readiness · Ready
- VeldBuild · owns
- Reconciles receipt against the ordered revision, tracks certificates and staging, and records a short kit as short.
- VeldMind · proposes
- Flags commitments at risk and finds a short kit against the governing revision before it stalls the floor.
- Named authority
- Material acceptance · receipt inspection and any substitution
05 Yard resource The station, workcell, crane and qualified people the package needs, reserved temporally and revocably.
- M. Okafor Releases field joining to 2 qualified welders
- Hot-work permit Zone released · may stop the work
- Welder qualification for the process · established
- Field joining released · 2 welders
- VeldBuild · owns
- Holds resource and calibration state, and authorizes a workcell only while its governing revision, established material, valid calibration, and a separate safety authority all hold.
- VeldMind · proposes
- Matches packages to qualification and access windows and proposes a sequence that respects crane and station contention.
- Named authority
- Assignment & safety authority · who works, and stop-work
06 Execution Crews and machines carry out the bounded work inside the authorized envelope.
- Field joining started · by hand
- Weld record per joint · 2.4 h each
- Complete · 9 joints · 22 welder-hours
- VeldBuild · owns
- Records production state (released, underway, waiting, blocked) without averaging an unknown into progress, and revokes the authorization automatically if any precondition changes.
- VeldMind · proposes
- Watches for drift against the plan and proposes an intervention. It cannot authorize itself, and the safety authority can inhibit motion even on an authorized cell.
- Named authority
- Supervision & the separate safety authority · a hot-work permit or a machine-safety system can stop the work
07 Evidence The measured facts the physical world returns, with their uncertainty. A cell produces evidence; it never accepts its own work.
- Dimensional laser scan · 0.4 mm ±0.3
- Machine-vision inspection · 0.5 mm
- VeldBuild · owns
- Admits a record as evidence only when authority, applicability, and time hold. Two conflicting measurements are never averaged into a pass, and failed evidence is retained, never deleted.
- VeldMind · proposes
- Identifies missing or stale evidence and the unresolved dependency behind an unknown. It reports the gap rather than filling it.
- Named authority
- Deterministic record. Given evidence already accepted, no new human decision is required here.
08 Inspection A named inspector reviews the evidence and renders the acceptance verdict.
- R. Vance Closes the dimensional acceptance hold point DIM-B30-019
- Accepted · R. Vance
- VeldBuild · owns
- Holds the required inspections and hold points, and records the verdict against the evidence. An unknown measurement is never read as accepted.
- VeldMind · proposes
- Checks record completeness and surfaces any contradiction in the evidence for the named inspector. It never renders the verdict itself.
- Named authority
- Inspection authority · accept, reject, or open a nonconformance
09 Accepted physical state The accepted as-built, what actually exists, recorded over an immutable history.
- As-built · Rev D
- pressure test outstanding
- VeldBuild · owns
- Records the accepted as-built and recomputes readiness, configuration, and schedule, which can block or release the next package. The loop closes here.
- VeldMind · proposes
- Reads the newly accepted state and re-examines the packages downstream of it, proposing what a person should look at next.
- Named authority
- Deterministic record. Given evidence already accepted, no new human decision is required here.
What the record now knows
- RequirementREQ-1847 Rev A became work: the seawater cooling spool set package at Rev D, 9 joints.
- WorkBy hand: 9 field welds, 2 welders, 22 welder-hours. Released only once their process qualification held; the structural weld class holds none for this alloy.
- EvidenceTwo independent reads: 0.4 mm by laser, 0.5 mm by vision, inside ±1.5 mm.
- InspectionR. Vance closed the dimensional acceptance hold point DIM-B30-019 on 2 of 2 independent reads.
- Accepted stateAs-built recorded at Rev D.
- Not yetINS-124 has no evidence, so the package is not accepted.
Accepted physical state is not the end of a line. It returns to governed truth, where recomputed readiness, configuration and schedule decide what work becomes executable next.
observereasonproposeverify / challengeauthorizeexecuteinspectrecord evidenceupdate accepted state
Synthetic run on WP-019. Veldarium operates no machine.
The operating layers
Seven layers, one authority each, and what of each is built.
Read across the path above, layer by layer: what each takes in and hands on, the authority it holds, and the authority it never holds.
- Runs today, on synthetic records
- Source authority rules · Work readiness and evidence · Change impact across the build · As-built recording · Deterministic reasoning · The decision record · Workcell authorization · Measurement evidence rules
- In development
- Program-wide material and production state · The standalone application
- Designed, not built
- A persistent store, written automatically · A language-model adapter (none is connected)
- Not started
- Source-system connectors · Part identity across systems · The as-built record as an operator surface · Reasoning over a yard’s live state · A machine interface · A physical cell Veldarium operates · Inspection and measurement connectors
- Never Veldarium’s
- The machine-safety function
Each layer: its job, what crosses in and out, its authority
| Layer | Its job | Takes in, hands on | Holds, and never holds |
|---|---|---|---|
| The yard’s own systemsThe yard’s, not Veldarium’s | Own the facts. PLM holds which revision is released, ERP what was bought and received, MES what the floor reports done, QMS what inspection accepted, planning the schedule. | The yard’s work, as each system already captures it.Hands on: Records, read under access the yard grants. Nothing flows back into them. | Authority over every fact it owns. That never moves.Never: The composed answer. None of them alone says whether a package may start. |
| Integration and provenance⊳ Source-system connectors (Target) · ⊳ Part identity across systems (Target) · ◇ Source authority rules (Synthetic) | Read each record, tie it to the thing it describes, keep where it came from, and turn away what may not decide. | Records from each system, read-only.Hands on: Admitted facts, each with its source, revision and owner; and the records turned away, with the reason. | The rule for which system may establish which class of fact, configured per yard.Never: Any fact. It never edits a record, and never picks the newer of two. |
| VeldBuild: governed build state◇ Work readiness and evidence (Synthetic) · ◇ Change impact across the build (Synthetic) · ◐ Program-wide material and production state (Building) · ◐ The standalone application (Building) · △ A persistent store, written automatically (Concept) · ◇ As-built recording (Synthetic) · ↗ The as-built record as an operator surface (Long-term) | Hold the governed state of the build, and compute whether work may start, what a change reaches, and which evidence still applies. | Admitted facts, decisions recorded by named people, and evidence returned from the work.Hands on: Readiness (ready, not ready or cannot establish) with the gate that holds and its owner, what a change reaches, and the decision record. | The governed answer composed from the sources, and the record of who decided what on which evidence.Never: Release. It computes ready; a named person releases. |
| VeldMind: bounded reasoning◇ Deterministic reasoning (Synthetic) · ⊳ Reasoning over a yard’s live state (Target) · △ A language-model adapter (none is connected) (Concept) | When something changes, find what deserves attention, assemble the evidence, say what cannot be established, and propose one bounded action with what would overturn it. | The governed context VeldBuild assembles: the question, the admissible evidence and what is still unknown.Hands on: A proposal, routed to the person who holds the decision. Never a release. | No authority at all. It may not grant itself any.Never: Nine consequential acts, each named on VeldMind with the person who holds it. |
| Named human authority◇ The decision record (Synthetic) | Decide. Release, configuration approval, disposition and acceptance each belong to one role, and the person in it decides on the evidence VeldBuild shows. | The verdict, the records behind it, and a proposal if one was made.Hands on: A decision (authorize, hold, or return for evidence), recorded against the evidence it was made on. | Every consequential decision.Never: A decision outside its scope. Release is not offered while any gate is open or unknown. |
| Workcells and machine safety◇ Workcell authorization (Synthetic) · ↗ A machine interface (Long-term) · ↗ A physical cell Veldarium operates (Long-term) · ○ The machine-safety function (Not claimed) | Do the work inside an authorization bound to one cell, one package, one revision and one window. It is revoked the moment calibration expires, a qualification lapses or the governing revision moves. | A released package, and a cell authorization derived from current governed state.Hands on: Measurements and completion events. | Motion belongs to a separate, certified safety system at the cell. It can stop a fully authorized cell, and no Veldarium software may clear it.Never: Acceptance of its own work. |
| Evidence and acceptance◇ Measurement evidence rules (Synthetic) · ⊳ Inspection and measurement connectors (Target) | Bring what the work returns back into governed state: admit a measurement only when it is applicable, current and independent, and let a named inspector accept or reject. | Measurements with their uncertainty, and inspection results from QMS.Hands on: Accepted as-built state, and recomputed readiness for the work that waits on it. | Inspection authority: accept, reject, or open a nonconformance.Never: A sensor never accepts, and two conflicting readings are never averaged into a pass. |
Why the layers are built in this order
Each layer is built only once the layer it acts on can be trusted, and each step is the cheapest place to find out the plan is wrong.
- Rung 0 · Governed build state Synthetic
- Governed state first, because it is useful alone and cheapest to disprove. A readiness answer is useful with no reasoning and no machine. Read-only, it can run beside current practice on one work area, checked by the people who rebuild the answer by hand today, without touching anything the yard depends on.
- Rung 1 · Operational reasoning Target
- Reasoning second, because it can only be checked over governed state. A proposal must cite records the system can resolve, and an unknown gate must still block it. Without governed state underneath, a model’s output can be fluent and unverifiable at once.
- Rung 2 · Program-wide governed state Target
- A whole program third, because one work area proves the method, not the volume. Real authority boundaries, real change traffic and real exceptions appear only across a program. That is where the configuration effort per deployment is measured.
- Rung 3 · Bounded physical cell Long-term
- Cells after that, because an authorization is only as good as the state it is derived from. A cell may run only while its governing revision, accepted material and valid calibration hold. Connecting a machine before that state can be trusted automates the error at the speed of the machine.
The systems the yard already runs
Every system of record keeps the authority it has.
- Read in
- Read into VeldBuild with the system that issued it, its revision and when it was captured. No connector exists today; every record on this site is synthetic.
- Back to a source
- Nothing is written back into a source system. A named person’s decision is recorded in VeldBuild with the evidence it rested on, and the source fact stays exactly as its owner holds it.
- Not built
- Automatic write-back into a persistent VeldBuild store is architecture direction, not built. Writing into a source system is not on that path. All 11 connectors are target connectors.
Each system of record: what it stays authoritative for, and what it alone may establish
| System of record | Stays authoritative for | Contributes | May establish on its own |
|---|---|---|---|
| PLMTeamcenter · Windchill · 3DEXPERIENCE | Released engineering configuration | Released product definition, revisions, configuration and effectivity. | Which revision governs an objectBears on, never decides: Geometry and model state · The controlled document and its approval state |
| CAD / ship designNX · CATIA · ShipConstructor · AVEVA · CADMATIC | Geometry & model state | Engineering geometry, model and drawing context for a governed object. | Geometry and model stateBears on, never decides: Which revision governs an object |
| ERPSAP · Oracle · Infor | Commercial & material transactions | Procurement, purchase orders, inventory transactions and material receipts. | What was ordered, shipped and receivedBears on, never decides: Whether received material was accepted · Program and customer context |
| MES / MOMOpcenter · DELMIA Apriso | What the floor reports as executed | Execution state, operation completion and shop-floor events. | What the floor reports as executedBears on, never decides: Whether an inspection accepted the work |
| QMSEnterprise QMS · Yard quality systems | Recorded acceptance & quality evidence | Inspection results, nonconformances, dispositions and acceptance evidence. | Whether received material was accepted · Whether an inspection accepted the work |
| Scheduling / project controlsPrimavera P6 | The schedule of record | Baseline schedules, activities, resource windows and planned dependencies. | The schedule of record |
| CRMSalesforce · Microsoft Dynamics | CRM data only, never engineering or acceptance | Program, customer and commercial context: accounts, programs and milestones intended for CRM users. | Program and customer context |
| Documents / collaborationSharePoint · Controlled document systems | The controlled document itself | Controlled documents, work instructions and their approval state. | The controlled document and its approval stateBears on, never decides: Which revision governs an object |
| EAM / CMMSIBM Maximo | Asset & maintenance state | Asset and equipment state, maintenance history and work orders. | Asset and maintenance state |
| Identity / SSOMicrosoft Entra ID · Okta | Who a user is | User identity, roles and group membership for access decisions. | Who a person is |
| Supplier / logisticsEDI · ASN / supplier portals | What the supplier reports | Supplier milestones, advance ship notices, quality evidence and delivery events. | What a supplier reportsBears on, never decides: What was ordered, shipped and received · Whether received material was accepted |
The authority rule in full, and why every row is a target
VeldBuild never overwrites a source system’s truth. It records where each fact came from, which system is authoritative for it, its revision and when it was observed, then resolves one governed answer across them. A system that may only contribute never decides, however many of its records agree. Where two equally authoritative sources disagree, the answer is cannot establish, not the newer one. Authority is configuration-driven, never assumed.
These are representative target systems, not running integrations or partnerships. No production connector exists today, and no enterprise system sends anything to Veldarium. The authority rule these rows describe does run, on synthetic records: a record from a system not permitted to establish a class of fact is refused, not counted.
When ERP says the material is there and the crew cannot use it When the drawing itself changes: the review designed for it The doctrine behind this architecture
What computes what, and what each kind may never do
| Layer | What it does | Limit |
|---|---|---|
| Records Synthetic | What a source system asserts: which revision, observed when, by whose authority. Read with its lineage, never computed or learned. | Never rewrites a fact its source owns. |
| Rules Synthetic | Readiness, change impact, evidence sufficiency, applicability and authority. The same records give the same answer, and every answer cites its records. | Never turns an unknown into a yes. |
| Reasoning Synthetic | VeldMind composes the rules’ answers into one proposal and names what would overturn it. A language model could draft here, with the rules checking every draft. None is connected. | Never approves, releases, or writes governed state. |
| Statistics Concept | Only where records are genuinely uncertain: matching one part across PLM and ERP, classifying documents, flagging an odd measurement. Nothing statistical is shown until it is calibrated against later outcomes, yard by yard. | Never sets a state. It may only suggest. |
| Outcomes Synthetic | Later records are checked against what each recommendation said it rested on. What it missed goes to configuration control as a question, and never enters governed state on its own. | Never widens what the system may do. A better track record earns no authority. |