
Robotic Shell V1
The earliest workable cabinet-bodied vessel: improvised, limited, and still important because it established Huey as a physical machine.
Huey is the public name of the system when it is addressed as one machine rather than as a collection of boards, tools, and experiments.
Huey Core is the present proof body: the smallest embodied machine that still carries the project’s identity, electrical layering, and long-term direction in one place.
The current phase is about proving continuity, bounded control, local reasoning, and a credible route from this single body toward the broader district-based architecture that comes later.


Huey is being separated by power and responsibility instead of pretending one board should do every job.
The 12V-and-under layer is reserved for bounded support work: body-state, simple sensing, indicators, switch logic, and the watch-and-act functions that need to stay dependable even when the main machine is sleeping or offline.
Higher-power systems carry inference, storage, orchestration, interaction, and the heavier runtime path that belongs on the core machine rather than on the low-voltage edge.

The present proof phase is still trying to demonstrate a small number of things clearly and honestly:

The current machine makes more sense as a line of physical waypoints rather than as one repeated crop. These are the stages that still matter to the present proof body.

The earliest workable cabinet-bodied vessel: improvised, limited, and still important because it established Huey as a physical machine.

The stage that bound the project’s identity to an actual face and body plan instead of letting it drift into a generic computer build.

The present machine where electrical layering, control paths, and local reasoning are being tested as one embodied system.

Kernel work, audio bring-up, and the system-side path keeping Huey Core operational.
Open →
The umbrella initiative that holds Huey, the shell lineage, and the wider technical roadmap together.
Open →
The machine-facing implementation spec for hardware direction, boot logic, and governance baseline.
Open →
The constitutional text shaping lawful growth, authority, and continuity across the system.
Open →
The canonical route into the README, master plan, constitution, and project memory.
Open →
Public bundles, kernel files, and support materials aligned with the current build.
Open →