Change one rule.Prove everything changed.
RippleProof traces a business-policy change through documents, chatbots, forms and backend behaviour, proposes repairs, keeps a human in control and produces executable evidence that the organization now follows the new rule.
Customer Refund Policy
refund_period_days <= 14A policy rarely lives in one place.
A single business rule can be repeated across customer documentation, support prompts, forms, APIs and application logic. Updating the source document does not prove that the organization actually changed its behaviour.
From policy change to proof.
The workflow combines semantic AI with deterministic software verification instead of asking an LLM to simply claim that everything is correct.
Define the change
Provide the previous and updated business policy.
Trace the ripple
AI discovers semantic dependencies across documents, prompts, forms and code.
Review repairs
RippleProof proposes evidence-backed patches while a human remains in control.
Prove behaviour
Deterministic boundary tests verify that the new rule is actually enforced.
AI interprets. Software proves.
Semantic impact analysis
Find policy dependencies even when artifacts describe the same rule using different language.
Executable proof
Move beyond AI explanation with deterministic tests against machine-verifiable contracts.
Human approval
Every proposed repair stays reviewable before verification or operational acceptance.
Persistent evidence
Runs, findings, patches and verification results are persisted in PostgreSQL.
Every decision leaves a trail.
Policy contracts, affected artifacts, findings, patch approvals, deterministic tests and verification receipts are persisted as auditable evidence.
Test a real policy change.
Upload organizational artifacts and see which surfaces still enforce the old rule.