| App | The root runtime object from packages/api/src/lib/context.svelte.ts. It owns workspace, vault, configuration, commands, metadata, and plugin management. |
| Vault | The file-backed note store exposed through API storage abstractions. New browser-local vaults use OPFS by default; legacy/manual setups can still use Lightning FS. |
| OPFS vault | A browser-local vault whose canonical file bytes live in the origin private file system. |
| Real-folder vault | A vault backed by a user-selected directory through the File System Access API. |
| Vault profile | Browser-persisted startup state that records which vault backend to reopen and the stable vault id used for scoped IndexedDB data. |
| Sidecar stats | IndexedDB metadata used to supplement browser file handles with vault stat fields such as creation time and folder modified time. |
| Workspace | The runtime model for panes, splits, tabs, leaves, and views. It is not just the repo root. |
| Leaf | A single visible view host inside the workspace tree. Leaves can be duplicated, split, and persisted in layout state. |
| View | A runtime screen attached to a leaf, such as text, markdown, file explorer, or search. |
| Core plugin | A plugin loaded directly by the workspace shell during boot, for example the app, file explorer, markdown, search, and bases plugins. |
| Community plugin | A plugin discovered from /.obsidian/plugins and loaded through PluginManager. |
| Configuration schema | JSON-schema-like definitions registered into the app configuration system and rendered in the settings UI. |
| Metadata cache | The app service that tracks parsed file metadata and emits change events used by search and metadata views. |
| Data adapter | The storage backend used by the vault and directory watcher. |