At go-liveDocumentation captures what. People carry why.
Every program leaves design documents, configuration workbooks and runbooks. They record what the system does. The reasons behind it stay with the people who were in the room: why a rate was modeled with an override, or why an interface tolerates a duplicate record.
Then go-live passes, the program winds down, and the team that built the system disperses over a short window.

