What it is good for. And what it is not.
It reads the files you already have and learns how things are done in them — the procedures, the practice, the lessons — with the page behind every line. That makes it very good at one kind of question and no use at all for another. Here is the honest list.
How things are done, buried in text nobody has time to read.
Standard procedures
Operating procedures, work instructions, checklists — the steps that are written down in ten places and the same in none. It learns the procedure and where each step comes from.
The process inside expert reports
Assessment reports, inspection reports, incident write-ups. From a pile of them it learns how the work is done — what gets checked, in what order, what counts as a fault — not the details of any one case.
Know-how in unstructured text
Emails, meeting notes, handover documents, chat exports. The way things actually get done, written down in passing, becomes chapters a newcomer can read.
Rules and their exceptions
Policies, regulations and contracts, read for their rules: what applies, when, and what happens otherwise — with the clause behind each one.
Files that disagree with each other
Old and new versions, two departments' procedures. It finds where they clash and asks you which is right, rather than quietly picking one.
Questions that start with "how do we"
Support desks, technicians, new colleagues: an assistant that answers from your own practice, shows the passage it rests on, and has passed a test on your files first.
Looking things up.
What happened in which report
It learns how things are done, not what happened when. Which case was assessed on which date, what one report concluded, who signed it — that is a search through records, and it will not be reliable at it.
Facts, figures and records
Names, dates, amounts, serial numbers, the entry for one customer. It is not a database and not a filing system: it keeps the practice, not the record.
Things nobody wrote down
It knows only what is in your files. What lives in someone's head, in a chat you did not add, or on the internet is out of its reach.
Numbers that change by the hour
Stock levels, prices, order status, live systems. It learns from files at the moment it reads them; it is not a live connection to your databases.
Spreadsheets, drawings and pictures
It reads text: PDFs, Word files, plain text, scans with text in them. Tables of numbers, technical drawings, photos and handwriting are not text to it.
Advice, opinions and predictions
It tells you how your files say things are done, not what you should decide. It will not judge, forecast or take a side.
If the answer is a way of doing things, it is for you. If the answer is a record, it is not.
Ask what you want back. "How do we handle a complaint?" is a lesson: it lives in many files, it is the same each time, and it can be learned. "What did report 47 conclude?" is a record: it lives in one file, it is different every time, and it should be looked up, not learned. It learns the first kind — and for the second it will say your files do not cover it rather than guess.
Create your workspaceCreate your workspace and drop in a few files.
You do not need to talk to anyone first. Make a workspace, add some files, say what you want learned from them, and watch the first reading run.