Workspace Overview

Locus uses one dockable Editor tab with top-level navigation for Notes, Pins, and Documents. Each workspace owns a different kind of project knowledge while sharing familiar search, selection, toolbar, and Settings patterns.

Choose a workspace

Workspace	Use it for	Authoritative storage
Notes	Searchable written notes, folders, tags, and asset references	External .uenote files in Shared or Private roots
Pins	Spatial annotations associated with saved maps	External .locuspin files in Shared or Private roots
Documents	Longer project-owned Markdown documentation	External .md files under ProjectDocuments

Notes and Pins let you choose Shared or Private ownership. Documents have one project-owned domain and do not have Shared or Private variants.

Shared layout concepts

• The workspace toolbar exposes actions that apply to the active content type.
• Search and filters narrow the current workspace without changing stored content.
• Selecting an item displays its editor or details. Documents open in dedicated tabs; Notes and Pins use their workspace editors.
• Refresh actions rescan the active storage when external files have changed.
• Status and recovery surfaces appear when content needs attention.
• The Settings button opens product-wide and workspace-specific preferences.

Keyboard behavior follows the focused workspace. For example, Ctrl+F focuses the current search, while create, save, rename, and delete commands act only where their context supports them. See Keyboard Shortcuts.

Saving differs by content type

• Notes and Pins save automatically after edits. Ctrl+S flushes or retries the active save.
• Documents use explicit save. Ctrl+S writes the current Markdown source.

Locus uses recovery snapshots and external-conflict handling to avoid silently replacing unresolved work. Those safeguards are not a substitute for backups or source control.

Source-control status

Source control is optional. In Local Mode, all supported local editing remains available without provider calls. When a provider is active, Locus applies checkout, mark-for-add, and delete rules according to the content ownership boundary. See Source Control.