grounded-document

Phase 6 — DOCUMENT: Leave the Client in Control

A solution is not delivered until the client has everything needed to understand, operate, and evolve it. Deliver knowledge, not just software. All documents go to the project folder in editable formats the client owns.

The Delivery Package

1. Final Requirements Document — plain-English record of what was built and why (reflects reality, not the original plan).
2. Test Suite — permanent verification record for future changes.
3. Known Limitations Document — honest account of edge cases and boundaries. No known issue may be omitted.
4. Maintenance & Evolution Guide — how to operate, modify, and extend the system, written for the client's level of technical sophistication.
5. Architecture Overview — plain-English description of how the system is structured.
6. Handover record — ownership of code, data, credentials, and infrastructure.

Rules

• The client must be able to leave: the package must be sufficient for independent operation.
• Leave no black boxes — every part is explainable in plain English.
• Document what the system cannot do as carefully as what it can.

Gate E

Delivery is complete when the full package is handed over and the client can operate independently.