The method behind SOV3, stated so it can be checked.
Whitepaper · v1 · 2026-07-12
The SOV3³ / OWEM architecture — one paper, every claim independently assayable.
The substrate is bound to a person, not a platform. It runs on permissively-licensed open weights (MIT / Apache-2.0 / CC0), so it is portable across any host — the owner can switch clouds and the substrate follows. Copyleft components (AGPL/GPL) are quarantined to the free/open tier only; the paid/sovereign tier is built on permissive-only dependencies plus the owner's own IP.
Six invariants never change as the substrate grows: the care-floor, Article 0 (no equity, board seats, revenue-share or success fees from certified institutions), the 12 governance pillars, BFT-33 quorum, SIGIL attestation, and sovereign-binding. Growth that would violate an invariant is rejected outright — this is what separates accretive growth from unconstrained drift.
Stated plainly so no reader is misled: traffic-driven automatic brain addition, memory tiering, and GPU auto-provisioning are designed but not live; any GPU or spend action is owner-gated and does not run unsupervised. Capability vs. frontier models (a GSM8K/MMLU head-to-head) is unmeasured in this record — it requires a dedicated benchmark run and the governance metrics above are explicitly not a substitute for one.
Most labs claim "it scales." Few can say — and back with a re-runnable number — that a system grows without forgetting, stays with its owner across platforms, and holds a fixed, auditable safety floor while it grows. That auditability, not a larger parameter count, is the differentiator this paper is making the case for.