Skip to content
online

Docs · route D01

Source Map

Source map for v200.8: six truth layers, four provenance origins, distinct document roles, and a visible repository synchronization gap.

Source map plate for truth layers, provenance, and documentation roles.
D01 · visual fieldSource status and source origin remain separate dimensions.purpose-built graphic field · source architecture

SOURCE MAP

Truth layer and source origin are separate axes.

A statement may be accepted direction from the current session, merged implementation from GitHub, observed lab reality, or historical lineage. v200.8 records both what a claim is and where it came from.

STATUS AXIS

Six truth layers.

01

Current reality

Observed hardware, merged code, working commands, and directly verified behavior.

02

Accepted direction

Architecture Dylan has selected even where integration is incomplete.

03

Active working direction

The strongest present choice, still replaceable through evidence.

04

Unresolved design

Questions deliberately left open pending inventory, testing, or review.

05

Target state

Longer-term capability dependent on resources, maturity, and validation.

06

Historical lineage

Earlier decisions and artifacts preserved without overriding the current route.

PROVENANCE AXIS

Four source origins.

Current session

Explicit node-first and V4 decisions supplied for this release.

Pinned repository

GitHub main at 2b613238, still carrying the v120.3 predecessor.

Lab / physical record

Observed or explicitly reported hardware facts that still require evidence and measurement.

Continuity lineage

Older plans, images, notes, and transcripts used to preserve history rather than dictate current architecture.

DOCUMENT ROLES

Each surface has one job.

Huey pagePublic node explanation, embodiment, V4 direction, and node-local status.
Monkey-Head-Project pageUmbrella and eventual collective above nodes.
README pageRepository front door plus clearly separated candidate orientation.
Master Plan pageMachine-facing predecessor/candidate transition and unresolved register.
Repository LedgerExact commit, source paths, merged evidence, drift, and sync state.
Runtime filesWhat actually executes; never inferred from the website.
Governance documentsTarget doctrine and authority questions, not current operation.
Research and archivesLineage, speculation, and provenance without automatic authority.
MACHINE RECORDS

The transition is inspectable offline.

PRIVACY AND CONTINUITY

Machine context is not public biography.

The Human-Counterpart continuity profile was used to prevent flattening, false completion, and role confusion. The file itself is not packaged or reproduced as a public page.