Resources

Everything you need to run it well

A knowledge base is a practice, not a purchase. These are the guides, references and notes we use ourselves — how to seed one, how to read what the grooming agent tells you, and how to keep it worth trusting a year in.

Start here

Six collections, ordered roughly the way most teams need them.

Docs

Documentation

Setup, connecting your assistant, ingesting your first documents, and the shape of a knowledge card.

Guides

Playbooks

Opinionated walkthroughs: seeding a knowledge base from a messy shared drive, and what to do with the first contradiction report.

Notes

Field notes

What we learn from watching real knowledge bases decay — and the tuning decisions that came out of it.

Reference

MCP tool reference

Every tool the connector exposes, what it returns, and how rate limiting behaves under load.

Templates

Starter templates

Category structures for onboarding, engineering practice, and company policy that you can adapt rather than invent.

Changelog

What's new

Release notes for the ingestion pipeline, the grooming agent, and the connector.

Latest writing

Longer pieces, newest first.

Common questions

Do I have to move my documents into noūs?
No. noūs digests copies. Your source of truth stays wherever it already lives.
What happens when two documents disagree?
The grooming pass raises a contradiction with both claims quoted, and a human decides. noūs never silently picks a winner.
Which file types can it read?
PDF, DOCX, Markdown and plain text today. Anything with extractable text is a candidate.
Can I see what the agent changed?
Yes — every merge, retirement and edit is attributed and reversible from the web app.

Still have a question?

If it isn't answered above, it probably belongs in the docs — tell us what you were looking for and we will write it.