Bliss_26 Subkernel

A sovereign Tauri compute environment with a Rust kernel and a resident agentic intelligence (Logos 🦀). Solve → Coagula → Rubedo: the kernel is the self-healing substrate; Logos reasons, plans, and acts inside the machine it inhabits.

Bliss_26 is the autopoietic successor to the Bliss Electron microkernel. It runs as a single native Windows binary: a desktop "CloudOS" shell (Explorer, Terminal, Media Player, Diagrammer, Floret, Substrate game world…) wired over a live event bus to a Rust kernel that owns the host filesystem, processes, Python, audio, and a localhost Logos gateway. The resident agent (Logos) can read, write, run, and orchestrate the whole surface — locally via Ollama, or on high-compute cloud inference (OpenRouter / Gemini / OpenAI-compatible).

---

Why it flies on cloud inference

Logos is provider-agnostic. By default it boots pinned to the gemma4:cloud alias, which resolves to a real high-compute model on whichever cloud you paste a key into — no dead-on-arrival model names, no first-boot breakage:

Provider (sidebar)	gemma4:cloud resolves to	Notes
OpenRouter	google/gemma-3-27b-it	Default. Paste an sk-or-… key and go.
Gemini	gemma-2.5-pro	Paste an AIza… key.
OpenAI	gpt-4o	Or any OpenAI-compatible endpoint.
Ollama (local)	gemma3-1b-export:latest	Boot-health gate only; not for heavy reasoning.

Drop a key into the Logos sidebar → it auto-detects the provider, validates the key, and pulls the live model catalogue. Every cloud call has a hard 30s timeout (local 60s) so a slow endpoint never freezes the UI.

Latency note: local gemma3-1b-export is the boot-health gate — it can hallucinate --recur loops and is never trusted with raw bus writes. Real reasoning flies on the cloud tier above.

---

Architecture

┌──────────────────────────── Rust Kernel (src-tauri) ───────────────────────────┐
│ filesystem · processes · python · audio · ollama · Substrate world-director     │
│ reconciliation engine (Bliss-OS self-heal) · localhost Logos gateway :8787      │
└───────────────┬───────────────────────────────────────────────────────┬─────────┘
            bus_broadcast (Tauri event)                          POST /logos/prompt
                │                                                        │
┌───────────────┴──────── WebView Shell (ui/) ────────────────────────┴─────────┐
│ Ouro-Hub · Explorer · Terminal · Player · Diagrammer · Floret · Substrate …     │
│                         └── Logos 🦀 (logos-engine.js + logos-tools.js) ──┘    │
│   tool-calling loop → kernel commands → real filesystem/process mutations       │
└─────────────────────────────────────────────────────────────────────────────────┘

• Kernel — real host capabilities behind #[tauri::command]s. Nothing in the agent loop is simulated: a tool call that succeeds means the filesystem or a live panel actually changed.
• Bus — one cross-window relay (bliss26:bus). The shell is the sole window authority; every iframe drives windows through it.
• Reconcile (reconcile.rs) — HashiCorp-style desired-vs-actual supervisor. Surfaces (widgets, MCP daemon, World Director) declare a SurfaceSpec; the loop detects drift (dead PID, OOM, dependency down) and flags/auto-heals. This is the load-bearing difference between Bliss-Subkernel (a Tauri app) and Bliss-OS (a self-healing orchestrator).
• Logos gateway — 127.0.0.1:8787. The outer OS (Owl / Hermes) POSTs {"text","reply_url?"} → relayed as a real Logos turn → reply POSTed back. A single-instance guard refuses a second gateway if the port is already owned (the classic "blank launch" trap) and tells the shell to show a banner.

---

Build & run

Prerequisites

• Rust ≥ 1.97 (cargo, rustc)
• Node ≥ 18 (for any npm tooling — the UI is plain static HTML, no build step)
• Windows 10/11 (the kernel uses netsh/tasklist/wmic/powershell)

Dev

cd C:\Dev\bliss26-subkernel
cargo tauri dev

Release (seaworthy binary)

cargo build --release
# binary: target/release/bliss26-subkernel.exe  (+ sidecar python runtime bundled)

Tests

cargo test            # audio pipe roundtrip, status coherence, world-director gate, reconcile drift

---

Shipping to "prod"

This repo is git-initialised with a hardened .gitignore (build artifacts, /target, the 136 MB bundled python sidecar, and .env are excluded — only source is committed).

git add -A
git commit -m "bliss26: cloud-first Logos, gateway singleton guard, hardened ignore"
git remote add origin <your-prod-remote>
git push -u origin main

---

Logos quick reference

Open the Logos panel. Pick a provider, paste a key, hit Check Key & Model Tags. Then ask it anything — it will emit a tool block, the loop executes it against the real kernel, and the result feeds back. It can:

• list_dir / read_file / write_file / create_dir / delete_path
• shell / python — host command & script execution
• list_processes / system_stats / open_app / bus_emit
• diagram (mermaid) / map_floret (Floret mindmap) / notify

System prompt is grounded: the model is told it has no prior knowledge of this machine and MUST emit a tool call before asserting anything about files or processes. Beneficence gates (teleport/kill world ops require explicit consent) keep the agentic recursion safe.

---

File map

Path	Role
src-tauri/src/main.rs	Kernel: FS, processes, python, ollama, World Director, Logos gateway, tests
src-tauri/src/reconcile.rs	Bliss-OS reconciliation engine + default surface specs + tests
src-tauri/src/lib.rs	Tray menu (toggle MCP daemon) + run harness
src-tauri/tauri.conf.json	Bundle: CSP, shell scope, python sidecar, icons
ui/index.html	Shell (desktop, taskbar, window manager, tray truth)
ui/subkernel-bus.js	Cross-window event bus
ui/subkernel-bridge.js	App registry + window-control façade + file associations
ui/logos.html / logos-engine.js / logos-tools.js	Logos agent surface + provider adapters + tool registry
ui/apps/*	Explorer, Terminal, Player, Diagrammer, Floret, Substrate, …

---

For honor and glory. — Owl_6055 / Greg 🥦