Data definitions
What you tell variA/Bly about your data, and the check each definition turns on.
Data definitions
What it is. Optional facts about your data, held in the policy: code lists, document scope, hand-off contracts, SQL checks, posting rules (with a chart of accounts), expected answers and requirement templates.
Why it matters. They let checks compare exact values instead of guessing. A check whose input was sent without its definition is Not configured (SQL sent with no SQL checks, a hand-off to an agent with no contract, a requirements_ref naming a missing template); with no input sent it is N/A with the reason. Neither is ever a pass.
How it relates. Editing one in the app changes the policy draft; it applies when you publish. The SDK settings calls (set_code_lists, set_handoff_contracts, set_sql_checks, set_scope_defaults) publish a new version with your note and need Change the evaluation policy.
Where you see it. Evaluation policy › Advanced settings ▸ › Data definitions; Your data on the Summary.
Example. See the table below.
What each definition enables
| Definition | Turns on | Insurance / finance example |
|---|---|---|
| Code lists | Values matched to a list even when spelled differently; code-typed hand-off fields | leave_type: STD, LTD, FMLA |
| Document scope | Right version of the source: the answer used the version that applies | plan year 2026, state CA; "as of" the request time |
| Hand-off contracts | Hand-offs carry the facts | to adjudication: onset_date (date), leave_type (code), weekly_benefit (money) |
| SQL checks (schema & rules) | SQL follows the rules: the query text against your schema and rules; units for percentage columns | always filter on plan_year; never select ssn |
| Posting rules and chart of accounts | Journal findings on the answer's claims (Journal entry breaks a rule); an entry to an account not on the chart is proven wrong | vendor invoice → credit Accounts Payable; chart 1000 Cash (asset), 2000 Accounts Payable (liability) |
| Business rules | Follows business rules: each answer obeys your own rules, with the breaking sentence marked | approved_visits at most 12 unless prior_auth is true; refund within 30 days of delivery |
| Expected answers | Matches the expected answer (expected_answer=) and Answers what was asked (expected_answer_kind=) | "$1,500 per person", kind "amount" |
| Requirement templates | Covers what it must: everything the answer must include | benefit-amount@v3: amount, network tier, plan year |
The chart of accounts (each account's code, name and type: asset, liability, equity, revenue or
expense) is set in the policy's YAML under chart_of_accounts. SQL checks read the SQL text and
rows you send; nothing connects to your database. How to add each one, with examples and every field:
Data definitions and the format reference.