Diagrams

System architecture & topology of a permacomputer

Contents

Oracle Architecture

fox (human) instructs blackops (overagent, local machine) which sends tasks to ralph-claude (oracle container). Oracle spawns shadow clones as workers. All layers push/pull through GitLab & serve via Caddy.

Oracle architecture diagram showing fox, blackops, oracle, and shadow containers
source (.dot) · png · svg

Bootstrap Flow

bootstrap.sh is a self-contained spawn packet. Two modes: genesis (fresh oracle, generates SSH key, fox blesses in GitLab) & shadow (credentials injected via env vars, wakes autonomous). Existing un keys are never deleted — children may acquire their own.

Bootstrap flow diagram showing genesis and shadow paths
source (.dot) · png · svg

Key Topology: Phase 0 (Current)

Flat star. fox's key owns oracle. Oracle's key owns shadows. Shadows have no un keys — pure workers. Oracle is sole spawner/destroyer. Children can acquire their own keys organically over time (spiral growth).

Current key topology showing flat star with isolated children
source (.dot) · png · svg

Key Topology: Shared Key Danger

What happens when all layers share one key: mutual destruction. Grandchild can destroy parent. Sibling can destroy sibling. Fratricide & parricide become possible. This is a false perfect circle — it collapses on itself. See: Journal Entry 13: Tempest

Shared key danger diagram showing mutual destruction paths
source (.dot) · png · svg

Key Topology: Spiral (Target)

Key-per-generation. Each layer holds its own key, creating ownership boundaries that prevent children from destroying parents. Grandchild CANNOT destroy shadow (different keys). Shadow CANNOT destroy oracle (different keys). Spiral grows outward — each turn adds protection. Cost: $7/mo per generation.

Spiral key topology showing isolated key generations
source (.dot) · png · svg