A.6.RSIR:4.5 - Shortcut Cost and Reopen Condition

A.6.RSIR is a deliberately weak first-level recovery move. The baseline is full use of the subject pattern: A.6.P for relation repair, A.6.5 only for reusable RelationSignature SlotSpec discipline and compatible participant-designation typing, C.2.1 plus the direct claim family for assertion or description content, A.6.1 for operation declarations and any exact application binding, C.29 or the pattern that defines the exact representation claim for positions and correspondence, A.2, C.3, and A.2.1 for system-role kinds and system-role assignments after that branch is selected with E.10.ROLE, A.6.M for module-interface, A.6.F for function-like repair, or the evidence, status, publication, architecture, method, work, gate, or problem pattern named by value.

The saved effort is that a practitioner does not run several full patterns before knowing which one is current. The loss budget is narrow: RSIR may select a direct pattern, preserve a reduced-use source label, or record a blocker. It may not decide the system-role kind, system-role assignment, signature, operation application or binding, evidence-use relation, status assertion, exact service or access relation, architecture description, or Method relation that belongs to the selected pattern.

Reopen RSIR when the selected pattern shows that the source phrase carried more than one governed object, the object kind was selected too early, a needed slot distinction was missed, or evidence, status, publication, gate, method, work, architecture, capability, or concern claims were folded into one label. The reopened repair splits the phrase into multiple governed values or keeps the excess wording reduced-use.