Skip to main content
GoRules continuously analyses every graph and policy as you edit - no run required. Findings appear in the document’s Problems tab, on the Quality Control page, and as a pre-flight check when you save.
Problems tab showing PREFER_DICTIONARY hints on decision table output columns, with explanations and suggested fixes

The Problems tab with two findings and suggested fixes

Each finding has a severity:
Static analysis needs to know your types. A graph whose input node has no schema - or an empty one - reports MISSING_INPUT_SCHEMA and skips deeper checks until you define one in the Interface tab.

Names and types

Writes and dependencies

Data models, dictionaries, and imports

Structure and completeness

Quality hints

Hints don’t indicate bugs - they point at rules that could be simpler, safer, or easier to maintain.