When one thing changes, see everything built on it.

Ex-Grapha maps what your decisions, code, and documents depend on. When a spec or assumption changes, every item built on it is flagged for review. Not just the ones you remembered.

Works inside Codex and Claude Code via MCP

Impact trace · payment-orchestration
Tracing impact
Changed 1 hop away 2 hops away 3 hops away
Capture Is Hard to Reverse
Timeouts Can Still Succeed
Provider APIs Differ
Define Internal States
Normalize Provider Events
Authorize Before Capture
Report From Internal Ledger
AxiomUpdated
Webhooks Can Be Late
retry window24h72h
provider changelog · v2.4
DecisionReview
Save Idempotent Requests
dedupe window sized to 24h
DecisionReview
Guard Webhook Updates
stale-event cutoff = 24h
CodeReview
idempotency_store.rs
KEY_TTL = hours(24)
CodeReview
webhook_guard.rs
reject_if_older_than(24h)
DocReview
Integration guide › Retries
"replays ignored after 24h"
TestReview
replay_after_ttl_expiry
asserts a duplicate at 25h
RunbookReview
Nightly key purge
deletes keys older than 24h

A single update can invalidate many prior decisions.

Choose a field to see how the impact travels.

Condition updated

API rate limit
1,000 requests/min 100 requests/min

The decisions built on it need review

Without Ex-Grapha

Review depends on whether the team can remember everything.

  • Retry and backoff policy Identified
  • Response cache TTL Missed
  • Request concurrency limit Identified
  • Thread pool size and cloud spend Missed
Only 5 of 17

decisions identified

With Ex-Grapha

Every affected decision is surfaced.

  • Retry and backoff policy Flagged
  • Response cache TTL Flagged
  • Request concurrency limit Flagged
  • Thread pool size and cloud spend Flagged
17 of 17

decisions flagged

Without visible connections, teams are left to rely on memory.

Ex-Grapha graph view tracing downstream dependencies from Guard Webhook Updates to Report From Internal Ledger

How it works

  1. Map dependencies

    Link each decision to the assumptions, constraints, evidence, and earlier decisions it depends on.

  2. Change

    When a condition changes, Ex-Grapha marks the decisions built on it for review.

  3. Review

    Review the affected decisions and update only what needs to change.

Video upload limit is updated. The architecture decisions built on the video size constraint now need review.

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, constraints, evidence, and earlier decisions.

Ex-Grapha system graph showing the dependencies and dependents of Guard Webhook Updates

Documents store information. Ex-Grapha shows hidden dependencies.

Ex-Grapha is a desktop app that keeps a dependency graph of your decisions, code, and documents, and exposes it to your AI tools over MCP.

Ex-Grapha desktop app showing a payment provider orchestration graph with the node list, canvas, and edges
OpenAI Codex
Claude Code

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.

The same question, with and without the graph.

Through MCP, Codex and Claude Code trace what a proposal touches before they answer, so conflicts surface before the recommendation reaches your team.

Without Ex-Grapha

AI Chat Context unavailable

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.

  • Sounds plausible, but misleading
  • Misses lockout recovery

With Ex-Grapha

AI Chat Graph connected

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.

  • Grounded in the incident runbook
  • Catches the lockout conflict

Built from inside the problem.

Özgün Özerk

Ex-Grapha started in a large library that tracks a fast-moving protocol. Every protocol change meant finding which parts of the code depended on it. We knew the obvious ones. The rest surfaced months later, when someone found a module still built on the old rules.

The problem was never missing information. The specs existed, the design notes existed, the code existed. What was missing was the map from each fact to everything built on it, kept current as the facts changed.

Ex-Grapha is that map, built by an engineer who ran into this problem first-hand, more than once. It works the same way for a portfolio rule, a research finding, or a supplier lead time.

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

We use these details only to reply to your request. Privacy notice

Assumptions change. Their impact should be visible.

Ex-Grapha shows which decisions need review.