RuleGap

Product logic intelligence

Your code runs.
Does your product make sense?

RuleGap reconstructs the rules behind your application, attacks the places where those rules collide, and produces evidence you can verify.

No card for trial Exact source evidence Secrets redacted first
RG—0142 High confidence
Broken promise

A free workspace can keep two projects active.

The interface checks the one-project limit before creation. The import path inserts directly and the database has no invariant to stop it.

app/projects/new.tsxUI limit check · lines 42–55checks
but
api/import/route.tsUnrestricted insert · lines 88–103bypasses
Smallest counterexample
  1. Create one active project.
  2. Import a second project through the API.
  3. Both receive paid processing.
92%

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

Correct components.
Irrational product.

RuleGap reads code, schema, copy, tests, permissions, billing, and recovery flows as one product world.

01Broken promiseThe pricing page promises one thing. The database permits another.Inspect patternClose field note
How it fails

Broken promise

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.

Smallest counterexample

A free workspace creates one project in the interface, imports a second through the API, and both receive paid processing.

Evidence returned

The conflicting promise, the exact bypass path, and the invariant or focused test that closes it.

02Layer driftThe frontend, API, worker, and webhook disagree about the same rule.Inspect patternClose field note
How it fails

Layer drift

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.

Smallest counterexample

The API cancels a subscription immediately, while a delayed webhook and worker still grant the next month’s credits.

Evidence returned

A cross-layer rule map showing where agreement ends, which event exposes it, and the safest enforcement point.

03Impossible stateIndividually valid actions combine into a product state that should not exist.Inspect patternClose field note
How it fails

Impossible state

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.

Smallest counterexample

An owner transfers a project, removes the last admin, then deletes the account—leaving a billable workspace nobody can govern.

Evidence returned

The shortest reproducible state trace, the violated rule, and the transition guard needed to make the state unreachable.

04Money gapCredits, refunds, entitlements, or inventory are duplicated, lost, or misapplied.Inspect patternClose field note
How it fails

Money gap

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.

Smallest counterexample

A timed-out scan is refunded and retried; the original worker later finishes, producing paid output without a durable charge.

Evidence returned

An event-by-event ledger trace, the non-idempotent edge, and a proof that the repair survives retries and reordering.

The Triad Logic Engine

Three adversaries.
One defensible finding.

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.

  • 01World modeler reconstructs actors, rules, and states.
  • 02Causal auditor traces consequences across systems and time.
  • 03Counterexample engineer finds the smallest sequence that breaks a promise.
FableWorld model
SolCausal audit
KimiCounterexample
RGEvidence
adjudicator
No critical finding without proof-quality evidence.

Product Constitution

The rules your code already believes.

Turn scattered checks, tests, copy, schema constraints, and tribal knowledge into a versioned system of record your team can approve.

Build your constitution
RULE / BILLING—004Approved

“A failed scan returns every credit reserved for work that did not complete.”

Actors
Customer · Worker · Ledger
Must happen
Reservation release is append-only and idempotent.
Must never happen
A retry produces a second refund.
Enforced at
Database function · job finalizer · webhook replay guard

Evidence before theater

Not a hunch. A proof.

Every confirmed gap links the claim to exact source evidence and the smallest reproducible path.

Exact evidence

Open the cited file, lines, rule, constraint, or copy behind every claim.

Executable artifact

Generate a focused test, SQL reproduction, API sequence, or state trace.

Isolated execution

Run approved proofs in a sandbox without inherited production credentials.

Pricing by logic surface

Pay for reasoning.
Never open-ended tokens.

Every scan is estimated before it starts. The final charge cannot silently exceed the estimate.

Builder

For a solo builder shipping one product.

$49/ month

16 credits included

  • Quick Sense scans
  • Triad analysis
  • Product Constitution
  • Evidence-backed findings
Start with one free scan

Team

For shared rules, owners, and merge policy.

$449/ month

180 credits included

  • Quick Sense scans
  • Triad analysis
  • Product Constitution
  • Evidence-backed findings
Start with one free scan

Private by construction

Your repository is evidence, not training material.

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

Find the rule
your tests forgot.

Start with one repository and one completed Quick Sense scan. No card required.

Scan a repository