ToolJovia
Data

Finite Decision Table Auditor

Enumerate declared categorical domains and show every rule gap, overlap, conflicting outcome and selected-rule witness.

✓ Browser-local processing

Loading tool…

How to use Finite Decision Table Auditor

Check a finite rules document before depending on its coverage. You declare the possible values of each input and the accepted values in each rule; the tool enumerates that complete Cartesian domain. Unique, Any and First policies make conflicts and priority explicit while preserving every matching rule instead of hiding later rules behind a single result.

  1. Declare one to six named finite string domains and up to fifty distinct-ID rules.
  2. For each rule, list accepted values for constrained domains; omit a domain to match any of its declared values.
  3. Choose Unique, Any or First and review complete combination rows, policy violations and rule coverage.

Good to know

  • At most 100,000 JSON characters, six domains, twenty distinct nonblank string values per domain, fifty rules and 2,000 Cartesian combinations. Domain names and rule IDs are distinct; unsupported keys and duplicate JSON members are refused. Domain order and value order determine evidence order.
  • Conditions are nonempty arrays of exact declared strings. Missing conditions are wildcards; an empty array, scalar condition or unknown value is refused. Values such as "*" are ordinary strings if declared, not expression syntax. No numbers, ranges, FEEL, DMN XML, regex or arbitrary code is interpreted.
  • Unique fails whenever more than one rule matches, even if outputs agree. Any fails only when matching outputs differ. First selects the first matching rule. No match is a separate gap and returns null. For Any with equal outputs, the first rule ID is only a stable result witness.
  • Every matched rule and distinct output remains visible under all policies. neverMatches and neverSelected describe only the declared finite domain. Complete evidence exceeding the bounded output budget is refused atomically rather than truncated. This is not a production rule engine or full DMN conformance check.
  • Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.

Common questions

Can a table pass its hit policy while still have missing cases?

Yes. A gap matches no rule, which is reported separately from a conflicting match. Inspect both complete and policyValid: neither alone establishes that the authored domain represents every real-world input.

Is this input sent to a server?

No. The application processes this input inside your browser tab and does not save it to persistent storage.

Keep going with related tools

All data →