Cluesora Corpus
Coming soon
Your organization already knows.
It just can't tell you.
The answer is in a doc someone wrote in March, a thread that scrolled away, a runbook two people ever read. Nothing is missing. It's just unreachable — by your team, and by every agent you've pointed at it.
Corpus turns all of it into something an agent can actually reason over.
Corpus isn't open yet. We're taking names, not payments.
The knowledge didn't leave. The people who could find it did.
Every organization runs on things that were only ever explained once — why the pipeline is configured that way, what the client actually meant, which of the four documents is the one that's still true. It gets written down often enough. It just gets written down somewhere.
So search returns the document instead of the answer. A new hire spends three weeks assembling what a colleague could have said in a sentence. And when you finally hand the whole pile to an agent, it does what the search box did, faster — because a folder of files is not a thing you can reason over. It's a thing you can grep.
What Corpus does
Three indexes. One document. Nobody files anything.
Most systems index a document one way and live with what that costs them. Corpus lays every document down three ways at once, and keeps all three current in the background as the document changes.
Every document is laid down three ways at once — as concepts in a tree, as entities and relations that reach across documents, and as full text over every entity. An agent's question is answered from all three, and never reaches anything the person behind it isn't entitled to see.
Concept tree
Ideas resolved into leaves, branches and a trunk — so two documents that say the same thing in different words land in the same place instead of sitting beside each other forever.
Entity graph
The people, systems, clients and processes your documents keep mentioning, and the relations between them — the connections that only exist across documents, which no single file can hold.
Full text
Every entity searchable on its literal words, because sometimes the right answer is the exact phrase somebody used and no amount of structure beats finding it.
All three are maintained continuously and eventually consistent — the work happens after the write, not during your query. You add a document and carry on. Corpus catches up.
Entitlements
A memory an organization can actually switch on.
The reason most organizations never point an agent at everything they know is not that the technology can't hold it. It's that nobody can promise what comes back out, to whom.
Corpus assembles every answer inside the asker's boundary. Not a filter bolted on at the end — the entitlement is part of how the answer is built, which is the only version of this that survives the awkward cases: the half-shared document, the contractor with access to one project, the person who moved teams last week and should stop seeing the old one.
An agent inherits the permissions of the person behind it. Nothing else was ever safe to ship.
Built in, not bolted on
- Multi-tenant from the first commit — not a single-user tool that grew an organization mode.
- Boundaries that hold on the ambiguous cases, not just the obvious ones.
- The same rules whether the question arrives from a person, an agent, or an integration.
There are other memory products. These are the differences that are structural.
Structure it derives, not structure you author
Commonly
Link-based tools ask you to draw the connections yourself, then go stale the week you stop.
In Corpus
Corpus reads what you already wrote and works the structure out — which ideas are the same idea in different words, which sit under which, which reach across documents.
Relations with a direction
Commonly
Most memory stores keep flat facts and retrieve whatever looks similar to the question.
In Corpus
Corpus keeps directed relations between concepts — what has to make sense before this does. A similarity search cannot answer that question; it has nowhere to put the arrow.
Boundaries built for an organization
Commonly
The category grew up around one developer and one vault, so permissions arrived late and thin.
In Corpus
Corpus was built inside a multi-tenant product from the first commit. Entitlements are not a filter applied at the end — they are part of how the answer is assembled.
Not a prototype
This layer is already carrying a product.
Corpus isn't a new idea we're announcing early. It's the substrate underneath everything Cluesora already does — the layer that reads an institution's own textbooks, works out which ideas depend on which, and follows a single concept from the page it was written on to the learner who never quite got it.
That product needed a knowledge base that could hold ordered, derived, permissioned structure at organizational scale. We had to build one. Corpus is that layer, opened as its own door.
We'd rather open this properly than early.
Corpus works. What it doesn't have yet is the pricing, the limits and the self-serve path to let you run it without us in the room. Leave your name and we'll come to you when it does — no waitlist theatre, no drip campaign.