docs: Formalize Three-Class Architectural Roadmap (Class 1 Simple, Class 2 Orchestrator, Class 3 Global Multiplier)

Author: hyperpolymath

0-AI-MANIFEST.a2ml

@@ -9,9 +9,9 @@ This is the AI manifest for **Bundle of Joy Server**. It declares:
 - Critical invariants (rules that must NEVER be violated)
 - Repository structure and organization
 
-## 🏰 DUAL-TRACK ARCHITECTURE (CLASS 1 vs CLASS 2)
+## 🏰 THREE-CLASS ARCHITECTURE (ROADMAP)
 
-This repository implements a Dual-Track design to balance simplicity and scale.
+This repository implements a tiered design to balance simplicity, technical rigor, and global scale.
 
 ### **Class 1: Simple Track (Canonical)**
 - **Focus:** Zero-infrastructure simplicity.
@@ -25,7 +25,13 @@ This repository implements a Dual-Track design to balance simplicity and scale.
 - **Cartridge Pattern:** Uses core generic handlers to wrap cartridge FFI.
 - **Path:** `adapter/v/src/class_2_orchestrator/`.
 
-**INVARIANT:** Class 2 features must NEVER damage or replace the Class 1 foundation.
+### **Class 3: Multiplier Track (Global)**
+- **Focus:** Extreme fault tolerance and mass concurrency.
+- **Workflow:** Extension Store proxying (Claude, ChatGPT, Mistral).
+- **Multiplier Pattern:** **Elixir / BEAM** piggyback unit for massive scale.
+- **Project:** `elixir-mcp-server` / `boj-server-gemini`.
+
+**INVARIANT:** Advanced features must NEVER damage or replace the Class 1 foundation.
 
 ## CANONICAL LOCATIONS (UNIVERSAL RULE)
 

README.md

@@ -12,21 +12,27 @@ A genuine 'bundle of joy'.
   <img src="https://www.bestpractices.dev/projects/12164/badge" alt="OpenSSF Best Practices passing (115%)" />
 </a>
 
-## 🏰 Dual-Track Architecture
+## 🏰 Three-Class Architecture
 
-BoJ Server provides two distinct ways to interact with cartridges, catering to different needs for simplicity and scale.
+BoJ Server provides three distinct deployment tiers, catering to different needs for simplicity, security, and global scale.
 
 ### **Class 1: Simple Track (Canonical)**
 - **Focus:** Simplicity, local-first, zero-infrastructure.
-- **Workflow:** Repositories use standard GitHub Actions (`curl` triggers) to talk to the server.
-- **Implementation:** Each cartridge is self-contained with its own adapters.
-- **Best for:** Most users, quick setups, and easy debugging.
+- **Workflow:** Repositories use standard GitHub Actions (`curl` triggers) to talk to the server REST API.
+- **Implementation:** Self-contained V-lang adapters wrapping Idris2/Zig logic.
+- **Best for:** Personal infrastructure, solo developers, and easy debugging.
 
 ### **Class 2: Orchestrator Track (Advanced)**
-- **Focus:** Unified transport, high-performance, massive scale.
+- **Focus:** Secure gateways and technical orchestration.
 - **Workflow:** Uses secure Webhooks (HMAC-SHA256) and unified real-time gateways (MQTT/WebSockets).
-- **Implementation:** Core-level generic handlers located in `adapter/v/src/class_2_orchestrator/`.
-- **Best for:** Production environments, IoT integration, and multi-agent orchestration.
+- **Implementation:** Core generic handlers located in `adapter/v/src/class_2_orchestrator/`.
+- **Best for:** Corporate settings, VPN-backed services, and technical power users.
+
+### **Class 3: Multiplier Track (Global)**
+- **Focus:** Extreme fault tolerance, concurrency, and mass distribution.
+- **Workflow:** High-performance proxying for extension stores (Google, Claude, ChatGPT, Mistral).
+- **Implementation:** **Elixir / BEAM** "piggyback" unit providing massive-scale process supervision.
+- **Best for:** Mass audiences, distributed Umoja networks, and commercial extension hosting.
 
 ---