Hi everyone,
I wanted to share a personal experience with using LLMs on a long-running technical project, particularly when accuracy matters more than the amount of content produced.
My interest in Tor started during my bachelor's thesis and continued over several years. Eventually, I decided to turn that material into a free, open-source educational project called Anatomia di Tor.
During development, I worked extensively with Claude Code, including Opus 4.8 and Opus 5.5 in the later stages, alongside GPT-6.
The project now includes a technical book about Tor's internal protocols and 20 hands-on laboratories using Python, Docker, Chutney, and a private Tor network.
What I found particularly challenging was maintaining technical consistency across a large body of material.
LLMs can produce convincing explanations of complex protocols, but that doesn't necessarily mean those explanations are correct.
Throughout the process, I had to deal with inconsistent terminology, translation errors, technical inaccuracies, and the difficulty of keeping multiple chapters and laboratory implementations aligned.
The most useful approach was to treat AI-generated material as something that needed verification rather than something ready for publication.
For the practical components, this meant running actual tests in a controlled environment instead of relying exclusively on the models' assessments.
I also want to be transparent about authorship: AI contributed substantially to drafting the book, code, and translations. I directed the project, made editorial decisions, reviewed the outputs, and coordinated testing and corrections. Independent expert review is still missing, and I know that errors may remain.
I've made the complete project publicly available, including the source files and laboratories:
https://github.com/aleff-github/onion-routing-anatomy
I'm sharing this as a practical example of what working with LLMs on a larger technical project can involve, including the limitations.
For those using advanced models in research, software engineering, or technical documentation: how do you manage consistency and independent verification across large, AI-assisted projects?
I'd be interested in learning about other approaches.