ClauseRipple
A contract-clause change impact analysis tool based on a graph database that places contract clauses, dependency chains and regional facts in the same graph, identifying affected customers and responsible parties through graph traversal.
Timeline (last 90 days)
ClauseRipple is a graph-database-based application built by developer bilal-feroz at the Graph Hacks hackathon (FalkorDB x WeMakeDevs) to track the impact chain of contract clause changes.
ClauseRipple's graph contains 20 node labels and 20 synthetic source documents, with a baseline of 144 nodes and 173 relationships.
A complete agent run (14 tool calls, 63 graph reads, 13 graph writes) totals about 75 milliseconds inside FalkorDB.
ClauseRipple wraps 10 graph queries as MCP tools, so the planner only needs to choose tool names and parameters without generating Cypher.
ClauseRipple's compliance rule is: violation region = vendor processing region - customer allowed region; affected = a dependency path exists and the violation region is non-empty.
ClauseRipple has three layers: the large model (planner) decides which tool to call and explains results in natural language; FalkorDB stores facts and traverses relationships; ordinary code determines compliance.
In ClauseRipple, running a bounded shortestPath against GulfGov returns empty, and this empty result is used as evidence of "not affected".
All Facts (7)
ClauseRipple is a graph-database-based application built by developer bilal-feroz at the Graph Hacks hackathon (FalkorDB x WeMakeDevs) to track the impact chain of contract clause changes.
50%UnverifiedClauseRipple's graph contains 20 node labels and 20 synthetic source documents, with a baseline of 144 nodes and 173 relationships.
50%UnverifiedA complete agent run (14 tool calls, 63 graph reads, 13 graph writes) totals about 75 milliseconds inside FalkorDB.
50%UnverifiedClauseRipple wraps 10 graph queries as MCP tools, so the planner only needs to choose tool names and parameters without generating Cypher.
50%UnverifiedClauseRipple's compliance rule is: violation region = vendor processing region - customer allowed region; affected = a dependency path exists and the violation region is non-empty.
50%UnverifiedClauseRipple has three layers: the large model (planner) decides which tool to call and explains results in natural language; FalkorDB stores facts and traverses relationships; ordinary code determines compliance.
50%UnverifiedIn ClauseRipple, running a bounded shortestPath against GulfGov returns empty, and this empty result is used as evidence of "not affected".
50%