Traditional robotics stacks are a chain of hand-tuned modules — perception feeds prediction feeds control — where an error anywhere becomes an error everywhere. CerebrumFlow replaces that chain with a single learned loop that keeps sensing, reasoning, and motion coherent, end to end.
We fuse cameras, lidar, IMU, and joint encoders into a single probabilistic scene. Every estimate carries calibrated uncertainty — a per-estimate covariance that says how wrong it might be — so the system knows what it doesn't know, and passes that knowledge downstream instead of dropping it at the module boundary.
This is the part most stacks get subtly wrong. An occluded corner is not empty space. A dust-obscured lidar return is not a wall. Treating "no signal" as "nothing there" is how robots drive confidently into the thing they couldn't see.
Planning here is model-predictive control over a short receding horizon. We roll out a few hundred milliseconds of candidate trajectories against a learned dynamics model, score them against cost and safety, and commit only the first action before the world moves again.
Constraints aren't penalties tuned by hand — they're hard. Joint limits, velocity and acceleration caps, and the non-holonomic constraints of a wheeled base are enforced as feasibility filters, so an unsafe candidate never reaches the controller.
Intent becomes motion through a feedback loop that measures and corrects in real time. Whole-body control resolves arm and base together — a reach that needs the base to shift produces one coordinated motion, not a two-step shuffle. Errors are corrected within the cycle they occur, not accumulated until failure.
Contact is where most motion stacks come apart. For insertion, assembly, and grasping, we run impedance control with force/torque feedback, so the robot complies instead of jamming when a part is a millimeter off.
The loop doesn't touch the cloud. Perception, planning, and actuation run on embedded compute under a real-time scheduler with a fixed latency budget — so "fast" is a guarantee, not a hope.
Perceive–plan–act completes 40 times a second, the rate real motion needs.
Perception 11 ms, planning 8 ms, actuation 5 ms — a fixed, enforced budget.
Jetson-class and automotive SoCs. No cloud round-trip on the control path.
Real-time scheduler with watchdog. A stage that overruns degrades, it doesn't stall.
If a stage misses its budget, the loop drops to slower replanning and keeps the safety filter running.
ROS 2, DDS, and EtherCAT for motor-level I/O — drops into existing robot stacks.