Documentation
What ships with the system
Every build is handed over documented. This is the standard set — a project can need more, never less.
Architecture
How the pieces fit: services, data stores, and every boundary the system talks across. Drawn as it is built, not reconstructed afterwards.
Data contracts
The shape of what moves between systems — message formats, field meanings, and what happens when a field is missing.
Runbook
How to start it, stop it, and what to do when it misbehaves at 2am. Written for the person who will operate it, not for us.
Decision log
Why it was built this way and what the alternatives cost. The part that saves the most time when someone new picks it up in two years.
Environment & deploy
What it needs to run, how it is configured, and the exact steps from a clean machine to a running system.
Handover session
Time with your team walking the code, not a PDF dropped in a shared drive.
Documentation for a system we have not built yet
Per-project documentation lives with the client, not here. If you want to see the shape of it before committing, ask and we will walk you through a real handover pack.