@ceejbot I believe strongly in "literate infrastructure design" though. The build/config turnover-to-operations templates I pushed onto my teams had specific sections for narrative descriptions of the system.
"This is the grouping of server types, real or virtual, their common affinities, and any known damage propagation vectors."
"This is the journey of a packet from end-user to DB and back, port by port."
"Here's an order, from user search to cart to checkout to card approval/tax to ERP"