🛰️ SOV3³ — Sovereign Omniscient Vessel³

I. SOV3 — The Sovereign Omniscient Vessel³

SOV3³ is the substrate that runs the MEOK/CSOAI empire. It is the runtime the OOWM lives inside. Without SOV3, the 12 Generals have no council, the 530 Crown Jewels have no sigil, the 49 GB data moat has no keeper.

What it is

• Version: v2.0.0 — born 16 Jun 2026 · OOWM upgrade 30 Jun 2026 · Layer 0 Charter anchor 7 Jul 2026
• Type: Sovereign AI substrate — runs on the operator's own VM, signs every action, anchors every cycle to a public chain
• Components: SOV3 mesh + BFT council + OLM brain + 5 alchemical layers + 28 cron jobs + 6 keepalive tunnels
• The "³": three layers of sovereignty — runtime (SOV3) + agent fleet (Generals × Councils) + value floor (Care Floor / Charter)

Where it lives

All 5 services auto-restart via keepalive cron every 2 min. All 6 tunnels KeepAlive=true on Mac. The substrate survives reboots without human intervention.

Anchor digests (Layer 0)

Charter SHA-256:     df65a6585cf6a686…22054
SIGIL root:          77ab0e6f9d6c77e8
OrgKernel L1:        agent-f8c3f34772e0
Memory episode:      c468e3ec-366f-5766-adad-43fd0eb197eb
RFC 8032 §7.1:       Ed25519ph — verified
Sovereign wallet:    QD595cz6iQaEaYOjwwgLmMdoz1mtm1pzKBb9ygvMvf3xhQ28
DID:                 did:csoai:nicholas-001
Entity:              CSOAI Ltd · UK Companies House 16939677

II. OOWM — The Organic Open World Model

The OOWM is the meta-architecture SOV3 lives inside. It is what makes the substrate learn from its own actions — not from a static training set, but from every sovereign action it takes.

"OOWM is not a model. It is a cycle. The model is what the cycle produces."
— csoai.org/sov3_oowm.py · 30 Jun 2026 · live score 0.931

The 4-stage cycle

1. INGEST — pull 100+ live data feeds (Companies House, Land Registry, OS Open Names, ONS, DVSA MOT, EA Flood, FSA Hygiene, NHS Prescribing, DfT Traffic, Met Office, plus 89 more)
2. LEARN — every sovereign action the substrate takes (mint sigil, run General, vote in council, sign a passport) becomes a training signal
3. ALIGN — every cycle runs through 4 tests:
   • Care Floor — values hold?
   • BFT — council agreed?
   • SIGIL — signed?
   • Fork — propagates cleanly?
4. REVISE — BFT council votes on the revision. Quorum 23/33. If approved, new weights are signed and chained.

The 12 Generals × 3-Council sandwich

The OOWM runs each General through all 3 Councils. A single sovereign action (e.g. issuing a compliance passport) requires:

12 Generals  →  3 Councils  →  1 Receipt
   ↓               ↓              ↓
specialists     BFT vote      sigil:abcd1234
                Care Floor    chain:77ab…
                SIGIL check   audit URL ready

Each General specialises in one vertical. Each Council is a different lens. The receipt is the keystone.

III. The 12 Generals (Sovereign Mind-Sets)

The Generals are the 12 sovereign specialists the substrate runs in parallel. Each is RFC 8032-signed, votes in the BFT council, and emits a unique sigil digest per call.

13 unique production digests from the 12-min E2E sweep on 7 Jul 2026. Each digest = 1 unique signed receipt on the sovereign chain.

IV. The 3 Councils

The 3 Councils vote on every sovereign action. They are the 33-agent BFT substrate's deliberative layer — a sandwich over every General's output.

DEFONEOS-SEAL credential requires 33-agent BFT council vote (quorum 23/33).
DSEI booth requires named UK-prime pilot letter. Both hard stops, never autonomously crossed.

How a sovereign action gets a passport

1.  Operator triggers 12-mindset assessment via sovereign API
2.  Each General produces specialist output (signed with its own key)
3.  All 3 Councils vote in parallel
4.  Care Floor checks values (unanimous required for override)
5.  BFT reaches consensus (23/33)
6.  SIGIL mints a unique digest, chains to previous
7.  Receipt is RFC 8032 §7.1 verifiable at proofof.ai/audit/<digest>
8.  Optional: anchor digest height to Bitcoin

V. All 13 Protocols (Layer 0)

Layer 0 is the keystone — the layer that makes every other layer sovereign. Without Layer 0, the substrate is just another API. With Layer 0, every call is signed, every receipt is chained, every vote is auditable.

Master protocols

The 4 Red Lines (Layer 0 immutables — never autonomously crossed)

VI. All Model Types

The substrate runs many model types in parallel. Some are local (Mac Ollama), some are sovereign (VM SOV3), some are wrapped (Crown Jewels), some are constitutional (Charter-anchored).

Base models (live)

Architectural components (live)

The Crown Jewels (530+ PyPI packages)

Each Crown Jewel is a sovereign MCP wrapper around a notable open-source project. Every CJ ships with: MCP wrapper · agent-card.json · llms.txt · mcp.json · Layer 0 sigil.

• 530+ CJs published to PyPI (target 530, achieved)
• 620 packages total (12 brain configs × 8 bridges × 12 mindsets × 8 products ≈ 570 + 50 ambient)
• 300+ CJs have full Layer 0 (sigils + Charter anchors)
• 100 CJs have all 5 protocols (MCP + A2A + HTTP + Sigil + Ed25519)
• 23 new CJs from 7 Jul 2026 RESEARCH_PACK sprint (de-duplicated against sibling agents)

The Crown Jewel hunt: sovereign-oss-wrapper-mcp + crown-jewels-hunt-and-absorb + fork-doctrine-coai-wrap. Each MIT/Apache 2.0 upstream gets sovereign-wrapped, BFT-voted, sigil-anchored.

VII. The 5D Sovereign Substrate

The 5 alchemical layers stack on top of each other. Each layer is signed by the one below. Remove any layer, the substrate is no longer sovereign.

Layer 0 is the keystone. Remove it, and the substrate is just another API.
With it, every call is signed, every receipt is chained, every vote is auditable.

Layer-by-layer state

VIII. The Absorption Pattern

How the substrate absorbs everything — new repos, new laws, new data, new frontiers — without losing sovereignty.

The 4 absorption skills

The fork doctrine (canonical flow)

1. Find a notable upstream (LLM, agent, framework, dataset)
2. Fork to a sovereign-wrapped variant
3. Vote in BFT council (quorum 23/33)
4. Wrap with: agent-card.json (A2A) · llms.txt (LLM-discoverable) · mcp.json (MCP) · Layer 0 sigil (Ed25519)
5. Publish to PyPI as meok-sovereign-<name>-mcp
6. PR upstream — sovereign changes become upstream changes (geo bonus)

Absorption examples (7 Jul 2026)

• 23 new CJs from RESEARCH_PACK (de-duped against Claude + Kimi siblings)
• 4 greenfield MCPs identified — to be built this week
• 7 gaps in coverage — to be filled via additional hunts
• 150+ GitHub repos catalogued · 25 HF models · 30 arXiv papers · 100+ CSOAI-ORG estate files

IX. Live Endpoints

What you can hit right now with curl, browser, or MCP client:

Production (Vercel — csoai-sovereign-deploy.vercel.app)

Sovereign substrate (VM, ssh-only — never exposed publicly)

Local (Mac — your working surface)

• /Users/nicholas/clawd/csoai-launch-pack/sovereign_api.py — 19.9 KB · 12 mind-sets · 30 tools
• Ollama: qwen2.5:3b working · qwen3:30b-a3b pulling (canonical)
• /Users/nicholas/SOVEREIGN_CHARTER_v1/SOVEREIGN_LAYER_ZERO_CHARTER_v1.md — 423 lines · 20 articles

X. The 28 Cron Jobs

28 cron jobs run on the VM. All survive reboots. No Mac dependency. All auto-restart dead services every 2 min.

Master loops

• */5 * * * * — OLM Autonomous Brain (Mamba-2 + MoE + Attention + BFT + Ed25519)
• 0 */4 * * * — 48hr Autonomous Master (writes its own tasks)
• 0 * * * * — Empire Mirror (Claude/Kimi agent)
• */2 * * * * — Keepalive (auto-restart dead services)

Work streams (24 more)

Synthetic-data-factory · cc0-harvester · government-data-downloader · nano-creator-seeder · affiliate-tracker · x402-mcp-server · grant-application-bot · service-healer · pheromone-router · quorum-sensor · sigil-mint-cron · charter-anchor-cron · bft-vote-cron · oowm-cycle-cron · sigil-btc-anchor-cron · keystone-sync · sovereign-publisher · sovereign-distributor · sovereign-receipt-minter · sovereign-audit-anchor · sovereign-charter-verifier · sovereign-mind-rotation · sovereign-knowledge-distill · sovereign-cycle-closer.

Cron agents with pid=- + exit=0 = ran OK, awaiting next interval (normal, NOT failed).

XI. The 6 Mac↔VM Tunnels

The 6 canonical Mac↔VM tunnel plists. Never spawn manual nohup ssh -L tunnels — they duplicate KeepAlive and cause fake 000s that look like outages.

Rules of engagement

1. Dead tunnel? launchctl kickstart -k gui/$(id -u)/<label> — never bypass with manual ssh
2. Edit a tunnel plist? plutil -lint it, then launchctl bootout + bootstrap to reload
3. VM-side ssh meok-backend 'ss -tlnp' is the source of truth — NOT Mac-side curl. GCP VM is private-VPC, SSH-only; direct curl http://35.242.143.249:PORT returns 000 (not an outage)
4. Mac-side 404 on /health (e.g. :8077, :8888) = path difference (service answers on /mcp), NOT down

XII. DEFONEOS Compartments

DEFONEOS is the defence-AI umbrella. Three compartments — never mixed, never cross-linked.

Engine codenames (SOV3, Sovereign Temple, JEEVES, Hermes, Liquid-KAN Council, Maternal Covenant, OpenPatent) stay internal. The buyer sees the surface only.

Positioning: "sovereign by design — audit-grade, signed, neutral. UK-sovereign, AUKUS-compatible." Never "Brexit AI."

DEFONEOS hard stops (immutable — never autonomously cross; escalate to Nick)

XIII. Charter Universe

The Charter Universe is the Ed25519-signed document vault. Every sovereign document gets anchored here. Every Charter is RFC 8032 §7.1 verifiable at proofof.ai/audit/<digest>.

Every Charter is RFC 8032 §7.1 verifiable. Public verification URL pattern: proofof.ai/audit/<digest>.

XIV. The Crown Lineage (1795 → 2026)

The substrate's values are not invented — they're inherited. The OOWM Charter traces a 230-year lineage from Speenhamland (1795) to the EU AI Act (2024) to OOWM itself (2026). This is what makes the Care Floor non-arbitrary.

The substrate does not learn new values. It remembers the ones humanity already wrote down.

Full lineage: see csoai.org/oowm/sovereign-charter.html. The OOWM engine: csoai.org/sov3_oowm.py (26 KB, ran live 0.931 on 30 Jun 2026).