Ask your first question
How to phrase a question, what happens while Tattva works, and how to read the Answer and Trail tabs.
Once at least one source is Ready, open Reasoning in the sidebar.
The composer
The box at the bottom reads "Ask anything against the current project…". Type your question the way you would ask a colleague. You don't need column names or SQL.

- Enter sends the question. Shift + Enter adds a new line.
- Sessions opens your past conversations. New starts a fresh one.
When nothing has been asked yet, the page shows What you can ask: example questions your analytics team wrote, grouped by topic. Click one to ask it. Below them, Not available yet lists topics the team does not answer yet, with the reason.
Not sure what to ask? Ask What can you answer? for the metrics, data and example questions in this project, or Do you do ROAS? to check a single metric or topic.
Other good first questions:
- "What was net revenue last month by channel?"
- "Why did repeat rate drop in March compared with February?"
- "How did RTO rate move week over week for the last 8 weeks?"
Name the period. "Last month" or "1–31 March" is clearer than "recently".
While Tattva works
You can watch the answer's phases in the Trace rail on the right:
- Analyze: a model reads the question, the period, the metrics you mean, and anything ambiguous. Code then checks that reading against your project's definitions and computes the figures.
- Answer: code lays out the answer's tables, notes and chart; a model writes the prose, a second model lists every claim it makes, and code checks each one against the figures. A sentence that fails is revised once, then dropped.
A question one run of your definitions cannot answer is planned instead: the rail shows each step as it runs.
While it runs, the button in the composer becomes Stop.
If Tattva needs to ask you something
When your question can be read more than one way, Tattva asks instead of guessing. A Needs clarification card shows the question and a few choices.

Click a choice, or type in "Or type your own answer…" and click Reply. Tattva then carries on with your answer.
Read the answer
The answer card has two tabs.
Answer is the written answer: the headline, the figures, and tables where they help. It ends with how long the answer took, its approximate model cost in rupees and how much data it read, for example "Answered in 42 s · ≈ ₹19 model cost · 19.3 MB scanned".

Trail · N shows every step behind it, phase by phase. On the Analyze card, the Compute block shows, for each metric Tattva computed, the value, the period, the filters, where each input came from, and the SQL that ran. This is where you check a number.

A sentence of the prose that failed its check was revised once or dropped before you saw the answer; the run keeps what the check found.
Why you can trust the figures
If your analytics team has written down what the data covers, a Scope line under the answer says so, for example "Scope: D2C website orders only".
For metrics your data analysts have defined, the figures are computed by code from the stored definition, and code lays out the tables and chart. A model may add a few sentences about them, but never types a figure. Where a figure is Tattva's own calculation rather than a stored definition, the answer says so. See Review an answer.
When Tattva can't answer
- It asks. A Needs clarification card appears. Pick an option.
- It says the topic is not answered yet. Your analytics team has marked some topics (for example a metric whose data is not loaded) as not answered yet, or switched off some kinds of question. You get a short card saying why, with questions you can ask instead; click one to ask it. There is no Trail for it, because nothing was computed.
- It says a period is not available. A metric can have a first date it is valid from. The part of your period before that date is not answered; the rest is.
- It says the data isn't there. The columns or rows you need are not in any connected source. Connect the missing source, or ask your data analyst.
- It flags a figure. The Compute block may say a figure is provisional (recent days have not settled yet) or incomplete (the period has not finished). Treat these as early readings.
Next steps
- Keep it. Save as tracker, Save as report, or Pin to board from the toolbar under the answer.
- Follow up. Ask the next question in the same session. Tattva keeps the context.
See Ask a question for the full workflow.