Omnigraph

Developer Docs

Audience: contributors, maintainers, and coding agents

Audience: contributors, maintainers, and coding agents

This is the contributor-facing entry point. These docs explain architecture, invariants, implementation contracts, test ownership, and upstream Lance constraints. User-facing behavior should still be documented through docs/user/index.md and the relevant public reference docs.

Required For Every Non-Trivial Change

NeedRead
Architectural rules, known gaps, deny-listinvariants.md
Upstream Lance source-of-truth indexlance.md
Existing test coverage and test placementtesting.md

Architecture And Storage

AreaRead
System structure, L1/L2 framing, component diagramsarchitecture.md
On-disk layout, manifest schema, URI behaviorstorage.md
Direct-publish writes, D2, staged writes, recovery sidecarswrites.md
Query execution, mutation execution, loader flowexecution.md
Index lifecycle and graph topology indexesindexes.md
Branch and commit internalsbranches-commits.md
Three-way merge implementation and conflictsmerge.md
Diff/change-feed implementationchanges.md
Branch protection policybranch-protection.md
CODEOWNERS source of truthcodeowners.md

Language, Runtime, And Boundaries

AreaRead
Schema grammar, catalog, migration plannerschema-language.md
Query grammar, IR, lints, mutation restrictionsquery-language.md
Embedding client and @embed integrationembeddings.md
Cedar policy surface and server gatingpolicy.md
Server auth, OpenAPI, endpoint handlersserver.md
Error taxonomy and serializationerrors.md
Constants and tunablesconstants.md
Transaction model public contracttransactions.md

Project Operations

AreaRead
CI and release workflowsci.md
Install and deployment packaginginstall.md, deployment.md
Release historyreleases/

Contribution & Governance

AreaRead
How to contribute (external)CONTRIBUTING.md
Governance model, roles, decision authorityGOVERNANCE.md
Public contribution RFC trackrfcs/

The docs/rfcs/ track is the public, externally-authorable RFC process. The maintainer/internal RFCs below (rfc-00N-*.md) are a separate, team-owned track; don't conflate the two.

Active Implementation Plans

Working documents for in-flight feature work. Removed when the work lands.

AreaRead
Schema-lint chassis v1 (MR-694) — --allow-data-loss, soft/hard dropsschema-lint-v1-plan.md
Inline + stored queries, request/response envelope, MCP (MR-656 / MR-976 / MR-969)rfc-001-queries-envelope-mcp.md
Config & CLI architecture — layered config, client targeting, file naming (MR-973 / MR-974 / MR-981)rfc-002-config-cli-architecture.md
MCP server surface — full tool parity, stored queries, modular auth (MR-969 / MR-956 / MR-974)rfc-003-mcp-server-surface.md
Future cluster control plane — declarative as-code config, JSON state ledger, reconcilercluster-config-specs.md, cluster-axioms.md, cluster-config-implementation-spec.md
Cluster graph & schema apply — Phase 4 sidecars, roll-forward recovery, approval artifactsrfc-004-cluster-graph-schema-apply.md
Server boots from cluster state — Phase 5 mode switch, applied-revision servingrfc-005-server-cluster-boot.md
Per-operator config — ~/.omnigraph/ identity, keyed credentials, named servers (the operator slice of RFC-002)rfc-007-operator-config.md
Deprecate omnigraph.yaml — one concern per config surface; key-by-key migration map and staged retirementrfc-008-deprecate-omnigraph-yaml.md
Unify CLI embedded/remote access paths — parity referee, shared wire-DTO crate, GraphClient trait, declared plane capabilitiesrfc-009-unify-access-paths.md

Boundary

Developer docs may mention implementation details, stale gaps, upstream Lance blockers, and review rules. User docs should not require that context unless the detail changes the public contract.

On this page