Six months ago, I started building TaterTOS64, an x86_64 kernel. As any systems dev knows, once you hit the 10,000-line mark across a mix of C, Assembly, and Linker scripts, your brain starts to leak. I needed a way to document the architectural "why"—how the interrupt vectors hand off to the scheduler, how the paging logic relates to the physical memory map.
Naturally, I tried the modern approach: I fed the code to LLMs.
The Result was a Disaster.
Generic "AI Doc" tools failed me in three specific ways:
The Context Amnesia: They'd understand a single .c file but completely hallucinate the #include chain. They had no idea where the paging.h constants were actually defined in my repo structure.
