Resources
From a document in SharePoint to a cited answer.
A good answer is not merely fluent. It is authorised, evidence-grounded, temporally correct, auditable, and explicit about what it does not know. Here is the path every answer takes.
- Step 1 Connect
Rounic reads from where your firm already works — SharePoint, OneDrive, Outlook, your CRM, VDR exports, board packs, and direct upload. Nothing is migrated. Connectors cursor and resume, so a re-sync never double-counts and never silently skips.
- Step 2 Parse, without losing the structure
PDFs keep their page and region. Excel keeps its sheet, cell, and formula. PowerPoint keeps its slide; Word keeps its paragraph. Tables stay tables and financial figures keep their precision — because a number you cannot trace back is a number you cannot use.
- Step 3 Resolve the entities
Aliases, project code names, and duplicate records are resolved into canonical companies, deals, funds, and people — with a confidence score, and reversibly. A company and a deal episode stay distinct, so the third time you look at a business you can see the first two.
- Step 4 Type the claims
Facts, derived calculations, and model inferences are different objects and are stored that way. Each claim carries its period, its unit, its source version, and its state — including whether it currently contradicts another claim.
- Step 5 Assemble the context
A query plan decides what the question actually needs: this deal, a strategy, the whole firm history, an as-of date. Retrieval is filtered by your permissions before anything reaches a model — not after.
- Step 6 Answer, and show the work
The answer arrives with its evidence rail, its citations, and a panel explaining how it was assembled. Where the evidence does not support a conclusion, Rounic abstains and says so.
Non-negotiables
Six guarantees the product will not trade away.
Permissions before retrieval
Authorisation is decided before a document is retrieved, not by filtering an answer afterwards.
Fail closed
When authorisation, provenance, or parsing is uncertain, Rounic withholds rather than guesses.
Temporal truth
What the firm believed in 2023 is recoverable in 2026. Answers can be reconstructed as of any decision point.
Corrections propagate
Fix a number once and everything derived from it is marked, re-checked, and regenerated — not left quietly stale.
Documents are not instructions
Text inside an ingested file is data. It can never issue commands to the system that reads it.
Human authority
Consequential actions — decisions, approved lessons, external write-backs — require a person.