AERQORA + AEVON / PROPOSED INTEGRATION

Connected by design.
Defined by boundaries.

Aevon supplies the OS foundation. Aerqora owns the vehicle systems and integration.

01 / SOFTWARE FOUNDATIONAevon OSAgents · authority · resources · device servicesIntegration planned
Versioned interfaces · bounded requests · health

AI proposes. Deterministic control validates and acts. Timing and stop behavior need qualification on each target.

01 / OWNERSHIP

Each layer has a job.

Platform responsibilities
LayerOwnsScope
Aevon OSKernel · agents · authority · resourcesIndependent software project
Aerqora shared modulesPerception · communications · interfacesReusable engineering candidates
Aerqora DronesFlight control · propulsion · airframesAircraft-specific releases & validation
Aerqora RoboticsMotion control · machines · hands / armsProposed track · separate validation
Board profilesBoot · drivers · hardware bindingsEvidence for each exact target

02 / AEVON + HARDWARE

One architecture.
Target-specific support.

Board and OS status · UNO Q updated 18 November 2026
TargetIntended roleCurrent evidenceStill to establish
Arduino UNO QSplit compute / controller researchNative Aevon port completeVehicle integration & control qualification
Raspberry Pi CM5Aevon reference · Aerqora communicationsScoped RAM evidenceVehicle integration pending
STM32 controllersFlight / motion-control candidatesTarget-specific workControl firmware & timing qualification
NVIDIA OrinAerqora perception computeEngineering packageNative Aevon support not established

Native port completion and vehicle qualification are tracked separately.

Aevon project

03 / UNO Q

Two processors.
Native Aevon on board.

UNO Q / NATIVE PROCESSOR ROLES

QRB2210 + STM32U585

QRB2210Native AevonApplication compute
STM32U585Native AevonReal-time MCU
Arduino board documentation
AEVON NATIVE PORT / COMPLETE

Ported and running

The QRB2210 runs the native Aevon image with storage and inference services. The STM32U585 has its own original Aevon MCU port. Linux is retained as a separate maintenance boot.

Next: carrier sensor integration, measured control-loop timing and aircraft validation.

Native Aevon port complete

04 / CONTROL PRINCIPLE

AI proposes.
Local control decides.

Bounded requests, explicit authority and platform-specific limits connect intelligence to physical action. Each implementation needs measured evidence.