A.6.RSIR:4 - Solution

Use A.6.RSIR as a first-level recovery move. RSIRRepairNote is optional working support, not a required record, schema, or publication layout. Omit every branch that is not current. The ordinary path may stop after projectConcern, recoveredEntityOfConcernOrClaimKind, selectedSubjectPatternLocator, and one result stated as retainedSourceLabelUse, blockedOverread, or nextAdmissibleUse. The PatternID is only a locator for applicable defining, constraining, or testing content.

RSIRRepairNote (optional working support; keep only current lines):
  projectConcern:
  recoveredEntityOfConcernOrClaimKind:
  selectedSubjectPatternLocator?: PatternID used only as a locator
  retainedSourceLabelUse?:
  blockedOverread?:
  nextAdmissibleUse?:
  encounteredWording?:
  currentUse?:
  directParticipantMeaningAndActualParticipant?:
  relationDeclaration?:
  assertionOrDescriptionDesignation?:
  operationDeclaration?:
  exactOperationApplicationAndBinding?:
  representationUseAndCorrespondence?:
  neighboringCandidateValues?:
  stopCondition?:

When the optional note is used, it is complete when the current object or claim kind is clear enough to apply the subject pattern, keep ordinary prose, keep quote-only wording, or stop the stronger claim. No unused branch is filled for completeness.

A.6.RSIR:4.1 - Recovery order

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.
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.
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.
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.
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.
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.

A.6.RSIR:4.2 - Subject pattern selection

Recovered object or claim kind	Apply this rule or pattern family	RSIR boundary
direct relation wording	`A.6.P` for recovery, then the rule that defines or tests the direct relation; use `A.6.REL` only when a receiving claim needs explicit occurrence identity or reference	RSIR stops when that direct rule is selected. An ordinary readable assertion may stop before explicit occurrence individuation or identifier assignment.
direct relation-participant meaning or actual participant	the direct relation pattern; add `A.6.5` only if a receiving use needs a reusable typed declaration	State the participant meaning and actual participant directly. Neither one is a `SlotKind`, `SlotSpec`, designation, operation binding, or representation position.
reusable relation-declaration slot, field, parameter, argument, or endpoint	`A.6.5` for one complete `SlotSpec` inside one exact `RelationSignature`, with `A.6.0` for the containing signature	The `SlotKind` is declaration-local and corresponds to one already recovered participant meaning; the declaration does not make the relation obtain.
assertion- or description-side participant designation	`C.2.1` for episteme identity and content; the direct assertion, evaluation, evidence-use, or description family for predicate, polarity, and use; `A.6.5` only when a compatible current `SlotSpec` types the designation	An ordinary assertion may name actual participants directly. A typed designation remains episteme content: it is neither the actual participant nor evidence that the direct predicate obtains.
operation argument or result declaration	`A.6.1` and the exact mechanism edition and operation declaration	`ArgumentDeclaration` and `ResultDeclaration` are declaration content. Do not reuse relation `SlotSpec` vocabulary for them.
exact operation application or declaration-local argument or result binding	`A.6.1` and the exact mechanism edition and operation declaration	Identify the application occurrence independently; assert a binding only for the exact application and actual bound value under the declared predicate. Do not admit public `OperationApplication`, a universal input/output/result relation, or infer production, a produced entity, result episteme, evidence, or work from a result binding.
tuple component, formula or method-call argument, graph-edge endpoint, schema field, or other representation position	`C.29` or the exact representation or publication pattern	Keep the position inside that representation and state explicit correspondence when an FPF claim consumes it; do not turn it into a relation participant, declaration, or actual binding by form.
signature or law-governed declaration	`A.6.0`; use `A.6.5` only for `SlotSpec` declarations inside a `RelationSignature`, and `A.6.1` for operation argument and result declarations	Do not put mechanisms, methods, work, evidence, actual participants, operation applications or bindings, or representation positions into signature identity-bearing content.
bare role already recovered as an exact local system-role kind — RSIR non-use	Apply `E.10.ROLE` once, then `A.2`, `C.3`, and the description or naming rules when their use is current	Do not apply RSIR. A system-role kind classifies entities already admitted as systems. It is not a `SlotKind`, assignment, capability, Method, status, or representation position.
bare role already recovered as a system-role assignment — RSIR non-use	Apply `E.10.ROLE` once, then `A.2.1`; when precise performed Work is claimed, recover each exact actual performer through A.13 and let A.15.1 independently admit the dated Work, adding F.6 only when the claim expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; apply `A.6.5` only for a reusable species declaration	Do not apply RSIR. Recover the assignment occurrence and its declared `U.SystemRoleAssignment` species. The species defines the participant meanings; the occurrence supplies the holder System, assigned local kind, and any other participants. Taxonomy and scheme epistemes are not generic participants. Assignment extent follows uninterrupted predicate truth; a receiving assertion or use names any interpretation edition it depends on.
state of an assignment to a system role, or structure of relations among system-role kinds	`A.2.5`, `A.2.7`	Recover `SystemRoleAssignmentStateRelation` or `SystemRoleKindRelationStructure`; infer neither from ordinary label chains.
system-role-kind description or durable system-role-kind name	`F.4`, `F.5`, `F.18`, and `F.17` when public or cross-context reuse is current	Name the exact local kind or its description episteme. Do not hide assignment, capability, Method, or Work inside the name.
independently encountered system-role enactment or assignment wording	When precise performed Work is current, apply A.13 first and let A.15.1 independently admit the dated Work; apply A.2.1 and F.6 afterward only when the claim expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment. If the starting cue was bare role, apply `E.10.ROLE` once and do not apply RSIR after it selects this branch	Recover the exact actual performer `S : U.System` and dated `W : U.Work`. For an attribution-bearing claim, also recover the exact obtaining `RA : U.SystemRoleAssignment` and use `performedUnderAssignment(W, RA)` or the Plain sentence `S performed W under RA`; F.6 identifies neither S nor RA, and missing or failed F.6 leaves W intact. Create no second enactment object beside Work and assignment.
module interface or architecture interface	`A.6.M` for module-interface claims; `C.30`, `C.30.ASV`, `C.30.AD`, or `C.30.TFS-REL` for architecture-of, structural-view, architecture-description, or transformation-flow-structure claims; `A.6.0` plus `A.6.5` only for a reusable `RelationSignature` and its complete `SlotSpec`s; `C.29` or the exact representation pattern for interface diagrams or schema positions and their correspondence	Do not create generic `U.Interface`.
Markov blanket, Markov border, computational boundary, boundary leak, or active-inference boundary	Recover the current claim before choosing a pattern: accepted local Markov dynamics (`A.3.3`), mathematical or probabilistic lens (`C.29`, sometimes `C.26`), viability or measure-model-act envelope (`C.26.3`), holon delimitation or boundary crossing (`A.1` plus the direct governing relation pattern), relation precision (`A.6.P` after a relation-bearing case is recovered), reusable `RelationSignature` and `SlotSpec` declaration (`A.6.0`, `A.6.5`) or representation position and correspondence (`C.29` or the exact representation pattern), module-interface or interface-specification claim (`A.6.M`), functional port or functional element (`A.6.F`), physical component (`A.14`, `C.13`, `B.3.5`), boundary description or publication (`C.2.1` for claim-bearing description content, `C.30.AD` for architecture descriptions, `E.17` for reader-facing publication of an already accepted account), agency-threshold claim (`A.13` for the agency criterion, `C.16` when a value must be made interpretable as a measurement, `A.19` when a declared `CharacteristicSpace` or reusable by-value `CharacteristicSpacePredicate` over it is the current object), or boundary-package statement classification (`A.6.B`) only when L, A, D, or E classification is the recovered object.	Do not create `U.MarkovBlanket`, generic `U.Boundary`, generic `U.Interface`, or binary `U.Agent`; do not treat a statistical separation, interface, interface module, physical component, description, and boundary-package classification as the same object.
functional port or functional structure	`A.6.F`, `A.3.4`, `E.18`, `C.30.TFS-REL`	Do not equate port, function, module interface, and signature by vocabulary alone.
API, protocol, connector, service-access wording	Recover the governed object first: `E.17` for API or interface-description publication; `A.6.0` and `A.6.5` for a reusable `RelationSignature` and its `SlotSpec`s; `C.29` or the pattern that defines the exact API-description claim for schema or representation positions and explicit correspondence; `A.6.M` for module-interface claims; `A.6.C` only when recovered protocol, service-term, SLA, or agreement-like wording bundles promise, utterance or publication, governance, Work or consequence, or evidence claims; `A.6.P:4.11a` when service or service-access wording still hides its exact referent or direct relation; `A.6.B` only for L, A, D, or E statement classification inside a boundary package.	API may be description, protocol episteme, exact service or access referent or direct relation, signature, publication, module interface, representation, or boundary-package statement classification.
capability	`A.2.2`; method, work, evaluation, or gate patterns only when they use an explicit capability criterion	Role labels and interface labels do not establish or demonstrate capability.
affordance or action invitation	`A.6.A`	Do not rename affordance as role, interface, or capability until its exact predicate and current subject assertion establish that value.
method, method description, work plan, or dated work	`A.3.1`, `A.3.2`, `A.15`, `A.15.1`, `A.15.2`	Method, description, plan, and work are distinct even when source wording says process.
function or functional wording	`A.6.F`	Function-like wording can point to several patterns; `A.6.F` governs that recovery.
concern, interest, viewpoint, problem, or characteristic-space selection	`A.7` for EntityOfConcern and description distinction; `C.22` or `C.22.2` for problem-card claims; `E.17.0` or `E.17.2` for viewpoint or view claims; `F.4` or `F.18` for system-role-kind-description or naming cases; `A.19` or `E.21` for characteristic-space cases	Do not mint generic `U.Concern` or `U.Interest` by wording alone.
publication, description, declarative representation, source wording	`C.2.1`, `E.17`, `C.2.P.DR`, `E.10`, `E.10.ARCH`	Do not let description or publication use displace the EntityOfConcern selected by the project concern.

A.6.RSIR:4.2.1 - Relation-defined wording dispatch

When wording derives a qualification, status, or category from participation in a relation, recover the object needed by the next use before naming it:

If the claim concerns an actual entity participating under one named relation-participant meaning, state the direct relation, that meaning, and the actual participant. The participant retains its direct kind.
If reusable typed declaration is current, use A.6.5 for the corresponding SlotSpec inside one exact RelationSignature. Its SlotKind is declaration-local and neither is the participant nor makes the relation obtain.
If an episteme asserts, evaluates, or describes the participation, C.2.1 governs the 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 participant designation’s ValueKind and refMode discipline; without reusable declaration, the assertion may designate the actual participants directly.
If repeated local quantification over such actual participants is current, use C.3 and C.3.1 for the local U.Kind, membership rule, and extent rule. Neither the participant-meaning label nor the declaration-local SlotKind admits that kind.
If the source exposes a tuple component, argument, edge endpoint, schema field, or other representation position, keep it under C.29 or the exact representation pattern and state an explicit correspondence before an FPF claim consumes it. A value shown at that position establishes neither actual participation nor relation obtaining.

For parameter, argument, or result wording, separately recover the A.6.1 declaration content, one independently identified exact operation application and any obtaining declaration-local binding, and the selected representation position. Open the binding only when the actual bound value matters to a receiving claim. Neither the declaration nor representation syntax establishes the binding; a result binding is distinct from production, a produced entity, a result episteme, evidence, and work.

When a receiving use compares or constrains a whole organization of relation occurrences, A.22 may govern a selected U.Structure. One actual participant, corresponding SlotSpec or designation, operation binding, or representation position does not by itself establish such a structure.

A.6.RSIR:4.3 - Replacement candidate rule

Do not replace one umbrella with another. The minimum admissible repair candidate names:

the current object or claim kind;
the subject pattern;
one result current for the receiving use: a retained reduced-use source label, a blocked stronger reading, or the next admissible use.

Name a direct relation, claim-bearing episteme, declaration-local SlotSpec, A.6.1 operation declaration or actual application binding, or representation correspondence only when that exact object is current for the receiving use. Do not fill an unused branch or require both a retained source-label use and a blocked overread. If the minimum cannot be named, leave the phrase in quote-only or reduced-use form and record the blocker.

A.6.RSIR:4.4 - Reduced-use source labels

Reduced-use labels are allowed. They are not failures. A source label remains reduced-use when it helps readers find or recognize the case but does not carry FPF-governed content.

Examples:

“API role” can remain a quoted source phrase while the branch is selected with E.10.ROLE. The repaired claim may be an API description, an exact provider system-role assignment, a declaration or representation position, a promise-content episteme under A.2.3, an independently obtaining commitment under A.2.8, PromiseContentUse, a delivery or acceptance relation, another named direct relation, or an interface specification.
“parameter” can remain ordinary prose while a complete SlotSpec is named only for a current reusable relation declaration, an operation ArgumentDeclaration or ResultDeclaration and any exact application binding stay under A.6.1, and a method-call, formula, or other representation position stays under C.29 or its exact representation pattern.
“function” can remain ordinary engineering language when no architecture, capability, method, work, mathematical, quality, or module claim depends on it.

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.