Most system confusion comes from not being able to name what the system is actually doing.
Once those four things are named — purpose, repeated action, governing rules, and failure point — the system becomes legible enough to diagnose.
This scan applies that lens to any system you run or operate inside. Answer four questions. The scan surfaces a structural read. If the pattern appears structural, send the answers as your brief.
This is not a quiz or a score. It is a structured method for locating where a recurring failure is actually sitting.
Not what it claims. What it actually exists to do.
The primitive — the smallest unit of real work. Every system repeats something. Point at it.
As they exist in practice, not in policy documents.
What breaks first, who notices, and who absorbs the cost. Failure is clarifying — watch for the workarounds.
Once you answer the four questions, the scan will surface where the rule failure is most likely sitting and what to examine before changing anything.