Hserver Failure Notes: Production Acceptance · intermediate
A Post-Deploy Inventory Snapshot Is Forensic Evidence
Recording containers, ports and revisions after deployment gives future incident response a known-good comparison point.
The deployment runbook captures fresh inventory before and after major changes and stores timestamped snapshots alongside the infrastructure documentation. The first production deployment produced a live inventory snapshot after OTA and Operations stacks were verified. That file became more than documentation; it captured what the accepted host actually looked like at a specific point. Without a baseline, later operators have to infer whether a port, container or network is new, missing or intentionally changed.
Baselining is a standard incident-response technique. Diffing known-good state against current state is faster than debugging an undocumented environment from first principles.
Automate safe inventory collection, keep secrets out of snapshots, and record the Git revision so runtime evidence can be correlated with desired state. The concrete hserver evidence is commit 2aead37, so this note is tied to an actual production change rather than a hypothetical failure.