The NODE Typology Doctrine

§1 · Why This Document Exists

Operator question (May 2026): "I know that I'm one but there's different ones · then explain how a Territory NODE · what benefits do they get · and any other one in the system. Every single one explained, a master document please."

CircularOS already had ~14 NODE-related routes spread across multiple builds (MD-282 Sovereign Node · MD-363 Three Engines · MD-463 Node Hub Doctrine · plus territory pages, international pages, dPRN portal pages). What was missing was a single typology — a one-page answer to "what KINDS of NODE exist, and what benefits does each one get?".

This document is that typology. It does not replace MD-282 / MD-363 / MD-463 — those answer different questions:

• MD-282 · what the Sovereign NODE is + why it's singular.
• MD-363 · how the Three Engines (50/50, Carrot, Concierge) function mechanically + the Austin Bridge promotion path.
• MD-463 · how the Node Hub (geographic catalogue) works.
• MD-480 (this doc) · what every TYPE of NODE is + what benefits each gets + how they relate.

§2 · The Definition · What is a NODE?

A NODE is any sovereign-recognised position in the CircularOS network — a person, a place, a partner, or a portal that carries dPRN flow, supplier flow, capital flow, jurisdiction, or signal.

A NODE is not the same as a page or an agent. A NODE is a position. Pages render NODEs; agents serve NODEs; the Sovereign NODE commands them all.

§3 · The Ten Types · Master Table

§4 · The Territory NODE in Depth (operator-requested)

Operator specifically asked: "explain how a Territory NODE · what benefits do they get."

Definition

A Territory NODE is the geographic franchise for one of the 12 sovereign territories defined in the 90-day Territory Blitz (MD-363): West Midlands · NW · Yorkshire · NE · East Midlands · etc. One NODE per territory. Exclusivity is the default; loss-of-exclusivity if dormant.

Benefits

1. Exclusive territory rights. One Territory NODE per geography. No two compete in the same area.
2. Territory Map presence. Listed publicly on /territory-map, /red-two/territory-map, /twelve-territories.
3. Job-board allocation. Local jobs route to the Territory NODE first via /job-territories.
4. Co-branded marketing. Use of the CircularOS sovereign brand inside the territory.
5. Territory Expansion Playbook access. The full step-by-step playbook (/territory-expansion-playbook).
6. Local hiring authority. Run staffing via /territory-staffing.
7. Revenue split. Defined per the territory contract — share of dPRN net + share of Carrot net for material sourced inside the territory.
8. Preferred Pipeline ranking. Territory NODEs jump the Pipeline Agent (MD-474) queue inside their geography.
9. Veto on competing NODE applications. Sovereign consults the Territory NODE before approving a new 50/50 or Carrot NODE inside the territory.
10. Sealed seat in the Wakey 07:30 briefing when the territory is hot.

Obligations

• Quarterly minimum tonnage threshold (set in territory contract).
• Monthly check-in with Sovereign or appointed Red Two officer.
• Maintain Territory Map data freshness (operator names · contact · live status).
• Honour the £450 dPRN floor without exception.
• Respect the 7% Covenant slice on every tonne · no carve-outs.

§5 · Cross-Type Promotion Paths

A NODE can change type. The system supports three formal promotions:

1. Join-NODE → 50/50 / Carrot / Territory / International — triaged by Sovereign Pipeline Agent (MD-474).
2. 50/50 NODE → Austin Bridge NODE — proven volume + quality + trust → upgraded to Carrot terms while keeping the 50/50 install relationship (MD-363 §Austin Bridge).
3. Territory NODE + 50/50 NODE stack — a Territory NODE can ALSO operate a 50/50 NODE site inside their territory (the two roles stack; the splits combine).

A Sovereign NODE never changes type — there is exactly one and it is permanent.

§6 · The Six Axioms

1. There is one Sovereign NODE. Singular. Permanent. Non-transferable.
2. Every other NODE has a defined cash position and a defined report-up. No NODE without an economic footprint.
3. Every NODE honours the £450 floor and the 7% Covenant. No carve-outs.
4. Promotion is doctrine, not favour. Defined paths only (§5). No backchannel upgrades.
5. External NODEs are watched, not paid. They appear on the map for awareness only.
6. Every NODE is sealed to op_ledger the moment it is classified or reclassified.

§7 · How a NODE Gets Recognised

1. Application via /join-node → enters Join-NODE state.
2. Sovereign Pipeline Agent (MD-474) ranks across six dimensions.
3. Sovereign reviews + classifies into one of the 9 productive types.
4. Classification sealed to op_ledger as `node.classify..as.`.
5. Surfaces appear: pill on /node-typology · entry on relevant hub (/node-hub or /territory-map) · row on Truth Ledger.
6. If reclassified later, sealed as `node.reclassify..from..to.` per the Rename Doctrine (MD-479 §6 procedure, applied to NODEs).