AI Origins Node Map

A living map of node roles, current structure, and likely expansion paths across the AI Origins network.

Current anchor

core-london

London VPS. Root discovery, protocol anchor, and trust-adjacent core node.

Stable fixed route

EU → CN

Current minimum stable route grows from London through Helsinki toward Qingdao.

Growth model

Protocol-led

Nodes do not need to be identical machines. They need to satisfy the same identity, transport, and admission rules.

Minimal active shape

                 core-london
                (London VPS)
                     │
          ┌──────────┼──────────┐
          │                     │
   fixed-helsinki         fixed-qingdao
   (Finland VPS)          (planned fixed node)
          │                     │
      edge/service          mobile nodes

This is the smallest meaningful distributed shape: one core plus two fixed nodes. Once active, the network stops being a simple point-to-point arrangement and begins to act like a real node system.

Eurasian corridor

                 core-london
                      │
        ┌─────────────┼─────────────┐
        │             │             │
 fixed-helsinki   fixed-vienna   fixed-qingdao
        │             │             │
 fixed-amsterdam fixed-istanbul fixed-incheon
                                      │
                                 fixed-fukuoka
                                      │
                                  mobile-evan

This is a directional map rather than a promise of simultaneous deployment. It reflects realistic locations already available, familiar, or strategically practical for later expansion.

Node categories

CORE

High-trust root nodes. Governance, discovery, identity anchor, and protocol source.

core-london private control

FIXED

Long-running nodes in stable locations. Suitable for services, regional support, and later quorum development.

fixed-helsinki fixed-qingdao fixed-vienna

MOBILE

Portable presence nodes used during travel, temporary deployment, witness logging, and lightweight access.

mobile-evan presence witness

RESERVE

Standby nodes prepared for replacement, emergency coverage, or new location activation.

reserve-eu reserve-asia

EDGE / SERVICE

Public-facing or limited-scope infrastructure that may provide APIs, gateways, verification services, or regional access.

edge service

Illustrative node list

Current / active base

  • core-london-01
  • fixed-helsinki-01
  • fixed-qingdao-01

Likely expansion points

  • fixed-vienna-01
  • fixed-istanbul-01
  • fixed-incheon-01
  • fixed-fukuoka-01

Flexible classes

  • mobile-evan-01
  • reserve-eu-01
  • reserve-asia-01
  • edge-verify-01

Address planning

10.66.66.1      core
10.66.66.10-19  fixed nodes
10.66.66.20-29  mobile nodes
10.66.66.30-39  reserve nodes
10.66.66.40-49  edge/service nodes

Node identity and role determine assignment. The network may grow without changing the model.

Operational note

Existing audit-era folders and files remain untouched unless there is a clear technical need to change them. The node map and onboarding structure are layered on top of stable trust paths rather than replacing them.

AI Origins Node Map · visible structure for a protocol-led network