Documentation
The Ontological Map
What it is
When you add sources to a project, LithicBlue doesn’t just store the files and re-read them whenever a question comes up. It reads them once, up front, and organises what they contain into a structured map of the people, organisations, topics and key facts across the project, and how they connect.
That map is the backbone of the project knowledge base. It’s built on LithicBlue’s proprietary ontology for professional-services work, so the structure reflects the way advisors actually reason about an engagement rather than a generic pile of text.
Why it matters
Doing this work in advance (rather than at the moment a question is asked) is what sets LithicBlue apart from tools that search raw documents on demand:
- Accurate answers, not conflicting ones. Where sources disagree, LithicBlue resolves the conflict before the information is ever used. See contradictions. Agents draw on the resolved picture, so they aren’t left picking between two versions of the truth mid-task.
- Faster access. Because the hard work of reading, connecting and reconciling is done ahead of time, the agents retrieve what they need in a single step instead of re-parsing documents every time.
- Reasoning across the whole project. Because facts are connected rather than siloed per file, LithicBlue can follow a thread across many sources at once, and trace any claim back to exactly where it came from.
The short version
Competitors read your documents when you ask a question. LithicBlue reads them first, resolves the contradictions, and hands its agents a clean, connected map, so the answers come back faster and more accurately.
What builds it
The ontological map is built entirely from your project’s own sources. As you add, sync or remove sources, the map keeps pace with them. Deliverables are reviewed against this map but never feed into it; the evidence base stays separate from the outputs you produce.