mirror of
https://github.com/ModernRelay/omnigraph.git
synced 2026-06-15 01:55:13 +02:00
Move the 23 flat docs/user/*.md files into topic subdirectories so the user guide is organized by area (schema, queries, search, branching, cli, operations, clusters, concepts, reference) instead of a flat list. This is a pure structural move — whole files relocated, every cross-doc link recomputed, no prose rewrites or content splits (those follow in Phase 2). - 19 `git mv`s (install.md, deployment.md stay top-level); history preserved (renames detected at 92–100% similarity). - All intra-doc links, AGENTS.md's topic table (52 pointers), and the docs/dev + docs/releases back-links recomputed via relpath from each file's new location. - docs/user/index.md rewritten as a sectioned nav hub. - Fixed 5 doc-path references in Rust (comments + two user-facing server settings error strings) to point at the new locations. Verified: zero broken .md links across tracked docs; check-agents-md.sh green (with the untracked scratch docs set aside); touched crates build. Note: the public site (omnigraph-web) imports docs/ via a flat-only script; its import-docs.mjs needs a subdir-aware update before the next re-sync. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
1 KiB
1 KiB
Audit / Actor tracking
Omnigraph::audit_actor_id: Option<String>is the actor in effect._asvariants of every write API let callers override the actor:mutate_as,load_as,branch_merge_as,apply_schema_as, etc.- Actor IDs are persisted on
GraphCommit.actor_idwith split storage in_graph_commit_actors.lance(the commit graph is split into_graph_commits.lancefor the linkage and_graph_commit_actors.lancefor the actor map). - HTTP server uses the bearer-token actor automatically. The CLI resolves one actor chain everywhere:
--as> legacycli.actorinomnigraph.yaml>operator.actorin~/.omnigraph/config.yaml> none (RFC-007). - Pre-v0.4.0 graphs also stored actor IDs on
RunRecord.actor_idin_graph_runs.lance/_graph_run_actors.lance. The Run state machine was removed in MR-771; those files are inert post-v0.4.0. The v2→v3 manifest migration sweeps any stale__run__*branches on first write-open (MR-770); the inert dataset bytes remain until adelete_prefixprimitive lands.