Status: pre-launch. This page describes target design; this document does not establish a deployed service.

C5 -- The Uplink: Complete Orientation

Read this before touching code, strategy, or surface language.

What Is the Uplink?

The Uplink is the organism's compressed orientation layer -- the set of high-density context files that take a new operator or AI agent from zero context to the current executable company logic.

It is not just philosophy and it is not just code orientation. It is the bridge between canon, architecture, product, launch rights, and current strategic sequence.

What Lives in It Now

The current uplink spine (a private repository folder) includes the core seed/framework/organism files plus later guardrail, planning, and disambiguation notes. Do not define it by a fixed historical file count.

• 00_INDEX.md — reading order and routing rules
• 00_CORE/00_ROSETTA_ROW_ROUTER.md — L1-L7 ownership map and tidy law
• 01_SEED.md — 60-second orientation
• 02_FRAMEWORK.md — what IS
• 03_ORGANISM.md — what FOR
• 04_ECONOMICS.md — financial logic
• 05_ARCHITECTURE.md — organs and signal flow
• 06_AGENTS.md — castes and cognitive pipeline
• 07_NEXUS.md — sovereign person root
• 08_PRODUCTS.md — product stack and rooted flywheel
• 09_STATE.md — compiled state sketch; current blockers plus historical route telemetry, not a standalone universal source of truth
• 10_GLOSSARY.md — canonical definitions
• later guardrail, reconciliation, and flagship-path files that keep the packet honest

Reading Order

For operators: 00_INDEX -> 00_ROSETTA_ROW_ROUTER -> 03_ORGANISM -> 07_NEXUS -> 08_PRODUCTS -> 09_STATE

For builders: 00_INDEX -> 00_ROSETTA_ROW_ROUTER -> 05_ARCHITECTURE -> 06_AGENTS -> 07_NEXUS -> 08_PRODUCTS

For commercial teams: 03_ORGANISM -> 07_NEXUS -> 08_PRODUCTS -> 09_STATE

For AI agents: start at 00_INDEX.md, then descend by need. Do not ingest the whole folder flat unless the task actually requires it.

The Current Rooted Sequence

The Uplink now has to be interpreted through one commercial spine:

NEXUS -> Private Business Account -> API PAY -> proof event -> POS scale

Everything else is downstream of that.

• NEXUS acquires through sovereign identity and graph ownership
• the Private Business Account is the first paid bridge
• API PAY is the first clean external activation surface
• the first event proves the loop in bounded reality
• tablet POS becomes the scale surface after proof

Why This Matters

If the Uplink drifts, agents and operators start speaking in future tense about surfaces that have not earned launch rights yet.

The current constitutional rule is simple:

No surface gets broader language than its current proof rights justify.

The main protection against drift is now explicit:

• lane-home canon outranks root compatibility stubs
• the row router clarifies which row owns which claim
• P-SCORES.md, ORGANISM_RUNTIME_TRUTH.md, and dated receipts must not be collapsed into one blanket status word

How the Uplink Is Maintained

The Uplink is version-controlled alongside the codebase. When the genome changes, the Uplink must be updated in the same commit. Stale documentation is worse than no documentation -- it teaches the wrong genome.

Many files carry dated review notes, but not every file uses one uniform freshness field. If verification posture is unclear, route through 00_INDEX.md, the latest audit surface, and current management reorientation notes before treating a file as live authority.

Run the uplink compiler's check mode after source changes that should ripple into the compressed layer.

Where to Find It

A private repository folder, not reproduced here.

See Also

• B0 Nexus Overview
• 96 Nexus
• 94 Pos

---

Uplink Governance Rules (Operator Edition)

The Uplink is a compiled cognitive interface; govern it like infrastructure.

Rules

1. No direct manual drift in compiled files when source should be edited
2. Every major source change triggers recompile check
3. Staleness is measured, not guessed
4. Agent-facing docs must preserve constitutional semantics

Quality controls to maintain

• Staleness report attached to release notes when release notes are produced
• Canon-vs-uplink contradiction scan
• High-impact term diff (invariants, equations, gates)

Operator warning

If Uplink and source diverge, agents execute fiction. Keep the synapse clean.

---