Provider catalogue

Providers extend the filesystem. A provider teaches omnifs how one system should appear in the mounted namespace. This catalogue documents provider path surfaces that have manifests, route registrations, and examples.

Provider catalogue

Provider	Mount prefix	What it exposes
GitHub	/github	repositories, issues, pull requests, Actions runs, repo tree handoff
Docker	/docker	daemon metadata, containers, Compose projects
arXiv	/arxiv	papers, paper JSON, PDFs, source archives, category paper lists
Linear	/linear	teams, issue lists, issue fields
DNS	/dns	DNS-over-HTTPS records and reverse lookups
db	/db	SQLite metadata, tables, schemas, counts, samples

The same shell verbs work across the listed providers:

ls /omnifs/github/0xff-ai/omnifs/issues/open
cat /omnifs/docker/system/version.json | jq .
cat /omnifs/arxiv/papers/1706.03762/paper.json | jq .title
cat /omnifs/linear/teams/ENG/issues/open/ENG-1421/state
cat /omnifs/dns/example.com/MX
cat /omnifs/db/tables/users/schema.sql

How to read provider pages

Each provider page covers:

• what the provider exposes,
• required auth or local resources,
• important path families,
• useful reads to try,
• capability and cache notes.

For exhaustive path lookup, use Path schemes. Provider pages should explain the surface; the reference page is the compact source for copy-paste paths.

Provider availability

The idea catalogue on the homepage can show what other systems might become, but those names are not documented as usable providers until their manifests, route registrations, and examples exist.