A.6.RSIR - Relation, Signature, Interface, Role, and Slot Precision Restoration
Type: FPF precision-restoration pattern Status: Stable Normativity: Normative unless marked informative
A.6.RSIR:0 - Use This When
Plain name. Relation-signature-interface-role-slot recovery.
Use this pattern when engineering wording such as role, interface, signature, slot or parameter hides the object or claim needed by the task. For bare claim-bearing role, apply E.10.ROLE once. If it identifies the object and rule or settles ordinary use, proceed with that result. Use RSIR only for a remaining question about direct participation, a reusable declaration, an interface, an operation declaration or binding, or a representation position.
Primary EntityOfConcern. The EntityOfConcern is one encountered use of an ambiguous engineering phrase together with the claim that this use is intended to carry.
RSIR recovers the object, direct relation and participant meaning, actual participant, declaration-local SlotSpec or operation declaration, operation application and binding, assertion- or description-side designation, representation position and correspondence, or claim before selecting its subject pattern. The phrase remains wording in an episteme or in speech; it is not the world-side object, occurrence, value, or relation named by the recovered claim.
The intended reader is an FPF practitioner, author or reviewer repairing an engineering phrase so that its next user can recover the object, rule and action it concerns.
First useful move. Recover the project concern first, then recover the EntityOfConcern or claim kind. As soon as the applicable definition, constraint, or test is clear, apply that rule and stop the RSIR repair. Keep a reduced-use source label only when no governed value is being asserted.
What goes wrong if missed. The same word is used for differently defined objects without saying which claim is meant. For example, interface may denote an API description, reusable signature, functional port, compatibility claim, or module-boundary relation. Bare role may point to a system-role kind, one assignment, direct-relation participation, a declaration-local SlotKind, a representation position, use of an episteme, another object, or ordinary wording. A later reader then cannot recover which relation obtains, which participant is meant, which declaration is current, whether an operation application binds an actual value, or which representation correspondence is intended.
What this buys. The reader gets one recovery move before the subject pattern is applied. The repair preserves useful engineering words while preventing a lexical cue from minting a new root kind or collapsing direct participation, reusable declaration, assertion or description, operation application and binding, and representation correspondence.
Not this pattern when. Do not use A.6.RSIR after the subject pattern is already clear. Do not use it for general relation repair after A.6.P is selected, for slot discipline after A.6.5 is selected, for function-like repair after A.6.F is selected, for module-interface repair after A.6.M is selected, for transformation wording after A.3.4.P is selected, or for publication and description repair after E.17, C.2.1, or C.2.P.DR is selected.
A.6.RSIR:1 - Problem frame
The RSIR cluster sits at a common failure point in FPF texts. A project team sees one word and treats it as if it already selected the ontology:
- bare “role” whose E.10.ROLE branch may be a system-role kind, assignment, direct relation-participant meaning, declaration-local
SlotKind, representation position, evidence use, another object, or ordinary wording; - “interface” in a module relation, functional port, API description, protocol, signature, or publication view;
- “slot”, “field”, “parameter”, or “argument” in wording about an actual relation participant, a
RelationSignaturedeclaration, an A.6.1 argument or result declaration, one actual operation application and bound value, a data, formula, or method-call representation, or ordinary prose; - “signature” in a law-governed declaration, API shape, interface specification, or plain sign-off phrase;
- “function” in architecture, capability, method, work, mathematical modeling, or quality wording.
A.6.RSIR is the first-level recovery pattern for this bounded cluster. It does not decide every neighboring subject ontology. It helps the practitioner recover which object or claim is meant, identify the rule that defines or tests it, and then stop the RSIR repair.
A.6.RSIR:2 - Problem
Misreadings to resolve:
- Lexical cues create shadow kinds. Interface, role, slot, endpoint, and function words become local root kinds because they sound technical.
- Participant, declaration, and representation uses become system roles. A direct relation-participant meaning, declaration-local
SlotKind, argument, field, endpoint, or representation position is renamed as a system-role kind. Evidence-use, transformation, and interface claims then lose their direct relations and patterns. - System-role kinds become declaration or representation labels. A context-local system-role kind is demoted into a SlotKind or source-schema field. Its KindSignature can no longer be recovered, and any separately needed assignment, state or Work claim loses its own basis.
- Signatures absorb implementations. A law-governed
U.Signatureis used as if it were a mechanism, method, work-start gate decision, interface conformance proof, or publication. - Participant, declaration, application, and representation boundaries are skipped. A field or parameter is edited without deciding whether it denotes a direct relation-participant meaning or actual participant, a declaration-local
SlotSpec, an A.6.1 argument or result declaration, one operation application and actual binding, or a position in a selected representation. - Evidence and status uses keep old role grammar. An episteme, standard, report, publication, or badge is said to have a role instead of being used in an evidence-use, source-use, status-use, publication-use, assurance-use, or gate relation.
- Neighboring patterns are copied locally. A pattern repeats negative catalogues such as “not proof, not permission, not gate” instead of recovering the current object and applying the pattern that defines or constrains the claim.
A.6.RSIR:3 - Forces
| Force | Tension |
|---|---|
| Recognition vs ontology | Engineering words are useful entry cues, but FPF use needs the governed object or claim kind. |
| First-level repair vs overreach | The pattern must recover enough to choose the direct pattern without becoming a second ontology for relation, role, interface, capability, method, function, evidence, or status. |
| Declaration and binding precision vs system-role ontology | One direct participant or bound value may itself be a system-role kind, assignment, system, or another entity. A compatible SlotSpec or A.6.1 declaration may type the reusable use, but participant, declaration content, application, binding occurrence, designation, and representation position remain distinct. |
| Interface usefulness vs interface-as-kind collapse | Interface words are often useful, but they may point to several different subject patterns. |
| Minimal rewrite vs precision | Ordinary prose can remain ordinary; claim-bearing prose must name the governed object, direct relation use, declaration, or representation correspondence on which it relies. |
| Source label preservation vs misuse | A source label can remain quote-only or reduced-use, but it cannot silently make work, evidence, assurance, gate, publication, or architecture claims admissible. |
A.6.RSIR:4 - Solution
Recover the project question, the object or claim that answers it, and the applicable rule. State the resulting next action or the condition that prevents it. A short note can retain that result when later use needs it; the RSIRRepairNote described below is working support, not a required form.
A useful RSIRRepairNote contains only the question, recovered meaning and rule, and next action or missing condition. Keep a source label or a blocked stronger interpretation only when it helps recognition or prevents a plausible consequential misreading. No unused branch needs filling.
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 object or claim kind. Decide whether the wording points to a direct relation or participant meaning, an actual participant, a reusable
RelationSignatureorSlotSpec, an assertion- or description-side participant designation, an A.6.1 argument or result declaration, one 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.2only 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.5only when one completeSlotSpecin oneRelationSignatureis 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.1governs that episteme’s identity and content, while the direct assertion, evaluation, evidence-use, or description family governs the predicate, polarity, or use relation. When a compatibleSlotSpecis current,A.6.5governs the designation’sValueKindandrefModediscipline; an ordinary assertion may instead name actual participants directly without opening a reusableRelationSignature. - Separate operation declaration, application and binding from representation. Use A.6.1 for ArgumentDeclaration and ResultDeclaration content. Open an actual binding claim only after identifying the application and the relevant bound value. Interpret a call, formula, tuple, edge or schema position under the conventions for positions in that expression; it represents the declaration or binding without being that object.
- 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 for a place in a selected representation, such as a tuple component, call argument, edge endpoint or schema field. Recover its correspondence through the selected scheme and conventions; state it explicitly when the receiving claim needs that detail. The position remains distinct from the participant, SlotKind or SlotSpec it may represent. Its content can express or support a claim, but the position’s presence alone establishes no obtaining relation. In every representation branch below, use C.29 only when a separate mathematical representation or transfer question remains.
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 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, distinct from the participant. Its presence alone does not establish obtaining; assess any asserted claim and grounds under the direct rule. |
| 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. |
| 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 | the chosen representation and its rule for interpreting that position | Keep the position within its representation and recover the correspondence the receiving use needs. Form alone does not establish a participant, declaration or actual binding. |
| signature or law-governed declaration | A.6.0; A.6.5 for SlotSpecs in a RelationSignature, and A.6.1 for operation declarations | Recover the declaration’s subject and ranges, Vocabulary, Laws and Applicability. Keep the signature episteme distinct from its subject, actual applications, evidence and publication. Describing an object does not make the declaration that object. |
| bare role already recovered as a 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 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 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 actual performer S : U.System and dated W : U.Work. For an attribution-bearing claim, also recover the 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. Missing or failed attribution alone leaves independently admitted W intact; if the same finding defeats a consumed admission premise, recheck that premise and its dependent conclusions under A.15.1. 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 SlotSpecs; the selected 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 (the selected 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, with B.3.5 only when a publication choice or named current requirement elects that assurance profile), boundary description or publication (C.2.1 for claim-bearing description content, C.30.AD for architecture descriptions, E.24.PUB for publication availability, E.17 for a needed reader-facing form 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.24.PUB for publication availability and occurrence identity; E.17 for a needed reader-facing form of the accepted API or interface description; A.6.0 and A.6.5 for a reusable RelationSignature and its SlotSpecs; the pattern defining the API-description claim and selected scheme for representation positions and needed 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 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, 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 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 for episteme identity and content; E.24.PUB for publication availability and occurrence identity; E.17 for a needed reader-facing form; C.2.P.DR, E.10 and E.10.ARCH for the remaining description or wording question | 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.5for the correspondingSlotSpecinside oneRelationSignature. ItsSlotKindis declaration-local and neither is the participant nor makes the relation obtain. - If an episteme asserts, evaluates, or describes the participation,
C.2.1governs the episteme’s identity and content, while the direct assertion, evaluation, evidence-use, or description family governs the predicate, polarity, or use relation. When a compatibleSlotSpecis current,A.6.5governs the participant designation’sValueKindandrefModediscipline; without reusable declaration, the assertion may designate the actual participants directly. - If the receiving use needs a local classification or quantification over such actual participants, use
C.3andC.3.1for the localU.Kind, membership rule, and extent rule. Neither the participant-meaning label nor the declaration-localSlotKindadmits that kind. - If the source exposes a tuple component, argument, edge endpoint, schema field or another representation position, interpret it under the selected scheme and recover the correspondence needed by the claim. A displayed value can state a participant or binding claim; its presence alone does not establish that claim.
For parameter, argument, or result wording, separately recover the A.6.1 declaration content, one independently identified 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 object or claim kind;
- the subject pattern;
- one result 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 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, a 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
SlotSpecis named only for a current reusable relation declaration, an operationArgumentDeclarationorResultDeclarationand any application binding stay underA.6.1, and a method-call, formula, or other representation position is interpreted under the conventions of the chosen expression. - “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
The subject pattern supplies the substantive definition or test once RSIR has identified the question. The selection table keeps relation and slot rules, operation declarations and bindings, representation, system-role kinds and assignments, and the neighboring engineering claims separate. RSIR does not perform those operations merely by naming their patterns.
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, 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.
A.6.RSIR:5 - Archetypal Grounding
System case: module interface claim. A team says “the cooling module exposes the heat-exchanger interface.” RSIR first asks what claim is current. If the claim is substitutability or separate change, use A.6.M. If a reusable relation declaration for exchanged-medium and boundary-condition participant meanings is current, use A.6.0 plus A.6.5 for the RelationSignature and complete SlotSpecs. If the current use is a diagram, API schema, or other representation, interpret its positions under the selected scheme and state the correspondence needed by the receiving claim. If the claim is a functional port in a transformation-flow structure, use A.6.F, A.3.4, and E.18. RSIR does not create U.Interface.
Bare-role case: API provider wording. A source says “the API role is provider.” Apply E.10.ROLE once. If it recovers a provider System, local ProviderSystemRole kind, assignment, capability, provider Work, promise, access relation, publication, or another direct object, apply that object’s rule and do not apply RSIR. Apply RSIR only when the still-unanswered question is the participant meaning in a direct relation, a reusable declaration, an interface claim, an operation declaration or binding, or an API-schema representation position. For protocol, service-term, SLA, or agreement-like wording that bundles several claims, use A.6.C to unpack the claims before stating each object or relation. Use A.6.M only for a module-interface claim and A.6.B only for boundary-package statement classification. Do not assign a system role to the API description.
Evidence case: reviewer and report wording. A report says “reviewer evidence role approved the gate.” Apply E.10.ROLE once and split the claims. Apply A.2/A.2.1 for any reviewer system-role kind or assignment. Use A.10 for evidence reliance on a named claim, B.3 only for a named assurance claim, F.10 for a status-use relation, E.24.PUB when publication availability is current, and E.17 when the accepted account needs a reader-facing publication form. Use A.21 for the gate decision and A.2.9 for any issuing speech act. None of those recovered branches needs RSIR unless a separate direct-participation, reusable-declaration, interface, operation, or representation-position question remains. No episteme receives a system-role assignment by being evidence.
Slot case: method parameter. A method description says “parameter target controls the model.” The sentence does not identify what target designates or which control relation is claimed. Keep it as reduced-use source wording and recover those missing values before asserting the control claim.
A separate positive example illustrates an A.6.1 argument label. In the current recognizeAdmittedHolonCandidate declaration, candidate is an ArgumentDeclaration meaning one entity being evaluated, with ValueKind = U.Entity; recognitionJudgment is the declared result meaning. Under A.6.1, the project independently identifies the bounded recognition-evaluation invocation P-37 by that declaration’s application predicate, identity rule, and extent rule. During P-37, Pump #37 is bound under candidate, and the returned value unknown is bound under recognitionJudgment.
In a call representation such as recognizeAdmittedHolonCandidate(target = Pump-37, ...), the named-argument position target corresponds to the declared candidate meaning but is neither the declaration nor either binding. The practitioner writes: “target is the call label; A.6.1 declares candidate : U.Entity; during application P-37, Pump #37 is bound as candidate.” Stop there unless the receiving claim needs the result binding or another subject pattern.
A.6.RSIR:5.1 - Near-Miss Checks
| Source phrase | Positive recovery | Near miss to reject |
|---|---|---|
| “API role is provider” | Apply E.10.ROLE once. If it recovers ProviderSystemRole, an assignment, provider Work, API publication, promise, access relation, or another direct object, apply that object’s rule and leave RSIR closed. Apply A.6.RSIR only for a remaining declaration, direct-participation, interface, operation, or representation-position question; use A.6.C only when protocol, SLA, service-term, or agreement-like wording bundles unlike claims. | Do not assign a system role to an API description or protocol, and do not repeat the E.10.ROLE recovery inside RSIR. |
| “endpoint parameter source” | Use the direct relation pattern when the phrase hides a participant meaning or actual participant; use A.6.5 only for a complete SlotSpec in a current reusable RelationSignature; use A.6.1 when it names an operation ArgumentDeclaration, ResultDeclaration, or an actual binding in one independently identified application; use the selected representation rule for a representation position, E.24.PUB for publication availability, or E.17 for a needed reader-facing form of the accepted API description, and A.6.P:4.11a when a service-documentation label hides the concrete subject or relation; recover correspondence from the selected scheme, making it explicit when the receiving claim needs it. | Do not create an endpoint kind, a work-facing role from the word “source”, a parameter ontology, a public application kind, a universal input/output relation, or a world-side participant or binding from representation shape. |
“Engineer-7#Verifier:Lab-A” | Recover Engineer-7 as the holder System, VerifierSystemRole as the local kind, and any claimed assignment under its declared U.SystemRoleAssignment species. In this case Lab-A denotes the facility System where verification Work occurs; that Work-location claim is separate. | The spelling alone does not make Lab-A an assignment participant or establish Holder#Role:Context as an identity rule. Apply the species’ own participant and identity rules. |
| “function of the pump” | A.6.F, A.3.4, E.18, or C.30.TFS-REL when the phrase names functional structure; A.2.2 when it names a system capability. | Do not treat “function” as the recovered kind before the current claim is known. |
| “standard evidence role” | Apply E.10.ROLE once, then use A.10, B.3 or F.10 for the recovered evidence, source, status or assurance claim under its own conditions; use E.24.PUB for publication availability and E.17 for a needed reader-facing form. Leave RSIR closed unless a separate direct-participation, declaration, interface, operation, or representation-position question remains. | Do not invent U.EvidenceRole or put the standard episteme into U.SystemRoleAssignment. |
A.6.RSIR:6 - Bias-Annotation
This pattern has a relation-cluster bias because it sits in A.6. It mitigates that bias by stopping as soon as the applicable definition, constraint, or test is clear.
It has an interface and software-language stress case because API, endpoint, protocol, and interface wording often enters from software. The pattern keeps the recovery general: architecture interfaces, physical ports, functional ports, service-access descriptions, and publication forms are all possible, and none is selected by word choice alone.
It resists semio-bias by keeping descriptions, publications, records, reports, standards, and source labels under the patterns that define or constrain those objects and uses: C.2.1, E.24.PUB, E.17, C.2.P.DR, A.10, B.3, F.10, C.28, E.10, or E.10.ARCH when those objects or uses are current. A source label may help recognition; its presence is not evidence that the denoted object is the current EntityOfConcern or that a proposed action is admissible.
A.6.RSIR:7 - Conformance Checklist
- The repair starts with project concern, not with a replacement word.
- The EntityOfConcern or claim kind is named before a subject pattern is applied.
- The repair stops once the applicable rule and concrete next action are clear.
- When reusable relation declaration is current, slot discipline uses
A.6.5and states one completeSlotSpec = <SlotKind, ValueKind, refMode>inside oneRelationSignature; actual participants and representation positions remain outside it. - An assignment claim uses its declared U.SystemRoleAssignment species and participant meanings. A positive claim needs facts satisfying that predicate; add explicit occurrence identity when the receiving use needs it. A governed negative claim creates no obtaining assignment. Apply A.2.5 for a state claim, A.2.7 for a structure among kinds, and the applicable rule for capability, Method or Work. Do not repeat a settled result through RSIR.
- Evidence-use and status-use cases are not represented through
U.SystemRoleAssignmentfor epistemes. ApplyE.10.ROLEonce to bare role; if it recovers evidence use, status use, or another direct object, apply that object’s rule and leave RSIR closed. - Interface wording is kept as a recognition cue but is not admitted as generic
U.Interface. - Every neighboring object family selected in the dispatch table uses its defining or testing rule rather than being redescribed inside RSIR.
- Relation-defined wording dispatches separately to the direct participant meaning and actual participant; a declaration-local
SlotSpecwhen reusable typing is current; an assertion- or description-side designation whose episteme identity and content stay withC.2.1, whose predicate, polarity, and use stay with the direct claim family, and whose typing stays withA.6.5only when a compatibleSlotSpecis current; a C.3 local kind when the receiving classification or quantification needs it; or a representation position with its recoverable correspondence. It does not create one umbrella qualification object. - Operation wording keeps A.6.1
ArgumentDeclarationorResultDeclarationcontent, one independently identified application and obtaining argument or result binding, and any call or formula representation position distinct; it infers neither a public application kind nor production, a produced entity, a result episteme, evidence, or work from the binding. - Quote-only or reduced-use labels carry no action-facing claim beyond the claim admitted by the selected rule.
A.6.RSIR:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Why it fails | Repair |
|---|---|---|
| Rename role to position everywhere | It loses system-role-kind and assignment cases and creates a new umbrella. | Start with E.10.ROLE; recover a system-role kind, assignment, direct participant, declaration-local SlotSpec, representation position and correspondence, episteme-use relation, another object, or ordinary prose from the current claim. |
| Treat interface as one root kind | It merges module, functional, protocol, API, signature, publication, representation, architecture, and boundary-package claims. | Recover the governing object first; then apply A.6.M for module-interface, A.6.F for functional port or functional structure, A.6.0 plus A.6.5 for a reusable RelationSignature and its SlotSpecs, the selected representation pattern for positions and needed correspondence, E.24.PUB for publication availability and occurrence identity, E.17 for a needed reader-facing form of an accepted account, A.6.C only when recovered agreement-like, protocol, or SLA wording bundles promise, utterance or publication, governance, Work or consequence, or evidence claims, A.6.P:4.11a when service or service-access wording hides its referent or direct relation, A.6.B only for L, A, D, or E statement classification inside a boundary package, or C.30, C.30.ASV, C.30.AD, or C.30.TFS-REL for architecture claims. |
| Put evidence and status into a system-role assignment | It gives epistemes a work-facing assignment they do not have. | Use evidence-use, source-use, status-use, assurance-use, or publication-use relations under A.10, B.3, F.10, E.24.PUB, E.17, or C.2.1 when those relations are current. |
Use A.6.5 as relation identity | Slot discipline does not say which relation is being asserted. | Apply A.6.P or the relation-specific pattern for relation identity; use A.6.5 only for SlotSpecs. |
| Treat function as the recovered kind | Function-like wording may point to capability, method, work, architecture, mathematical function, quality, or module allocation. | Apply A.6.F after RSIR selects function-like recovery. |
| Keep a quoted source label but use it as governing content | Reduced-use wording carries an unsupported stronger claim. | State the use and its governing rule. Add a restriction only for a grounded, plausible misreading that changes the receiving use. |
A.6.RSIR:9 - Consequences
A.6.RSIR adds a bounded recovery step when the engineering object or claim remains unclear after the F.19 reading with E.10 cues. The selected subject pattern then handles the substantive claim; neighboring patterns can refer to this recovery instead of repeating it.
The pattern also keeps useful source vocabulary alive. Engineers can still say interface, API, role, parameter, function, and endpoint. FPF refuses to let those words select ontology by themselves.
A.6.RSIR:10 - Rationale
The RSIR cluster needs a bounded recovery step when F.19’s whole-span reading and E.10’s compact cues leave an engineering object or claim unclear. Direct relation, declaration, interface, system-role, Work, publication, evidence, and status rules retain their own objects and predicates. Apply the thinner E.10.ROLE entry once to bare role. If one concrete direct-participation, declaration, interface, operation, or representation question remains unanswered, apply RSIR to that question; otherwise leave RSIR closed.
The main ontological principle is separation among participant, declaration, application and binding, assertion and designation, and representation. An actual direct-relation participant retains its direct kind under one participant meaning. A corresponding SlotSpec, when reusable typed relation declaration is current, states a declaration-local SlotKind, exact ValueKind, and refMode. An assertion or description remains a C.2.1 episteme; its direct claim family supplies predicate, polarity, or use, and A.6.5 types a participant designation only against a compatible current SlotSpec. An A.6.1 declaration states reusable operation meaning, while one application and obtaining binding relate that occurrence to an actual value. A representation position may correspond to any of those objects without becoming one.
The second principle is direct rule use. Once the current object is recovered, apply the rule that defines, constrains, or tests the claim. RSIR only identifies that rule and its PatternID locator when the reference must travel.
A.6.RSIR:11 - SoTA-Echoing
The comparisons below inform this bounded recovery: distinguish the engineering objects before selecting their direct rule. They do not supply the obtaining or identity rule for the recovered object.
| Practice or source line | Why it matters for RSIR | FPF adoption in this pattern |
|---|---|---|
| Modular ontology design-pattern work, including MODL, MOMo, and commonsense ontology micropatterns such as Shimizu and Hitzler 2024 and Eells, Dave, Hitzler, and Shimizu 2024. | Ontology-engineering contribution: use small reusable ontology structures without copying local slot doctrine across patterns. | Adopt and narrow: RSIR does not become an ontic registry. It recovers the current governed object, leaves participant meaning and actual participation with the direct relation pattern, uses A.6.5 only for a current RelationSignature SlotSpec, uses the chosen representation’s conventions for positions and their correspondence, and uses E.24 only for durable ontic decisions. |
| Ontology-interoperability lifecycle work such as Qiang 2025 and 2026. | A caution that overlapping labels and conflicting local concepts become expensive if not settled before reuse, matching, and validation. | Treat interface, slot, function, Method, concern, and bare role as recovery cues until the current EntityOfConcern, direct relation and participants, declaration, any representation position and correspondence, and direct pattern are named by use; bare role starts at E.10.ROLE. |
| Process-representation ODP work such as Norouzi, Hertling, Waitelonis, and Sack 2025. | A warning that process and workflow ontologies often hide implicit patterns from domain users. | Adapt for RSIR source labels: “process”, “workflow”, “method”, “function”, “parameter”, and “interface” may remain useful source labels, but they do not carry FPF-governed content until the direct method, work, transformation-flow, role, slot, publication, or evidence pattern is selected. |
| gUFO, UFO, and OntoUML role, relator, situation, and high-order type practice, including Almeida, Guizzardi, Sales, and Fonseca 2026. | A foundational-ontology warning against flattening system classifications, assignment occurrences, participant meanings, declaration-local slots, representation positions, status classifications, and evidence uses into one taxonomy. | Use only as a bounded comparator. FPF recovers local system-role kinds and direct U.SystemRoleAssignment species separately; direct patterns retain participant meanings, A.6.5 retains declaration-local SlotSpecs, the chosen representation and its conventions supply positions and their correspondence, and episteme uses retain their direct relations. |
| Engineering architecture practice around functions, ports, modules, interfaces, signatures, and views. | A.6.M, A.6.F, A.6.0, E.18, C.30, C.30.ASV, C.30.AD and C.30.TFS-REL define the different objects named by these related terms. | Adapt as a positive recovery map: preserve interface and function language as recognition cues, then recover module-interface, signature, functional port, transformation-flow, architecture-of, structural-view, architecture-description, API publication, protocol, or plain source-label use by current claim. |
A.6.RSIR:12 - Relations
Use F.19 for the whole-span reading with the compact cues in E.10:0.2. Apply E.10.ROLE once to bare claim-bearing role. Apply RSIR afterward only if one concrete direct-relation, declaration, interface, operation, or representation question remains; all other recovered branches use their direct rules and leave RSIR closed. E.10.ARCH describes both entries in the shared restoration architecture.
A.6.5 defines complete declaration-local SlotSpec = <SlotKind, ValueKind, refMode> content inside one RelationSignature and, only when a compatible SlotSpec is current, participant-designation typing. C.2.1 supplies the assertion or description episteme’s identity rule, while the direct claim rule supplies predicate, polarity, and use. An ordinary assertion may designate actual participants directly without reusable declaration.
Apply A.6.P for relation precision restoration after the recovered object is a relation or relation-bearing claim.
A.6.0 defines U.Signature; A.6.1 defines operation argument and result declaration content plus the rules for any independently identified application and declaration-local binding; E.20 supplies mechanism-introduction rules. A.6.1 admits no public OperationApplication U-kind or universal input/output/result relation, and its result binding alone establishes none of production, a produced entity, a result episteme, evidence, or work.
A.2, A.2.1, A.2.2, A.2.5, A.2.7, A.15, and Part F system-role-description and naming patterns define or constrain local system-role kinds, direct system-role assignments, capability, SystemRoleAssignmentStateRelation, SystemRoleKindRelationStructure, system-role–Method–Work alignment, and durable system-role-kind names.
Apply A.6.M, A.6.F, A.6.A, A.3.4.P, E.18, C.30, C.30.ASV, C.30.AD, or C.30.TFS-REL for the corresponding module-interface, functional, affordance, transformation, transformation-flow, architecture-of, structural-view, or architecture-description question.
Apply C.2.1 for episteme identity and content, E.24.PUB for publication availability and occurrence identity, and E.17 for a needed reader-facing form of an accepted account. Use C.2.P.DR, A.10, B.3, G.6, F.10 or C.28 for the corresponding declarative representation, evidence, assurance, provenance, status or causal-use question; the direct claim rule still supplies the predicate, polarity or use asserted through that content.