The aviation guide.
Aviation manuals exist because a pilot’s memory, however good, is not a certifiable safety system. Every procedure, from engine start to emergency descent, is written down, version-controlled, and updated the moment a better way is found or a new failure mode is discovered somewhere in the world. This is the actual definition of a manual: not a reference nobody reads, but a living document the entire operation is legally and practically built around.
The parallel to software is direct and deliberate. A runbook telling an on-call engineer exactly what to check first during an outage, in what order, is doing the same job a pilot’s emergency checklist does: replacing panic-driven improvisation with a pre-decided sequence, written by someone calm, for use by someone who will not be calm when they need it. The manual is not there for the easy day. It is there for the day everything is going wrong at once.
The full piloting manual for this site is still being written chapter by chapter, the same way this portfolio builds everything: shipped once it is real, not before a single page is ready. The philosophy behind it, cloud-native systems built for teams who cannot afford downtime, already runs on the Avionions page.