A.1.SCR:4.2 - Take the subject-pattern exit first
Before testing systemhood, ask whether the current decision already concerns one of these objects:
| Current object | Subject pattern or exit |
|---|---|
| Holder-dependent capability | A.2.2 |
| Local system-role kind or obtaining system-role assignment | A.2 and A.2.1 |
| Reusable way of doing or its description | A.3.1 and A.3.2 |
| Intended work | A.15.2 U.WorkPlan |
| Dated performed occurrence | A.15.1 U.Work |
| Actual bounded change | A.3.4 and the exact transformation pattern |
| Claim-bearing model, rule, report, code, or other episteme | C.2.1 |
| Selected structure or transformation-flow structure | A.22 or E.18 |
| Promise, commitment, speech act, or permission result | A.2.3, A.2.8, A.2.9, or A.2.8.PER |
| Service/access referent, status, evidence, evaluation, delivery, acceptance, or other relation | A.6.P §4.11a and then the exact subject pattern |
If this result answers the decision, stop here. Name the object, its subject pattern, and what you can now do. Do not apply A.1 as a recurring project ritual.
If a needed relation has no current governor, state the exact participants and blocked receiving use, return missing-governor[...], and continue under A.6.RCD. Do not substitute relatedTo, a graph edge, or a local bundle.