06 Inside
Two runtimes, one contract.
Python and the browser meet at a strict, predictable boundary. Python manages the virtual file system, users, and logic; the browser renders the stage.
STAGE / JAVASCRIPT
The visible machine
terminal · windows · apps
audio · clipboard · mesh UI
syscall()
< JSON >
effects
KERNEL / PYTHON
The source of truth
VFS · users · commands
executor · audit · AI
INDEXEDDB the file system persists here JSON
The effect contract
Python never touches the DOM. When it needs the browser to play a sound, open a window, split a pane or copy to the host clipboard, it returns a structured effect. JavaScript performs it.
{
"effect": "play_sound",
"notes": ["C4", "E4", "G4"],
"duration": "4n"
}
- Kernel
- CPython 3.14.2, Pyodide 314.0.7
- Runtime
- WebAssembly; no build step, no npm
- Shell
- 150+ Python commands; pipes, redirects, jobs
- Storage
- IndexedDB; export and import the VFS
- Mesh
- WebRTC data channels + BroadcastChannel; optional signaling
- AI
- Ollama locally or Gemini; configured in
/etc/ai.conf
- Safety
- voltage scoring, confirmations, package hashes and audits
- Platforms
- Browser, Neutralino desktop, Raspberry Pi / x86_64
JARGON, TRANSLATED
- Kernel
- The part that actually does the work: files, users, commands.
- Shell
- The place where you type. It is a program, not a metaphor.
- WASM
- A compact, sandboxed way to run compiled code in a browser.
- Mesh
- Computers talking directly to each other, with no cloud in the middle.