- Someone updates the source.
- Some decisions get reviewed.
- Others remain hidden.
Your business runs on decisions. But the conditions behind decisions keep changing.
Ex-Grapha shows which decisions need review when a condition changes.
MCP support for Codex and Claude Code
A single update can invalidate many prior decisions.
A policy, fact, or technical constraint can change.
Identifying every decision that needs review becomes a separate task.
Without Ex-Grapha
With Ex-Grapha
- The new lead time is entered in Ex-Grapha.
- Ex-Grapha surfaces every connected decision that needs review.
- A human decides whether each one remains valid, or needs revision.
Without visible connections, teams are left to rely on memory.
How it works
-
Map dependencies
Link each decision to the requirements, assumptions, evidence, and earlier decisions it depends on.
-
Change
When a connected fact changes, Ex-Grapha marks the decisions built on it for review.
-
Review
Review the affected decisions and update only what needs to change.
Show new team members why the project is shaped this way.
Someone joins the team. They can see the decisions, but not the reasons behind them.
With Ex-Grapha, they can start from any decision and trace what shaped it: assumptions, evidence, constraints, and earlier conclusions.
Native support for OpenAI and Claude through MCP.
Ex-Grapha exposes your active graph through an MCP endpoint and includes setup flows for OpenAI Codex and Claude Code.
AI finds facts,Ex-Grapha reveals consequences.You need both!
-
01
Map
Ex-Grapha MCP gives AI a dependency map of your business decisions.
-
02
Trace
Before proposing a change, AI traces the supporting facts, existing constraints, and decisions the proposal would affect.
-
03
Surface
Conflicts become visible before the recommendation reaches your team.
Ex-Grapha Smarter recommendations and fewer mistakes from your AI.
Without Ex-Grapha
user One customer wants non-bypassable two-step admin transfer. Does it align?
AI model Yes. A non-bypassable two-step admin transfer is a strong security improvement: it reduces account takeover risk, enforces explicit authorization, and creates a clearer audit trail. I would accept the request and treat it as the safer default.
With Ex-Grapha
user One customer wants non-bypassable two-step admin transfer. Does it align?
Ex-Grapha MCP ex_grapha_get_graph_snapshot
Ex-Grapha MCPdependency map loaded ✓
AI modelrunbook +--> transfer
support +--> transfer
lockout x-- transfer
AI modelReject: if the customer is locked out, they cannot initiate the two-step transfer, so customer support has no recovery path.
Built for decisions based on changing information.
Assumptions change. Their impact should be visible.
Ex-Grapha shows which decisions need review.
Stop carrying every decision in the back of your mind.
Tell us how to reach you. We will get back to you personally.
Prefer to choose a time directly? Open the calendar