When numbers or relationships matter, a Mind answers with more than text: a chart, a set of KPI cards, or a diagram inside the answer, alongside a reference that opens the query or the document behind it. This page lists the blocks DataMind's AI, Kartlos, can add and the rules each one follows; how a Mind plans and shapes an answer is on How a Mind answers.
An answer draws its numbers as one of these chart kinds:
| Chart | What it shows | Its rules |
|---|---|---|
| Pie | Parts of one total. | At most six slices; with more groups, the smallest fold into a single "Other" slice. If a value is negative, the same numbers are drawn as a bar chart instead. |
| Pie comparison | Two totals side by side. | Exactly two pies. |
| Bar | Comparisons and rankings. | Bars stack when the mix is the point; read a stacked bar as parts of one whole. |
| Line | Trends over time. | Can carry actual figures and a forecast in one line: the forecast continues from the last actual point. |
| Area | Trends where the volume matters. | Drawn like a line. |
| Composed | Two measures in one picture. | Bars and lines or areas together, each series on its own scale when needed. |
| Radar | A profile across several measures. | Best for four to eight measures across two to five items; all values share one scale. |
| Radial bar | Cyclical data, such as months or weekdays. | Values are percentages or normalised figures. |
| Sankey | Flows. | Shows how a quantity splits between stages. |
A profit and loss is always drawn as a Sankey: money runs from revenue through costs to profit, and a deeper structure is split into several diagrams by category. To read a chart in the chat itself, with its views, zoom and full screen, see Charts, KPIs and diagrams in chat.
Headline numbers come back as KPI cards: each card carries a title, a value and a change line. The change reads at a glance: an arrow up in green when the number grew, down in red when it fell, a plain dash at zero, and no arrow when the change is not a number.
When the point is structure rather than numbers, the Mind draws a diagram instead of a chart. The kinds an answer can use include flowcharts and graphs, Gantt charts, entity relationship diagrams, sequence, class and state diagrams, timelines, quadrant charts, mindmaps, journeys, kanban boards, XY charts and block diagrams.
Two rules keep a diagram drawable: its labels keep to plain words, without brackets, braces or quotation marks, and a diagram that cannot be read shows an error card in place of the drawing.
A visual answer follows a fixed order: KPI cards first, then charts, then tables, and plain text last. Even a small result can arrive as a picture, and plain text stays for single values and short explanations.
An answer also points to what the conversation produced:
For how a reference looks and opens in the chat, see Formatting messages and rich answers.
Ask for a presentation and the Mind builds it from the conversation. It finishes the analysis first: the deck reads the conversation up to the moment the build starts, so everything it should include must already be in the chat. When the build starts, the chat shows "Your presentation generation has started." The finished deck is saved in Artifacts as a Slide Deck, ready to page through, present or download.
Generate a presentation or slide deck covers the dialog and its settings. For the AI that changes a deck inside the Slides editor, see The Slides AI.
No. A pie block draws at most six slices; when the data holds more groups, the smallest ones fold into a single "Other" slice, so the picture stays readable.
With a pie comparison: that block holds exactly two pies, so two splits can be read against each other in one picture.
Yes. A line block can carry both: the actual figures run to the last known point, and the forecast continues from there, so past and forecast read as one picture.
The bars are stacked when the mix is the point: read the segments as parts of one total, not as separate totals.
A profit and loss is a flow, so it is always drawn as a Sankey: you see how money runs from revenue through costs to profit, and where it splits on the way. A deeper structure is split into several diagrams by category.
The order is fixed: a visual answer opens with its headline numbers as KPI cards, then charts, then tables, and plain text last. The cards put the key numbers in front of you before the detail.
When the point is structure rather than numbers: how things relate, how a process runs, or how work sits on a timeline. Relationships become entity relationship diagrams, processes become flowcharts, and schedules become Gantt charts.
Whenever the conversation produced a query or a document, the answer includes a reference to it. That is deliberate: a document is never only named in passing, and the reference is how you open the item behind the answer.
The exact one the answer was built from. A reference points at the item itself, not just at its name, so a shared name opens the right item.
The analysis is done and the deck build has begun. The deck is built from the conversation up to that moment, so anything added later does not change it; when it is ready, it is saved in Artifacts as a Slide Deck.