Technical severity is measured by impact on systems. Downtime, data loss, user reach, failure radius.

Political severity is measured by exposure. Who noticed. Who is affected. Who has to be told, and how quickly.

The two scales rarely align. A silent data corruption in a back-end pipeline may rank low on the political scale because nobody visible is complaining. A cosmetic bug on an executive dashboard may rank high because the wrong person saw it first.

The operator triages by the technical scale because that is where actual risk lives. The operator is judged by the political scale because that is where attention lives. The same incident carries two severity labels simultaneously, and the distance between them is almost never discussed openly (FN-0005).

Implication:

Operations inside a multi-audience project is not a single priority queue. It is two parallel queues that the operator reconciles in real time.

The gap between technical and political severity is itself a risk signal. Where the two scales diverge most, communication between operators and stakeholders is the weakest, and the next incident will be misread by somebody.

Part of the Field Notes series documenting operational patterns observed in real-world platform architectures.