Skip to content

feat(inference+mobile): sovereign inference on our mesh + installable mobile PWA (twin or box) - #31

Merged
mdheller merged 1 commit into
mainfrom
feat/sovereign-inference-mobile
Aug 4, 2026
Merged

feat(inference+mobile): sovereign inference on our mesh + installable mobile PWA (twin or box)#31
mdheller merged 1 commit into
mainfrom
feat/sovereign-inference-mobile

Conversation

@mdheller

@mdheller mdheller commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Two asks, one capstone: run LLMs on our infrastructure (not a cloud provider), and see/reach it from a phone.

Sovereign inference (tools/inference.py)

  • A model is an immutable data sphere (provenance, pinned integrity, residency-fenced); loading weights needs a read Grant; a mutated model is un-citable.
  • Serving a model = a GPU workload the compute plane places on a trusted backend (the Needs firewall keeps a sensitive model off untrusted/volunteer/vendor).
  • route_inference is fail-closed sovereign-first: a sensitive prompt (or residency-fenced model) routes to a sovereign endpoint or BLOCKS — it never leaves for a cloud LLM. That's the difference between "our infrastructure" and "a cloud provider like Claude."

Mobile PWA (portal_server.py)

  • Installable (manifest + service worker, offline-ish shell), mobile-responsive, a twin/box endpoint badge. /api/inference shows the sovereign posture + per-model routing.
  • Access model: default to the twin (always-on rendezvous — the box sleeps, the twin doesn't; grants + coordinator live there); opt-in direct to the box for LAN/offline. Same reference-vs-direct lattice from the mount analysis, applied to control access.

156 tools tests green (+11). capd/sovereign-inference.mesh.capd.json.

… mobile PWA (twin or box)

Two asks, one capstone: run LLMs on OUR infrastructure (not a cloud provider), and see/reach it
from a phone.

Sovereign inference (tools/inference.py):
  - a model is an immutable DATA SPHERE (provenance, pinned integrity, residency-fenced); loading
    weights needs a read Grant; a mutated model is un-citable.
  - inference_service_workload: serving a model is a GPU workload the compute plane places on a
    TRUSTED backend (Needs firewall keeps a sensitive model off untrusted/volunteer/vendor).
  - route_inference: FAIL-CLOSED sovereign-first. A sensitive prompt (or a residency-fenced model)
    goes to a sovereign endpoint or BLOCKS — it never leaves for a cloud LLM. Non-sensitive may fall
    back to a vendor connector only when policy allows.
  This is the difference between "our infrastructure" and "a cloud provider like Claude."

Mobile PWA (portal_server.py):
  - installable (manifest.webmanifest + service worker, offline-ish shell), mobile-responsive, apple
    web-app tags; a twin/box endpoint badge (SOURCEOS_ENDPOINT).
  - /api/inference surfaces the sovereign posture + per-model routing; a "Sovereign inference" console
    section shows sensitive prompts routing sovereign or blocked.
  Access model: default to the TWIN (always-on rendezvous — the box sleeps, the twin doesn't; grants
  + coordinator live there), opt-in DIRECT to the box for LAN/offline. Same reference-vs-direct
  lattice from the mount analysis, applied to control access.

capd/sovereign-inference.mesh.capd.json. Tests: +7 inference +4 portal = 156 tools tests green.
@mdheller
mdheller merged commit 76c1bd7 into main Aug 4, 2026
1 check passed
@mdheller
mdheller deleted the feat/sovereign-inference-mobile branch August 4, 2026 06:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant