Check what a company decision will break before approving
A developer built DecisionDebt, which maps docs, tickets and chats into a cited graph; on a made-up company it flagged 12 affected services and one owner gap.
Done with Custom agent
What they did
Himanshu Kumar fed 40 docs, 30 tickets and 24 chat threads from a fictional company into a graph. Each link cites the exact sentence that supports it. When someone proposes a change, the system walks the graph to find what breaks. A limited agent drafts follow-up work but cannot approve anything.
How it went
The author reports 315 checked links from 94 sources, and perfect scores against a separate checker. Editing a ticket added and then removed one affected service, as expected.
Worth knowing
The author stresses the perfect score only shows the pipeline matches its own made-up data. It does not prove accuracy on real company writing.
Try it yourself
Read the documents, tickets and chat threads in [folder]. List which systems depend on [system being changed], directly or through other systems, and who owns each one. Quote the exact sentence that supports every link, and mark anything hedged or unclear as unconfirmed. Flag systems with no owner or two owners, and docs not reviewed in [number] days. Show me the report and draft review tasks, but do not assign owners or change any records without my approval.
Swap the highlighted [parts] for your own details.
Source: DEV Community · Himanshu Kumar · Oct 17, 2026
Written with AI assistance from the original post and checked against our editorial guidelines. Results are as reported by the source, not independently verified.
