Glossary

This glossary defines the terms used across the docs. It is model vocabulary, not marketing vocabulary.

Term	Meaning
Path	The filesystem address a user or tool reads, such as /omnifs/github/0xff-ai/omnifs/issues/open/42/title.
Mount	A configured provider instance bound to a top-level namespace such as /github or /db.
Host	The trusted runtime that owns FUSE, credentials, capabilities, callouts, cache storage, provider lifecycle, and container/session setup.
Provider	A wasm32-wasip2 component that projects one system into paths.
WIT	The component interface contract between host and provider.
Provider step	A provider response that is either suspended with callouts or returned with a terminal result and effects.
Callout	Host-mediated work requested by a provider, such as HTTP fetch, Git repo open, blob fetch, archive open, or blob read.
Effect	A terminal host mutation requested by a provider return: canonical store, filesystem view write, or invalidation.
Object	A provider-defined domain resource with a logical id, canonical bytes, and rendered leaves.
Logical id	The object identity used by the host cache and provider self-checks.
Canonical bytes	Verbatim upstream object bytes stored by the host as durable source material for an object.
Field leaf	A file path derived from an object field, such as title, state, or description.md.
Rendered view	A filesystem record derived from provider output or canonical bytes.
Object cache	Durable host cache for canonical object bytes.
View cache	Host cache for derived files, directories, attributes, and listings; recreated on startup.
Blob cache	Host disk storage for large byte payloads such as PDFs, source archives, and archive trees.
Tree-ref	A host handle for a real backing tree, such as a cloned Git repository.
Capability	A host grant that allows a provider-requested effect, such as a domain, Git repo pattern, Unix socket, preopened path, or auth injection.
WASI preopen	An explicit local filesystem path made visible to a provider sandbox.
No ambient authority	The provider has no direct network, arbitrary disk, Docker, Git, or credential access outside host-mediated capabilities.