Most AI vendors treat documentation as a nice-to-have that ships last and gets abandoned first. We treat it as a deliverable. If your team can't operate the system without us, we haven't finished the job. Every engagement comes with written documentation at four levels: strategic, architectural, operational, and reference.
What's documented on every project
Architecture
System diagrams, data flow, component responsibilities, deployment topology, dependency graph. Readable by both engineers and executives.
Runbooks
"What to do when X breaks" — step-by-step playbooks for the 20 most likely failure modes. No guessing at 2 AM.
API reference
Every endpoint, every parameter, every response shape. OpenAPI spec + Markdown + working curl examples.
Decision log
Why we chose this model, why we rejected that architecture, what the tradeoffs were. So your team can revisit with context.
Public documentation
We're currently building out our public-facing knowledge base covering:
- Fine-tuning guides for Llama, Mistral, and Qwen model families
- Self-hosted LLM deployment guides (Ollama, vLLM, TGI)
- n8n workflow automation patterns for common business use cases
- RAG architecture patterns — when to use what, and why
- Cost calculators for on-prem vs. API at various scales
- Compliance checklists (GDPR, HIPAA, DPDP, SOC 2) for AI systems
Expected to launch Q3 2026. Want early access? Email us.
For existing clients
If you're an existing Adorbis client looking for documentation on your deployment, check the shared Notion or Git repository we set up during your engagement. Can't find what you need? Email info@adorbistech.com and reference your project code — we'll route you to the right engineer.
Documentation standards we follow
- Written first, generated second — architecture docs are human-written before any auto-generated API reference
- Versioned with the code — docs live in the same repo as the software they describe
- Tested — every code example in our docs runs as part of CI; if an example breaks, the build fails
- Reviewed by a non-author — at least one engineer who didn't write the doc has to sign off on it