Your business has many moving parts. You changed 1 assumption. 7 decisions depend on it. You remembered only 2.
Ex-Grapha shows which decisions, code, and documents need another look.
A single update can invalidate many prior decisions.
Research
Finance & Investment
Operations & Sales
One thing changes
Your API provider cuts its rate limit.
1,000100requests /
min
What could need review
- Retry intervals tuned for the higher limit
- Cache settings that allow frequent API calls
- Concurrency limits that permit too many requests
What else still assumes 1,000 requests per minute?
Ex-Grapha surfaces every connected item that still depends on the old assumption.
Ex-Grapha surfaces every connected item that still depends on the old assumption.
One changed assumption. Seven things to review.
A provider extends its webhook retry window from 24 to 72 hours... Follow the 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
Webhooks Can Be Late
retry window24h→72h
provider changelog · v2.4
Save Idempotent Requests
dedupe window sized to 24h
Guard Webhook Updates
stale-event cutoff = 24h
idempotency_store.rs
KEY_TTL = hours(24)
webhook_guard.rs
reject_if_older_than(24h)
Integration guide › Retries
"replays ignored after 24h"
replay_after_ttl_expiry
asserts a duplicate at 25h
Nightly key purge
deletes keys older than 24h
See the full impact.
Even the parts you’d forget.
How it works
Follow a change from its source to the decisions that need another look.
-
Change
Your product now accepts videos up to 100 MB instead of 25 MB. Which earlier decisions need another look?
The changed source
Video upload limit 25 MB100 MB -
Trace
Ex-Grapha flags the decisions built on that assumption and groups them under the source that changed.
The review queue
Video compression · Video storage 2 to review -
Review
Review each decision in context. Larger uploads call for a new compression policy. Your storage choice still works.
The reason to review
Storage still works with the new limit. Review, then resolve
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.
Your memory is not a dependency tracker. 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.
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.
Generic AI answers can sound right and still be wrong for your team. Ex-Grapha exposes your reasoning system through MCP, grounding their answers in your decisions, constraints, and rationale.
Without Ex-Grapha
UserOne customer wants non-bypassable two-step admin transfer. Does it align?
AI response 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
UserOne customer wants non-bypassable two-step admin transfer. Does it align?
Ex-Grapha MCP
✓ Dependency map loaded
ex_grapha_get_graph_snapshot
Evidencerunbook +--> transfer
support +--> transfer
lockout x-- transfer
AI responseReject: if the customer is locked out, they cannot initiate the two-step transfer, so customer support has no recovery path.
Built from inside the problem.
Ex-Grapha started with a problem we kept running into while working on a large library built around a protocol that changed quickly.
Every time the protocol changed, we had to work out what else might be affected. Sometimes everything looked fine, and then months later we would discover a module following the old protocol.
We had the specs, the design notes, and the code. What we did not have was a clear way to see how those pieces depended on each other.
That is where Ex-Grapha came from. We had seen often enough how easily a dependency could be overlooked, even when everyone was being careful.
Ex-Grapha keeps track of facts and what depends on each one. When a fact changes, you can see what else needs attention.
The same idea applies outside software too. A portfolio rule, a research conclusion, or a production plan can all depend on facts that change.
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.
