Small systems, clear evidence.

Scope

The notes cover the operational layer that tends to be missed by a quick setup guide: which process owns a socket, whether a saved firewall matches the live ruleset, whether a certificate reload reached the public endpoint, and whether a backup can be opened without the production application.

This is not product documentation or a company status page. Commands are examples for a generic host. Names, addresses, ports, and credentials from live systems do not belong in published notes.

Editorial rules

• ObserveRecord live state before interpreting a configuration file.
• ConstrainName the transport, bind address, process, and failure boundary.
• RecoverPrepare a rollback before taking the path that might close remote access.
• VerifyTest the application from the side where a real client will use it.

Using the notes

Read a command before running it. Paths, service names, interfaces, and package behavior vary between distributions. The useful part is the order of checks and the evidence they preserve, not blind command reuse.