Skip to main content
You don’t attach a causal graph to an Agent directly. The reference is derived from the Agent’s existing data sources: if an Agent is bound to a document folder (or a specific document, or a memory space) that a graph is connected to, that graph is automatically in scope for both the verifier and retrieval. This means the setup happens on the graph, not on the Agent.

​
The one-time setup

  1. Open the causal graph.
  2. Settings → Connected sources → Add — pick the documents, folders, or memory spaces this graph is derived from.
  3. Save.
From that moment, any Agent whose data sources overlap with the graph’s connected sources will use the graph. No per-Agent toggle needed.

​
Where the graph is used

Two consumers:
  • Verifier — always on. The graph’s approved (LIVE) edges are folded into grounding checks for every answer.
  • Retrieval — governed by the graph’s dedup policy (see below). Not automatic like verification.

​
Dedup policy — how the graph shows up in retrieval

Because the graph is derived from the connected documents, retrieving both the raw chunks and the graph’s facts would duplicate information. The graph’s dedup policy decides how they mix. Configure per graph: Graph → Settings → Dedup policy. The default dedup_by_source matches “docs are the primary evidence, graph adds the causal logic on top” — the rule for how the graph should behave in retrieval.

​
What the graph’s role really is

  • The verifier’s primary consumer — always folds in approved edges to check factual claims.
  • Retrieval’s auxiliary logic — supplies the causal edges that documents alone don’t state, without duplicating chunks the retrieval already found.
If you’re used to “attach the graph to the Agent,” reframe: attach the sources to the Agent (or the graph — either direction works), and the connection between them wires the graph in automatically.

​
Multiple graphs

An Agent can end up referencing multiple graphs — one per set of overlapping connected sources. Each graph’s dedup policy applies independently to its own contribution.

​
Configuring from the CLI

See nora causal for the full command surface.

​
Legacy explicit binding

For backward compatibility, the explicit causal_graph data-source binding still works — an Agent that has an old-style causal-graph attachment short-circuits to its prior path. New Flows should use the connected-source model instead.

​
What to do next

Verify agent answers

How the verifier uses the graph — always on.

Grounding (retrieval)

How retrieval uses the graph — via dedup policy.