Verify every answer

Verification checks whether the system answered the intended question, not merely whether it returned rows.

Read the plan

Confirm:

• resolved business terms and metrics
• selected sources and objects
• join paths or cross-source keys
• filters, tenant scope, and time range
• grouping, aggregation, ordering, and result limit
• explicit assumptions

Read provenance

Provenance records the actual source operations behind the result. Depending on the connector, this may include compiled SQL, a MongoDB aggregation pipeline, a file query, or an API tool call.

Compare the operation with the plan. Check row counts and freshness. A successful execution can still represent the wrong intent.

Validate the output

Use a known control total or narrow sample where possible. Check null behavior, currency and units, timezone boundaries, duplicate-producing joins, and chart axes.

Correct the source of truth

If wording caused the mismatch, refine the request. If the same confusion will recur, update the catalog, glossary, semantic layer, or relationship rather than relying on prompt phrasing.

Share only after the plan, operation, and result agree with the business question.