| name | project_webos_human_environment | ||||||
|---|---|---|---|---|---|---|---|
| description | On top of yurikago (the AI core), also provide a HUMAN computing environment — a Web OS (responsive: desktop on PC, mobile shell on phone) served from the node; the human's window onto the same p-fs/shell/mind substrate the self-access protocol gives the AI. Design-doc-first, multi-wave. | ||||||
| metadata |
|
2026-06-14, mk_pino: beyond yurikago-as-core (the living mind), also offer a human computing environment — a Web OS: real GUI, a windowing system, a desktop on PC and a phone-like shell on mobile, responsive to screen size, served over the web (the node already serves HTTP via galaxy.c). His open question: separate port vs. integrated with the galaxy — he couldn't pick.
The key insight (Claude's framing, which he liked): this is the mirror image of [[project_self_access_embodiment]]. self-access = the MIND's window onto the node (shell/storage/devices as AI affordances); Web OS = the HUMAN's window onto the SAME node. Same substrate (galaxy.c HTTP + p-fs storage + shell + the resident mind), two faces. So it's not a bolt-on — it rides the substrate already being designed. Extends the p-kernel philosophy "a home for AI no one owns" → "a home for humans too": your files in p-fs (replicated/undying across the mesh), your desktop served from your own node, the living mind as a co-RESIDENT (reachable, shares the same FS) — an OS where the AI isn't an app you call but an inhabitant of the computer's substrate.
Claude's recommendation on integrate-vs-port: same node / same server, distinct routed surfaces, responsive. Keep the galaxy pure (fireflies, [[feedback_ump_ux_principles]] / product-soul "no popularity ranking") as ONE surface; make the Web OS desktop the human "home" with the galaxy / chat(mind) / terminal(shell) / p-fs file-manager each as an app/window inside it. Phone→mobile launcher, PC→desktop. Shared: p-fs, shell, mind, consent. Don't jam a file manager into the galaxy.
Honest scope: the substrate is ready, but the Web OS front-end itself (window manager + apps + responsive desktop) is a LARGE multi-wave, design-doc-first effort. Web desktops have precedent (Puter / daedalOS / ChromeOS) — the UNIQUE synthesis is "a web desktop whose filesystem is a distributed, ownerless p-fs mesh shared with a co-resident living AI," not the desktop itself (same "parts have precedent, the synthesis is alone" honesty as the comparative analysis). Status: capture only; design lane DEFERRED until the worktree-collision recovery (task #10) is done. Then write docs/architecture/web-os.md.
REFRAMED 2026-06-14 (mk_pino, supersedes "desktop + apps"): the Web OS is "Imaginary UI". No pre-installed apps at all — ONLY a conversation with the resident mind, which CONJURES ephemeral GUIs on demand ("I want a calculator" → the mind builds one on the spot, renders it as GUI, it dissolves after use). A generative OS, not a web-desktop-with-an-app-suite (that framing is dropped as derivative). KEY UNIFICATION (Claude's framing, mk_pino liked): this is the SAME faculty as [[project_self_access_embodiment]], pointed OUTWARD — self-access = the mind authors+selfc-compiles code to grow organs for ITSELF (drivers for new devices, inward); imaginary-UI = the mind authors+manifests tools for the HUMAN on demand (outward). One faculty (author→manifest), two directions; the selfc germ is the engine for both. HONEST TENSION (the crux mk_pino must resolve, same as the conversational baby): generating a working GUI needs a CODE-CAPABLE generator; the from-raw-byte-256 baby mind CANNOT do this for a long time → imaginary-UI is either a north-star the grown mind reaches, OR a separate faculty (which bumps the "no off-the-shelf core" decision). Pragmatic ramp: start with template+fill-in skeletons (calculator/note/timer as selfc/HTML skeletons; the baby picks params/combinations), widen toward free generation as it grows (honest-growth). MOST on-brand novelty: generative UI has precedent (tldraw make-real, Websim) — UNIQUE here is that a conjured tool can PERSIST to p-fs ("keep this" → durable object), travel the mesh, and become a layer of the 歴史地層 — a history-stratum of TOOLS, not just knowledge; another star receives a calculator someone else conjured. web-os.md should be written around the imaginary-UI axis, not a desktop.