WfOS (Workflows Operating System) is a local-first control layer for a developer machine. It does not replace your OS, shell, or package managers — it organizes them, routes to them, and exposes their meaning through a consistent local interface. It is modular and non-disruptive: adopt one package, keep your own environment, and grow into the rest when it earns its place.
Full documentation lives in docs/. Start with
architecture.
| Archetype | Product | CLI | Role | Status |
|---|---|---|---|---|
| native-substrate | Dust | dust |
Local Unix/Rust tool execution | implemented |
| metadata-plane | Archon | — | Descriptors, registry, schemas, policies | implemented |
| runtime-controller | Kraken | krk |
Discovery, routing, sessions, rails | planned |
| package-translator | Hypercube | hqb |
Intent → packages and artifacts | planned |
| portable-runtime | Ether | — | WASM/WASI sandboxed components | planned |
Archetypes are stable roles; products are swappable implementations. Above the filesystem, three interface layers — toolchain, agent, application — expose the system at the depth that matches how you work.
This workspace is a moon monorepo with toolchains pinned by proto. Install proto + moon, then:
moon run wfos:setup # proto install — fetch pinned toolchains
moon run dust:doctor # detect tools + write the Archon registry (read-only)
moon query projects # inspect the project graphPins live in .prototools; graph and tasks in .moon/ and per-project
moon.yml. See docs/monorepo.md and docs/setup.md.
| Package | Role | Status |
|---|---|---|
archon/ |
metadata plane — descriptors, schemas, policies | implemented |
dust/ |
native substrate — global low-level tools | implemented |
ether/ |
portable runtime (WASM/WASI) | planned |
hypercube/ |
package translator (hqb) |
planned |
kraken/ |
runtime controller (krk) |
planned |
| App | Purpose | Status |
|---|---|---|
apps/docs/ |
render the docs for humans (Zola) | planned |
apps/web/ |
single-page marketing site (Zola) | planned |
| Doc | Covers |
|---|---|
| architecture | Archetypes vs products, interface layers, system map |
| runtime-architecture | Terminal-first engine: client-daemon, Rust stack |
| monorepo | moon + proto graph, tasks, conventions |
| native-substrate | Native substrate — tools, modules, config |
| metadata-plane | Metadata plane — descriptors, registry, schemas, policies |
| runtime-controller · package-translator · portable-runtime | Planned products |
| agent-rails | Agent rails, gates, MCP, skill scanning |
| apps | Docs + marketing sites |
| tool-catalog | Grouped tools, libraries, skills, crates |
| workflow-apps | Core native workflow apps — notes, writing, AI engine, sessions |
| setup | Developer and agent setup |
For agents, see AGENTS.md.
This workspace is its own standalone git repository (main), local-first with no required
remote. Generated, host-specific output (the Archon tools registry, target/, .moon/cache)
is gitignored; sources, contracts, and docs stay tracked.