Provenance
It separates proof from opinion
A fact backed by a message is stored differently from something a person only claimed. The difference is a field in the record, not a matter of wording.
AI memory for your company
Your company already knows.Now it can answer.
CorpusGrid captures the decisions, findings and delays buried in the email and documents your teams already produce, along with the reasons behind them. Nobody has to write anything down. Ask in plain language, get an answer with its sources, and only what you’re cleared to see.
- Each person only sees the work they are cleared to see
- Every answer shows the messages it came from
- A new employee can ask what normally takes years to learn
In one picture
Your company’s knowledge, in one memory.
Every day your company produces more than anyone could read. CorpusGrid keeps the part that matters, connects it, and hands it back as answers, as warnings, and as a short list of what needs you today.
01 Three teams, six weeks
- SupportUnit runs hot after an hourMail
- Team lunch on Fridayignored
- PurchasingNew fan, 11% cheaperMail
- Industry Weekly #214ignored
- ProductionFan at heat limit, approvedMeeting
- Out of office until Fridayignored
- SupportService report: batch 2602File
4 kept · 3 ignored · 0 filed by hand
Nobody changes how they work.
02 One connected memory
Context
C40 overheating complaints
- DevelopmentFan supplier changed, 11% cheaper
- DecisionBatch approved with fan at heat limit
- Finding3 complaints, one cause: batch 2602
3 departments · 11 messages · linked to 2 other contexts
Not a folder. One story, told by three teams.
03 What comes back
Answers
“Why are C40 complaints up?” Three customers, three descriptions, one cause: batch 2602, built with the new fan.
4 sources
Warnings
Purchasing is about to order 5,000 more fans from the same supplier.
1 open order
Actions
Four things need you today. The most urgent: 1,200 units already in the field.
from 3 contexts
Lessons
Approving a new supplier’s part at its test limit has brought complaints every time.
4 contexts
A new employee knows what a fifteen‑year veteran knows.
Email, the documents attached to it, and the notes people write after a meeting. One department’s message becomes another department’s answer, and the record keeps the same fields whichever of the three it came from.
What you get
One colleague who knows everything and forgets nothing.
No one person could keep all of this in their head. CorpusGrid does, for every team at once.
01 · Answers
Ask a question. Get an answer, not a search result.
Ask in normal words, the way you would ask a colleague. You get the answer itself, with the messages it came from. If the record cannot answer, it says so instead of inventing one.
Why did C40 complaints jump in March?
It is one fault, described three ways. All three units come from batch 2602, the first built with the new fan supplier (Purchasing, 12 Feb). The new fan ran close to its heat limit in testing, and Production approved the batch anyway to make the ship date (19 Feb).
Drawn from
- Fan supplier changed, 11% cheaper
- Fan at heat limit, batch approved
- Service report: 3 units, batch 2602
When nothing in the record supports an answer, CorpusGrid says so instead of producing one.
02 · Warnings
It warns you before the same mistake happens twice.
You do not have to know that a question exists. When new work starts to look like something that went wrong before, CorpusGrid tells you, and shows you the case it means.
new thread · Purchasing · today
Supplier
Order confirmed: 5,000 fans for the C40, shipping 2 May
This has happened before
All three C40 complaints in March came from units built with this supplier’s fan. The last time a new supplier’s part was approved at its test limit, it ended in a recall.
- C40: 3 complaints, all batch 2602Support · 1 file
- K12: new supplier, approved at limit, recallProduction · 3 notes
Open the caseNot relevant
03 · Actions
It tells you what needs you today.
Not a task list somebody typed in. CorpusGrid reads what is open across your work and puts the few things that need a person in front of you: this expires soon, these two answers disagree, nobody replied to this.
this morning · 4 things need you
DecideC40 batch 2602Support
1,200 units from this batch are in the field. Three have already failed.
3 complaints · 1 file
CheckFan orderPurchasing
5,000 more fans from the same supplier ship on 2 May.
Confirmed today · 1 email
ReplyNorthwind complaintSupport
Northwind reported a shutdown six days ago. Nobody has replied.
Waiting 6 days
ReadHeat testProduction
Batch 2602 was approved at the heat limit. Nobody has reviewed that approval since.
Since 19 Feb · 1 decision
Nobody wrote this list. It came out of the record.
04 · Lessons
Lessons write themselves.
Most companies do keep lessons learned. Then they sit in a folder nobody opens again. Here they form from the record on their own, and each one is checked against the work in progress, so you hear about it when it applies.
lessons · product qualitywritten from the record
- 01
When a new supplier’s part was approved at its test limit, complaints followed within six weeks, three times out of three.
3 contexts · 2022–2026
- 02
The same fault reached Support in different words. Closing tickets one by one hid the pattern for weeks.
4 contexts · 2024–2026
- 03
Batches held back until the part passed with margin had no returns from the field.
5 contexts · 2023–2026
Nobody held a workshop to write these.
The idea
Not a pile of messages. A context.
A folder puts files in one place. A context records how they affect each other, and contexts are linked to each other too. That is how a delay at a supplier becomes a warning on a schedule nobody had connected to it.
Nobody has to feed it
Every system that needs maintenance stops being maintained. That is why the knowledge bases your company has tried are empty. Here there is no approval queue, no weekly review, and nobody whose job becomes keeping the system alive. When it gets something wrong, the person who noticed fixes it on the spot.
Why nothing else worked
The knowledge exists. Nobody can reach it.
Your company already wrote all of this down. It is spread across thousands of messages that nobody will ever open again.
- 01
It is buried in day-to-day messages
Four months of discussion across three teams end up as one line in a contract.
- 02
It leaves when people leave
The engineer who approved that exception is gone. The exception is still in force.
- 03
Search finds words, not meaning
The two messages that explain the change never use the word you searched for.
- 04
Your AI knows nothing about you
Every conversation starts from zero, so the answers fit any company except yours.
For your AI
Your AI stops starting from nothing.
Models reason well and remember nothing. That is why their answers sound like they were written for somebody else’s company. CorpusGrid is the missing half: the long memory the model reads from.
A model on its own
What it can see
- Your question
- —
- —
- —
- —
Its answer
“Overheating usually points to blocked vents, a hot room or a worn fan. Check where the unit is installed…”
True of every company. Useless to yours.
The same model, on CorpusGrid
What it can see
- Your question
- The context it belongs to
- 6 events, in the order they happened
- 3 decisions and the reasoning behind them
- 11 messages the answer can point at
Its answer
“All three complaints come from batch 2602, the first built with the new fan supplier. On 19 February the fan ran close to its heat limit in testing, and the batch was approved anyway…”
Your history, not general knowledge.
The memory grows every week from mail that was going to be written anyway, so the gap between what your company knows and what it can answer keeps closing on its own.
Why it holds up
A memory is only useful if you can trust it.
Three things that had to be decided at the start, because none of them can be added later.
Residency
It runs where you decide
On your own servers, if your data must not leave the building. If it may, on our own infrastructure in Europe and Türkiye.
Correction
Mistakes take one click to fix
Move an event, split a context that became two, merge two that were always one, merge a person who appears under two addresses.
See it for yourself.
A short demo first. Then let’s work out together how you could use it at your company.