In someone’s head
The person who decided it has left the thread, or the company.
Company knowledge
Decisions should not live in Slack.
People ask. The answer is kept. The next person does not have to find the same expert.
01
Heads, threads, then silence.
The decision exists. It is just not in a place the next person can trust.
Buried in Slack
The reason is in a channel nobody searches, next to ten other reasons.
Search leaves the reading
Search hands you ten files and leaves the reading to you.
Before
“Why do we bill enterprise yearly?” lives in a Slack thread and one person’s memory.
After
The question lands on “Why we bill annually”, with the reason and the source.
02
The loop for this team.
Ask what you meant. If the map is empty, ask the person who knows. Keep that answer.
Ask by intent
A question is matched to what the organization decided and meant.
See the line
The answer shows the exact line, its source, and why it matched.
Fill the hole
At a dead end, Teammate finds the person who knows and writes their answer back.
- Ask
- Land on the line
- Nothing there? Route to who knows
- Keep the answer
The kept answer is where the next question lands
03
What you decided, and why.
The question does not have to use the words on the page.
The billing question
“Can a new enterprise customer go monthly?” finds “Why we bill annually.” The question never says annually.
The reason stays
Enterprise pays yearly. Customers on monthly plans left at renewal. Billing cannot prorate mid-term.
The whole story
If the reason is split across pages, the path is already mapped.
Asked“Can a new enterprise customer go monthly?”
Why we bill annually.
Enterprise customers pay yearly.
- Why
- Customers on monthly plans left at renewal.
- Source
- Confluence · Pricing policy
- Matched
- By intent
04
When nobody wrote it down.
Cluesora notices where the answer should have been, finds the person who knows, and asks.
Named expert
Teammate matches on role, field, and expertise tags, then puts the question in that person’s queue.
Answer kept
The asker gets the answer. The answer is kept. The same question is not routed again.
Fallback
If no expert fits, it goes to the teammate’s manager.
05
What this team uses.
Corpus holds the decision. Teammate is how people ask and how holes get filled.
Corpus
The map of decisions, reasons, people, and systems, with the exact line on every answer.
Teammate
Ask in the app, Slack, or Teams. Unknown questions go to the person who knows.
Chrome clipper
Save the page where the decision was actually written.
AI agents
Tell an agent to add this to Cluesora when a decision is settled in a tool.
06
What to measure.
Outcomes you can see without inventing a score.
Still in someone’s head
Whether the same decision still needs the same expert the next time it is asked.
Landed on intent
Whether a question lands on the decision you meant, not on ten files.
Conflict in view
Whether two disagreeing decisions stay visible instead of becoming one wrong answer.
Stuck questions
What people actually get stuck on, as a list of routed questions.
07
The map stays true.
New versions take over. Old ones are kept and dated. Sources are never rewritten.
Agents extend
Agents update the existing decision instead of filing a second version.
Anyone can correct
Anyone can correct what is wrong, and their edit wins.
About a minute
Small updates are usable within about a minute.
Questions people ask.
Does this replace Slack?
No. People still ask in Slack. Teammate answers there, and the answer is kept in the map.
What if the decision was never written down?
Teammate finds the best-matched expert, asks them, and writes the answer back.
How does a question find a decision that uses different words?
It is matched to what you decided and meant, not only to the words on a page.
Will two opposing decisions be merged?
No. You see both sides and where each came from.