Context
An infrastructure project is easier to sustain when the operating team understands how it was built and how to change it. Plan that handover during discovery.
Document architecture decisions, access ownership and essential operating procedures. Keep instructions close to the systems they describe, and identify who maintains them.
Walk through a representative deployment, an alert investigation and a restore exercise where scope permits. Practical examples reveal assumptions that a document alone may miss.
Agree the support boundary. The team should know which responsibilities belong to the provider, which belong to the application team and how an issue is escalated.