ARIA DYNAMICS

Systems

The operation, cut at subsystem granularity.

A machine shop is not eighteen stages; it is 89 subsystems across 11 systems, and each one can fail on its own. We track every one of them — including the ones that do not exist yet.

The cut rule

A subsystem is the smallest thing with one owner, one failure mode, and one piece of evidence that it worked. If two things can fail separately, they are two entries. A box that groups things which fail independently cannot tell you which failed.

Every state below is measured against the code, not claimed. This page is regenerated from the same board the shop runs on, and the build refuses if the two disagree.

State legend strictest reading wins
RUNSexercised, with a control that could have failed
PARTIALexists and runs, but a check fails or a number is unverified
BUILTcode exists, unfed or unwired
NONEdoes not exist anywhere
MANUALa person does it; no system planned yet

The board

11 systems. 89 subsystems. No rounding up.

9 subsystems run with a control that could have failed, 30 exist with an open check, and 40 do not exist yet. We publish the third number because it is the one that changes — and this page will keep saying so until it does.

Subsystem board counts per system
1Demand capture3 RUNS 3 PARTIAL 1 NONE
2Estimating1 RUNS 3 PARTIAL 4 NONE 1 MANUAL
3Contract administration3 PARTIAL 1 BUILT 1 NONE
4Engineering4 RUNS 7 PARTIAL 1 BUILT
5Material and planning1 RUNS 7 PARTIAL 2 NONE
6Shop-floor execution4 BUILT 7 NONE 3 MANUAL
7Inspection3 PARTIAL 6 NONE
8Certification and records1 PARTIAL 5 NONE
9Packaging and marking6 NONE
10Delivery and acceptance1 PARTIAL 5 NONE
11Finance and the loop back2 PARTIAL 3 NONE
TOTAL89 subsystems across 11 systems
states measured against the code, not claimed9 RUNS 30 PARTIAL 6 BUILT 40 NONE 4 MANUAL

The internal board carries each subsystem’s owner, its evidence and its failure note. This page publishes the counts, not the contents — the evidence strings describe live solicitation work and belong inside the shop.

Instrumentation

1,302 controls, run as one chain.

Every module in the operation carries its own self-test, and one sweep runs them together so a change in one cannot break another silently. The sweep grades on two signals at once — process exit status and the module’s own verdict line — because a script that prints a failure and exits zero must not count as a pass.

Control sweep Recorded 2026-09-01 20:45 UTC
PASS 1,302 controls executed, all passing
across 51 modules; 42 publish a counted tally, the rest a verdict line 51 modules
RULE A module that exits cleanly but prints no pass signal at all is graded suspicious, never passing — a pass and a no-op must not be indistinguishable.
RULE Deliberate failure cases sit exactly on every limit, and a check that has never failed is treated as decoration until it does.

Displays

What runs inside the shop.

The operation is driven through its own consoles. They are internal — this page publishes what each one is, not what it currently shows.

Delivery console

Operator console over the acceptance, preservation, packing and paperwork chain. A module that refuses is rendered as a refusal — never dressed up as an answer.

Pipeline walkthrough

The end-to-end chain from print to verified program, stage by stage, with each stage’s gate and what that gate can reject. Built toward lights-out running. Unattended operation is an objective, not a current capability. ARIA Dynamics has not yet demonstrated it.

Subsystem board

The board this page is generated from, at full granularity — every subsystem with its owner, its state, its evidence and its failure note, plus a readiness view that shows which greens rest on a control that could have failed.

Ownership map

Which function belongs to which system — the machine, the record system, or this operation — so a boundary crossing is a decision, never an accident.