How an answer is made. Four steps, all on the machine.
Mail, files, calendar, Teams, watched folders, connected systems.
Microsoft 365 is indexed on a fifteen minute cycle with a live count of each type. A watched folder is read the moment a file lands in it. Spreadsheets are read sheet by sheet so an answer can cite the exact rows it used.
- Cycle
- Fifteen minutes for Microsoft 365, immediate for watched folders
- Detail
- Sheet and rows for spreadsheets, page numbers for PDFs
Enforced in the database, before ranking.
Access is a property of the record, and the filter runs inside the query rather than after it. What a person is not cleared to see is never a candidate. An empty result means nothing matched, not that something was hidden.
- Scope
- Private, team and organization levels on every source
- Sign-in
- Microsoft and Google single sign-on, an authenticator second factor
The nearest passages the person is cleared to see.
The question is embedded on the machine and matched against the index. The passages that come back are the closest ones inside that person's scope, ranked, with the file and the location of each attached before any writing starts.
- Models
- Every tier serves locally: fast, standard, deep, vision and embedding
Resolved from the documents actually retrieved.
A citation is a pointer into the retrieval result, not text the model wrote. If a source was not retrieved it cannot be cited, so a fabricated reference cannot appear as one. When the sources do not hold the answer, ℚ says so.
- Where you ask
- The browser, Microsoft Teams, and email
- When it does not know
- It says so, instead of filling it in
What it indexes, with a live count of each.
Mail, files, calendar and Teams from Microsoft 365, watched folders on the machine, uploads, and the records of every connected system. Each source shows what is indexed and when it last ran.
- Microsoft 365
- Mail, files, calendar and Teams messages on a fifteen minute cycle
- Watched folders
- Read the moment a file lands
Thirty five connectors, one approval ledger.
CRM, finance, developer, project, support and marketing tools connect with a key that is verified against the live service before it is saved. Every connection shows what it did, who asked, and when. Revoke it and it stops the same second.
The sources, the vocabulary and the workflow are fitted to you during deployment. ℚ learns the words your team uses and who approves what.