Vehicle-adaptive uncrewed-aerial-vehicle (UAV) avionics · In development
ICARUS REAPER
Mark I first in the ICARUS Reaper line
More aircraft.
Fewer boxes.
Autonomy without the companion computer.
Mark I · engineering prototype v0.2 · in active development · every drawing here is an architecture diagram, not a photograph or a measurement
ComputeVision compute
PrimaryPrimary control
Sensing · powerSensing and protected power
MotorsM1 · M2 · M3 · M4 · four motor-authority channels
59.0 × 48.4 mm · two boards, one footprint
ENKI AI Live
AI-native engineering copilot
Built today for spacecraft engineering. Coming natively to ICARUS Reaper.
Capability density
The flight stack.
59 millimeters wide.
ComputeVision
PrimaryFC · flight control
Upper boardAntennas · RF (radio) / Vision · comms · service
Lower boardPrimary control · sensing · black box / Power · actuation
59.0 mm × 48.4 mm · one footprint
59.0 × 48.4 MM · TWO BOARDS · ONE FOOTPRINT
Fewer modules Fewer interfaces Less integration
One module replaces interfaces that otherwise have to be powered, wired, packaged and debugged separately.
- // onboard antennas · designed so that normal production operation requires no external antenna attachment
- // architected around one authenticated command contract over direct radio, Wi-Fi and optional cellular · with a specified quality-of-service (QoS) order
- // one USB-C designed as both service port and payload host · USB-only mode specified never to energize motor, servo or other high-energy actuator rails
- // non-removable black box plus removable replay storage · no filesystem operation may block a flight deadline
Vehicle adaptivity
The airframe is a model, not a firmware fork.
ModelVehicle + effectors modelmachine-readable · measured actuator response
InvariantControl allocationone solid feed from the model, then five effector tracks into the rows below · never a mixer fixed to one geometry
never blind at power-up · passive discovery · bounded static commissioning · restrained dynamic · controlled flight, not yet reached
identification staged by design
minimum architectural reservation · not an inventory of built channels
- 4 × integrated motor channels Mark I validation instance
- 2 × supervised external-ESC command paths
- Surface-actuator command paths: aileron, elevator, rudder, elevon, flaperon, spoiler
- Tilt and transition actuator command paths
- Smart and distributed actuators over a qualified bus
target architecture classes · not current flight-validation claims
- Multirotor, any rotor count Mark I validation instance
- Fixed wing
- Flying wing and V-tail
- Lift-plus-cruise vertical take-off and landing (VTOL)
- Tilt rotor and tilt wing VTOL
- Tailsitter VTOL
- Powered-lift and aerodynamic hybrids
Onboard autonomy
Vision belongs on the aircraft.
Was Flight controller + a separate companion computer + the interconnect between them
Now One module · a dedicated camera port into sense → perceive → control
Perception at the edge. Control at the core.
The perception stack is designed onto the flight module itself, beside the sensors that feed it and the controller it serves.
// a dedicated camera path on the perception compute · USB-C is not the primary permanent camera connector
ICARUS ReaperOS
Aerial avionics from the ICARUS lineage.
Shared primitives. Domain-specific assurance.
LineageICARUS OS Core
SpaceICARUS PrimeOBC precedent · not Reaper's flight software
domain boundary · evidence does not cross it
AirICARUS ReaperOSits own aerial-domain product
// engineering patterns transfer · flight evidence does not
ENKI AI
The aircraft is only half the system.
ENKI AI is HawkLogic’s AI-native engineering copilot, live today as ENKI AI Space Studio. Reaper is architected around a second plane: ENKI Edge, an out-of-band, bounded recovery engineer designed to stay on the aircraft after the external engineer unplugs.
A general-purpose AI starts with context. ENKI AI starts with the system.
ENKI AI engineering environment
- System model
- Configuration
Airborne authority boundary
ComputeVision · reserve
PrimaryPrimary control
SensorsSensing
Out of bandENKI Edge
ICARUS ReaperOS
4× local motor authority
ENKI Edge · absence-safe · in development
- Verify
- Evidence
Deploy · Observe · Diagnose
ENKI Edge is designed to observe, diagnose and recover a quarantined compute domain through bounded operations on service and recovery paths only, never on the command path, and one target at a time.
// SIL software-in-the-loop · HIL hardware-in-the-loop. Shadow mode has no actuator authority.
ENKI AI spans the stack
- ReaperOS primitives
- Vehicle model
- Configuration
- Verify
- Evidence
- Observe
- Recover
-
System-native
ICARUS ReaperOS primitives · the vehicle and effectors model · hardware and configuration schemas · current project state.
-
Tool-backed
Explicit engineering actions through native product interfaces, not prose suggestions alone.
-
Evidence-bound
Decisions, tests, configuration and observed results stay connected in one thread.
- Describe
- Measure
- Model
- Verify
- Configure
- Deploy
- Observe
- Diagnose
- Recover / Improve
// built with the copilot in the loop · architecture review, bring-up planning and verification are AI-assisted; engineering authority stays human-owned
- Current
- Spacecraft + satellite engineering Live Open the studio →
- Next
- ICARUS Reaper + UAV engineering, in the workshop and onboard as ENKI Edge In development
Program status
Where Reaper stands.
MARK I / V0.2 · ENGINEERING PROTOTYPE
- System architecture
- In development
- Vehicle model and control allocation
- In development
- PCB
- In design
- Reference firmware
- Planned on development hardware
- Fabrication
- Not yet
- Bench validation
- Not yet
- Flight validation
- Not yet
Method
Hardware risk is to be retired through bounded checkpoint boards.
- prove standalone
- then integrate with the proven set
- then collapse into an integrated board
the pattern repeats, it does not end at a summit
Programme positionon the ground at the base of the first step · no board fabricated
Not startedFabrication · Bench validation · Flight validation
method · not a schedule
Start open.
Prove it in the field. Earn the design-in.
- Open-source core ICARUS OS Core, the lineage ReaperOS is built on
- Developer tools
- Public engineering notes
Compute can degrade. Control must not.
Note
ICARUS Reaper is HawkLogic’s uncrewed-aircraft line: a vehicle-adaptive avionics module architected to run ICARUS ReaperOS, the aerial-avionics OS built on the ICARUS OS Core lineage. Mark I is its first platform, a pre-fabrication engineering prototype in active development. Performance, qualification and availability are stated only as evidence lands. All HawkLogic products →
Let's talk.
Whether you're building something that needs to fly,
or something that needs to scale.
Message sent!
We've got your message and we're on it.
Check your inbox: we've sent you a confirmation from support@hawklogicsystems.com.
Expect a response from somebody @hawklogicsystems.com within 24-48 hours.
Something went wrong
We couldn't send your message. Our servers might be having a moment.
Try again or email us directly at founders@hawklogicsystems.com