fungOS
Download Markdown

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

ComponentOwnsDoes not own
fungOSRuntime profiles, generic rootfs assembly and provisioning seamsEvery application's implementation or license
MyceliumMachine identity, discovery, topology, access and signed distributionApplication transport or inference kernels
GenesisBootstrap, disk/image provisioning and first identity deliveryOngoing application message routing
UnibusAuthorized application envelopes, routing and transportDomain effects or machine lifecycle
CanvasHuman/agent composition, surfaces and application-owned controlsHost provisioning or generic transport
BifrostInference-facing interfaces and routingMachine identity or generic service supervision
UMIEModular inference execution and model recipesFleet authority or arbitrary model compatibility
YggdrasilCompute placement/execution integrationIssuing host identity
ShroudWorkload packaging and execution substrateBare-metal provisioning authority
IPFS/storage providersContent-addressed bytes and cachingApplication permission policy
DCPBounded state-derived decision contractProvider internals or execution authority
HolodeckXR room, interaction and bounded Lua room interfacesCAD/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

  1. First contact delivers a protected machine-specific claim through a provisioner-owned adapter.
  2. Update verification consumes artifact, manifest and signature paths without owning installation.
  3. Application transport consumes narrow domain contracts without interpreting their effects.
  4. DCP execution consumes exact catalog/state revisions and provider-defined arguments.
  5. Inference consumers use the engine's declared model recipes and interfaces rather than backend internals.
  6. 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.