Continuity, lab, documentation, shared services, and future coordination.
Huey · route H02
Monkey-Head-Project
The umbrella, lab-scale continuity system, and eventual collective above one or more valid embodied Huey nodes.
PROJECT BOUNDARY
Monkey-Head-Project is the umbrella and eventual collective.
It contains Huey, HueyOS, LabTech, documentation, hardware work, archives, experiments, shared services, and the later possibility of more than one valid embodied node.
Current centerOne real Huey V4 node—not a running federation.
STRUCTURE
The collective sits above the node.
One embodied AI unit with node-local Brain and Body functions.
Development, archival, diagnostic, recovery, and ingress tooling outside Huey sovereignty.
Shared compute and storage at the collective layer, not a required part of every Huey.
Additional valid physical units with explicit lineage and authenticated coordination.
NOW
Re-centralize around one real machine.
The immediate work is physical cohesion: finish one node boundary before inventing obligations for many.
Inventory
Establish shell, donor, kernel, wiring, storage, power, thermal, and rollback facts.
Integrate
Mount the kernel and supporting systems into one maintainable object.
Validate
Prove boot, evidence, thermals, recovery, safety, and a declared useful function.
Define the node
Record what must persist before reproduction or collective membership makes sense.
CONTINUITY FROM v120.3
Re-scope Brain / Body / Farm—do not erase them.
Huey BrainNode-local cognition, orchestration, memory access, evidence, and operator-facing runtime functions.
Huey BodyNode-local embodiment, sensing, interaction, actuation, power, cooling, safety, and serviceability.
Huey FarmOptional shared compute, model, storage, and support infrastructure at the collective layer.
Huey nodeOne physically individual AI unit containing Brain and Body functions plus its local compute kernel.
COLLECTIVE-LAYER LINEAGE
Bifurcation follows node validity.
Preserve a defined baseline
A controlled lineage or replication event intended to preserve a documented canonical state or profile, with explicit provenance.
Diverge deliberately
A controlled lineage event that intentionally specializes or changes from a documented base.
Neither process automatically establishes identity, sovereignty, authority, citizenship, or collective membership.
TARGET STATE
The collective is a future coordination problem.
Authentication
How nodes and services prove identity.
State placement
Where canonical memory, evidence, models, and logs reside.
Membership and refusal
How a node joins, leaves, disconnects, or rejects coordination.
Authority
What remains node-local and what may be delegated above the node.
Governance
Legitimacy, representation, offices, and conflict handling remain target-state work.
DOCUMENTATION DISCIPLINE
One project; distinct truth surfaces.
Public coherence and clearly labelled candidate alignment.
Human-facing repository front door.
Machine-facing architecture and status.
What actually executes.
Doctrine and future authority, not present operation.
Lineage and continuity without automatic precedence.