No. The structure and the arithmetic are computed in code. The model is told what the numbers measure; it does not get to work that out for itself.
A spreadsheet stays a spreadsheet. Gyrium reads it, understands its units, and states what it says, without shredding the grid into loose facts.
Learn next: Organizational Intelligence · Data Visualization Studio · Table Studio · Strategic Composition
Somewhere to keep the numbers. A workbook you add becomes a dataset: stored whole, read column by column, and available to compose from. It is not shredded into individual facts, because a number without its row and its column does not mean anything. Excel workbooks arrive with their tabs intact, and Gyrium opens the one that actually holds figures, so a cover sheet is never the thing you end up charting.

Numbers are the part of a communication that must not be wrong. Every other approach either retypes them by hand, which invites error, or lets a model read the grid, which invites invention. A dataset is read once, correctly, and every use points back at it.
The reader works out which row is the header, what each column is for, and which rows are totals. Then it tells you what it decided, in plain words, and every part of it can be overruled. Move the header, change what a column is for, put a totals row back, and your answer wins: the reading is redone around it.
It carries units through, so a column of euros stays euros and a percentage is never averaged as though it were a count. It reads European decimals, and French, Dutch and German workbooks: totals, notes and month names are read correctly. From the grid it computes what the table actually says: the leading finding, the runners-up, and which cell deserves emphasis.
When you sign the reading off, the record keeps who agreed it and which reading they agreed to. Change the header or the column roles later and the sign-off lapses, because it no longer describes what you approved.
That reading is handed to the writer at composition time, so the prose about a chart comes from what the numbers show. A check runs the other way too, flagging a slide whose words contradict the chart beside them.
No. The structure and the arithmetic are computed in code. The model is told what the numbers measure; it does not get to work that out for itself.
Not by themselves. A grid is kept as a grid. Turning a row into a citable claim takes a deliberate step. Uploading alone will never do it.
Read correctly, including comma decimals and the units in the header.
A figure on a slide drawn from a table cites that table, pinned to the version it was read from; a claim in running prose drawn from a table is not yet cited that way. Charts and tables from a dataset are composed into presentations and social posts; documents do not draw from datasets yet. Drift between a dataset and a deck that used it is detected and offered, but never applied on its own.
The memory of your organization. Everything it knows, captured as sourced facts, structured by a curated taxonomy, and available to everything you make.
Turn a spreadsheet into a branded, accessible chart, ready to place in a deck or a report.
Clear, accessible, on-brand tables composed from your data.
Strategy before words. Gyrium sets the objective, the narrative, and the structure before it composes, grounded in your intelligence base.
The pilot takes a small number of organizations at a time. Bring what you already have.