Skip to content
omnifs

Roadmap

omnifs supports read operations. The roadmap focuses on making the read surface reliable, the provider SDK usable, and the host boundary easy to inspect.

Supported surface

Section titled “Supported surface”
  • Linux FUSE runtime.
  • Container workflow for macOS through omnifs shell.
  • npm-distributed CLI.
  • Provider path surfaces documented in the provider catalogue.
  • WASM provider boundary using wasm32-wasip2.
  • Host-mediated callouts and capabilities.
  • Object, view, and blob caches.
  • omnifs inspect for local runtime observability.

Active work

Section titled “Active work”
  • Provider SDK ergonomics.
  • Object-shaped provider patterns.
  • Cache invalidation and trace clarity.
  • CLI setup, auth, status, and doctor output.
  • Provider reference generated from manifests and route registrations.

Planned

Section titled “Planned”
  • More providers.
  • Standalone provider packaging and loading.
  • Runtime frontends for environments where FUSE is not the right interface.
  • Offline snapshots beyond warm cached reads.
  • Write flows that stage intent before applying upstream mutations.
  • Signed provider manifests and richer capability display.

Do not document planned providers, runtime frontends, or write flows as supported behavior until their manifests, command paths, and examples exist.