A.6.RSIR:4.1 - Recovery order

1. Recover the project concern. Say what the project is trying to do: assign work responsibility, declare a signature, check an interface, compare functions, name a port, use evidence, assert status, describe a method, or make another claim.
2. Recover the current object or claim kind. Decide whether the wording points to a direct relation or participant meaning, an actual participant, a reusable RelationSignature or SlotSpec, an assertion- or description-side participant designation, an A.6.1 argument or result declaration, one exact operation application and actual binding, a representation position and correspondence, a signature, interface claim, system-role kind, system-role assignment, system-role-kind description, port, boundary claim bundle, capability, affordance, Method, function, concern, interest, publication, source label, or ordinary prose.
3. Name the applicable rule. Use the table in A.6.RSIR:4.2 only until the definition, constraint, or test needed by the current question is clear. Record its PatternID only as a locator.
4. Separate direct participation, reusable declaration, and assertion or description. Use A.6.5 only when one complete SlotSpec in one exact RelationSignature is current. The direct relation pattern defines or constrains participant meaning, actual participants, obtaining, and occurrence identity. If an assertion or description episteme designates a participant, C.2.1 governs that episteme’s identity and content, while the direct assertion, evaluation, evidence-use, or description family governs the exact predicate, polarity, or use relation. When a compatible SlotSpec is current, A.6.5 governs the designation’s ValueKind and refMode discipline; an ordinary assertion may instead name actual participants directly without opening a reusable RelationSignature.
5. Separate operation declaration, actual application and binding, and representation. Use A.6.1 for declaration-local ArgumentDeclaration and ResultDeclaration content. Open an actual operation-application binding only after one exact application has been independently identified and its actual bound value matters to a receiving claim. Keep a method-call, formula, tuple, edge, or schema place under C.29 or its exact representation pattern and state correspondence separately.
6. Keep the source label reduced-use when no governed claim is current. A word can remain a cue, quotation, title, or local shorthand without being admitted as FPF-governed vocabulary.

Use Tech position only for a place in a selected representation, such as a tuple component, formula or method-call argument, graph-edge endpoint, or schema field. Until an explicit correspondence is stated, that position is neither a relation-participant meaning, actual participant, SlotKind, SlotSpec, nor evidence that the direct relation obtains.