Know which work can start.

• PLM and released drawingsReadsReleased drawing and model revisions, change orders with their status and effectivity, and the part and spool lists each revision carries.BecomesDrawing · Revision · Change order · Configuration baseline · PartNeverIt never releases, edits or supersedes a revision. Configuration control closes a change in PLM, and VeldBuild reads that it was closed.May decideWhich revision governs an objectBears on, never decidesGeometry and model state · The controlled document and its approval stateFeeds, in the demonstrationConfiguration gate (CFG-029, change in flight)
• ERP and material controlReadsPurchase order lines and the revision each was ordered against, goods receipts, heat and lot numbers with their certificates, stock location and kit allocation.BecomesPurchase order · Material · Material lot · SupplierNeverIt never reads a receipt as acceptance. ERP knows the material arrived; whether it may be used is a quality judgment made elsewhere.May decideWhat was ordered, shipped and receivedBears on, never decidesWhether received material was accepted · Program and customer contextFeeds, in the demonstrationMaterial gate (KIT-B30-019, material receipt)
• MES and the floorReadsOperation status as the floor reports it (started, complete, suspended) and the work package each operation belongs to.BecomesOperation · Work packageNeverIt never reads “complete” as “accepted”. A finished operation is execution state; the predecessor gate also needs the inspection that accepts it.May decideWhat the floor reports as executedBears on, never decidesWhether an inspection accepted the workFeeds, in the demonstrationPredecessor gate (WP-022-ACC, predecessor acceptance)
• QMS and inspectionReadsInspection and test plans with their hold points, inspection results, nonconformances and their dispositions, and receipt inspection of material.BecomesInspection · Test · Nonconformance · Hold · AcceptanceNeverIt never accepts, rejects or dispositions anything. An inspector or the review board decides in QMS, and VeldBuild records the decision with the record it rested on.May decideWhether received material was accepted · Whether an inspection accepted the workFeeds, in the demonstrationMaterial gate (KIT-B30-019, material receipt); Predecessor gate (WP-022-ACC, predecessor acceptance); Quality gate (INS-124, inspection plan)
• Planning and schedulingReadsArea and zone release for the window, crew and trade assignments, and bookings of cells, cranes and stations.BecomesZone · Trade · Resource · MachineNeverIt never reschedules. Where two packages compete for one cell, the resource gate reads open and names who owns the window.May decideThe schedule of recordFeeds, in the demonstrationAccess gate (AREA-MS-03, area release); Resource gate (CREW-B30-019, resource assignment)

Every connector these rows need is at ⊳Target: none is built, and every record on this site is synthetic. The other systems a yard runs, and what each may establish, are on Systems.

1. 01

   Read, under access agreed in writing

   One connector per system reads the records that govern the work area, with the credentials and on the schedule the yard grants. It holds read access only. Nothing is written back.

   ⊳Target
2. 02

   Resolve each identifier to one object

   The yard’s drawing, part, heat and package numbers map to governed objects through a table the yard’s own people review. An identifier that maps to no object, or to two, is never guessed: every answer that needs it reads cannot establish until the mapping is settled.

   ⊳Target
3. 03

   Keep where it came from

   Every record keeps nine fields of provenance, so any answer traces back to the native record behind it. The demonstration’s records carry a subset: the record, its issuer, the object and revision it was captured against, and when.

   △Concept
4. 04

   Admit it, or turn it away with a reason

   A record about another object, captured against a revision that no longer governs, not yet effective, or from a system not permitted to bear on the question never enters the answer. It is kept, with the reason it was turned away.

   ◇Synthetic
5. 05

   Let only the owning system decide

   A system permitted only to contribute never decides, however many contributing records agree. Two permitted records that disagree resolve by configured precedence or not at all: the answer is cannot establish, and a person reconciles them. Recency never decides.

   ◇Synthetic

The rule, run on five synthetic situations. The record ids are invented; the answers are computed.

• ERP shows the kit received in full. Quality has recorded nothing yet.AnswerCannot establishWhy1 record bears on Kit B30-019, but none comes from a source permitted to establish this class. Contributing evidence never becomes a governing answer.
• Quality records the receipt inspection of the same kit as accepted.AnswerEstablishedWhyQMS establishes whether received material was accepted for Kit B30-019 (RI-0419, owned by Quality).
• PLM has released the new revision. The document system still holds the old drawing.AnswerEstablishedWhyPLM establishes which revision governs an object for DR-118 (PLM-REL-2207, owned by Configuration control).
• Two receipt inspections of the kit, both in QMS, disagree.AnswerCannot establishWhySources of equal authority disagree for Kit B30-019: accepted (RI-0419) vs rejected (RI-0420). A person resolves this; the system will not pick, average, or take the newest.
• The only acceptance on file was recorded against the revision the change superseded.AnswerCannot establishWhyNo admissible record establishes this claim for Kit B30-019. Not admitted: RI-0419 was captured against Rev C, not Rev D.

Readiness is a three-valued conjunction, not a checklist score. One gate known open makes the package not ready, whatever the others say. With none open, one gate that cannot be established makes the answer cannot establish. Only when all six are established from current records is it ready. The gates, as the demonstration configures them:

• ConfigurationAsksWhich released revision governs WP-019, and is it the one the work is written against?Satisfied bychange in flightCounts forValid until supersededOwner when not establishedEngineering / configuration controlIn the demonstration nowOpenChange CFG-029 is open against Rev C; the route is held until Rev D is released.
• MaterialAsksIs the correct material present, and accepted at receipt?Satisfied bymaterial receiptCounts forValid until the object or configuration changesOwner when not establishedReceiving / material controlIn the demonstration nowOpenKit: 2 of 9 spools held, because Rev D re-specifies them; they clear when the reworked and remade ones are accepted at receipt. The material to do the work at the governing revision is not on hand.
• PredecessorAsksIs the upstream work (WP-022) complete and accepted?Satisfied bypredecessor acceptanceCounts forValid until the object or configuration changesOwner when not establishedProduction planningIn the demonstration nowEstablishedWP-022 complete and accepted; the upstream work WP-019 starts from is closed.
• AccessAsksIs the physical area (zone MS-03) released and reachable for this work?Satisfied byarea releaseCounts forDescribes one momentOwner when not establishedProduction planningIn the demonstration nowEstablishedZone MS-03 in B30 is released for outfitting; no conflicting hot-work or staging hold is open on the area.
• QualityAsksAre the quality requirements satisfiable, with no open nonconformance blocking the start?Satisfied byinspection planCounts forValid until the object or configuration changesOwner when not establishedQualityIn the demonstration nowEstablishedINS-124 (pressure test) is planned as a hold point at completion; no open nonconformance stands against the start of work.
• ResourceAsksIs the required trade and qualified capacity actually free in the window?Satisfied byresource assignmentCounts forDescribes one momentOwner when not establishedProduction planningIn the demonstration nowEstablished2 pipefitters and 2 pipe welders assigned across 2 shifts, the trades the 9-joint scope requires. Outfit crew capacity (3) is free in the window.

An unknown gate means a record that should exist cannot be found, or was taken on a basis that has since moved. Reading it as a pass sends a crew to cut, fit and weld against something nobody has checked, and the cost lands in steel: rework, re-inspection, a block that waits for its neighbor.

Reading it as a fail sends the wrong person. A known-open gate needs its owner to close it; an unknown one needs someone to find or re-baseline a record, and nothing about the work may be wrong. So the three answers stay apart, and each offers the release authority different actions.

• ReadyThe release authority mayAuthorize release · HoldAuthorize release: Work is released against the evidence set as it stands at this moment. Hold: No gate is open; a hold records that the named person chose to wait, and the verdict is unchanged.
• Not readyThe release authority mayHoldHold: A gate is known open. Someone closes it; the verdict recomputes from the record, not from this decision.
• Cannot establishThe release authority mayHold · Return for evidenceHold: A gate cannot be established. Release is withheld until the record is located; the verdict recomputes from the record, not from this decision. Return for evidence: A gate cannot be established. Someone locates or re-baselines the missing record. Nothing about the work is asserted to be wrong.

Across all 256 combinations of the eight program events on the readiness console, the engine answers ready in 1, not ready in 248 and cannot establish in 7. Ready is the narrow answer, as it should be: every gate has to hold at once.

1. 01

   The build graph finds the candidates

   From the revised drawing, VeldBuild follows the build graph to the work, material and neighboring work the change could reach. That set is what might be affected, and nothing more.

2. 02

   An assessment record decides each one

   A candidate is known affected or known not affected only when an impact assessment says so. One nobody has assessed, or one whose assessments disagree, is impact not established: never read as unaffected, never settled by picking one assessment, and queued for the change authority.

3. 03

   Evidence on the old basis stops counting, and is kept

   Records captured against the superseded revision no longer establish their gates, so those gates read cannot establish, not open: the record may still be right, but it was taken on the old basis. Nothing is deleted, and a release given on the old basis is refused under the new one.

4. 04

   Work downstream recomputes

   Packages that wait on affected work have their readiness recomputed, and each names the role that releases it. The change reaches the floor as named holds, not as a rumour.

In the demonstration, CFG-029 reaches 5 objects: 2 known affected, 1 known not affected, 1 not yet assessed, and 1 downstream package that must recompute. 3 records stop establishing what they did. Each one, and who reconsiders it, is under the graph.

VeldBuild computes whether a package is ready. It never releases one. Release belongs to one named person for the work area, who decides against the evidence as it stands, and VeldBuild records the decision with that evidence attached. Authorize release is offered only on a ready verdict; a decision recorded on one basis does not survive a change to it.

In the demonstration, release for the area is held by M. Okafor, Production release authority · B30. The package is not ready, so VeldBuild offers hold, and records the decision:

1. Decision

   AUTH-WP-019-HELD

2. Action

   Hold

3. Verdict when decided

   Not ready

4. Decided by

   M. Okafor, Production release authority · B30

5. Rationale

   Held: configuration and material known open. Release withheld until they close.

6. Evidence it rested on

   CFG-029 · KIT-B30-019 · WP-022-ACC · AREA-MS-03 · INS-124 · CREW-B30-019

7. Recommendation it answered

   REC-WP-019-NOT-READY

In a yard, the gates are configured, not coded: which gates apply to the area’s packages, which record satisfies each, how long that record counts, and who owns the gate when it is not established. The six gates above are the demonstration’s configuration; a deployment writes the yard’s own, with the people who hold those gates today.

• The boundaryOne work area: the work packages of one block, zone or module, and the release decisions made on them.
• Who uses itThe release authority for the area, the planners who prepare its packages, and a reviewer who checks answers against their sources.
• What it readsRead access to the records that govern the area: revisions in PLM, material in ERP, work in MES or planning, inspection in QMS. Nothing is written back.
• What is configuredConnectors to those systems, the mapping of the customer’s identifiers into governed objects, the release gates its acceptance plans require, and its authority roles.
• What stays with peopleRelease, engineering disposition and quality acceptance. VeldBuild computes and records; the named authority decides.
• What it producesA recorded readiness answer for every package in the area, measured against a baseline agreed before anything is connected.

1. 01

   Name the work area

   The block, zone or module, the release decisions made on it, who holds them and what a wrong release costs. Stops if no release there is rebuilt by hand.

2. 02

   Agree access

   Read access, data rights, handling, the baseline and the success and stop conditions, in writing. Stops if access cannot be made safe and testable.

3. 03

   Run alongside

   VeldBuild reads the area’s records and answers beside current practice, so every answer is checked. Stops if answers do not survive review.

4. 04

   Extend or stop

   Your release authority and reviewer decide whether it extends to the program. If it extends, the connectors and mapping carry forward.

Built once, carried between yards: The governed build-state model and its object classes · The readiness, change-impact, evidence and authority engines · The decision record · VeldMind’s bounded reasoning · A connector for each kind of source system. Configured for each yard: Read access and data rights for the customer’s systems · Mapping of its identifiers, work packages and revisions · Its release gates, acceptance plans and authority roles. The engines run today on synthetic records and are tested in Veldarium’s code. The standalone application is in development, and no connector exists yet.

⊳TargetWork-area deploymentThe offer, and what each side keeps

Nothing here has been measured, because VeldBuild has not run on a yard’s records. These are the outcomes a production director would watch on the first work area, each against a baseline agreed before any record is read. None carries a figure, and none is claimed.

• Less time rebuilding the current state by hand from several systems.Measured byTime from a question to an answer the reviewer accepts, against a baseline agreed before anything is connected.Where the worked case shows it
• Earlier sight of what a change reaches, and of what nobody has assessed.Measured byAffected objects found before work started against those found after, on reviewed changes.Where the worked case shows it
• Fewer packages released while a condition is still open.Measured byHow often released work was later found blocked, before and after.Where the worked case shows it
• The binding constraint and its owner named, instead of a status color.Measured byWhether the named owner was the person who actually cleared the gate.Where the worked case shows it
• Evidence that stays attached to the decision it supported.Measured byWhether every source cited in a decision survives an independent review.Where the worked case shows it
• Clear ownership of each consequential decision, recorded where the next person can check it.Measured byWhether the release authority acts on the answers without authority moving off the people who hold it.Where the worked case shows it

The work area earns the next level when: The answers survive the customer’s technical and operational review, and the release authority acts on them without authority moving off the people who hold it. VeldBuild itself would be scored on: Readiness verdict correctness · Unknown preservation · Change-impact precision and recall · Authority-resolution correctness · Configuration and effectivity correctness · Provenance completeness · Source-conflict detection · Deterministic reproducibility.

⊳TargetEvery outcome above

Every failure below ends in a held package or a refused decision, never in a release. Software that is wrong in the open direction puts a crew on unchecked work; software that is wrong in the closed direction costs a planner an hour. VeldBuild is built to be wrong only in the second way.

• A record a gate needs cannot be found, or its link is broken.VeldBuild answersThe gate reads cannot establish, and so does the package. Authorize release is not offered; the release authority may hold or return it for evidence.Who actsThe gate’s owner, to find or relink the record.◇Synthetic
• Evidence was cleared against a revision that no longer governs.VeldBuild answersThe gate it supported drops to cannot establish, never to open, and the record stays on file as what was true then.Who actsWhoever captured it, to re-baseline it against the governing revision.◇Synthetic
• Two records from systems permitted to decide disagree.VeldBuild answersCannot establish, with both records and their values shown. No vote, no average, and never the newer one.Who actsThe authority that owns the fact, to reconcile them in its own system.◇Synthetic
• A system that may only contribute says yes: ERP shows the material received.VeldBuild answersThe record is kept as context and decides nothing. Material acceptance still waits on quality.Who actsQuality, through receipt inspection.◇Synthetic
• Someone tries to release a package that is not ready.VeldBuild answersVeldBuild refuses the record outright. Approval is never offered on a package with an open or unknown gate.Who actsNo one can; the gate has to close first.◇Synthetic
• A release was given, and then the revision it rested on was superseded.VeldBuild answersThe earlier approval is refused under the new revision. It is not carried forward.Who actsThe release authority, deciding again on the new basis.◇Synthetic
• Two measurements of the same work disagree.VeldBuild answersConflicting evidence: the as-built record is held. Readings are never averaged into a pass, and a sensor never accepts its own work.Who actsThe named inspector.◇Synthetic
• A connector stops updating, or a source system is unreachable.VeldBuild answersAnswers that depend on its records stop being current, and read cannot establish rather than repeating the last good value.Who actsThe yard’s system owner and the integration owner.△Concept
• A yard identifier maps to no governed object, or to two.VeldBuild answersNothing is guessed. Every answer that needs it reads cannot establish until the mapping owner settles it.Who actsThe mapping owner named for the deployment.⊳Target
• VeldBuild itself is unavailable.VeldBuild answersNo answer is not a yes. The area releases work the way it does today, and every source system is untouched, because nothing was ever written into one.Who actsThe release authority, by current practice.△Concept

1. 01

   Engineering state

   The definition allowed to govern the work.

   Requirement · Configuration · Revision · Release · Change · Effectivity · Interface definition

2. 02

   Supply state

   What was required, sourced, received, inspected, accepted, substituted, certified and staged.

   Requirement · Source · Purchase · Receipt · Inspection · Acceptance · Shortage · Substitution · Certification · Staging

3. 03

   Production state

   The lifecycle of the bounded work, without averaging unknowns into progress.

   Planned · Ready · Released · Underway · Waiting · Blocked · Completed · Inspected · Accepted

4. 04

   Quality state

   The conditions and evidence between performed work and accepted work.

   Required inspection · Hold point · Nonconformance · Disposition · Repair / rework · Acceptance · Evidence

5. 05

   Physical state

   What actually exists, where it is, and how it differs from intent.

   Location · Installed configuration · Interface completion · Access · Sequence · As-built condition

6. 06

   Authority state

   The source and person allowed to make a consequential state transition.

   Governing source · Named role · Decision scope · Approval · Exception · Waiver · Expiration / effectivity

1. Product definition

   Program · Vessel · Variant · System · Subsystem · Zone · Compartment · Block · Module · Assembly · Part · Asset

   What is the vessel, and how is it decomposed?

2. Engineering authority

   Requirement · Specification · Drawing · Model · Revision · Configuration baseline · Change order · Release

   What defines the object, and which definition controls?

3. Supply and material

   Material · Supplier · Purchase order · Material lot

   What was sourced, received, certified, and made applicable?

4. Work and resources

   Work package · Operation · Trade · Resource · Machine · Tool

   What must happen, in what sequence, with which bounded resources?

5. Quality and acceptance

   Inspection · Test · Nonconformance · Deviation · Waiver · Hold · Acceptance

   What proves the work, what exception remains, and who accepted it?

6. Physical and as-built state

   As-built record

   What physically exists, where is it, and what record survives delivery?

Typed relationships connect them: requires · satisfies · supersedes · installed in · located in · depends on · blocked by · released by · inspected by · accepted by · sourced from · affected by · governed by · derived from · configured as · connected to.

A revision governs because it is effective, not because it is newest. Each one moves through: Created · Reviewed · Approved · Released · Superseded · Effective for a program, hull, zone, object, or time window · Field exception or approved deviation · As-designed · As-planned · As-built.

Evidence counts for as long as its kind allows: Valid until superseded · Valid until the object or configuration changes · Valid until a declared date · Describes one moment. A record that stops being current reads superseded, basis changed, validity window elapsed, and is kept as what was true then.

State moves only on a recorded event: Created · Revised · Released · Superseded · Held · Installed · Inspected · Accepted · Nonconformance opened · Nonconformance closed · As-built reconciled.

1. 01Build control△ConceptOverall governed state, and the exceptions that need a person now.
2. 02Build graph◇SyntheticThe typed dependency and configuration graph for any object.
3. 03Readiness queue◇SyntheticWhat may start, what may not, and what cannot yet be established.
4. 04Change impact◇SyntheticWhat one revision affects downstream, and what it does not.
5. 05Material exceptions△ConceptShortage, wrong revision or lot, late arrival, and provenance gaps.
6. 06Quality & acceptance△ConceptHold points, inspections, nonconformances and acceptance evidence.
7. 07Configuration△ConceptWhich revision and effectivity govern which object right now.
8. 08Evidence ledger△ConceptWhy the system believes the current state: the records behind it.
9. 09Integration health△ConceptWhich external sources are healthy, stale, conflicting or unavailable.
10. 10As-built↗Long-termWhat was actually installed and accepted versus what was intended.

The capability ledger, dated Every claim and its evidence

• May this unit of work lawfully begin at all?AboutOne work package, under the revision that governs itEstablishes a fact from evidenceDoes not decideIt does not decide that any particular cell can do the work. A package can be READY while every cell qualified to execute it is held, uncalibrated or busy.
• Can this exact cell perform this exact work, against this exact basis, right now?AboutOne workcell, for one work package, at one revision, at one evaluation timeEstablishes a fact from evidenceDoes not decideIt does not start the work and it is not a safety system. Machine safety is a separate, dominant authority that can inhibit motion on a fully authorized cell, and no Veldarium software may clear it.
• Has a named person actually said go?AboutOne release decision, by one named authority, for one work packageA named person decidesDoes not decideIt does not make the machine move, and it does not survive a change in what it rested on. Release is recorded against the evidence set that existed when it was taken; a revision that supersedes that basis withdraws the authorization rather than carrying it forward.
• Is motion permitted right now, by the system that owns that question?AboutOne cell, continuously, not once at the start of the workA separate system reports its own stateDoes not decideIt does not authorize work and it does not accept quality. An inhibited cell is not a defective package, and a clear inhibit is not a release.
• May what came back off the workpiece enter the governed record?AboutOne measurement, against one hold point in the governing acceptance planEstablishes a fact from evidenceDoes not decideA sensor never accepts its own work. It establishes a bounded physical fact with an uncertainty; a named quality authority decides acceptance, and a rejected measurement is real evidence that does not satisfy a threshold.

Three questions, three subjects, three engines. Approved is not executable and executable is not accepted: a package can be READY while no cell may run it, and a cell can be AUTHORIZED while what comes back off the workpiece is rejected. Every verdict here is computed from synthetic teaching fixtures; Veldarium authorizes no cell and operates no machine.