Sovereign cognition // beyond the provider boundary
ENTER THE
LOCAL EVENT.
AVORBYSS opens a cognition aperture inside this device. Cross the horizon, awaken the sealed model cell, and your intent is resolved where you stand—without sending the prompt to OpenAI or invoking a paid model API.
$0 per local model event≈207 MB first cell crossingON-DEVICE execution boundary
Adaptive Aperture // device inspection
LOCATING A COMPATIBLE APERTURE.
Awaken the sovereign cognition cell
The first crossing retrieves the pinned cell into this browser. Once present, AVORBYSS can invoke it here without crossing an external model endpoint.
Direct communion // sovereign device mode
ADDRESS THE
EVENT CORE.
Your intent crosses a local event horizon and returns from the same physical device. The AVORBYSS runtime binds policy, computation, and an exact-result receipt around every completed event—without calling an external model endpoint.
Architecture beyond the horizon
INTELLIGENCE WITHOUT
A CENTRAL THRONE.
DISTRIBUTED DEVICE CELLS
Compatible devices become autonomous inference cells, spreading sovereign events across an expanding constellation and reducing dependence on central GPU fleets.
ADAPTIVE APERTURE
The runtime measures privacy, context, browser, memory, storage, and connectivity before opening the path to a declared model that can fit the event.
EXACT-WORK COLLAPSE
An identical canonical request inside the same principal/device boundary can reuse one verified result. Similar-looking requests never silently collapse.
SEALED ACCELERATION GATE
An optional premium route is architected to reserve finite customer-funded units before execution, settle measured usage, and return what the event did not consume.
Ownership boundary // written into the foundation
AVORBYSS IS ITS
OWN CONTROL PLANE.
ACN 700 220 784 PTY LTD controls the original AVORBYSS control plane: its identity, interface, policy, encrypted Vault, work contracts, evidence system, evaluations, and future Company-trained adapters, subject to the Company’s existing records and assignments. The sovereign device cell is the first provider-independent execution path within that architecture.
PROTECTED NODE BOUNDARYTHE CELL TRAVELS.
THE CELL TRAVELS.
THE SINGULARITY CORE DOES NOT.
A device receives only the bounded runtime and model matter needed for its declared local event. Proprietary orchestration, private equations, scheduler and optimiser logic, evaluation corpus, founder authority, release-signing keys and Company-trained private adapters remain beyond the server-side Event Horizon. The commercial node target is signed, versioned, expiring and revocable.
Technical, capability and licence disclosure
Today’s device cell is the sovereign bootstrap: a pinned third-party open model inside the AVORBYSS runtime, with a deliberately bounded capability envelope. It proves local, provider-independent execution while the Company’s own trained cognition remains a separate research and capital programme. Verify consequential output.
Device inference distributes computation rather than making it disappear. The first load uses bandwidth and browser storage; execution uses the device’s GPU, electricity, and heat. Browser-cached artifacts can be cleared or evicted.
WebLLM and the upstream SmolLM2 model state Apache-2.0. The converted MLC artifact chain is third-party and remains subject to provenance and redistribution clearance before paid node distribution. AVORBYSS claims its original control plane and expression—not another creator’s code or weights.
The downloadable receipt binds the exact contract, output self-check digest, and page-observed execution counts. It can expose changed cached bytes; it is not independent hardware attestation or proof that an answer is factually correct. Durable receipt and Vault writes require authenticated Sites identity; anonymous inference stays local.