YAML Metadata Warning:empty or missing yaml metadata in repo card

Check out the documentation for more information.

Sovereign Dual Runtime

License: BSL-1.1 WASM 6502 M5 Docker θ

Author: Ahmad Ali Parr
Trust: Bel Esprit D'Accord Irrevocable Trust · EIN 42-697643

Three runtimes. One WORM chain. Everything sandboxed.


Architecture

graph TD
    subgraph BROWSER["Browser / Agent Interface"]
        WASM["WASM Sandbox\nPyodide iPython\nOnly tool: Python\nNo network · No FS write"]
    end

    subgraph DOCKER["Docker Container (isolated)"]
        M5["M5 Bridge :9091\nWASM ↔ 6502 API\nRuntime status\nDoorbell proxy"]
        VM6502["6502 Sovereign VM :9090\nHeartbeat T0-T10\nWORM sealing\nMMIO doorbell"]
        WORM["WORM Chain\n/sovereign/worm/chain.jsonl\nSHA-256 append-only\nEvery event sealed"]
        QEMU["QEMU ARM64 :5555\nAndroid phone emulator\nTermux bash inside\n(Option 4 — full phone)"]
    end

    WASM -->|"fetch /api/runtime-status"| M5
    WASM -->|"fetch /api/doorbell/kick"| M5
    M5 -->|"Unix socket IPC"| VM6502
    VM6502 -->|"append seal"| WORM
    M5 -->|"append seal"| WORM
    QEMU -->|"virtio-serial doorbell"| VM6502

Three Runtimes

Runtime 1 — WASM Agent Sandbox (iPython)

  • What: Pyodide WebAssembly Python in the browser
  • Tool: iPython only. No network. No filesystem write. Fully isolated.
  • Use: Agent runs Python code, calls sandbox.seal() for WORM entries
  • Port: 8788

Runtime 2 — 6502 Sovereign VM (Control Plane)

  • What: Rust implementation of the sovereign 6502 heartbeat (T0-T10)
  • From: sovereign-agent-kernel architecture
  • Does: 12ps/gate tick heartbeat, WORM sealing, MMIO doorbell reception
  • Port: 9090

Runtime 3 — M5 Compatibility Bridge

  • What: Axum HTTP API bridging WASM ↔ 6502 VM
  • From: sovereign-hypervisor-arm64 M5 engine
  • Does: /api/runtime-status, /api/doorbell/kick, /api/worm/latest
  • Port: 9091

Option 4 — QEMU ARM64 Full Phone (optional)

  • What: QEMU emulating ARM64 Android device with Termux
  • How: scripts/dual-runtime-start.sh → qemu/launch-phone.sh
  • ADB: adb connect localhost:5555

Quick Start

# With Docker (recommended)
cd docker
docker-compose up --build

# Open agent sandbox
open http://localhost:8788/agent-sandbox.html

# Check runtime status
curl http://localhost:9091/api/runtime-status

# Watch WORM chain
docker exec sovereign-dual-runtime tail -f /sovereign/worm/chain.jsonl

WORM Chain

Every event across all three runtimes is sealed to a single append-only chain:

{"hash":"a3f9c2e1b4d7","prev":"genesis","agent":"system","event":"dual_runtime_start"}
{"hash":"7b2e1f4a9c3d","prev":"a3f9c2e1b4d7","agent":"6502","event":"T10 SOVEREIGN_ACTIVE"}
{"hash":"2c8f5a1e7b4d","prev":"7b2e1f4a9c3d","agent":"agent","event":"code_exec"}

θ = 89/2462

The sovereign constant is injected into the WASM sandbox as THETA = 89/2462. Every Python execution environment has access to it. The 6502 VM uses it for TDMA phase alignment.


© 2026 Bel Esprit D'Accord Irrevocable Trust · Patent Pending · θ = 89/2462

Downloads last month

-

Downloads are not tracked for this model. How to track
Inference Providers NEW
This model isn't deployed by any Inference Provider. 🙋 Ask for provider support

Space using Snapkitty/sovereign-dual-runtime 1