Upload today
Upload PDF and Markdown today. More formats are coming.
Corpus
The map of what you meant.
It starts with everything your organization already knows. It stays true.
01
Every way in, one map.
Upload, clipper, Confluence, Teammate, and any MCP agent. Same checks. Same permissions.
Clip and import
The Chrome clipper saves only the page you choose. Confluence imports as a copy with a link back.
Agents and Teammate
Tell an agent to add this to Cluesora. Ask Teammate in the app, Slack, or Teams.
Your wiki stays
Your wiki and search stay. Cluesora sits beside them.
Your workspace · permissions follow every source
Ways in
- Upload — PDF, Markdown
- Chrome clipper — only what you Save
- Confluence import — copy with a link back
- AI agents (MCP) — Claude, Cursor, Codex, Devin, any MCP agent
- Teammate — app, Slack, Teams
- Jira · email · code hosts — planned
arrives
Read on arrival
Same checks for every way in
- Read and summarised (short + study summary)
- Connected to everything related
- Checked — garbled scans held back, repeats count once
- Permissions attached from the source
kept
The map (Corpus)
- Pages, with their sources
- Ideas and what they depend on
- People, systems, customers, vendors
- Tables kept as rows
- Every version kept, dated
used
Put to work
- Search by intent → exact line + why it matched
- Teammate answers, with sources
- Agents search first — reads never metered
- Fathom — courses, checks, vivas
Dead ends and agent updates are written back
02
What the map keeps.
Decisions and their reasons, sources, people, systems, what to learn first, and data tables.
Decisions and reasons
What you decided, and why, stays findable by intent, not only by the words on a page.
People and systems
Teams, services, vendors, customers, and who can actually answer, not only who is mentioned.
What to learn first
For every idea it knows what must be understood first.
Tables stay tables
Tables stay as rows you can query and total. Pages cite them live.
- Decision
- Enterprise customers pay yearly.
- Reason
- Customers on monthly plans left at renewal.
- Source
- Confluence · Pricing policy
- System
- Billing · owned by the Billing team
- Learn first
- Plan types · Proration rules
- Table
- Plan tiers, cited live
03
Finding by intent.
A question is matched to what your organization actually decided and meant.
Words still work
It also matches keywords and meaning, but intent is the difference.
The billing question
“Can a new enterprise customer go monthly?” finds “Why we bill annually.” The question never says annually.
The reason attached
Enterprise pays yearly. Customers on monthly plans left at renewal. Billing cannot prorate mid-term.
Asked“Can a new enterprise customer go monthly?”
Why we bill annually.
Enterprise customers pay yearly.
- Why
- Customers on monthly plans left at renewal.
- Because
- Billing cannot adjust partway through a term.
- Matched
- By intent. The question never says “annually”.
04
The exact line, and why.
Every result shows the exact line, its source, why it matched, and what it connects to.
The sentence itself
You see the line that answers you, not a file to go hunt through.
Why it matched
Each result says why it matched: by intent, by meaning, or by the words.
What it connects to
Related ideas, owners, and other sources sit next to the line.
Search result · illustrative example
Asked“Who signs off when a new laptop costs more than usual?”
Hardware above the standard budget needs the department head’s approval.
- Source
- IT purchasing policy · Exceptions · Confluence
- Why it matched
- By intent. “Costs more than usual” means “above the standard budget”.
- Connects to
- Department heads
- Purchase request form
- Standard laptop list
05
The whole story, already mapped.
When the story is spread across several places, Cluesora follows connections it has already mapped.
Ready before you ask
The reading is done before anyone asks, so a question lands on the answer in one hop.
No guessed route
It does not guess the path from page to page while you wait.
Caveats travel
An edge case in a second document arrives with the main answer, cited.
- Pricing policy
- Exception memo
- Billing FAQ
06
Disagreements stay in view.
When sources disagree, you see both sides and where each came from.
Both sides shown
One page says refunds take 14 days, three others say 30. Both stay visible.
Nothing blended
Nothing is blended into a confident wrong answer.
Agreement, cited
When sources agree, you get one answer with all of them cited. A caveat is kept.
Before
A tool picks 30 days because more pages say it, and hides the 14-day page.
After
You see 14 days and 30 days, each with its source.
14 days
- Refund policy (2023)
30 days
- Support handbook
- Billing FAQ
- Customer terms
07
The map stays correct.
Routine upkeep is automatic. Unclear calls get checked first. Anyone can correct what is wrong, and their edit wins.
Dead ends write back
At a dead end it finds the person who knows, asks them, and writes their answer back.
Agents extend, not fork
Agents update the existing doc instead of filing a second version.
Versions kept, dated
New versions take over. Old ones are kept and dated, never deleted.
About a minute
Small updates are usable within about a minute. Large PDFs take up to ten minutes.
- Today
Enterprise P1s: first response within one hour.
Written back from Slack by the support lead - Before
No answer on record.
The question hit a dead end
08
What the library assumes.
When something your content needs is not taught anywhere yet, Cluesora keeps a list.
Assumed, never taught
It shows exactly what your library assumes but never explains.
Listed once
Fifty topics assume basic Python and nothing teaches it. Cluesora lists it once.
Links fill in
When a Python primer is added, all fifty connect to it.
09
Quality it will not bend.
Bad input cannot bend the map. After a big change it checks its own work and fails loudly.
Garbled scans wait
Garbled scans are held back until fixed. A passage repeated fifty times counts once.
Headings do not glue
Generic headings do not glue unrelated things together.
Summaries rewrite
Every page gets a short summary and a longer study summary. Both rewrite when content changes.
Loud failure
It checks its own work after every big change and fails loudly instead of quietly getting worse.
10
For people and for agents.
The same map answers a person in the app and an agent in a coding tool.
People get lines
A person gets the answer, the exact lines, the sources, and the conflicts.
Agents search first
Agents search first, then save what they settle. Reads are never metered.
Same permissions
Nobody, person or agent, sees more than the source allows.
Questions people ask.
Do I have to tag documents as they arrive?
No. When content arrives it is read, summarised, connected, and checked. Nobody tags or files anything.
What does answered by intent mean?
The question is matched to what you decided and meant, not only to the words on a page.
What if two procedures disagree?
You see both sides and where each came from. Nothing is blended into one wrong answer.
Can I query the tables inside documents?
Yes. Tables stay as rows you can query and total. Pages cite them live.
Will an agent create a second copy?
No. Agents update the existing doc. Sources are never rewritten.