Response to RFI-ICE_ADTS_Sep2026

Arrona Tech Mission AI

Our agentic software factory, mapped onto ICE's three factory layers. The demo shows one real change moving through the factory from work order to merge, with every gate visible, and the planning app it built running on a synthetic southern-border scenario.

4 min 30 s · narrated · scenario data is synthetic and unclassifiedDownload 720p MP4

The demo, layer by layer

What the demo shows

One design rule frames all three of ICE's factory layers. Each point is marked IN USE (how we run today) or FOR ICE (how it runs on ICE work).

01
ICE §1.0 · Design rule

Generation, assurance and authorization stay distinguishable.

No component expands its own permissions or approves its own release.

  1. Layer 3

    Assurance

    02In use

    A fresh critic reviews every change; the builder never grades its own work.

    Merges require every enforcing check to pass and every reviewer blocker to be resolved.

  2. People

    Authorization

    03For ICE

    People keep authorization.

    The Government's reviewer approves and merges every change.

  3. Layer 2

    Runtime

    04In use

    Security gates on every pull request and before release.

    A command guard blocks unsafe commands before they run, shown live.

  4. Layer 1

    Control plane

    05For ICE

    Cost per accepted change, reported monthly.

    Government-owned pipelines and evidence, with a rehearsed exit plan.

Next step

Evaluate it with us

We will run a live scripted-disruption demo of safe failure against ICE's reference baseline, in a one-on-one session.

Contact

Rudy Arrona, CEO

Email Rudy