I never dealt with it or tried anything like you need, but isn't it a good use case for an AI with Retrieval Augmented Generation?

I've _never_ seen a wiki or internal documentation stay up to date.

My experience has been to encourage public blogging / speaking of technical information. If its public, there are several benefits. First you need to explain to people with little context from the company. You also feel scrutiny to make it accurate and not embarrass yourself. And readers will see the date of authorship, and have a sense of when this information was true. And of course, Google is a better search engine than anything you'll have internally!

For example, when I worked on search at Reddit, I didn't point people at anything internal (that stuff rots) but instead I would point people at places like:

https://www.reddit.com/r/RedditEng/comments/1985mnj/bringing...

https://www.youtube.com/watch?v=gUtF1gyHsSM

The downside to this approach is companies are too precious about IP so don't want you to be specific. (despite it almost certaintly not being special). Also company blogs can get over-edited to the point where they lose authenticity in favor of SEO spam.

This isn't the tool to use for things like runbooks, etc. It's a more useful thing for broader context.

I wish more companies just gave their developers their own personal blogs, and were less precious about preventing speaking.

cd ~/Documents

vim knowledge.md

I did that for a very large multi-continent automotive company. There were several unsuccessful attempts before. I did it with my own phpwiki, plus xapian integration for searching over all the other existing documentation and tickets, SAP and CQ. It's still doing good for the last 15 years.

It's markdown, with several plug-ins. Easier than mediawiki which relies on human forces. We preferred automation, but no insanities like on other wikis like WYSIWYG editing and such management nonsense.