User Docs

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

This is the public-facing entry point. These docs should describe behavior, commands, configuration, and operational contracts without requiring knowledge of MRs, internal recovery mechanics, or contributor-only invariants.

Start Here

Goal	Read
Install OmniGraph	install.md
Run the CLI locally	cli.md
Look up every CLI flag and config field	cli-reference.md
Validate and plan cluster config	cluster-config.md
Write schemas	schema-language.md
Read schema-lint diagnostic codes	schema-lint.md
Write queries and mutations	query-language.md
Use embeddings	embeddings.md

Operate A Graph

Goal	Read
Understand graph layout and URI support	storage.md
Work with branches, commits, and snapshots	branches-commits.md
Coordinate multi-query workflows	transactions.md
Read diffs and change feeds	changes.md
Build and use indexes	indexes.md
Compact and clean old versions	maintenance.md
Interpret errors and output formats	errors.md

Run The Server

Goal	Read
Deploy the binary or container	deployment.md
Use HTTP endpoints	server.md
Configure Cedar authorization	policy.md
Track actors and audit behavior	audit.md

Releases

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

Boundary

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

2 KiB Raw Blame History