ARMATURE
ROBOTICS
Contact →
Menu
AR / PILOT 02Bounded material recovery

PROVE THE TRANSFER BEFORE BUILDING THE FOUNDRY.

Pilot 02 defines the smallest Armature recovery system worth proving: one bounded bay, one authorized intake, one sorting path, one receiving volume, explicit machine and human authority, and an independent evidence chain that can reject a transfer the machinery reports as complete.

01 RECOVERY BAY

ONE INTAKE. ONE SORTING PATH. ONE RECEIVING STATE.

The pilot is intentionally smaller than the underground thesis. It isolates material authority, machine motion, transfer evidence, and bay isolation inside one physical envelope so a failure cannot disappear into a larger network.

PILOT BAY / BOUNDED RECOVERYAUTHORITY + TRANSFER EVIDENCE
Bounded material recovery bay pilotA sectional recovery bay inside a dominant authority envelope, with a tracked grapple handler at intake, an articulated sorting line, a three-stream receiving area with aggregate, billets and racked components, a human figure for scale, independent evidence stations, isolation gates, and an abort route ending at a safe hold inside the envelope.AUTHORITY ENVELOPE / POSITIVELY BOUNDEDSAFE HOLD
ARMATURE / PILOT 02

One recovery bay keeps intake, sorting, receiving evidence, isolation, and abort behavior inside the same inspectable authority boundary.

MODEBOUNDEDPROOFINDEPENDENT
A TRANSFER IS NOT COMPLETE BECAUSE THE LINE STOPPED. THE RECEIVING STATE HAS TO PROVE IT.

The useful result is not material moving through a sorter. It is a bounded system that can preserve identity, refuse ambiguous state, isolate itself, and close a transfer only when independent physical evidence supports the destination state.

02 PILOT ENVELOPE

MAKE THE BOUNDARY SMALL ENOUGH TO FAIL CLEARLY.

Pilot 02 earns credibility by excluding later-system complexity. The test is one attributable recovery loop with a known abort state, not a miniature claim of the entire Subsurface Foundry.

SPACE

One bounded recovery bay

One intake face, one sorting path, one receiving storage volume, defined machine operating zones, and an explicit isolation boundary. The bay may connect to an existing corridor or controlled surface access; it does not need autonomous tunnel advance.

MATERIAL

One attributable transfer

Incoming material must retain identity or explicit unresolved state, source, observations, parent/child lineage after separation, quantity basis, current location, intended destination, transfer state, and handling history.

ABORT

A known end state

A pause, abort, or isolation must leave machines and material in a state the system can explain. Recovery cannot depend on pretending an interrupted transfer completed.

EXCLUDED

Do not borrow credibility from later systems

Pilot 02 does not prove tunnel boring, multiple recovery bays, fabrication, growing, self-manufacture, city-scale logistics, automated release into external construction, production economics, or hands-off continuous operation.

03 AUTHORITY MODEL

UNSUPERVISED DOES NOT MEAN SELF-AUTHORIZING.

Machines can execute a released task without continuous supervision only while every boundary that justified the release remains valid. A bounded trigger may invoke only the predefined isolation sequence needed to make the bay safe; changes to intake, destination, unresolved material, recovery authority, or clearance and restoration after isolation belong to a person.

AUTONOMOUS / MAY

Act inside released authority

Machines may operate without continuous supervision only inside the released physical envelope, on authorized material, toward the authorized destination, while localization, material state, machine state, and required evidence paths remain valid.

AUTONOMOUS / STOP

Refuse, yield, abort, isolate

Machines must refuse or stop when authority, destination, material identity, required sensing, localization, or bay state becomes invalid. When a bounded trigger requires the bay to be made safe, they may execute a predefined isolation sequence only where its consequences are already bounded and the resulting state can be positively verified.

HUMAN / RELEASE

People grant consequential authority

A person authorizes intake and bounded machine work, resolves or quarantines uncertain material, changes task or material constraints, and decides whether verification evidence is sufficient to accept a transfer.

HUMAN / RECOVERY

Isolation does not clear itself

A person must authorize restoration, re-entry, release of stored material, and resumption after an isolation, safety, or uncertainty stop. A machine may execute the predefined isolation sequence autonomously, but it does not receive standing authority to clear the isolation or restore the recovery bay.

04 EVIDENCE CHAIN

CLOSE THE MATERIAL STATE AT THE RECEIVER.

The evidence chain follows the material rather than the machine. Intake, separation, movement, receiving measurement, verifier result, and final state must remain attributable to the same transfer.

EVIDENCE / 01

Authorized intake

Record the material source, intake authority, initial lot identity or unresolved state, bay state, and the observations available before movement begins.

EVIDENCE / 02

Separation lineage

When one lot becomes several streams, preserve parent/child identity and the observations supporting each classification instead of replacing uncertainty with a clean label.

EVIDENCE / 03

Execution state

Keep routing, machine state, pauses, aborts, isolations, and source/destination context attributable to the transfer that is currently open.

EVIDENCE / 04

Receiving measurement

Observe the destination independently enough to establish what arrived, where it arrived, and the accepted quantity basis without trusting the sender's completion signal.

EVIDENCE / 05

Verification verdict

Compare receiving evidence with the transfer contract and return accepted, rejected, or inconclusive. Contradictory or missing evidence remains disagreement, not success.

EVIDENCE / 06

Closed lineage

Retain the authority state, material lineage, receiving evidence, verifier result, and operator actions needed for a reviewer to reconstruct why the final material state was promoted or rejected.

05 VALIDATION PHASES

ADD MATERIAL AUTHORITY ONLY AFTER THE CHECK CAN REJECT IT.

The path moves from state-machine failure injection to observation, shadow decisions, bounded physical authority, and finally a verifier that is independent enough to disagree with execution.

00

Simulation + failure injection

Exercise authority, material, transfer, and isolation state machines without physical actuation. Stale state, unresolved identity, prohibited routing, interrupted transfer, and contradictory verification must fail for the intended reason before physical authority exists.

01

Bench + interface

Run the software against controlled equipment or a recovery-line test harness. Prove task-envelope validation, material-lot transitions, telemetry freshness, command rejection, communications-loss behavior, operator isolation, abort behavior, and attributable state transitions.

02

Observe-only material capture

Sense real recovery work without autonomous material authority. Compare classification with independent reference information, measure state freshness, characterize mixed or contaminated material, and keep unresolved identity visible to the operator.

03

Shadow routing

Generate proposed sorting and storage actions while a human-controlled process moves the material. Compare proposed routing, identity, transfer state, and the conditions that should have caused refusal, quarantine, isolation, or abort.

04

Bounded autonomous recovery

Release deliberately constrained handling inside the recovery bay. The system may act only on authorized material, inside the released authority envelope, toward an authorized destination, while required state remains valid; interruption or invalid state must narrow authority and may require explicit human re-authorization.

05

Independent transfer verification

Measure the receiving state separately from machine or sorting-line completion. Correct, incomplete, wrong-destination, unresolved-identity, contradictory, stale, missing, and post-isolation movement cases must produce the corresponding accepted, rejected, or inconclusive result.

06 EXIT CRITERIA

GRADUATE ONLY WHEN THE TRANSFER SURVIVES ADVERSARIAL EVIDENCE.

Pilot 02 exits because authority, lineage, isolation, recovery, and verification remain trustworthy under deliberately wrong and interrupted cases—not because material moved successfully once.

GATE / AUTHORITYAuthority

Intake and machine work are authorized against explicit current bay and material state, and machines stay inside the released physical and material envelope or yield and abort correctly.

GATE / LINEAGELineage

Material identity and parent/child lineage survive separation without silently promoting unknown material into a qualified stream.

GATE / RECEIVING STATEReceiving state

The destination is measured independently and a transfer cannot close on the machine or sorting line's own completion signal.

GATE / FAILURE REJECTIONFailure rejection

Deliberately wrong, incomplete, stale, missing, or contradictory transfer evidence produces rejection or an inconclusive state rather than false acceptance.

GATE / ISOLATIONIsolation

Bay isolation prevents new machine or material authority from crossing the boundary until a person explicitly restores the permitted state.

GATE / RECOVERABILITYRecoverability

Interrupted work can be reconciled without inventing completion or reconstructing authoritative material state from operator memory.

GATE / AUDITABILITYAuditability

A reviewer can reconstruct what entered, what authority was granted, what moved, what evidence closed or rejected the transfer, and why the final state was accepted.

07 FAILURE CONDITIONS

A PILOT THAT CANNOT FAIL CANNOT PROVE THE SYSTEM.

Any one of these conditions is evidence that the bounded recovery loop has not earned the next increase in consequence.

01

Completion is mistaken for proof

The pilot fails if a machine or sorting-line completion signal is sufficient to close the material transfer.

02

Unknown becomes usable by assumption

The pilot fails if unresolved material can be silently promoted into a qualified classification instead of being refused or quarantined.

03

Lineage disappears during separation

The pilot fails if the system cannot trace separated outputs back to the material state and evidence that produced them.

04

Receiving evidence is optional

The pilot fails if a transfer can close without independent evidence from the destination state.

05

Authority leaks across the boundary

The pilot fails if a machine or material path can continue outside the released physical, material, or destination authority.

06

Isolation depends on memory

The pilot fails if making the bay safe requires an operator to remember unstated manual steps that are absent from the authority and state model.

07

Abort destroys authoritative state

The pilot fails if interrupted work can only be recovered by reconstructing material location, task state, or authority from operator memory.

08

The verifier cannot reject a bad transfer

The pilot fails if deliberately incorrect, stale, missing, or contradictory evidence cannot force a rejected or inconclusive result.

THE NEXT STEP IS ANOTHER BOUNDARY, NOT A BIGGER CLAIM.

If the bay can preserve authority, material lineage, isolation, and independent transfer evidence, the next programme can add a controlled upstream hand-off without changing what “accepted” means.

See the validation ladder →