Skip to main contentSkip to navigation
Synthetic · one change

One drawing changes.
Follow it to the floor.

A piping drawing is re-released while a crew is planned against the old revision. Before anyone fits a spool, the yard must know what changed, what it reaches, who must act and who decides. Every answer below is computed from synthetic records, in the order the change travels.

Synthetic demonstration on a concept vessel · authority remains human

The worked case · synthetic Synthetic

A change has entered the vessel program.

Read the chain from mission to vessel. The change enters at the engineering-change link, and every link below it, from material to the block, is read again against the new revision.

Vessel
VS-001
Program date
2026-08-20
Change in flight
CFG-029, entered 2026-08-12
Work written against it
WP-019 · Seawater cooling spool set

Synthetic, on a concept vessel. Every record, cell, figure and person on this page is a teaching fixture; Veldarium operates no yard, crew or machine. What is real is the logic that computes each answer, and it runs in Veldarium’s code.

Something changed Synthetic

One drawing was re-released. It reaches 2 objects, misses 1, and for 1 nobody knows yet.

Before the release, 3 of the 3 workcells on this package’s route could start; after it, 0 can. A cell waits until its instruction is reissued to the new revision. No other cell does this work, so no other cell is held. Not reached is a finding. Not established stays open; it is never called clear.

Known affected2

  • WP-019 · Seawater cooling spool setwork packageAssessed (EV-IMP-019): The heat exchanger inlet nozzle moves, so the route the package installs moves with it. It is re-released at Rev D before anyone starts.
  • MAT-441 · Seawater spool set kitmaterialAssessed (EV-IMP-441): 2 of 9 spools re-specified. The closure spool shortens and its neighbour re-angles; the other spools keep their definitions. The re-specified items are held until they clear against Rev D.

Known not affected1

  • WP-014 · Machinery foundation structurework packageAssessed (EV-IMP-014): The change moves a nozzle on the heat exchanger, not the exchanger: its foundation, seating and bolting are unchanged, so no structural weld moves.

Impact not established1

  • WP-030 · Adjacent zone electrical routingwork packageNo impact assessment is on record. It is governed by DR-118, which the change re-specifies, and in the same zone as WP-019, so the impact is not established, and it stays unresolved rather than assumed clear.

Downstream: WP-021 · Cooling equipment installation. Waits on WP-019. Nothing about it is known to be wrong; its readiness is recomputed once the work it waits on is re-released.

Who needs to know Synthetic

See the change from your seat.

The change lands on seven seats, each with its own question. Pick one: the three possible answers, the one the system gives, what it refuses to guess, and who decides.

Can my crew begin WP-019 this morning?

  1. ReadyNone on file
  2. Not readyWP-019This is the system’s answer.
  3. Cannot establishWP-030
Needs to know
A yes or no that will still be true when the crew reaches the bench, and the reason if it is no.
The system can establish
Not ready. WP-019 may not proceed. Known open: configuration and material.
It will not guess
Whether the crew can work around an open gate. A known open gate is not waived by assertion, and a gate nobody can establish is never read as a pass.
A person decides
M. Okafor holds the release, and under this verdict the one action open is to hold.
The evidence path

Answered by readiness.ts from 6 records:

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

Every seat in full

Human authority Synthetic

Reasoning stops at a named person.

After Rev D is released, WP-019 re-released at it and every item accepted: every gate is established, and capability qualification still holds the start. Choose what the work measures once it has run. The reading decides acceptance, never the start, so the proposal does not move with it. VeldBuild records what the named person decides, not what was proposed.

What the work measures once it runs, and the person who decides

  • Binds the decision
  • Partly not established
  • Clear
  • Recorded

What the work measured

  1. Physical evidence1 of 2 observations acceptedBinds the decision.

At the decision

  1. Bounded reasoningVeldMind proposesHold: 1 of 3 domains blocks the startBinds the decision.
  2. Human authorityM. Okafor may only holdBinds the decision.
  3. Recorded stateVeldBuild recordsRecorded as held, bound by 1 domainRecorded.

Change what the work measured

As first measured

The work was measured once, and the measurement was accepted. The acceptance plan for this hold point requires two independent observations, so a perfectly valid reading is still not enough to accept the work. Valid is not the same as sufficient, and a shortfall here holds acceptance, never the start.

Records captured
1
Accepted observations
1
Release permitted
No
Every step in full: the engine that answered it, its own sentence, and the records it cites
  1. Physical evidence

    What does the work measure once it has run, and is that enough to accept it?

    Binds the decision

    DIM-B30-019 (dimensional acceptance) requires 2 accepted observations of laser-scan or machine-vision; 1 is on record. The evidence present may be entirely valid and still not be enough.

    Engine verdict
    insufficient
    Records cited
    1
    Holds
    Acceptance, not the start
    sensor-evidence.ts1 record
    • EV-SEN-SCAN-02-WP-019-ACCEPTED
  2. Bounded reasoning

    The domains disagree. What does the composition conclude?

    Binds the decision

    Do not release WP-019. Capability qualification is blocking, whatever the other domains report. Physical evidence holds acceptance of the work once it has run, not its start.

    Domains consulted
    5
    Domains blocking the start
    1
    Tensions settled by rule
    2
    veldmind-multidomain.ts2 records
    • qualification-outranks-availability
    • readiness-is-not-acceptance
  3. Human authority

    Who decides, and what may they do?

    Binds the decision

    M. Okafor, Production release authority · B30. The only action open is hold. A gate is known open. Someone closes it; the verdict recomputes from the record, not from this decision.

    Decider
    M. Okafor
    Actions open
    1
    Release permitted
    No
    decision.ts1 record
    • Hold
  4. Recorded state

    What exists afterwards, and what can the next decision be checked against?

    Recorded

    Held by M. Okafor: bound by Capability qualification. Do not release WP-019. Capability qualification is blocking, whatever the other domains report. Physical evidence holds acceptance of the work once it has run, not its start.

    Record state
    HELD
    Bound by
    1
    Evidence cited
    11
    decision.ts12 records
    • AUTH-WP-019-HELD
    • CFG-029
    • KIT-B30-019
    • WP-022-ACC
    • AREA-MS-03
    • INS-124
    • CREW-B30-019
    • pre-outfit
    • OUT-B30
    • nominal
    • REQ-ALLOY-SEAM
    • EV-SEN-SCAN-02-WP-019-ACCEPTED

Everything above is synthetic, on a concept vessel. Veldarium operates no yard, instrument, machine or crew and has no telemetry connection, so this is not a digital twin. What is real is the logic: which records count toward a decision, and what a named person may do about it.

The floor Synthetic

Only released work reaches the floor, and released work is not yet a ship.

The package passes through three program states, read against the same six gates. Closing the change does not release the work. It moves which gate binds. Every gate is established and the package reads ready. Ready is not authorized: capability qualification holds the release, because no weld procedure is qualified for the spool alloy. Acceptance evidence comes once the work has run, and it holds acceptance, not the start.

  1. CFG-029 is open and 2 of 9 spools are held for Rev DNot ready, configuration bindsReaches the floor: no
  2. Rev D is released and WP-019 re-released at it; the 2 spools are still heldNot ready, material bindsReaches the floor: no
  3. Rev D is released, WP-019 re-released at it, and every item is acceptedReadyReaches the floor: no
  1. Engineering release
  2. Material procurement
  3. Fabrication
  4. Assembly
  5. Integration
  6. Inspection
  7. Launch
  8. Commissioning
  9. Delivery

Step the package through its gates How a ship is physically built

Capacity Synthetic

Nameplate is not capacity.

The block those spools go into starts as cut plate. The synthetic plasma cutting cell loses hours to setup and faults, and parts to failed first inspection. What survives is the capacity a schedule may count.

  1. Nameplate, plate parts2400
  2. Accepted, after availability and first-pass yield1999.2
  3. Used by a demand of 160080%

effective capacity = staffed hours × qualified rate × availability × first-pass yield

The plasma table worked through

Industrial base

Where can this vessel actually be built? Unknown.

No facility record meets the standard for publication, so none is drawn. In the synthetic model, panel line weld binds first, at 90%, then structural weld (robotic + manual). Any yard depends on:

  • Yards
  • Technical authority
  • Long-lead equipment
  • Suppliers
  • Qualified processes
  • Tooling and fixtures
  • Material
  • Qualified labor
  • Facilities and utilities
  • Inspection
  • Transport

The network, tier by tier