Because content is loaded once at setup and never revisited. The product changes, the articles do not, and the assistant keeps answering confidently from material that is now wrong.
The knowledge base is the set of articles the assistant may answer from, each tracked as its own source.
Each article is a source with an owner, a date and a review interval. Answers cite the article, so you can see which sources are actually being used and which are dormant.
An article last reviewed fourteen months ago is producing thirty answers a week. That is visible as a risk, ranked by usage rather than buried in a content list.
It will not write articles. Where the failed-question report shows a gap, somebody who knows the product still has to answer it.
Its owner, last review, how many answers it has produced, and whether those conversations ended in handover.
Yes — internal sources answer staff, not visitors.
Yes, and the answers it supported stop.
Yes, with handover rates per article.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.