Release and recovery

Use this path when the question is not only “does it work?” but also “what evidence lets us replace it or recover it?” The notes keep artifact boundaries, rollback windows, and routine maintenance visible.

A strong default path with quieter fallback and recovery branches.

Reliable defaults beat clever recovery

Keep the common path explicit, observable, and safe to repeat before adding recovery branches.

A service inside a bounded and rate-limited restart loop.

Restart policies need a rate limit

Use an explicit service type, bounded restart behavior, and start-rate limits that leave evidence in the journal.

A compact service core connected to DNS, TLS, files, and logs.

The advantage of small systems

Small does not mean unfinished; it means each boundary has a clear job and a visible owner.