CAPABILITY / SEMANTIC GRAPHRAG BY LAVINIUM
Answers from your own documents, with the source, on infrastructure you control.
Semantic GraphRAG answers questions about your company's documents and systems. Each answer cites the document, the version and the passage it relies on, and is built only from what the person asking is allowed to see. It runs on infrastructure you control. We design and build it with your team, starting with one bounded pilot, and the first step is a review of your data and systems.
7 min read
Why search and chat tools fall short on company knowledge.
Company knowledge does not sit in one clean place. It sits in contracts, drawings, procedures, correspondence and records, some of them older than the systems that now hold them, spread across systems that were never designed to talk to each other.
The same document often exists in several versions, and only one of them is in force. Access differs by department, by site and by role. Some of the data cannot leave your infrastructure at all.
A general search or chat tool answers from whatever it can reach. It can quote a version that has been replaced, surface material the person asking should not see, or need your documents sent to an outside service before it can answer.
Who it is for
Operations and technical leads in mid-sized and larger companies whose knowledge lives in documents and older systems, where some data must stay on your own infrastructure or access rules are strict by department. Typical settings include industrial operations, energy, logistics, banking, healthcare and corporate operations.
If your data can leave and your access rules are simple, a hosted assistant may be enough, and we will tell you so.
What it does.
Cited answers
Each answer points to the document, the version and the passage it relies on. It separates what is confirmed from what was extracted from the text, and says when the evidence is thin or contradictory instead of guessing.
Permissions all the way through
People only get answers built from what they are allowed to see. The rules apply at every step, not just to the final text. It will not even confirm that a file you cannot open is there.
Versions that matter
It tells the version in force apart from a newer one still under review. The original document is kept intact and recoverable, so a newer version never overwrites the one people relied on.
Runs where you control the data
Processing stays on infrastructure you control by default. Anything that leaves does so only for a purpose you have agreed to, and it is recorded. You choose how isolated it is.
Works with the systems you have
It connects to your existing systems read-only first, without replacing your ERP, your CRM or your document stores. Coverage grows one source at a time, once each source has been checked.
Encryption throughout
Data is encrypted throughout the system, from the sources it reads to the answers it returns, with a post-quantum option for organizations that want it.
What an answer looks like.
Example (illustrative): not from a client system.
| Field | Content |
|---|---|
| Question | Which version of the supplier agreement with our parts vendor is in force? |
| Answer | Revision C is in force. It is signed by both parties. Revision D exists and is under legal review. It does not apply until it is signed. |
| Source | Supplier agreement, revision C, delivery terms. Open the source ↗ |
| Cited passage | "The supplier will deliver within the lead times set out in the schedule in force at the date of the order." |
| Confirmed | Signature status of revision C, from the contract record. |
| Extracted | Delivery terms, read from the document text. |
| Note | Revision D changes the delivery terms. Until it is signed, the terms of revision C apply. |
| Access | Answers use only documents you have access to. |
Your data stays under your control.
- Where it runs. On infrastructure you control by default. The options range from fully isolated to connected with outside services you have named.
- What leaves. Nothing leaves unless you have agreed to it for a stated purpose, and each use is recorded so you can check it later.
- Encryption. Throughout the system, with a post-quantum option.
- Training. Your operational data is not used to train models unless you decide it should be.
- A way out. Export, restore and handover are tested before go-live. You receive the code, the documentation and the tests.
Before the system goes live, we run these with your team and hand them over:
- Permission tests: two people in two departments, and one restricted document that only one of them may open.
- A restore test from backup.
- An export test of your data and of the system's records.
- Acceptance tests for citations, agreed before the pilot starts.
How a deployment starts.
01 / Readiness review. We review the sources, permissions and systems involved. The review decides what the pilot can safely include, and it stands on its own if you stop there. What the review covers ↗
02 / Pilot. One bounded set of questions and sources, connected read-only, with acceptance tests agreed before work starts. You see real answers on your own documents, inside your own access rules.
03 / Expansion. Further sources are added one at a time, each checked against the same tests before people rely on it.
04 / Handover. You receive the code, the documentation and the tests, so your team or another can run the system without us. Ongoing support is available as a separate, optional agreement.
Timing depends on the sources and systems involved. We confirm it after the readiness review, before the pilot starts.
What it does not do.
- It does not replace your systems of record. Your ERP, CRM and document stores stay where they are and remain the source of truth.
- It does not decide matters about people. Decisions such as hiring or pay stay with people.
- It does not give legal opinions. It can show you what a contract says and where. Interpreting it stays with your advisors.
- It can be wrong. That is why every answer shows its source, so a person can check it.
BEFORE WE GET TO WORK
A few answers.
What is permission-aware GraphRAG?
It is a system that answers questions from your documents and systems while applying each person's access rights at every step. GraphRAG means it also maps how documents, versions and records relate to each other, so it can follow those links when it puts an answer together. Permission-aware means each person only gets answers built from material they are allowed to open.
Can it run without sending our data to an outside AI service?
Yes. Processing stays on infrastructure you control by default. If you decide that a named outside service should be used, that use is agreed for a stated purpose and recorded. You choose anything from a fully isolated setup to one connected with services you have named.
How does it stop people from seeing documents they are not allowed to see?
Access rules apply at every step of finding and assembling an answer, not just to the final text. It will not even confirm that a file you cannot open is there. Access requests go to the person who can grant them, and nothing is delivered until access has been checked again. Before go-live, we run permission tests with your team.
What happens when the documents do not answer the question?
It says so. When the evidence is thin or contradictory, the answer states that instead of guessing, and shows what it did find. It can still be wrong, which is why every answer shows its source.
Does it replace our document management system or ERP?
No. It connects to the systems you already have, read-only first, and they remain your systems of record. It grows one source at a time.
Why do you review our data and systems before building it?
Because the review decides what the pilot can safely include: which sources, which permissions and which systems. It stands on its own if you stop there. How we audit before production ↗
PRACTICAL GUIDES
Plan the first deployment.
How to integrate AI with legacy systems ↗
START WITH THE QUESTIONS
Tell us which questions your teams cannot answer today.
Tell us where the knowledge sits, which systems hold it and who needs to reach it. If some of it cannot leave your infrastructure, or access differs by department, say so. We will reply with what a readiness review would cover and how a pilot could be bounded.
We'll use these details to respond to your enquiry.