Operational Runbooks

Runbooks turn preservation knowledge into repeatable operations. Every execution must name the baseline/artifact IDs and retain sanitized evidence.

Runbook	Use
Clean Installation	Generate a server/client working environment from preserved inputs.
Upgrade and Rollback	Change a pinned revision without losing the known-good state.
Database Backup and Restore	Protect and recover schema/state around destructive operations.
Client Working Copy	Generate a sanitized runnable client from an immutable snapshot.
Incident Recovery	Respond to corruption, data loss, compromise, or accidental exposure.
Forgejo Recovery	Recover repositories, wiki, issues, attachments, LFS, and permissions.

Execution record

Every run records operator, date/time, baseline ID, host/environment, input hashes, commands/tool versions, result, output/log locations, deviations, and follow-up issue. Secrets and restricted bytes never enter a public record.