Observability and Run Events
Producing the operational signal that feeds back into the foundation.
A program that cannot observe itself cannot learn from itself. This area captures what live operation reveals, interprets it, and feeds the interpretation back into the foundation so specifications can evolve.
Start here
Core tasks
Event specification
Define what events each artifact emits and in what form.
Signal capture
Collect events into a queryable store where they can be analyzed.
Baseline establishment
Know what normal looks like, so that abnormal can be detected.
Anomaly detection
Identify signal patterns that indicate issues before those issues become incidents.
Feedback distribution
Route operational signal to the roles whose decisions are affected by it.
From knowing to running
Knowing SPEED and running it are two different things. When you're ready to practice the methodology inside a program that runs it, the implementor path is where you begin.
Begin the implementor path