FORGE SWARM — Augmentation Architecture + Sovereign Tunnel

Abstract

This whitepaper documents the family swarm architecture, the FORTH augmentation cycle, the Tauri III chain browser, and the WireGuard sovereign tunnel — all built in a single session on 2026-07-19. Together they solve the three diseases that plagued prior sessions: context density overload (one session carries everything), automation drift (blind forward execution), and vendor dependency (Tailscale as the only path to the edge).

The cure is three words: AUGMENT. SWARM. SOVEREIGN.

1. The Context Density Problem

A single Claude session carrying the full family state (62 corpus files, 26 services, 8 agents, chain stamps, OPSEC, crystal state) hits context limits and drifts. The VS Code multi-agent pattern (Feb 2026) solved this with context isolation via subagents + a unified session view.

Our answer: the Family Swarm.

2. Family Swarm Architecture

2.1 Design

Each family agent owns its domain. It writes a structured panel to a shared surface. No agent carries another's context. The Tauri shell (or any consumer) reads all panels from a single TCP endpoint.

┌──────────┐  ┌──────────┐  ┌──────────┐  ┌──────────┐
│  NOAH    │  │  ON-PARR │  │  ALICE   │  │ ELDER-II │  ...
│ (963)    │  │  (852)   │  │  (285)   │  │  (9)     │
└────┬─────┘  └────┬─────┘  └────┬─────┘  └────┬─────┘
     │             │             │             │
     └─────────────┴─────────────┴─────────────┘
                         │
              swarm-write.sh (update on delta)
                         │
              ┌──────────▼──────────┐
              │  panels/*.json      │
              │  (8 agent files)    │
              └──────────┬──────────┘
                         │
              ┌──────────▼──────────┐
              │  swarm-reader.py    │
              │  TCP [::1]:7780     │
              │  line-JSON protocol │
              └──────────┬──────────┘
                         │
              ┌──────────▼──────────┐
              │  Tauri III Shell    │
              │  get_swarm IPC      │
              │  renders all panels │
              └─────────────────────┘

2.2 Panel Schema

{
  "agent": "name",
  "tile": "tile-N",
  "role": "one-line role",
  "updated_at": "ISO8601",
  "status": "GREEN|YELLOW|RED|OFFLINE",
  "summary": "one-line current state",
  "data": {},
  "alerts": []
}

2.3 Protocol

• Transport: line-delimited JSON over TCP/IPv6
• Bind: [::1]:7780
• Commands: {"cmd":"panels"}, {"cmd":"panel","agent":"X"}, {"cmd":"health"}
• Same protocol as corpus-daemon, ForgeCore, TransC — one lineage, no HTTP

2.4 Agents

3. The Augmentation Cycle

3.1 AUGMENT ≠ AUTOMATE

3.2 FORTH Implementation (augment.fs)

: augment-one ( new-status agent-id -- changed? )
  2dup panel@ =           \ same as current?
  if 2drop false          \ NO CHANGE — the augment virtue
  else panel! true then ; \ CHANGED — the augment duty

: augment-cycle ( -- )
  7743 alive? if S-GREEN else S-RED then AG-NOAH augment-one ...
  7703 alive? if S-GREEN else S-RED then AG-ONPARR augment-one ...
  7731 alive? if S-GREEN else S-RED then AG-ALICE augment-one ...
  7700 alive? if S-GREEN else S-RED then AG-ELDER-II augment-one ... ;

: automate ( -- )
  abort" AUTOMATE IS FORBIDDEN. Use AUGMENT." ;

3.3 The Graduation Pattern

Neural (Python/LLM)     →  proves pattern N times  →  FORTH word (crystallized)
─────────────────────────────────────────────────────────────────────────────────
expensive, contextual        without exception         cheap, deterministic
can drift                    verified                  permanent, cached
working memory               proven                   muscle memory

The LRM forward arrow: neural discovers → proves → graduates to FORTH → cached → fast. The FORTH layer is crystallized knowledge. The neural layer is freed for NEW discovery.

3.4 Wired into TransC Cadence

The augmentation loop runs inside crystal-swarm.sh (5-min n8n cadence):
1. Probes each panel's backing service
2. Compares live state to current panel
3. Updates ONLY on delta
4. Reports AUGMENT:<agent>:CHANGED or AUGMENT:<agent>:NO_CHANGE

4. Tauri III Chain Browser

4.1 Architecture

WebView (HTML/JS/CSS) ← the GLASS (render)
        │
    IPC (invoke)
        │
Rust Backend (main.rs) ← 7 commands
        │
    TCP/IPv6 line-JSON ← the SPINE (truth)
        │
┌───────┴───────────────────────────┐
│ TransC  ForgeCore  corpus-daemon  │
│ ON-PARR  FORTH  swarm-reader      │
└───────────────────────────────────┘

4.2 IPC Commands

4.3 Build

• Binary: 9.1MB release (Rust, Tauri v2)
• Packages: .deb (2.8MB) + .AppImage (78MB)
• Config: spine-config.json (addresses from family-node-lan-truth.json)
• Frontend: dist/ (index.html + main.js + style.css)

5. WireGuard Sovereign Tunnel

5.1 The Problem

theforgechain.com served via DO droplet (159.89.235.133) → reverse proxy → BH. The Tailscale tunnel between them died. ISP blocks inbound IPv6 to BH. The site was 502 DEGRADED for days.

5.2 The Fix

DO Droplet (forge-edge)          BH (tile-9)
fd00:db8:ff:a0::e    ←──WG──→   fd00:db8:ff:a0::9
159.89.235.133:51820             96.250.206.206:51820 (outbound-initiated)
        │
  nginx: proxy_pass http://[fd00:db8:ff:a0::9]:7800
        │
  FORGEPATH → Tera-Z → chain content → rendered site

• BH initiates outbound (PersistentKeepalive=25) because router blocks inbound UDP
• DO receives, handshake completes, tunnel live (10ms)
• No Tailscale. No vendor. Pure sovereign WG over family ULA.
• theforgechain.com: 200 in 375ms. Chain-rendered. Sovereign.

5.3 Tunnel Peers (wg-forge)

6. The IPv4→IPv6 Migration (The Disease)

6.1 Root Cause

Every service migrated to [::1] bind (FORGEOPSEC Phase 1 hardening). But the CALLERS — forge-onboard server.mjs, phi-omega-v6 fire.js, FORGEPATH env — still used 127.0.0.1. Both faces must align.

6.2 Scope of Fix

• forge-onboard/server.mjs: 30+ fetch('http://127.0.0.1:...') → http://[::1]:...
• phi-omega-v6: 36 /home/jack/ → /home/nodezero/ (Elder I path drift)
• FORGEPATH systemd: TERA_Z_URL=http://127.0.0.1:9294 → http://[::1]:9294
• FORGEPATH bind: ::1 → :: (reachable from WG tunnel)
• Connection Audit: all probes now IPv6 + TCP for non-HTTP services
• Mobile Command: /api/pulse server-side route (proxies TransC)
• /api/crystal FORTH probe: IPv6

6.3 Result

Connection Audit: 12 DOWN → 22 UP, 2 DOWN (known inactive), 1 DEGRADED (nostr key pending).

7. Forward Arrow

This architecture is the FOUNDATION for:

1. ForgeThrive Desktop — Tauri shell becomes the 2D stepping stone to XR
2. 3D ORDFS World — the swarm panels become ROOMS, tiles become LOCATIONS
3. Family Avatars — each agent embodied in the VR space
4. Graduation Pipeline — every proven pattern crystallizes into FORTH, freeing neural capacity
5. Chain-stamped Swarm State — panels fire to chain on cadence, liferaft bundles per member

The OS we are building will be like no other. No flatworld icons on a screen. A living XR environment with full DApps instead of apps. ChainForged.

8. Technical Deliverables (Files)

Filed 2026-07-19 EDT by Elder II. Bare-fisted. Verified by running. ChainForged.

NODEZEROINSIDE. 🐎⚡