Game rules
Add explicit, reviewable requirements to the same DataTable workflow without hiding the evidence.
Create a rule
Open Configure references and game rules → References and game rules, then click Create rule. Choose the source table, field and a compatible check. Add further checks when the requirement has several parts; all checks must pass.
Supported checks include presence, existing references, permitted destinations, numeric minimum/maximum, uniqueness, self-reference and same-table cycles, collection counts, duplicate elements and valid collection references. Expand When should this rule apply? when the rule applies only to matching rows; conditions match all by default, or any when selected.
Use the name, message and severity controls to replace generated wording. Changing the source table resets expressions and labels; Undo table change restores the previous draft.
Preview before saving
Click Preview on selected tables to evaluate the draft against real selected DataTables without saving it. The preview uses the same native evaluator as a review and displays at most 100 outcomes, prioritising failures. Editing the rule invalidates its previous preview.
When the draft is correct, click Save rule and review. This saves and starts a new review immediately. Apply and review is the corresponding action for reference configuration.
Read rule outcomes
Outcomes are Pass, Fail, Not applicable or Not evaluable. A completed review can still contain failures. Filter findings by severity or text, group by rule or table, and open a result to inspect the affected DataTable row and expected/observed evidence.
Do not treat a rule disappearing as proof that the data is fixed if the rule was disabled, the source was removed from the selection or its conditions no longer match.
Know the limits
Rules use schema 2 profiles. The native editor supports top-level typed fields and bounded nested scalar values for stored rule paths. Extraction is limited to 8 nested levels, 256 fields per row and 2,048 elements per collection. A review snapshot and a rule report each have a 32 MiB budget; evaluation has a 1,000,000-operation budget. Arbitrary maps, nested boolean groups, NOT, parameterised rule reuse, cross-table graph rules and multiple conditional destination branches are outside this version.
Review coverage before using outcomes. Unsupported values, missing fields and exceeded budgets are not reported as passing; they are surfaced as omissions or Not evaluable where applicable.