Core Embodied AI Framework for perception
+--------------+ +-------------+
| racing-drone | | scout-drone | ... Mission
+--------------+ +-------------+
| |
v v
+---------------------------------------------------------------------+
| Branes Anatomy | Mission
| data contracts, slots and composition, configs, replay log, | framework
| harness, closed-loop simulator |
+---------------------------------------------------------------------+
| | |
v v v
+---------------------+ +---------------------+ +---------------------+
| Branes Cortex | | Branes Synapse | | Branes Reflex | Platform
| perception (VIO, | | tensor graph engine | | stabilization, MPC, |
| SLAM), VLA, world | | for GGUF models, | | state propagation, |
| model, planning | | static memory plan | | fault recovery |
+---------------------+ +---------------------+ +---------------------+
| | |
v v v
+---------------------------------+ +---------------------------------+
| MTL5 | | Universal | Math
| high-performance linear algebra | | computer arithmetic |
+---------------------------------+ +---------------------------------+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+-----------+ +-------------------+ +-------------------+ +-----------+
| CPU | | CPU + GPU | | CPU + KPU | | KPU | Hardware
+-----------+ +-------------------+ +-------------------+ +-----------+
The Branes.AI stack has five tiers:
- Mission: one repo per vehicle and mission.
racing-droneandscout-droneare the two that stand up the architecture; more follow (interceptor-drone,isr-drone,nano-drone,counter-uas). A mission repo owns its task: its world, the slots that see it, its stack and scorer, and its data. Algorithms do not live there. - Mission framework:
anatomy, the body plan every mission composes its vehicle with: the data contracts, the slot concepts and their composition, configs, the replay log, the harness, and the closed-loop simulator. It holds no algorithms and no mission. - Platform: three sister repos,
cortex,synapse, andreflex, that provide the functionality and services a mission is built from. None of them sits above the others. - Math: MTL5 provides high-performance linear algebra and Universal provides computer arithmetic (posits, intervals, mixed precision, hardware-aligned types).
- Hardware: the configurations the stack targets: CPU, CPU + GPU, CPU + KPU, and KPU. Today the stack runs on CPU; GPU and KPU support are planned, and the KPU is a stub until the silicon ships.
Arrows point from a tier to the tier below it that it builds on. They show how the tiers relate, not the dependencies of individual repos: each repo's build declares the libraries it actually uses. A mission also uses platform components directly: it composes them into anatomy's slots.
| Repo | Biological analogue | Responsibility |
|---|---|---|
cortex (this repo) |
Cerebral cortex | Perception (VIO, LIO, SLAM, SfM), vision-language-action models, world building, path planning |
synapse |
The synapses: where signals are transmitted and computed | Tensor storage, graph construction, memory planning, and execution of ML models |
reflex |
Brainstem, spinal cord, autonomic system | Hard real-time control and safety: stabilization, IMU state propagation, MPC, fault recovery |
anatomy |
The body plan | The mission framework: data contracts, slots and composition, configs, replay log, harness, closed-loop simulator |
Create the branes-ai/cortex repository and establish the root folder structure. This strictly enforces the boundaries between your Rust hardware layer, your math, your algorithms, and your middleware.
branes-ai/cortex/
├── .github/
│ └── workflows/
│ └── ci.yml # GitHub Actions CI matrix
├── core/ # Rust Resource Manager (HAL, Memory, KPU sync)
│ ├── Cargo.toml
│ ├── build.rs # cxx C++ header generation
│ └── src/
│ ├── lib.rs
│ └── memory_provider.rs # The SITL vs SoC abstraction
├── math/ # C++ MTL5 NLS Solvers & Data Types
│ ├── CMakeLists.txt
│ └── include/
│ └── branes/math/ # Header-only implementations
├── sdk/ # C++ Spatial Operators (VIO, SLAM, 3DSG)
│ ├── CMakeLists.txt
│ ├── include/
│ │ └── branes/sdk/
│ └── src/
├── daemons/ # C++ Zenoh Wrappers (The Application surface)
│ ├── CMakeLists.txt
│ └── src/
│ └── vio_daemon.cpp # Zenoh pub/sub + YAML parsing + SDK invocation
├── config/ # Unified YAML configuration schemas
│ └── default_bot.yaml
└── CMakeLists.txt # The Master Build Script