F.12:2 - Problem frame

1. Plan ≠ proof. A diagram or playbook is treated as evidence that its promise was met.
2. Output ≠ outcome. Commands or setpoints are mistaken for the consumer-relevant result.
3. Word ≠ measure. Availability, latency, or incident is used without recovering its exact local meaning and characteristic.
4. Proxy by assumption. Monitor output is called a proxy before asking whether the observation and measurement model already concern the promised characteristic directly; when they do not, the needed indicator relation has no defining or testing rule.
5. Evaluation disappears. A verdict appears without evaluation Work, an enacted evaluation Method, exact operation inputs, or a result binding.
6. Status families collapse. Satisfied, Violated, and Inconclusive are treated as one universal scale even though the first two are RequirementStatus values and the third is an EvidenceStatus value unless an exact local result scale says otherwise.