NODE 00 // EDGE TERMINAL — BUILD 2027.1
A WEB-BASED OPERATING SYSTEM FOR THE EDGE
Standalone. Modular. Offline-first. Client-side agents. No server required.
This index.html is the doorway. Launch the sandbox for the full windowed environment, or step outside through any of the three external pathways listed below.
SEC/01 — THE INDEX PAGE
You are looking at the single-file landing page for webXOS 2027 — a browser-native operating environment for the edge. This file is not a marketing site or a download page. It is the front door to a complete system: a full windowed desktop that boots from this same HTML document when you launch the sandbox, plus a structured set of notes on how everything is assembled and where the rest of the project lives.
Everything interactive — the terminal, file manager, text editor, markdown forge, raster console, hardware survey, session manager — lives inside the popup triggered by the Launch Desktop button. This page itself stays deliberately static: no backend, no tracking, no external state. The three sections below — About, Pathways, Architecture — exist to orient you before you step into the sandbox or out to the wider project.
SEC/02 — EXTERNAL PATHWAYS
Beyond this index page, webXOS publishes across exactly three external services. Each one is a distinct doorway — source, weights, and playables. Everything the project has ever shipped is reachable from one of these three URLs.
The complete source tree. Browser-native agent toolkits — ShadowClaw (autonomous agent harness) and Phalanx (multi-agent orchestration) — alongside the Lack minimal POSIX-flavoured shell and the composable UnixAI utilities. Every project is a self-contained artifact you can clone, open, and run without a build step. The whitepaper and architecture notes also live here.
github.com/webxos ↗The published model line. Small language models — the micro-lm series of text encoders, instruction models and quantised chat checkpoints — plus the agent weights that drive ShadowClaw and Phalanx. Everything is quantised for the edge, sized to run in a browser tab, and shipped with the exact inference path used in the demos. Training scripts and evaluation harnesses are included in the repository.
huggingface.co/webxos ↗The playable side of webXOS. Procedural demoscene builds like Starship Builder — a seeded spacecraft construction kit with real-time shader preview — and MicroCraft, a compact voxel sandbox with chunked meshing and a procedural terrain generator. Each one runs in a single browser tab, no install, no account. Every build runs on the GPU of the device you open it on.
webxos.itch.io ↗SEC/03 — DESIGN NOTES
The privacy posture is not a policy — it is a consequence of how the system is assembled. There is no endpoint to call, so there is nothing to log.
There is no sign-up, no login, no session token. Identity is irrelevant to every code path.
Nothing is written to cookies. Preferences use localStorage; the sandbox file system uses IndexedDB.
No analytics, no beacons, no error reporting endpoints. The hardware survey reads browser APIs and renders them in-tab only.
Core modules never open a network connection. Fonts are the only optional external fetch, and the app degrades gracefully without them.
| STAGE | WHAT HAPPENS | WHERE DATA LIVES |
|---|---|---|
| LAUNCH | Popup opens, database is wiped, filesystem is seeded | IndexedDB |
| WORK | Apps read and write records locally | IndexedDB |
| SAVE | Session serialised to plain JSON you download | Your disk |
| CLOSE | Database dropped, storage reclaimed | Nothing |
SEC/04 — ENTRY POINT
// FULL PATHWAY INDEX
// EVERY MODULE IS STANDALONE. ALL DATA STAYS LOCAL.
All modules are standalone. All data stays local. The future is offline-first.