AVIX-AI
Avian Intersection · the computer-vision detection pipeline that publishes Animal-class entities directly to the Anduril Lattice catalog. Validated 19/19 HTTP 200 · grounded on ICAO Doc 9332.
Ingest → infer → publish.
Four stages, four seconds end-to-end. The pipeline is small on purpose — every additional component is one more thing the partner has to audit.
- 01 · INGEST
Camera, radar, acoustic
Multi-sensor capture at runway and approach corridors. Frame rates and channels per sensor are normalised at the edge before reaching the inference layer — no in-aircraft hardware required.
- CCTV (RGB + IR) · 30 fps
- Solid-state radar · 360° sweep
- Acoustic array · 4-channel
- 02 · INFER
Detection + Re-ID
On-edge computer vision pipeline runs detection on every frame and Re-ID tracking across frames. Trained on the AVIX dataset (Korean airfield species + global migratory profiles); model size kept small enough to run on Jetson-class hardware.
- YOLO-class detector · 4 ms / frame
- Re-ID tracker · multi-target
- Habitat Profile Engine · context layer
- 03 · PUBLISH
Lattice Entity API
Each tracked entity is mapped to a Lattice `TEMPLATE_TRACK` payload (or, since April 2026, native `platform_type: Animal` with `aliases.name: Bird`) and published with disposition `NEUTRAL`. Latency from detection to publish stays under 2 seconds.
- TEMPLATE_TRACK · NEUTRAL disposition
- altitudeHaeMeters (Animal HAE)
- `_uamkt_extensions:bird` (legacy)
- 04 · LATTICE
Allied operator surface
Entities surface in the operator's Lattice instance alongside friendly assets and CBRN control areas. Cross-pillar correlation (e.g. AVIX-AI track ↔ CBRN-CADS hazard zone) happens in the operator's own decision interface — we are a publisher, not a UI vendor.
- Anduril Lattice Dashboard
- Cross-tenant entity sharing
- 19/19 HTTP 200 validated
See the pipeline run.
What ships.
- Software version
- V5.1Animal-schema patch · 2026-04-24
- Detection latency
- < 2 sframe ingest → Lattice publish
- Validation
- 19/19 HTTP 200commit fbcb327 · 2026-04-20
- Sandbox
- 30dhgctoken expiry 2026-06-03
- Lattice template
- TEMPLATE_TRACKplus TEMPLATE_GEO/CONTROL_AREA for hazard zones
- Disposition
- NEUTRALofficial April 2026 · Animal-class default
- Min hardware
- Jetson Orin Nano8 GB · edge inference
- Doctrine reference
- ICAO Doc 9332IBIS bird-strike reporting
Where it goes.
Three operational contexts, three doctrine frames. The pipeline is the same; the surface it publishes to is the partner's.
- Context
Civilian airport
Runway approach + departure cones
Sensors mounted at the localiser and far-field markers. Output flows to airport ATC + airline operations. Anchored on the Muan 7C2216 incident envelope.
FrameICAO Doc 9332 · IATA WBSAFG - Context
UAM vertiport
Vertical-takeoff + low-altitude transit
Dense urban airspace where bird-strike risk overlaps with building-edge turbulence. Output feeds the vertiport operator's Lattice instance and the operating eVTOL's flight management.
FrameNASA UAM ConOps + KOCA UAM safety guidelines - Context
Military airfield
Coalition CBRN-aware operating environment
Co-located with CBRN-CADS hazard zones. AVIX-AI Animal-class entities and CBRN control areas share the same Lattice surface so the duty officer sees both threat layers in one decision interface.
FrameNATO STANAG 2103 + ATP-2.1.1
Request a live walkthrough.
Sandbox `30dhgc` is live and accepting partner test submissions through 2026-06-03 (token expiry). After that we issue a fresh sandbox per partner.