SYSE.17:8 - Common Failures and Repairs
These recurring failures hide a bearer, relation, claim status, or decision contribution:
| Failure | Repair |
|---|---|
| Only purchasers, owners, formal roles, or influential participants appear | Trace the proposed alternative or change outward and challenge the current boundary. |
| An affected-System claim is read as a project role | State the System and consequence; add a role or assignment only when that separate relation obtains. |
| A System is ignored because it cannot object | Discover bearers from possible consequences, whether or not they can object or are represented in project governance. |
| A diagram arrow becomes an actual relation | Keep it as a modal path claim until the represented relation occurrences and conditions are supported. |
| Scale labels become a System hierarchy | Recover actual Systems and the relations used to organize them; a scale label is only a search cue. |
| Every mentioned party is called affected | Require a decision-relevant possible or observed change under stated conditions. |
| Consequence list becomes an ethical verdict | Send actual value conflicts and authority questions to their governing practices. |
| Simulation becomes causal proof | Use C.28 and retain the narrower supported claim. |
| Inquiry produces no usable result until definitive research exists | Use a bounded expert estimate or uncertainty claim when it improves a reversible choice. |
| Official visibility becomes prevalence | Separate source status, enacted practice, observed consequence, and expert estimate. |