Exact evidence
Open the cited file, lines, rule, constraint, or copy behind every claim.
Product logic intelligence
RuleGap reconstructs the rules behind your application, attacks the places where those rules collide, and produces evidence you can verify.
The interface checks the one-project limit before creation. The import path inserts directly and the database has no invariant to stop it.
of an application can behave correctly while one cross-system rule still breaks the product.
“Tests ask whether the implementation did what we coded. RuleGap asks whether that behavior was sensible.”
What ordinary scanners miss
RuleGap reads code, schema, copy, tests, permissions, billing, and recovery flows as one product world.
RuleGap maps outward promises—from plan copy and onboarding to documentation—against every path that can change the promised state. A gap appears when one path can bypass the rule everyone else assumes is enforced.
A free workspace creates one project in the interface, imports a second through the API, and both receive paid processing.
The conflicting promise, the exact bypass path, and the invariant or focused test that closes it.
A rule is encoded in several places, but each layer uses a slightly different boundary, state, retry window, or ownership check. Every component can pass alone while the complete product tells two incompatible stories.
The API cancels a subscription immediately, while a delayed webhook and worker still grant the next month’s credits.
A cross-layer rule map showing where agreement ends, which event exposes it, and the safest enforcement point.
RuleGap composes allowed transitions across actors, flows, and time. It looks beyond single requests for sequences that leave the product without an owner, recovery path, valid entitlement, or legal next action.
An owner transfers a project, removes the last admin, then deletes the account—leaving a billable workspace nobody can govern.
The shortest reproducible state trace, the violated rule, and the transition guard needed to make the state unreachable.
RuleGap treats money-adjacent state as a ledger obligation. It follows reservations, retries, refunds, webhooks, and late completions until every unit is accounted for exactly once under failure and replay.
A timed-out scan is refunded and retried; the original worker later finishes, producing paid output without a durable charge.
An event-by-event ledger trace, the non-idempotent edge, and a proof that the repair survives retries and reordering.
The Triad Logic Engine
Each model receives a bounded evidence packet and a different reasoning role. They work independently, challenge one another, then a rotating judge applies the proof law.
Product Constitution
Turn scattered checks, tests, copy, schema constraints, and tribal knowledge into a versioned system of record your team can approve.
Build your constitution“A failed scan returns every credit reserved for work that did not complete.”
Evidence before theater
Every confirmed gap links the claim to exact source evidence and the smallest reproducible path.
Open the cited file, lines, rule, constraint, or copy behind every claim.
Generate a focused test, SQL reproduction, API sequence, or state trace.
Run approved proofs in a sandbox without inherited production credentials.
Pricing by logic surface
Every scan is estimated before it starts. The final charge cannot silently exceed the estimate.
For a solo builder shipping one product.
16 credits included
For teams reviewing commits and releases.
55 credits included
For shared rules, owners, and merge policy.
180 credits included
Private by construction
Secrets stripped first.Credentials are detected and redacted before model processing.
Least privilege GitHub App.Repository contents are read-only; broad organization writes are never requested.
Organization isolation.Every customer row is scoped by PostgreSQL row-level security.
Before the next release
Start with one repository and one completed Quick Sense scan. No card required.
Scan a repository