Omnigraph

Audit

  • Omnigraph::audit_actor_id: Option<String> is the actor in effect.
  • _as variants 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_id with split storage in _graph_commit_actors.lance (the commit graph is split into _graph_commits.lance for the linkage and _graph_commit_actors.lance for the actor map).
  • HTTP server uses the bearer-token actor automatically. The CLI resolves one actor chain everywhere: --as > legacy cli.actor in omnigraph.yaml > operator.actor in ~/.omnigraph/config.yaml > none (RFC-007).
  • Pre-v0.4.0 graphs also stored actor IDs on RunRecord.actor_id in _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 a delete_prefix primitive lands.

Policy (Cedar)

OmniGraph integrates AWS Cedar (cedar-policy = 4.9) for ABAC.

CLI reference

A reference for the omnigraph binary's command surface and omnigraph.yaml schema. For a quick-start guide, see cli.md.