
- SPREADSHEETSKPI dictionary, targets and CSV spreadsheets go into Knowledge.CSV only
- RECORDSEach CSV becomes chunks with the header repeated and the records numbered.
- QUESTIONThe team asks about a KPI, a period or a unit.
- CALCULATIONThe analyst shows the formula, each value with file, column and record, and the math.math shown
- MISSINGA value not in the base is not estimated: it says what is missing and where.nothing made up
- DECISIONThe team checks the original spreadsheet before deciding.human decision
How it works
During setup, the KPI dictionary, the targets and the spreadsheets exported as CSV go into Knowledge. Each CSV becomes chunks that repeat the header and number the records, so any retrieved passage says which column and record a value came from. The analyst answers the team showing the full calculation: the formula and the document it came from, each value with file, column and record, the math and the result. A missing value is not invented, estimated or projected: it says which data is missing and which spreadsheet it should be in. If the search did not return every record, the total is marked as partial. With the optional data connector, the analyst also queries released tables in a company Postgres, read only, showing the SQL and the source of the query; the KPI definition still comes from the dictionary in the base. Studio evaluates every agent version before publishing, and Guard applies the sensitive data policy before the model.



