Technology

The software behind every quote.

ARIA is built software-first. The operation is cut into 94 subsystems across 11 systems, each measured against the code and regenerated on every build. We track every one of them, including the ones that do not exist yet.

Systems

11each with one owner

Subsystems

94one failure mode and one piece of evidence each

Run with a control

41a check that could have failed, and did not

Do not exist yet

11published until the number changes

Subsystem board

11 systems. 94 subsystems. No rounding up.

41 subsystems run with a control that could have failed, 32 exist with an open check, and 11 do not exist yet. A subsystem is the smallest thing with one owner, one failure mode and one piece of evidence that it worked.

Subsystem boardcounts per system

1Demand capture5 RUNS 3 PARTIAL

2Estimating7 RUNS 4 PARTIAL 1 MANUAL

3Contract administration3 PARTIAL 1 BUILT 1 NONE

4Engineering4 RUNS 7 PARTIAL 1 BUILT

5Material and planning3 RUNS 7 PARTIAL

6Shop-floor execution2 RUNS 4 BUILT 5 NONE 3 MANUAL

7Inspection5 RUNS 3 PARTIAL 2 NONE

8Certification and records5 RUNS 1 PARTIAL

9Packaging and marking5 RUNS 1 PARTIAL

10Delivery and acceptance2 RUNS 1 PARTIAL 3 NONE

11Finance and the loop back3 RUNS 2 PARTIAL

TOTAL94 subsystems across 11 systems
states measured against the code, not claimed41 RUNS 32 PARTIAL 6 BUILT 11 NONE 4 MANUAL

State legendstrictest 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 internal board carries each subsystem’s owner, evidence and failure note. This page publishes the counts, not the contents: the evidence describes live solicitation work and stays inside the company.

Control sweep

2,682 controls, run as one chain.

Every module carries its own self-test, and one sweep runs them together so a change in one cannot break another silently.

Control sweepRecorded 2026-10-13 16:37 UTC

PASS 2,682 controls executed, all passing
across 107 modules; 98 publish a counted tally, the rest a verdict line 107 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.

The objective

Unattended 5-axis machining, built from its failure modes.

The direction: 5-axis machining that keeps running with no operator present, on programs verified before they reach the control, with the machine’s data captured on every part it makes. Most of what that takes is not software, and each requirement below is stated as it stands.

Unattended operation is an objective, not a current capability. ARIA Dynamics has not yet demonstrated it.

What it requires1 of 8 in place

IN PLACE01 · The program is right before it runs
A program that gouges is unrecoverable when nobody is watching. Ours are generated to a closed-form offset, gated on removed volume, and executed against a stock model before they reach a control.verified

NOT BUILT02 · Workholding that repeats without a hand on it
Load-once fixturing with measured repeatability, not a vice reset between parts.specified

NOT BUILT03 · Tool wear and breakage detected, not assumed
In-process tool monitoring and sister tooling that swaps without intervention.specified

NOT BUILT04 · Measurement inside the cycle
In-process probing and automatic offset correction, so a long run cannot drift out of tolerance unseen.specified

NOT BUILT05 · Chip and coolant management
Through-tool coolant, evacuation, and programs written so chips cannot gather where the cutter returns.specified

INSTRUMENT ABSENT06 · Machine state that is actually measured
Our current telemetry adapter reports a machine as running on any successful poll without inspecting the response, so it would read RUNNING through a stopped spindle. Until it is replaced with a real MTConnect implementation and an alarm taxonomy, we have no trustworthy view of an unattended machine.stub

NOT BUILT07 · Part handling
Pallet changer or robot cell: a hardware and integration problem before it is a software one.specified

NOT BUILT08 · Supervisory logic with a safe stop
What happens when something goes wrong at 3am. A cell that cannot decide to stop safely is unsupervised.specified

Order of work

Software first, because it can be proven early.

Rows 02 to 08 need a machine and a cell. Row 01 does not: a program can be proven correct against a stock model, with checks that fail. So that is what exists today, and it is what we ask a buyer to judge.

Proven today

Row 01: every program verified against a stock model before it is posted.

Next with the floor

Rows 02 to 08 arrive with a machine and a cell, each measured against a closed form or a physical standard first.

How a row moves

A row changes from specified to in place on this page when a control that can fail says so, and not before.