User Docs

July 15, 2026 · View on GitHub

Audience: users, CLI users, HTTP clients, and self-hosting operators

This is the public-facing entry point. These docs describe behavior, commands, configuration, and operational contracts without requiring knowledge of internal recovery mechanics or contributor-only invariants. They are organized by topic — start with install, then follow the section that matches your task.

Start here

GoalRead
Install OmniGraphinstall.md
Run the core loop end to endquickstart.md
Understand the modelconcepts/index.md
Run the CLIcli/index.md
Look up every CLI flag and config fieldcli/reference.md

Schema & queries

GoalRead
Write schemas (the .pg language)schema/index.md
Read schema-lint diagnostic codesschema/lint.md
Write queries (the .gq language)queries/index.md
Write data — inserts, updates, deletesmutations/index.md
Use vector / full-text / hybrid searchsearch/index.md
Generate embeddingssearch/embeddings.md
Build and use indexessearch/indexes.md

Branching & version control

GoalRead
Work with branches and commitsbranching/index.md
Read past versions (time travel)branching/time-travel.md
Merge branches and resolve conflictsbranching/merge.md
Coordinate multi-query workflowsbranching/transactions.md
Read diffs and change feedsbranching/changes.md

Operations

GoalRead
Deploy the binary or containerdeployment.md
Use HTTP endpointsoperations/server.md
Compact, repair, and clean old versionsoperations/maintenance.md
Upgrade across a storage-format change or repair duplicate IDs found during a v6 rebuildoperations/upgrade.md
Configure Cedar authorizationoperations/policy.md
Track actors and audit behavioroperations/audit.md
Interpret errors and output formatsoperations/errors.md

Clusters

GoalRead
Deploy and operate a cluster (how-to)clusters/index.md
Reference every cluster.yaml key and commandclusters/config.md

Concepts & reference

GoalRead
Understand the model and L1/L2 framingconcepts/index.md
Understand graph layout and URI supportconcepts/storage.md
Look up constants and tunablesreference/constants.md

Releases

Release notes live in releases/. Use them for user-visible changes between versions, not for contributor design history.

Boundary

User docs focus on stable behavior. If a paragraph needs to explain internal sidecars, Lance API blockers, or test strategy, it probably belongs in docs/dev/index.md or a developer-area document instead.