Program to weld.And back again.
Ten levels of hierarchy on VS-001, and a relationship graph cutting across all of them. Every object answers the same nine questions. That is the whole argument: a shipbuilding system is not a collection of screens, it is one consistent way of asking what is true about any object in the program — including the parts of the answer that live somewhere else.
SyntheticVS-001 is a concept vessel. No customer data appears anywhere on this page.Build Room explorer
Program to weld, and back to accepted configuration.
VS-001 — concept vessel
One hull, one identity, and one synthetic build-state model. ~30–35 m (about 100–115 ft); seven schematic visualization segments; 16 transverse reference stations shown.
Work is in progress against the governing revision.
- LOA envelope
- ~30–35 m
- Segmentation
- 7 schematic visual segments
- Engineering release
- 82%
- Material ready
- 71%
Upstream records this one cannot move without. Follow any of them.
- Acceptance moves the vessel baseline from Rev 28 to Rev 29.
The downstream effect of a change here — the question that is normally answered by a meeting.
- The vessel baseline only moves when this change is accepted.
- Synthetic drawing-set record at Rev 28, with the four authored systems below traced to it.
- Block progress and state are authored demonstration values. The separate WP-019 readiness verdict is computed from its canonical synthetic gates.
SYNTHETIC PROGRAM — NOT CUSTOMER DATAHand-authored to show the information architecture
Nine questions, or it is decoration.
Every synthetic product surface on this site has to answer these. Where one cannot, it is probably a picture rather than a product. Questions six and seven are the expensive ones — a held certificate in receiving is what actually stops a weld in a machinery space, and nothing in a containment tree will tell you that.
- 01
What object am I looking at?
- 02
What state is it in, and what does that state actually assert?
- 03
Who owns it — a person, not a department inbox?
- 04
What revision governs it, and has that revision moved?
- 05
What is it waiting on, named rather than implied?
- 06
What decides it that is nowhere near it in the hierarchy?
- 07
What moves if this moves?
- 08
How is the state evidenced, and can I go and look?
- 09
What has already changed here?
From build state to a recorded decision.
Select the work package the tree above is built around and run the whole loop: the deterministic verdict, VeldMind’s bounded recommendation and its reasons, and the named authority who holds or releases the work. Release is only lawful once the state is established — the system never waives a gate.
WP-019 may not proceed. Known open: configuration and material.
- Configuration
- Material
- Predecessor
- Access
- Quality
- Resource
Do not release WP-019. 2 gates are known open.
- Configuration: Route not yet re-released at Rev D. Change CFG-029 is open, so the package is still written against superseded Rev C.
- Material: Kit short: 2 of 9 spools short held at receipt. The physical material to complete the work is not on hand.
- Evidence consulted
CFG-029KIT-B30-019WP-022-ACCAREA-MS-03INS-124CREW-B30-019- Authority required
- Engineering / configuration control
VeldMind recommends and explains; it does not release work. A named human authority decides.
Approve is unavailable: release is only lawful once the verdict is READY. The system cannot release WP-019 while a gate is open.
- 15:04:00observedState observed — WP-019: Configuration = OPEN (CFG-OPEN) · Material = OPEN (MAT-SHORT)
- 15:04:11evaluatedReadiness evaluated — WP-019 = NOT_READY
- 15:04:22recommendedRecommendation REC-WP-019-NOT-READY — Do not release WP-019. 2 gates are known open.
Next: Close CFG-OPEN: Route not yet re-released at Rev D. Change CFG-029 is open, so the package is still written against superseded Rev C. — owned by Engineering / configuration control.
What does this revision affect?
The same synthetic program as a dependency graph. Introduce a controlled drawing revision and trace it: what is known-affected, what is known not affected, and what cannot yet be established — kept apart. Selecting a node shows its dependencies, downstream work and evidence.
DR-118 Rev C governing · stable
Dependency list (text)
- WP-022 — Pipe penetration & seat prep Downstream: WP-019.
- WP-019 — Seawater cooling spool set depends on WP-022 (requires predecessor), MAT-441 (requires material), DR-118-C (governed by). Downstream: WP-021.
- WP-021 — Cooling equipment installation depends on WP-019 (requires predecessor), MAT-442 (requires material), DR-220-A (governed by).
- WP-014 — Machinery foundation structure depends on DR-205-A (governed by).
- WP-030 — Adjacent zone electrical routing depends on DR-118-C (governed by).
WP-019 may proceed. Every required gate is positively established against governing evidence.
- Configuration
- Material
- Predecessor
- Access
- Quality
- Resource
WP-019 may be advanced to release review. Every required gate is positively established.
- Configuration: Rev D released; CFG-029 closed. The route the crew holds is the governing revision.
- Material: All 9 spools received and accepted at receipt against the kit.
- Predecessor: WP-022 complete and accepted; the upstream joint the spool set lands on is closed.
VeldMind recommends and explains; it does not release work. A named human authority decides.
M. OkaforProduction release authority · B30
- 15:04:00observedState observed — WP-019: all gates established
- 15:04:11evaluatedReadiness evaluated — WP-019 = READY
- 15:04:22recommendedVeldMind — advance WP-019 to release review
Introduce the controlled change to trace its propagation
Program state, for the person who has to answer for it.
Every value is invented for VS-001. What is worth looking at is the shape: named constraints with a consequence and an owner. This is an authored teaching view, not computed or live program state.
What a shipbuilder should be able to see without asking anyone.
- 18Work packages active
- 04Blocked
- 11Ready to release
- 07Inspections open
- 42Inspections accepted
- REV 28Configuration revision
- B10ACCEPTED
- B20ACTIVE
- B30BLOCKED
- B40ACTIVE
- B50READY
- B60READY
- B70ACTIVE
Not alerts. Named constraints with a consequence and an owner — the difference between a dashboard and something a program manager can act on.
- DEP-01Machinery engineering
Seawater cooling revision unresolved in B30
Holds WP-019, WP-028 and the B30 → B40 joint
- DEP-02Procurement
Chocking material against a 4-week lead time
Holds main engine seating in B20
- DEP-03Production planning
Deckhouse outfit hours before landing
Deferral past landing can add access and sequence burden; effect not quantified
Blocked blocks: B30. The values are authored synthetic data; the teaching model links each blocked state to the named constraints above.
Every record points toward a physical object, action, or decision.
In the synthetic model, WP-019 represents nine welded joints in a machinery space. INS-124 represents a witnessed pressure test. CFG-029 represents a named configuration decision. None is a record of work performed; the point is to keep the information tied to the physical build.
- Work package
WP-019 — seawater cooling spool set, MS-03
Nine welded joints in a machinery space
Two fitters, a welder, one shift each. Each joint carries the qualification of the person who welded it.
- Inspection
INS-124 — hydrostatic test, seawater cooling loop
A pressure test somebody has to witness
The loop is filled and held. Either it holds pressure against the governing criteria or it does not.
- Configuration
CFG-029 — P-204 Rev D incorporation
A signature accepting responsibility
A named person moves the baseline from Rev 28 to Rev 29, and owns that decision for the life of the vessel.