Knowledge

Everything the agent says comes from here. An agent with a thin knowledge base is not a bad agent — it is an uninformed one, and the fix is on this page.

Three kinds of source

Websites. Give Braid a URL and it crawls the pages beneath it. Set a re-crawl cadence — daily, weekly, monthly — so a changed price does not quietly become a wrong answer. Your own website is almost always the right first source.

Documents. Upload the files your team already relies on. They are read, split into passages and indexed the same way as everything else.

Articles. Written in Braid, for the things that live only in someone's head: the return policy nobody wrote down, the exception you always make, the phrasing you want used.

What makes a good source

• Specific beats comprehensive. A short page that answers one question exactly is worth more than a long one that mentions it.
• Say the thing. "Delivery to Croatia takes 3–5 working days" is usable. "Delivery times vary by region" is not.
• Prune contradictions. Two sources disagreeing about the same fact is the most common cause of a confidently wrong answer.

Sync status

Every source shows when it last synced and whether it failed. Check it occasionally — a silently broken crawl becomes a silently worse agent, which is why the status is on the row rather than buried.

Citations

Answers are grounded in the passages that produced them, so you can see which source said what. If an answer is wrong, the citation usually tells you which source to fix.

Knowledge gaps

The most useful screen in Braid. Every question the agent could not answer from your sources is recorded as a gap.

Work the list from the top. Each entry is a question a real customer asked that you had no answer for, which makes it a better content brief than anything you would have written yourself.