omnigraph/docs
aaltshuler 6d66b0537e docs(cluster): RFC-005 — server boots from cluster state (Phase 5 design)
The axiom-15 mode switch: omnigraph-server --cluster <dir> (mutually
exclusive with uri/--target/--config, zero omnigraph.yaml reads) serves the
APPLIED revision — graph set from state, query/policy content from the
content-addressed catalog at applied digests, cluster-scoped policy bundles
as the server-level Cedar engine. The load-bearing finding: state is not yet
serving-sufficient (policy applies_to bindings live only in cluster.yaml), so
slice 5A records binding metadata into the applied revision at apply time —
without it, boot-from-state silently becomes the merged read axiom 15
forbids. Fail-fast readiness table (missing state, pending sidecars, missing
blobs, unbound policies all refuse boot with remedies), the expose-all
mcp.expose bridge with its Phase 6 sunset, the operator migration path (exit
criterion 7), and 5A/5B/5C sequencing. The existing boot pipeline
(GraphStartupConfig -> registry -> routing/auth) is reused as-is — a new
source, not a new pipeline.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-10 15:01:04 +03:00
..
dev docs(cluster): RFC-005 — server boots from cluster state (Phase 5 design) 2026-06-10 15:01:04 +03:00
releases docs(releases): attribute the __run__ sweep (MR-770) to v0.6.2, not v0.6.1 (#161) 2026-06-09 22:31:50 +03:00
rfcs governance: external contribution model (issues/discussions/RFCs/PRs) (#143) 2026-06-06 23:58:08 +03:00
user docs(cluster): document Stage 4C — Phase 4 complete 2026-06-10 14:44:12 +03:00