# Huey Node and Monkey-Head-Project Collective Model

## Status and scope

This explanatory document accompanies the v200.8 website alignment and candidate Master Plan v121.0. It separates the current node-first direction from the still-merged v120.3 repository baseline.

## Definitions

**Huey node:** one physically individual AI unit integrating local compute, HueyOS runtime functions, operator interaction, structured evidence, recovery, and physical embodiment.

**Monkey-Head-Project:** the umbrella and eventual collective containing one or more nodes, LabTech, shared services, archives, optional Farm resources, and later supra-node coordination.

## Huey as one embodied node

A Huey node is not merely a language model, workstation, GUI, shell, or network endpoint. It must become one coherent machine with a declared physical boundary, local evidence, recoverable operation, and a useful function.

## Internal node domains

### Brain functions

Cognition, orchestration, memory access, evidence, recovery, and operator-facing runtime functions.

### Body functions

Physical embodiment, sensing, interaction, actuation, power, cooling, safety, and serviceability.

### Local compute kernel

CPU, storage, accelerators, I/O, firmware, drivers, and runtime support inside the node boundary. Multiple accelerators inside one machine do not create a collective.

### PyHuey operator interface

PyHuey remains the primary GUI and core runtime direction. It is the operator-facing interface of a node, not the physical embodiment or the collective.

## Monkey-Head-Project as umbrella and collective

The umbrella already exists as the project, lab, documentation, and continuity structure. The multi-node collective is a target architecture. It must not be described as operational before more than one valid node and explicit coordination contracts exist.

## Brain / Body / Farm continuity

Brain and Body move inside the node as functional domains. Farm moves above or beside nodes as optional shared compute and storage. A valid Huey node does not require Farm participation.

## Node validity before collective operation

A node should be physically coherent, attributable, recoverable, operator-visible, safe enough for its declared stage, and useful for a stated function. Multi-node governance is not a prerequisite.

## Exact bifurcation

A controlled lineage or replication event intended to preserve a defined canonical state or profile, with explicit provenance.

## Augmented bifurcation

A controlled lineage event that intentionally diverges or specializes from a documented base.

Neither path automatically determines identity, authority, sovereignty, or collective membership.

## Disconnection and degraded operation

Node-local operation must be defined separately from collective services. Authentication, refusal, network partition, shared memory, state conflict, and degraded operation remain unresolved.

## Current reality, direction, and target state

Current reality is one physical shell lineage and one external i9/TUF/Optane machine. Active direction is Huey V4 as one coherent node. Target state includes additional nodes, optional Farm resources, bifurcation, and legitimate collective coordination.