Initialize ops repository

This commit is contained in:
vaultsovereign
2025-12-17 15:13:19 +00:00
commit f375d21a9e
51 changed files with 590 additions and 0 deletions

View File

@@ -0,0 +1 @@

View File

@@ -0,0 +1,13 @@
# Panic Day
This folder contains rebuild-from-zero drills.
Rule: each drill must be runnable with only this repo, cold storage, and the vault keys.
Suggested drills:
- Rebuild `op-core-vm` from a clean base image.
- Restore this repo, validate integrity, and re-establish authority boundary.
- Rotate critical credentials and invalidate all prior device leases.
- Restore one representative backup set end-to-end and record proof.

View File

@@ -0,0 +1 @@

View File

@@ -0,0 +1,4 @@
# Provision
Create and bootstrap new nodes/services in a repeatable way.

View File

@@ -0,0 +1 @@

View File

@@ -0,0 +1,4 @@
# Incident
Containment, diagnosis, recovery, and postmortem procedures.

View File

@@ -0,0 +1 @@

View File

@@ -0,0 +1,4 @@
# Decommission
Safe teardown, revocation, and evidence capture for retired systems.

15
50-runbooks/README.md Normal file
View File

@@ -0,0 +1,15 @@
# Runbooks
Runbooks are executable documents: written to be followed under pressure.
Minimum required sections:
- Purpose
- Preconditions
- Steps (exact commands)
- Validation (how you know it worked)
- Rollback / abort criteria
- Evidence (what to record)
Use `ops/50-runbooks/_template.md` for new runbooks.

35
50-runbooks/_template.md Normal file
View File

@@ -0,0 +1,35 @@
# Runbook: <title>
## Purpose
What this runbook does and when to use it.
## Preconditions
- Access/role required:
- Systems required:
- Expected safe state:
- Time estimate:
## Steps
1.
2.
3.
## Validation
How to prove the procedure succeeded (commands + expected output).
## Rollback / Abort
What to do if validation fails, and when to stop.
## Evidence
What you record (timestamps, change IDs, logs, screenshots).
## Notes
Gotchas, dependencies, links.