- Verification approved (live) edges are folded into grounding checks, so answers that contradict the graph get caught.
- Retrieval the graph supplies causal facts your documents alone don’t state, without duplicating chunks retrieval already found.
Graph shape
- Nodes are variables numeric, count, or yes/no, plus non-measurable concept nodes.
- Edges are causal an arrow from A to B means “changes in A cause changes in B”.
- The graph is a DAG (directed acyclic). Adding an edge that would create a cycle is rejected on the spot.
Ways to build one
Open Causal Graph in the sidebar. An empty graph offers three starting points:- Add by hand author variables and edges yourself. Best when you’re the domain expert. See Variables and Edges.
- From a folder an LLM bootstraps a graph from a Documents folder.
- From a refinery seed the ontology from a refinery’s blocks.
Proposed vs. approved (live)
Every node and edge carries a review state:- Proposed staged for review. Not used downstream.
- Approved (live) treated as live by verification and retrieval.
Learn more
Variables
The nodes: what you measure, and their review state.
Edges
Direction, sign, strength, and review.
Bootstrap from documents
Let an LLM propose the graph; you approve.
Relationship analysis
Pick a cause and an effect; the graph tells you what to watch out for.
Verify agent answers
How live edges gate what agents say.
How agents pick up a graph
Graphs connect through data sources: no per-Agent attach step.
What causal graphs are not
- Not a replacement for knowledge. Keep your docs: the graph’s evidence chunks come from them.
- Not the reasoner. Your Agent still uses an LLM; the graph is a check and a source of causal facts.
- Not a general knowledge graph. It’s specifically for causal relationships.