Every answer has a footnote.
The promise
Every sentence carries its source.
You ask in your own words and get an answer with the passage it came from right behind it. Checking takes seconds instead of half an hour in the filing system.
fact reads what your organisation already has: contracts, minutes, concepts, manuals, shared drives, mail, recordings. A question does not produce a summary out of nowhere but a text with source markers. Clicking one opens the passage the sentence came from — not the document, the passage.
Belegte Antwort
Jeder Satz trägt seine Quellenmarke. Ein Tipp darauf öffnet die Stelle im Dokument, aus der er stammt.
Abläufe statt Prompts
Wiederkehrende Arbeit ist als Ablauf hinterlegt: Rolle, Datengrundlage, Aufgabe, Format, Sperren. Immer in dieser Reihenfolge.
Fertige Unterlagen
Präsentationen entstehen in der Vorlage des Hauses — Layouts, Fußzeilen, Schriften bleiben, wie sie sind.
What you do with it
From question to finished document.
- 01
Bring knowledge in
Folders, shares and SharePoint libraries are connected; PDFs, Office files, images containing text and audio recordings are read. Images are opened up by text recognition, recordings transcribed with a European model.
- 02
Ask — in chat or as a workflow
Chat for one-off questions. For recurring work, a workflow: role, source data, task, format and constraints, always in that order. Constraints come last because the final instruction is the one most reliably followed.
- 03
Check
Answers carry numbered references. The source view shows the quoted passage in context. Anything unsupported is marked as unsupported rather than asserted.
- 04
Reuse
Answers become reports, diagrams and presentations — in your house template. Layouts, footers, fonts and colours stay as they are.
- 05
Write back
Results land where they belong: a note on the customer record, a task, a filed document. Anything that cannot be matched comes back as an open item and is never guessed.
Subject experts
Separate collections rather than one big pot.
Knowledge is kept apart by subject: contracts, methodology, project archive, client file. You pick the collection and get an answer that did not come from an unrelated context.
The reason is unglamorous. A single large collection returns the statistically most similar passages for any question, not the factually right ones. Separation is the cheapest quality measure there is.
Prepared steps in the app — from a proposal paragraph to the weekly report.
Typed master data that workflows draw on. What is missing is shown by the completeness indicator.
For specially protected fields, personal identifiers are replaced before processing.
Documents
Presentations that look like your organisation.
An answer becomes a deck in your template — with the layouts your template provides and the footers your organisation requires.
No rebuilt design and no hard formatting that breaks your template’s inheritance. Open the file in PowerPoint afterwards and you get a file that could have been made by hand — and can be edited normally. Diagrams are generated as their own graphics in the house palette, with a visible note that they were machine-made.
What if we have several templates?
Then there are several. One is the house default, individuals can store their own, and a single document can use a third. They are resolved in that order.
Do headers and footers survive?
Yes, including the date field and slide number. That is less obvious than it sounds: the common libraries drop exactly those placeholders when adding a slide. We put them back deliberately.
What about templates that went through other software?
Those too. Templates that have passed through LibreOffice or a conversion tool have a fragmented layout structure. We read every level, not just the first — otherwise you see one layout in the picker instead of fourteen.
On the move
On the phone as well.
fact runs in the browser — at your desk, on a tablet, on a phone. For recording and scanning on the move there is the atrium app.