Ask HN: How do you keep documentation up to date with AI generated code?

I've seen numbers like 75% of code at Google is AI generated, huge %s of code overall is AI generated, open source projects overwhelmed with "slop" PR requests.

It's pretty undeniable that AI code is here to stay - so on your teams / companies how are you managing staying up on PR reviews, and documentation?

From my observations - by accumulating technical debt faster than US and EU financial combined.

If someone asks about the internals of the projects it is - you want the truth, you can't handle the truth.

have an ai workflow man it’s mid 2026.

any time ai does any work, it ensures the ADRs are up to date.

it is part of the execution workflow.

maintain the todos which are a record of work that was done. ADRs have the latest current documentation.

Honestly same way I did before, checking periodically. There's a real challenge though: I'm getting less and less knowledgeable about the details of my own code, so it's hard to fact-check everything all the time.

Anyway, for now we're assisting to either outdated Docs (Coding Agents often don't even look at them), or to over-bloated ones (the slop is not just in the code). We should probably still find a balance between human readable docs (e.g. README.md) and LLM-tailored ones (e.g. llms.txt)

replace documentation for an agent/chatbot accessing a RAG with the collection of requirements/design docs plus the code repository. I have been doing a POC at my day job and it works surprisingly well even with SLMs ( Gemma3 4B, i smy current favourite )