Docs · route D03

Master Plan

Machine-facing transition from the merged v120.3 Brain/Body/Farm plan to a clearly labelled v121.0 node-first candidate.

Machine-facing plan transition plate separating v120.3 from the v121.0 candidate. — D03 · visual fieldThe predecessor and candidate remain parallel, attributed, and status-labelled.purpose-built graphic field · plan transition

MACHINE-FACING TRANSITION

v120.3 remains the predecessor. v121.0 is the candidate.

The website preserves the actual Brain / Body / Farm record and stages a new node / collective plan separately. It does not manufacture a repository merge.

STATUS

Two plans, two explicit states.

PREDECESSOR ON MAIN

Master Plan v120.3

Records the July 12 Brain / Body / Farm architecture, PyHuey direction, open V1 position, namespace migration, fidelity, logging, testing, procurement, and unresolved boundaries.

The merged file still self-labels proposed_in_pr; v200.8 reports that provenance mismatch rather than editing history.

Open v120.3 ↗

CANDIDATE · SYNC PENDING

Master Plan v121.0

Moves the top-level unit from three constitutive parts to one embodied Huey node beneath the Monkey-Head-Project umbrella and eventual collective.

Encodes V4, node-local compute, Farm re-scope, bifurcation placement, non-claims, and unresolved implementation gates.

Open candidate JSON

ARCHITECTURE DELTA

The change is top-level, not cosmetic.

Primary unitv120.3: Brain / Body / Farm · v121.0 candidate: one embodied Huey node

Project boundaryv120.3: umbrella behind Huey · candidate: explicit umbrella and future collective above nodes

Identityv120.3: Brain-centred / unresolved distribution · candidate: physical node as primary identity-bearing unit; internal criteria still open

Bodyv120.3: broad active rework · candidate: concrete V4 embodiment program

Farmv120.3: principal part · candidate: optional collective-level service

Computev120.3: future pooled capacity · candidate: provisional node-local multi-GPU path

Bifurcationv120.3: lineage concept · candidate: explicit collective-level mechanism after node validity

PRESERVED

v121.0 inherits the disciplines that still hold.

Truth separation

Current reality, accepted direction, active working direction, unresolved design, target state, and lineage.

Evidence

Secret-safe structured logs, checksums, failures, recovery, versions, and attributable outputs.

Testing

Unit, mocked integration, fixture fidelity, manual live paths, and failure testing.

PyHuey and CLI

Primary GUI direction with recoverable command-line operation.

Open V1

Usefulness and evidence determine the declaration.

Authority

Dylan remains the sole current canon authority.

NON-CLAIMS

The candidate keeps uncertainty visible.

V4 is not declared built.

The i9 kernel is not declared installed.

V100 cards are not declared acquired.

GPU memory is not declared transparently pooled.

Farm is not required for one Huey.

Collective governance is not operational.

OPEN REGISTER

Questions remain machine-visible.

Identity

What persists through changes to shell, storage, GPU set, board, and software state?

V4 completion

What evidence distinguishes present, assembled, integrated, operational, validated, and complete?

Compute

Which cards, topology, framework, model, latency, throughput, and degraded mode?

Farm

What shared infrastructure qualifies, and what stays node-local?

Bifurcation

What is copied, what is prohibited, and how identity and authority are established?

V1

What recurring useful task earns the declaration, and must V4 participate?