Phase 2 · Continuity
SOTE must outlast its builders.
This dashboard shows whether the current infrastructure record contains the organizational knowledge required for another operator to understand, operate, recover, and eventually rebuild SOTE.
Continuity posture
Each rack is measured against the complete ten-control SOTE Definition of Operational. These indicators describe documentation and continuity maturity, not uptime or security certification.
Continuity data could not be loaded. The canonical continuity standard remains in GitHub.
Definition of Operational
Ten-control matrix
Operational means more than “it works.” Inventory, ownership, documentation, recovery, discoverability, and independent validation all matter.
Loading continuity matrix…
Continuity debt
What still depends on future work?
Pending and developing controls are visible so continuity defects can become missions, issues, documentation revisions, or validation work instead of remaining hidden in somebody's memory.
Loading continuity defects…
Action layer
Which continuity defects already have canonical work?
The work queue is now generated automatically from open SOTE-framework issues whose titles begin with CONTINUITY |. ProfessorSneaker does not maintain a second task list.
Loading continuity work…
What counts as complete?
A component should be inventoried, located, connected, addressed, reproducibly configured, documented, recoverable, role-owned, discoverable, and independently validated as applicable. The goal is not green boxes. The goal is an environment that a new operator can inherit without needing the original builder standing beside them.
See the runbooks, recovery gaps, validation records, and current continuity work →
Public-safe projection
This dashboard intentionally omits credentials, management addresses, sensitive topology, firewall details, and privileged access paths. ProfessorSneaker makes continuity visible without making infrastructure accessible.