Product
A knowledge base that maintains itself
Most internal wikis fail for the same reason: keeping them current is somebody's fourth priority. noūs treats maintenance as the product. Documents come in, an agent keeps them honest, and answers come back out wherever your team already asks questions.
The loop
Three jobs, running continuously. Digest turns documents into knowledge, Groom keeps that knowledge coherent, and Tap In puts it in front of people at the moment they need it.
Step one
Digest
Point noūs at the documents you already have — handbooks, PDFs, contracts, exported wiki pages, meeting notes — and it breaks them into atomic, single-topic knowledge cards. Each card keeps a link back to the passage it came from, so nothing becomes an unattributable claim.
- PDF, DOCX, Markdown and plain text out of the box
- One claim per card, so answers can cite precisely
- New documents are linked to related cards automatically
Step two
Groom
A scheduled agent re-reads the knowledge base the way a diligent editor would: finding duplicates, spotting claims that contradict each other, and flagging cards that have gone quiet long enough to be suspicious.
- Near-duplicate cards are merged rather than left to compete
- Contradictions are surfaced with both sides quoted
- Stale cards are flagged for a human to confirm or retire
Step three
Tap In
The knowledge base lives where the questions already get asked. Connect noūs to your assistant, and anyone on the team can ask in plain language — and write back to the knowledge base in the same breath.
- Search that returns cards, not a wall of raw document text
- Contributions from chat are checked against what is already known
- Gaps get reported, so you can see what people ask and you cannot answer
What you get
The details that decide whether an internal knowledge base gets used or quietly abandoned.
Answers with receipts
Every card carries its provenance: which document, which version, who last touched it. An answer you cannot trace is an answer nobody trusts.
Contradiction detection
When a new contribution disagrees with an existing card, noūs does not silently pick a winner. It raises the conflict with both claims side by side.
Works in your chat client
Claude Desktop, Claude Code, and anything else that speaks MCP. No new tab to remember, no separate wiki to abandon.
Scoped access
Per-workspace isolation and per-token rate limits. A token reads what its workspace can read, and nothing else.
Browsable by humans
The agent maintains it, but people still need to read it. Categories, cards and sources stay browsable in the web app whenever you want to look.
Nothing to migrate
Keep your documents where they are. noūs digests copies rather than asking you to move your source of truth into another silo.
Built for the way teams actually ask
Nobody opens the wiki. They ask the person next to them, or they ask an assistant. noūs makes the second one give the answer the best-informed person on the team would.
- A new joiner asks what the expenses policy is — and gets the current one, with the source attached.
- Someone answers a question in chat that isn't written down anywhere — and contributes it back in one step.
- A policy changes — and the grooming pass finds the three cards that still describe the old one.
- Nobody can answer a question — so it lands on a gap report instead of evaporating.
See it on your own documents
Upload a handful of the documents your team argues about most, and watch what the first grooming pass finds.