The Observability Tower
You are here · Protocol 39
Shift briefing · Observability Tower
An operation failed but the team cannot tell where. Existing logs contain no correlation IDs and one verbose log includes unnecessary user data.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Instrument a system so events, metrics, and traces reveal failures without leaking sensitive data.
- Logs
- metrics
- traces
- correlation IDs
- alerts
- privacy-safe telemetry
Construct Build a working system and prove that it holds.
The facility for this shift
3 rooms, 5 stations, two hands.
- 01Instrumentation FloorEvent logger · Metrics panel
- 02Trace HallTrace rail · Redaction filter
- 03Alert RoomAlert console
Compromised Signal · sealed
Something in this shift will change, and the briefing will not tell you what. You find it from the evidence, or your after-action review shows you where it was.
How the shift is assessed
3 criteria · 0 to 6
Scored from what you did: the evidence you checked, the stations you operated, the artifacts you produced and the gates you passed. The criteria are revealed in your after-action review, not before.
Capabilities evidenced
- PerceptionNotices relevant signals, discrepancies, provenance, and system state.In 13 of 48
- ReliabilityTests, reproduces, validates, recovers, and produces consistent outcomes.In 39 of 48
- ResponsibilityProtects privacy, limits permissions, documents decisions, and blocks unsafe releases.In 23 of 48
Chamber III · Action Chamber
Build only what you can stand behind, and stop a release that is not safe.
Construct, integrate, evaluate, debug, secure, deploy, observe and responsibly operate AI-enabled systems.
Play Protocol 39 in first person, with the clock running.