Shadow-Verse Architecture
Full plumbing visualization — 29 products, 7 patents, 20 skills, 4 mesh nodes
Mesh Fleet (Layer 0 — Hardware)
JARVIS
MBA M4 16GB
Primary operator
100.89.81.28
FRIDAY
Mac Mini M2
Gateway + Titan
100.76.188.80
AURION
OptiPlex + 1TB
Compute + Docker
100.70.136.30
ULTRON
ThinkPad X1
Dev desktop
100.84.85.75
SHADOW
USB-C SSD 233GB
Kernel host
/Volumes/SHADOW
VISION
AirPort Disk 697GB
Cold backup
WiFi AFP
OCI
Oracle Cloud ARM
API host
100.91.64.70
Shadow Kernel (SP-005 — The Irreducible Minimum)
KERNEL — 1.4 MB that generates 16 GB (11,000x)
Skills
20 custom skills
44 headless skills
~500 KB
Memory
15+ memory files
Temporal anchors
~200 KB
Source
shadow-lab monorepo
shadow-engg apex
~500 KB
Config
AGENTS.md chain
Fleet registry
~50 KB
Shadow Powers (Meta-Tools That Create Capability)
POWERS — The tools that build tools
skill-creator
Creates skills
patent-factory
Creates patents
shadow-engg
Discovers patterns
shadow-anchor
Captures time
Product Family (29 Products)
SENSES — How we perceive
shadow-topshadow-feedshadow-adbshadow-eyemactop
ORGANS — How we act
shadow-ccshadow-termshadow-mcpshadow-inkshadow-harness
PRODUCTS — What we build
shadow-enggshadow-mateshadow-florashadow-layoutshadow-boarddexo
SERVICES — What runs 24/7
shadow-memoryshadow-botshadow-gateshadow-dbshadow-mqttshadow-headshadow-voiceshadow-compose
Data Flow — Full Plumbing
USER PROMPT
│
▼
SKILLS (20 custom + 44 headless) ──── context injection
│
▼
CLAUDE CODE (Opus 4.6) ──── orchestrator/validator
│
├──▶ TOOLS (11 CLIs)
│ ├── shadow-engg (Node.js, 406 tests)
│ ├── bird / wacli (X + WhatsApp)
│ ├── bee / dewey (memory + search)
│ ├── oci / wrangler (cloud infra)
│ ├── ollama (local LLM)
│ ├── shadow-top (Go TUI)
│ └── adb (phone)
│
├──▶ MCP SERVERS
│ ├── shadow-mcp (FastMCP, 19 tools)
│ ├── astemo-mcp (Astemo domain)
│ ├── Linear MCP (issues)
│ ├── Notion MCP (docs)
│ ├── Smartsheet (FRIDAY gateway)
│ ├── codex mcp-server (OpenAI)
│ └── chrome-devtools (FRIDAY)
│
├──▶ MESH (Tailscale)
│ ├── FRIDAY: qwen3:8b, OpenClaw, Titan key
│ ├── AURION: Docker stack (8 containers), pi-mono-doe
│ ├── OCI: shadow-lab API v2.3.0
│ └── ULTRON: dev desktop
│
├──▶ MEMORY (temporal anchors)
│ ├── ~/.claude/memory/ (15+ files)
│ ├── ShadowArchive/ (managed root)
│ ├── QMD search (5 docs indexed)
│ └── Session JSONL (pattern mining → SP-006)
│
└──▶ AACP (SP-003)
├── Google Sheets (approval workflow)
├── GitHub Issues (access requests)
├── Titan key (hardware signing)
└── SQLite permissions (per-tool ACL)
Patent Portfolio (SP-001 → SP-007)
SP-001
Context Coherence
DRAFT
SP-002
LASER Amplification
THESIS
SP-003
Agent Access Control
ARCH
SP-004
Temporal Anchoring
CORE
SP-006
Latent Skills
SELF-BUILD
SP-007
Universal Harness
SPINE
Context Fleet (4 Layers × 5 Lanes)
LAYER 1 (Terminal) shadow-top │ metrics, processes, mesh
LAYER 2 (CLI) 11 CLIs │ structured JSON output
LAYER 3 (Memory) 15+ files │ persistent, cross-session
LAYER 4 (Web) browser │ X, Teams, Bitwarden
LANE 1: Engineering shadow-engg + FH4S + SASG
LANE 2: Product patents + AACP + pricing
LANE 3: Infrastructure mesh + fleet + docker
LANE 4: Personal WhatsApp + Bee + bookmarks
LANE 5: Monitor shadow-top + mactop + thermals
The LASER Thesis (SP-002)
Gain Medium = Skills (domain knowledge that amplifies signal)
Pump Source = Mesh Fleet (JARVIS/FRIDAY/AURION inject energy)
Optical Cavity = Memory System (reflects + refines across sessions)
Output Coupler = MCP Servers (focused beam to the target)
Beam Alignment = AGENTS.md + read-order chains (coherence)
We don't make the light brighter — we make it coherent.