#Recovering What “Role” Means in the Current Claim

E.10.ROLE · Stable · Lexical and ontological precision restoration (E) · Part E - The FPF Constitution and Authoring Guides

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Lexical and ontological precision restoration (E)

Status: Stable

Plain name: Recover what “role” means here

Use this pattern when claim-bearing wording uses role and the current sentence does not yet reveal which object or relation it means.

#Keywords

• ambiguous role wording
• system-role kind
• assignment
• relation participant
• declaration slot
• interface place
• representation position
• responsibility
• ordinary wording.

#Relations

#Content

#Use This When

Use this pattern when claim-bearing wording uses role and the current sentence does not yet reveal which object or relation it means.

A system role is a context-local kind for an entity already admitted under A.1 as a U.System, which may be a person, team, organization, or non-human technical object. The name creates no admission, assignment, agency, capability, or Work.

A system-role assignment is one exact occurrence under U.SystemRoleAssignment. The bare word role identifies neither object.

First useful result. Rewrite the ordinary domain sentence so that its recognizable object and action or relation are explicit. Select the pattern for that object or relation. Stop there unless the receiving claim needs a technical designation, exact occurrence, predicate, assertion, or reference.

For example:

• “Alice is reviewer” may remain ordinary recognition prose;
• “Alice holds the review assignment for this manuscript” makes an assignment claim current;
• “the report plays a role in approval” normally needs an evidence-use, source-use, reliance, or other direct relation, not a system-role assignment;
• “the first role in this tuple” normally points to a representation position, not a system-role kind.

Not this pattern when. Keep ordinary or quoted wording unchanged when no FPF claim relies on the word. When the object and its direct pattern are already clear, use that pattern directly. Use A.6.RSIR when the unresolved question is specifically about participation in a direct relation, a relation declaration, an interface, or a representation position.

ROLE remains in this PatternID because it is the ambiguous source word that opens this recovery. It is not a Tech designation for one governed object and is not a naming precedent.

#Problem Frame

Readers meet role in organizational, engineering, mathematical, software, documentary, and ordinary language. The same spelling may point to a local classification of systems, one assignment occurrence, participation in a relation, a declaration slot, a position in a representation or organization, functioning, capability, Work, authority, responsibility, use of an episteme, or no technical claim at all.

One remote definition cannot make the word safe in every sentence. Replacing every occurrence with SystemRole is also wrong: it would turn unrelated participation, slot, representation, evidence, and ordinary-language claims into a new ontology.

#Problem

A cold reader needs to answer two questions at the point of use:

1. What exact object or relation does this sentence claim?
2. What useful action or conclusion depends on making that distinction?

If the text answers neither question, a fluent rewrite can preserve the word while changing the claim. A mechanical replacement can be even worse: it can assign a report, schema field, relation participant, or diagram position to a system-role kind that was never intended.

#Forces

#Solution

Use the sentence's intended claim, not the trigger word, to select the result.

1. Quote or locate the bounded phrase only when its source identity matters.
2. Write the ordinary sentence the reader should understand, naming the recognizable object and action or relation.
3. Select one branch below from that recovered claim. The examples are non-exhaustive; they illustrate result families and do not define a new role taxonomy.
4. Apply the selected pattern only as far as the receiving claim needs. Add a Tech designation, occurrence identity, predicate, assertion, reference, evidence, or assurance only when omitting it would change truth, action, reuse, or reliance.
5. For one recovered claim, stop when one exact object or relation and its pattern are selected, or return the exact missing-governor, missing-information, quote-only, or ordinary-non-use result.

If recovery shows that the same bounded phrase carries several distinct claims at once, rewrite them as separate ordinary sentences and apply steps 3–5 to each sentence. Ambiguity by itself is not evidence of several claims. Use A.6.C Contract Unpacking for Boundaries only when its contract-like boundary-language trigger holds; otherwise apply the direct rule for each recovered claim. Do not create a multi-claim record or an umbrella role object.

#Boundary with A.6.RSIR

E.10.ROLE starts from the ambiguous word and recovers the sentence's work-facing or use-facing object. Use A.6.RSIR for the narrower question of direct-relation participation, reusable declaration, interface, operation declaration or binding, and representation position.

If the recovered claim leaves a direct-participation, reusable-declaration, interface, operation-declaration-or-binding, or representation-position question unanswered, apply A.6.RSIR to that question. If it recovers a system-role kind, assignment, capability, Work, deontic relation, evidence use, another direct object, or ordinary non-use, apply that object's direct rule and do not apply RSIR. Neither pattern duplicates the other's subject rules.

#Lightweight Result

For a local repair, the result is normally only:

source sentence: the report played a role in approval
recovered sentence: reviewers used Report-R as evidence for ApprovalClaim-C
applicable rule: A.10 evidence-use relation
blocked overread: Report-R has no system-role assignment by this claim
stop: ApprovalClaim-C remains the current question

No separate repair record is required unless another named use must inspect or reuse the decision.

#Archetypal Grounding — Worked Slices

#Alice Is Reviewer

“Alice is reviewer” may stay as readable recognition prose when no technical classification claim is consumed. If only the local kind matters, identify ReviewerSystemRole through C.3 and A.2. If a technical classification judgment matters, use A.2 and C.3.2 and keep Alice, ReviewerSystemRole, the current KindSignature edition, the context slice, and the true | false | unknown result recoverable. If assignment identity matters, first name the declared assignment species JournalReviewAssignmentRelation and establish that its direct predicate obtains for the actual participants, including Alice as holder, under the stated applicability. Only then identify ReviewAssignment-82 as the occurrence and state its extent. A roster, appointment label, description, or evidence item may support the assignment claim but does not make the assignment obtain. If performed Work matters, first recover Alice's A.13 core for this action and independently admit ReviewWork-82 under A.15.1. Because this branch also says that Alice performed the Work under ReviewAssignment-82, F.6 afterward relates the already admitted Work to that same assignment. Classification, assignment, Work, and attribution remain separate. None follows merely from the ordinary sentence. A short projection may omit an assignment identifier unused by its receiving claim only when every relation the claim consumes remains recoverable.

#A Report Plays a Role in Approval

The report is an episteme. Rewrite the claim as “reviewers used Report-R as evidence for ApprovalClaim-C”, then use A.10 for the evidence-use relation and B.3 only when an assurance claim or material-reliance threshold is current. The report becomes neither a system nor a holder of a system-role assignment.

#API Provider Role

“The API role is provider” does not yet reveal which claim is meant. It may hide several claims, but the wording alone does not establish that; recover the intended claim before selecting and applying a rule. First ask whether a provider System is current and whether its classification under a local provider system-role kind matters. If the assignment itself matters, name its declared assignment species and the obtaining occurrence separately; do not infer either from root-family typing or the word role. Provision, service, declaration, interface, schema position, publication, promise, and access claims each use their own pattern. Only when provider Work is current, recover every precise performer's A.13 core and independently admit the dated Work under A.15.1. Add F.6 afterward only if this provider account also needs precise assignment-bound attribution through the same obtaining assignment. The API description is neither assigned nor a performer.

#Passive Test Article

A passive test article may independently pass A.1 and be classified under TestArticleSystemRole. If an assignment claim matters, name its declared assignment species before identifying an occurrence. Neither classification nor assignment makes the article an agent or performer. The role-bearing source claim to recover is: TestArticle-7 participates passively in TestWork-9 during TestInterval-9; its intended participant order is article, Work, then applicability interval. No current pattern supplies a direct passive-participation predicate with those participants, applicability, and occurrence identity, so the current result is the A.6.RCD missing-governor for that exact attempted claim. Any tester or test-rig Work first reuses every precise performer's A.13 core and is independently admitted under A.15.1; add F.6 only when the tester account also needs precise assignment-bound attribution. A short projection may omit an unused assignment identifier, but it keeps the article, Work, interval, and missing relation recoverable.

#Bias-Annotation

Lenses tested: Gov, Arch, Onto/Epist, Prag, Did. Scope: Universal for claim-bearing uses of role that enter this pattern; ordinary and quoted non-uses remain outside it. The pattern deliberately favors Onto/Epist precision, which can tempt an author to expand every sentence into technical apparatus. Writing the ordinary sentence first, adding only distinctions used by the receiving claim, and stopping when the applicable direct rule is clear preserve Prag and Did usefulness, while the separate branches preserve Gov and Arch boundaries.

#Conformance Checklist

1. Is role being used in a claim, rather than only in ordinary or quoted wording?
2. Does the repaired ordinary sentence name the recognizable object and action or relation?
3. Was the result selected from the recovered claim rather than from the word alone?
4. If a system-role kind is current, are its local boundary and stable contribution distinction recoverable through C.3 and A.2? If a technical classification claim is current, are the candidate’s independent A.1 system admission, exact kind, current KindSignature edition, context slice, and true | false | unknown C.3.2 judgment separately recoverable?
5. If an assignment is current, can you identify both the assignment occurrence and its declared species? Does that species' direct predicate obtain for the actual participants, including the holder, under the stated applicability, and is the occurrence's extent recoverable? Is supporting evidence kept separate from whether the assignment obtains?
6. Are participation, declaration slot, operation binding, interface place, and representation position kept distinct?
7. Are functioning, capability, Work, deontics, access, authority, responsibility, evidence use, and results kept under their direct relations?
8. Does ordinary prose stay ordinary when no technical distinction changes the receiving claim?
9. Does the repair add a qualifier only for a live alternative and avoid a fixed formal expansion?
10. For each recovered claim, does the repair stop after one exact object or relation and its applicable rule are selected?

#Common Anti-Patterns and How to Avoid Them — Role-Word Repairs

#Consequences — Reopen Condition

Benefits. Cold readers can recover the intended object at the point of use. Natural practitioner language survives. Technical names become more precise without turning relation slots, evidence uses, or representation positions into system-role kinds.

Costs. A claim-bearing ambiguous sentence needs one bounded interpretation before it can be reused. Some old compact Tech names must be retired or made explicitly historical.

Reopen this pattern only when an actual bare-role use cannot reach one exact object, relation, ordinary non-use, or missing governor without duplicating A.6.RSIR, or when repeated cold readers still infer system admission, assignment, agency, capability, participation, or Work from SystemRole morphology.

#Rationale

The recurring problem is word-sense recovery, not a missing universal role category. FPF therefore makes an internal architectural choice: recover the claim expressed in this use, then use the direct pattern for the recovered kind, assignment, participant, declaration place, representation position, or relation. The trigger word neither supplies that ontology nor makes the recovered claim obtain.

The pattern therefore stays thin. It supplies an entry and a stop rule, while C.3, A.2, A.2.1, A.6.RSIR, A.6.5, C.29, A.10, A.15, and other direct patterns retain their own predicates and identity laws.

#SoTA-Echoing

No external source governs this design, and FPF imports neither an external upper ontology nor its terminology. Two current lines provide the main SoTA comparison. The gUFO account and OntoUML role documentation and specification test anti-rigidity, external dependence, and the connection to a base kind. Engineering-function work tests the separation among function, behavior, and capability. FPF uses both lines as bounded comparators and adapts their tests to keep holder identity, changing classification, assignment, capability, functioning, and Work distinct.

Other comparisons have narrower uses. FPF adapts Toyoshima's role facets as diagnostic questions about position, specification, and potential. It uses DOLCE, BFO, and CCO as bounded comparators for dependence and the distinctions among persistent entities, processes, roles, dispositions, capabilities, and functions. It keeps DnS as lineage for separating descriptions from entities participating in described settings. These comparisons supply distinctions and counterexamples, not FPF kinds or assignment identity.

Within FPF, E.10 and E.10.ARCH define trigger recognition and recovery distribution. A.2, C.3, and C.3.2 define system-role kinds and classification judgments; A.2.1 defines assignment occurrences; A.6.RSIR defines direct-relation, declaration, interface, and representation recovery; and F.19 constrains the final plain wording. Together they define the ordinary-sentence-first, thin entry, but cannot supply a missing direct relation or establish that the recovered claim is true. Reopen this choice if one of those patterns changes that boundary, or if a stronger current comparison exposes a case in which the thin entry cannot preserve both plain language and whether the recovered relation obtains.

#Relations

#E.10.ROLE:End

Last Updated: 2026-08-21 — this section last modified in upstream FPF commit f0b498dd (github.com/ailev/FPF)