Ask across sources

Chat converts plain-language intent into governed source operations.

Write a useful question

Include the measure, grouping, filters, and time window you care about:

Compare paid order count by status this quarter with fulfillment events by carrier.

Use @source-name to remove ambiguity. Ask a follow-up to refine the existing result, such as "exclude test customers" or "change this to a weekly line chart."

Cross-source work

Answerplane can plan across compatible sources when the catalog contains a reliable join key or relationship. A request might combine commerce records in MySQL with events in ClickHouse by sku.

Do not assume similarly named fields are equivalent. If the plan chooses the wrong relationship, stop and correct the catalog or semantic definition.

Charts

Ask for a bar, line, or KPI view when the result shape supports it. The chart is derived from the governed result, not a separate query. Always inspect labels, units, aggregation, and time grain.

When to split a question

Break a request into steps when it mixes unrelated measures, requires an undefined business term, or spans sources without a confirmed relationship. Verify the first result before continuing.

Learn how to inspect evidence in Verify every answer.