Component ownership and interfaces
fungOS is a Debian-based operating environment built from independent tools. Install the components your machine needs. Each service exposes a versioned interface and controls access to its own data.
Ownership map
| Component | Owns | Does not own |
|---|---|---|
| fungOS | Runtime profiles, generic rootfs assembly and provisioning seams | Every application's implementation or license |
| Mycelium | Machine identity, discovery, topology, access and signed distribution | Application transport or inference kernels |
| Genesis | Bootstrap, disk/image provisioning and first identity delivery | Ongoing application message routing |
| Unibus | Authorized application envelopes, routing and transport | Domain effects or machine lifecycle |
| Canvas | Human/agent composition, surfaces and application-owned controls | Host provisioning or generic transport |
| Bifrost | Inference-facing interfaces and routing | Machine identity or generic service supervision |
| UMIE | Modular inference execution and model recipes | Fleet authority or arbitrary model compatibility |
| Yggdrasil | Compute placement/execution integration | Issuing host identity |
| Shroud | Workload packaging and execution substrate | Bare-metal provisioning authority |
| IPFS/storage providers | Content-addressed bytes and caching | Application permission policy |
| DCP | Bounded state-derived decision contract | Provider internals or execution authority |
| Holodeck | XR room, interaction and bounded Lua room interfaces | CAD/CAM, audio or feed-owner internals |
Availability and setup requirements vary by component; follow each project's installation guide.
Select a deployment
- Base node: generic Debian prerequisites, first-contact and update verification.
- Headless edge: service and message runtime without a local desktop.
- Display edge: Canvas runtime prerequisites, plus separately installed native applications.
- Compute node: explicitly placed inference/accelerator services; resource observations inform eligibility, not trust.
- Existing workstation: independently installed services retain the native OS and security model.
Choose profiles from actual requirements. A GPU does not automatically grant a compute role; a reachable router does not authorize a MIDI output; a model CID does not grant access to private content.
Service interfaces
- First contact delivers a protected machine-specific claim through a provisioner-owned adapter.
- Update verification consumes artifact, manifest and signature paths without owning installation.
- Application transport consumes narrow domain contracts without interpreting their effects.
- DCP execution consumes exact catalog/state revisions and provider-defined arguments.
- Inference consumers use the engine's declared model recipes and interfaces rather than backend internals.
- XR programs consume the versioned room ABI, not credentials or private applet state.
Operational status
The fungOS builder produces root filesystem tarballs. Installer ISOs are not yet available. Persistent amd64 QEMU operation and signed visual rollback have documented test results. Board-specific boot images and a public package service are still in development.
Public owner sources: fungOS README.md, base/interfaces.md, docs/edge-dogfood.md. The broader ownership map is reviewed against the original Mycelium fungOS/ecosystem.md snapshot and Unibus/DCP contracts; freshness tracking here watches the public fungOS source, not every independent project.