#Exact Relation Recovery for Method and Work Claims

A.6.P.WMR · Stable · Architectural precision-restoration pattern (A) · Normative unless explicitly marked informative · Part A - Kernel Architecture Cluster

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

Plain label: recover the exact relation hidden by input, result, and handoff wording Type: Architectural precision-restoration pattern (A) Status: Stable Normativity: Normative unless explicitly marked informative Specializes: A.6.P Relational Precision Restoration

Use this when. Practitioners SHOULD use this pattern after A.6.P generic relation recovery has isolated one current method-or-work boundary claim and the exact entity is already in view, but words such as input, raw material, source data, source material, output, result, outcome, deliverable, or handoff still do not reveal the direct relation that makes the sentence true. They SHOULD also use it when method, intended-work, actual-work, production, evaluation, delivery, acceptance, transfer, or receiving-use wording leaves that claim's participant meaning or orthogonal claim dimensions unclear.

#Relations

#Content

#Problem Frame

Use this when. Practitioners SHOULD use this pattern after A.6.P generic relation recovery has isolated one current method-or-work boundary claim and the exact entity is already in view, but words such as input, raw material, source data, source material, output, result, outcome, deliverable, or handoff still do not reveal the direct relation that makes the sentence true. They SHOULD also use it when method, intended-work, actual-work, production, evaluation, delivery, acceptance, transfer, or receiving-use wording leaves that claim's participant meaning or orthogonal claim dimensions unclear.

The primary EntityOfConcern is one relation-bearing claim in an episteme. The trigger word helps a practitioner notice the problem; it is not the governed object, a participant kind, a relation kind, or a universal family of inputs and results.

Primary working reader, concern, and viewpoint. The primary reader is a practitioner or engineer whose current task is to make one boundary-word claim safe for a named receiving use. Their concern is which exact relation and claim dimensions can be stated safely for that use now; the viewpoint is the receiving use, while the direct subject-pattern owner supplies or rejects any missing governor.

First useful result. Start at the boundary-word sentence and answer three ordinary questions: what exact thing is being named, relative to what exact method, plan, work, operation application, transformation, delivery, or receiving use, and what direct verb can safely be said now—or why can it not yet be said.

For example, a note says, inspection report R-17 is the result of inspection. R-17 is an exact report episteme. If the current related object is independently identified inspection application P-17 and its declaration-local result-binding predicate actually holds, write: Inspection application P-17 returned report R-17. Then stop unless the receiver separately asks about report inception, inspection Work, evidence, publication, delivery, or acceptance.

The nearest three failures keep the same thing and related object while changing only the deciding deficit:

• if the binding governor is known and the case facts fail its positive predicate, the proposed positive binding is factually unsupported;
• if the governor is known but the fact needed to decide whether P-17 returned R-17 is unavailable, return missing-information;
• if no current result-binding predicate or direct report relation governs that pair, return missing-governor and name the inspection-application or report-forming owner that must supply, reject, or reframe it.

Only when another reading could change the answer should the practitioner make the formal distinctions explicit: reusable declaration versus intended, committed, current, or historical subject relation; exact extent; polarity; and whether the claim is assertable. A direct relation additionally names its exact RelationKind and resolving direct pattern or relation-declaration episteme. An operation binding or local claim instead names its declaration-local or admitted predicate and owner. These assurance details check the ordinary answer; they are not prerequisites for understanding a simple positive past-tense sentence.

What changes in practice. The engineer stops debating which broad word is correct. They name the thing, the exact object it is relative to, and the direct verb they can safely say now; if no verb is yet justified, they state the exact failed fact, unavailable fact, or absent governor. Formal claim dimensions and assurance apparatus appear only when they can change or check that answer. Planning, actual participation, production, evaluation, delivery, acceptance, and transfer no longer inherit one another through vocabulary.

Adoption test. Given one compressed sentence, the reader can replace it with either the shortest direct sentence under its exact governor or an exact factually-unsupported, missing-information, or missing-governor result, without turning a plan, description, binding, record, or label into actuality.

What goes wrong if missed. A plan is read as actual participation; a method description is treated as a work occurrence; an operation result binding is mistaken for a produced entity; a changed continuing entity becomes a new output; a delivery or handoff package is treated as the transfer; or a convenient missing relation is replaced by a new universal kind.

Ordinary non-use boundary. Practitioners SHOULD NOT use this pattern when the exact direct relation and all claim dimensions needed by the receiving use are already readable; they SHOULD apply that direct pattern and stop. They SHOULD use C.2.P first when the unresolved question is which source expression, episteme, publication, or source-to-use relation is current; A.15.PROD directly when the only current question is production-work participation, entity-identity inception, or production completion and its participants are already exact; and the direct measurement, evaluation, commitment, delivery, acceptance, transfer, resource, premise, transformation, method, planning, or work pattern when that relation is already selected.

#Problem

Boundary words are useful in ordinary language because they compress a relation into a role-like label. The compression becomes unsafe when a later claim depends on which relation actually obtains. The same entity can be a resource used by work, an argument bound in one operation application, an affected referent changed by work, a constituent of another entity, a premise used in reasoning, a newly constituted episteme, a delivered item, or an object used by receiving work. Those are not interchangeable positions.

The repair preserves ordinary readability without manufacturing a universal work-result ontology. It also recovers, without collapsing them, the claim subject, modality and temporal extent, polarity, and recovery or support state. A reusable declaration, an intended relation, an obtaining commitment, an actually obtaining or historically obtained subject relation, and an unresolved claim can overlap across those dimensions; they are not one posture axis. A sentence can be ontologically precise and still be false or unsupported; evidence and assurance remain separate questions.

#Forces

#Solution

Normative method boundary. The Conformance Checklist states each enforceable method duty once and assigns it to an applying practitioner, author or modeler, or accountable subject owner. Sections 4.0-4.8 explain the route, drafting shapes, and model-side constraints; they do not add parallel duties. Ontic identity, obtaining, polarity, non-entailment, and admissibility remain declarative.

Stable WMR lens. Treat the boundary wording as one use-specific claim about an exact thing relative to an exact object. Recover the direct verb or reason-specific stop first. Keep claim subject, time, polarity, and assertability independently recoverable when any of them can change the answer; do not turn the wording into a participant kind, relation kind, or universal input or result family.

The method handles one relation-bearing claim at a time. The trigger word stays in view only until the exact thing, related object, and safe direct verb or stop are recoverable. The result replaces the compressed phrase with the shortest ordinary sentence and continues under the direct owner.

#Thin recovery core and conditional interfaces

The stable ordinary core is one A.6.P-isolated relation-bearing claim, one exact thing, one exact related object, one direct verb or reason-specific stop, exactly one of four truthful exit families, and one readable sentence. The fourth family is an exact non-assertability result whose reason is independently factually unsupported, missing-information, or missing-governor; only missing-governor is an ontology blocker that names the affected receiving use and future owner.

Claim subject, modality and temporal extent, polarity, and recovery or support state remain four independent assurance controls. Their values must be recoverable whenever they can change the answer, but a practitioner does not have to recite the four labels when an ordinary sentence already makes the only material reading clear. WMR owns this recovery and stop. It does not absorb the algorithms, checklists, or ontics of the patterns to which an exit leads.

The substantial interfaces retained below distinguish exits or show why tempting exits differ. Repetition of a neighbor's full basis is not evidence of correctness; WMR consumes the neighbor's direct return.

#Three ordinary questions and two conditional assurance questions

The practitioner stops after question 3 when the ordinary answer has one clear reading and no current receiver needs more apparatus. Questions 4 and 5 inspect or reuse that answer; they do not replace it.

#Use the four claim dimensions only when they can change the answer

The four dimensions remain independent. Make a dimension explicit when two plausible values would change the sentence, the next action, or the stop. Otherwise let ordinary grammar carry it: CF-17 was consumed by W-204 during I-204 already states a positive historical subject relation at one extent and does not require the reader to label four axes.

Well-formedness constraint WMR-WF1 — orthogonal claim dimensions. Whenever one of the four dimensions can alter the result, its value must be separately recoverable from the sentence or its immediate governed basis. No dimension supplies another. Explicit axis vocabulary is required only for a material ambiguity, comparison, assurance replay, or reusable formalization; it is not a prerequisite for every simple direct sentence.

Factually unsupported applies when an applicable governor is known but the available facts fail to support the proposed assertion; no opposite polarity follows without its own basis. Missing-information applies when the governor is known but one named fact needed for the answer is unavailable. Missing-governor applies when the exact participants and question are known but no current direct predicate, condition, or owner closes it.

A current commitment is expressible without collapsing fulfilment only when its exact commitment RelationKind, participant meanings, extent, obtaining predicate, and direct owner are named; a local id such as COM-17 is not that settlement. The promised delivery remains intended and unfulfilled until its own exact token, owner, and facts establish fulfilment. A separately stated past case fact remains positive at its governed extent after its named participants satisfy the governor's predicate; it need not obtain now to remain historically true.

A change in any dimension is substantive. A plan does not become an actually obtaining relation because its date arrives; a later observation does not retroactively manufacture a missing relation; and stronger support does not substitute for the subject relation's own facts.

#Choose one of four truthful exits

Choose by the kind of answer the receiving use needs:

1. If one direct subject owner defines the relation between the exact participants, use the direct relation exit.
2. If the claim is only that one identified operation application used or returned one value, use the declaration-local A.6.1 binding exit.
3. If the question is production-work participation, entity inception, production completion, or another substrate-admitted local conjunction, use the local A.15.PROD or A.6.RCD claim exit.
4. If none of those positive routes has its required basis, stop with the exact reason: failed fact, unavailable fact, or absent governor.

The exit determines the next action; it is not a fifth claim classification.

A case-local positive direct relation needs two independent premises. An already published project relation-declaration episteme names the exact RelationKind, participant meanings, predicate, applicability, and owner. A separate didactic world-side fact says that the exact participants at the exact extent satisfy that predicate. A positive sentence needs both. If the governor exists and the fact fails or is unavailable, return factually unsupported or missing-information; reserve missing-governor for absence of the governor. WMR neither publishes the token nor copies its declaration.

A governed negative sentence needs the analogous negative or non-obtaining criterion and separate facts satisfying it. Failure to support a positive claim, an absent record, or an unobserved event is not a negative premise.

The rejected MethodDescriptionSlotFillingInWorkRelation is not a fallback. A method-description field, planned filling, compatible type, stored reference, matching token, work-card row, or nearby result record establishes no actual participant relation by itself.

#Ordinary sentence shapes

These shapes are informative drafting aids. A practitioner MAY use one after the ordinary answer is known. Only distinctions current for the receiving use appear. In either direct-relation shape, the relation wording is an ordinary reading of one exact RelationKind with its resolving direct pattern or relation-declaration episteme; any assertion id remains outside that governor position. The actually-obtaining and historically-obtained shapes are available only after a separate fact says that their exact participants and extent satisfy the predicate; the compact sentence need not copy the fact fixture or evidence package.

Reusable declaration:
  Under <applicability>, <exact declaration> declares that <exact entity position>
  has <participant or predicate meaning>; no particular intended or obtaining relation follows.

Particular intended relation:
  <exact WorkPlan or other intended-work episteme> states that <exact entity>
  is intended to <direct relation> <exact related object> under <condition>;
  actual obtaining remains open.

Actually obtaining now:
  <exact entity> <direct relation in ordinary words> <exact related object>
  during <current exact extent>; governed by <RelationKind token> under <direct pattern or relation-declaration episteme>.

Historically obtained:
  <exact entity> <direct relation in ordinary words> <exact related object>
  during <exact past extent>; governed by <RelationKind token> under <direct pattern or relation-declaration episteme>.

Governed negative:
  During <exact extent>, <exact entity> did not <direct relation in ordinary words> <exact related object>
  under <RelationKind token and direct owner>; <separate case facts> satisfy
  <the owner's explicit negative or non-obtaining criterion or closure basis>,
  and no relation occurrence is individuated.

Obtaining commitment, promised relation separate:
  <accountable subject> is committed to <promised relation> for <promisee>
  during <commitment extent>; the promised relation remains <intended | unfulfilled | fulfilled at exact extent>
  under its own <RelationKind token and direct owner>.

Factually unsupported:
  The <positive or negative> claim that <exact relation sentence> is not assertable
  because the available facts fail <named condition>; no opposite polarity follows.

Missing information:
  Whether <exact entity> <candidate direct relation> <exact related object> obtains
  is unresolved because <named required fact or information basis> is unavailable.

Missing governor:
  Whether <exact entity> <candidate direct relation> <exact related object> obtains
  is unresolved because <exact governor> is absent;
  the unresolved question names <accountable subject-pattern owner> as the future owner
  for supply, rejection, or reframing of that relation for <receiving use>.

For example, CF-17 was not consumed by W-204 does not follow merely because the positive consumption fact fails or is unavailable. It closes as a governed negative sentence only if the machining-work owner supplies an applicable non-consumption criterion or complete closure basis for the exact quantity, work, and extent and separate case facts satisfy it. Otherwise the proposed positive claim remains factually unsupported or missing-information, or the relation question remains missing-governor, according to the independently recovered deficit.

A practitioner MAY retain the trigger word as optional Plain orientation after the direct sentence is recoverable. The direct sentence and its dimensions, not the familiar label or support state, carry the claim into planning, work, evaluation, delivery, acceptance, transfer, or receiving use.

#Composition and universal-result stop

Invariant WMR-I1 — ontology economy. No universal work-result, transformation-result, production, input, output, outcome, deliverable, handoff, evidence, actual-filling, or status relation or kind follows from boundary-word recovery. Invariant WMR-I2 — transformation non-entailment. No actual transformation follows from a method, plan, desired state, model, description, evaluation result, publication, transfer, flow arrow, adjacency, shared work, or common affected referent.

When the repaired claim depends on transformation composition, its exact participants and receiving question pass to A.3.4 and the current direct composition owner. WMR consumes only their return: an independently retained set of transformations plus either one governed composition claim or the exact missing-governor or missing-substrate blocker. It does not restate or evaluate their contribution, compatibility, composition, or reidentification algorithm.

The blocker reaches only the composition-dependent claim; independent work, change, production, evaluation, delivery, acceptance, transfer, and receiving-use questions continue under their own governors.

#Recognition and assurance remain separate

For ordinary recognition, the first three questions and one of four truthful exits are enough. Use the two assurance questions and explicit claim-dimension vocabulary only when they can change the answer or a named receiver needs to inspect it.

A practitioner MAY open a separate assurance branch when the receiving use additionally needs evidence, warrant, assurance, gate, currentness, publication, or reliance. Pass that owner the exact direct subject claim, exact A.6.1 application binding, exact local A.15.PROD or A.6.RCD claim, or exact non-assertability result together with its governor. Preserve factually unsupported, missing-information, and missing-governor as different reasons; only the last names a future ontology owner. Support or assurance changes neither polarity nor whether the subject relation obtains.

DPF or FPF authoring may trigger the applicable E.19, A.10, B.3, or other assurance checks. Those checks remain with their owners rather than becoming a second WMR checklist.

#Decide the main result readings before scanning examples

When the trigger is result, use the deciding fact before any catalogue:

• if the same entity continues and changed, recover that continuing entity and its separately governed change;
• if an entity first began to exist, open A.15.PROD's entity-inception branch;
• if one operation application returned a value, state only its A.6.1 result binding;
• if the referent is a measured characteristic value, keep that exact value and its direct measurement relation; if it is a comparison, diagnosis, or evaluation claim, identify that exact C.2.1 episteme and its direct basis;
• if an entity was delivered or transferred, use the direct delivery or transfer occurrence;
• if the claim is a downstream effect, use the subject pattern that defines that effect relation;
• if result names a C.11 ChoiceResult, an acceptance verdict, a decision occurrence or record, an enduring condition, or another value, entity, fact, or claim already identified by its direct owner, keep that exact kind and write only the direct relation current for this use.

If no row has its deciding fact and governor, result remains unresolved and the answer is the reason-specific non-assertability result. These readings share no result kind or relation family.

The broader boundary-word palette below is an informative recognition aid. A row suggests a likely related object and candidate semantics; the result then leaves the palette for the direct governor. Several rows may apply to the same entity at different times or for different uses, and they remain separate claims.

When no direct governor closes a selected row, name the exact participants, proposed question, affected use, and future owner. A broader hypernym, another boundary word, or a new universal record does not settle the missing relation.

#Work-name grounding by morphology and occurrence

An action nominal such as testing, assembly, maintenance, evaluation, or inspection is a morphology cue, not an occurrence identification or recovered kind. Placement in function- or flow-structure prose does not identify a U.Function or any other object by itself. When the use remains function-like and claim-bearing while its exact FPF object or relation is hidden, A.6.F is the next owner. When the object is already recoverable, the label resolves to the exact U.Method, U.MethodDescription, required-transformation or required-effect claim, actual U.Transformation, TransformationFlowStructure locus, FunctionalElement@Context or other functional-view record, plan content, performed Work occurrence admitted under U.Work, or other governed value under its direct pattern. In a WBS element, activity, or Work Package the nominal ordinarily names plan or assignment content about intended work; none of these uses identifies an already performed Work occurrence.

A use that needs only the recovered method, method description, plan, structure, or other already governed value closes under that direct pattern. Only reliance on the label as one performed occurrence routes the candidate designation and required granularity to A.15.1.

WMR consumes only the direct A.15.1 return: one exact Work occurrence admitted under U.Work at the granularity needed by the receiver, an exact lowering to the neighboring method, description, plan, evidence, telemetry, temporal, or other object actually supported, or an exact blocker. A materially needed workContinuityPolicyRef remains part of the A.15.1 identity judgment rather than a WMR field. When one occurrence is established and needs a durable name, F.18 opens after that result.

Any output, result, outcome, production, delivery, or acceptance wording is a separate WMR claim only while its direct relation or claim dimensions remain hidden. Once readable, it proceeds under its own pattern and does not become part of work identity.

The preceding action-nominal routing is an FPF-scoped synthesis from recurring morphology-and-owner ambiguity, not a rule imported from PMI, PRINCE2, IDEF0, or IDEF3. A domain may conventionally use an action nominal as the durable name of an already grounded method, plan item, functional-view record, or dated work occurrence; that direct identity and governor win over morphology. The synthesis reopens if repeated practice shows that the cue routes a directly grounded value to the wrong owner, or if a trigger case cannot close through A.6.F, the direct owner, or A.15.1 without new ontology.

Inspection contrast. inspection method names the way of doing. planned Pump-14 inspection work is intended-work content. Pump-14 inspection on 2026-07-15 09:10-09:34 becomes an exact performed occurrence only when A.15.1 returns that result at the required granularity; otherwise retain its lowered object or blocker. If the receiver asks whether the work first constituted an inspection-report episteme, A.15.PROD returns either its local entity-identity-inception claim or the exact branch blocker. A measured or diagnostic result remains with its direct result pattern, and a pass/fail verdict remains a separately governed evaluation-result episteme rather than the inspected entity or a downstream effect.

#Archetypal Grounding

Informative worked examples. Start each case with the ordinary decision and result. Section 5.1 then expands one machining case as the sole author-side relation-declaration replay. Sections 5.2-5.7 retain only the situation, deciding fact or blocker, ordinary result, and stop needed to demonstrate a different branch. These cases add no RFC duty. Their identifiers, relation tokens, and assumed project settlements add no FPF ontology.

#Inspection and machining: one ordinary route, one assurance replay

A source says, the inspection report is the result of inspection. First identify report episteme R-17 and ask what it is relative to. If exact inspection application P-17 actually returned R-17 under its declaration-local result predicate, write: Inspection application P-17 returned report R-17. If the receiver instead asks when exact work first constituted the report, hand that question to A.15.PROD. If neither relation is governed, name R-17, the proposed application or work, the missing relation, and its owner; do not invent WorkResult.

Now a traveler says, raw stock WP-204 and cutting fluid CF-17 are inputs; the machined part and inspection report are outputs of machining. Exact machining Work W-204-MACHINE and continuing workpiece WP-204 are already identified. The ordinary result is:

• A.15.1 returned W-204-MACHINE with affectedReferent WP-204.
• Cutting-fluid quantity CF-17 was consumed by W-204-MACHINE during I-204 under MachiningWorkConsumesResource.
• T-WP204-GEOMETRY is the bounded geometry change of continuing WP-204; W-204-MACHINE caused it under MachiningWorkCausesGeometryChange.

The workpiece remains WP-204, not a newly constituted output. A report binding or inception claim stays open until its own application or A.15.PROD basis is present. If the consumption fact fails, the proposed positive fluid claim is factually unsupported; if it is unavailable, return missing-information; if the relation governor is absent, return missing-governor and name the machining-work owner.

A later measurement-result episteme R-204, diagnostic finding, evaluation verdict, or accepted-deliverable claim is a separately governed claim; delivery or physical transfer of continuing WP-204, and transfer or publication of R-204, are separate again. Shared chronology and one machining case entail none of them: each current claim needs its own direct governor and facts.

Author-side assurance replay — the one fully expanded relation-declaration fixture. Exact published relation-declaration episteme MFG-WORK-REL-2026, owned by MachiningWorkRelations@Plant-7, declares:

Separately stipulated world-side facts say that CF-17 was consumed by W-204-MACHINE during I-204 and that this Work caused T-WP204-GEOMETRY. The declaration episteme, work and transformation identities, chronology, and assertion epistemes MFG-RU-CF17-W204 and MFG-WC-W204-TWP204 supply none of those facts. The formal replay therefore yields the same ordinary sentences and the same three failure reasons. This is assurance for the result above, not the entry price for reading it.

#ETL data: direct participation, then a receiving-use stop

An ETL note says, RawOrders is the source input and WarehouseOrders is the delivered output. Exact Work ETL_Nightly_0811 and both dataset entities under their admitted subject kinds are known. Exact relation-declaration episteme ETL-DATA-REL-2025, owned by ETLDataUseRelations@WarehousePlatform, declares SourceDatasetParticipatesInETLWork and DestinationDatasetParticipatesInETLWork; separate case facts say that the two datasets actually filled those roles in that job.

Write: RawOrders_0811 participated as the source dataset in ETL_Nightly_0811, and WarehouseOrders_0811 participated as the destination dataset in ETL_Nightly_0811. Those facts establish neither delivery nor use by analytics. If decision Work D-0811 is now claimed to use WarehouseOrders_0811 as a premise but no premise-use, reference-use, or application-binding governor is available, stop with missing-governor and name the analytics-decision owner. This case demonstrates a positive direct relation followed by a distinct blocked receiving use.

Before calling WarehouseOrders_0811 a new output, decide which dataset continues. If the ETL job updates the same dataset in place, identify that dataset's bounded change under A.3.4. If a derived dataset begins, apply its dataset-identity rule and use A.15.PROD only when the exact inception basis closes. When a catalog entry, lineage view, or publication is the source from which a reader reaches either dataset, use C.2.P to identify the exact source expression, source-to-use path, allowed use, and reopen condition. An E.17 face or form, or an E.24.PUB publication or availability occurrence, neither creates the dataset nor proves that analytics used it. Row-count, quality, latency, and drift results remain separate measurement or evaluation objects; each evaluation names its own criterion, predicate, and direct owner.

#Clinical work: administration is not a health outcome

A case note says, the patient and dose were inputs; the summary and good outcome were results. Exact clinical Work Appendectomy_Case_8472 has affected referent Patient_8472. Exact relation-declaration episteme MED-ADM-2026, owned by ClinicalAdministrationRelations@Hospital-8472, declares ClinicalWorkAdministersDoseToPatient; a separate case fact says that MedicineDose_8472 was actually administered during the named interval.

Write: Appendectomy_Case_8472 administered MedicineDose_8472 to Patient_8472 during the named interval. Keep DischargeSummary_8472 as an episteme whose binding or inception needs its own basis. The phrase good outcome names no health-effect relation here, so return missing-governor for the proposed patient effect rather than treating a summary, discharge, or verdict as that effect. This case demonstrates a positive administration claim and an independently blocked downstream effect.

Administration is only one possible relation for MedicineDose_8472. The same medicine quantity may instead be a constituent of an administered preparation or compound therapy, or a resource consumed by the clinical Work; each alternative needs its own exact direct governor and case fact, and the positive administration sentence proves neither. If a patient-state change is current, first identify that exact transformation under A.3.4. Then ask separately whether a declared work-to-patient-change predicate with the exact Work, transformation, applicability, and a satisfying case fact obtains. Administration alone proves neither the change nor that the clinical Work caused it.

Keep a measured value, diagnostic finding, evaluation verdict, and claimed health effect as four different objects or claims. A discharge summary may cite any of them without becoming them. Each current claim names its own participants, temporal extent, predicate, criterion when applicable, and direct owner; a measurement or diagnosis does not establish a verdict, and a verdict does not establish the patient's later health effect.

#Pump 14: continuing entity and later decision use

A P2W note says, the pressure problem was the input, adjustment was the work, and restored pressure was the result. Keep accepted ProblemCard@Context PC-P14-PRESSURE as the separate problem-side object. Do not say that this accepted pressure-problem claim guided U.WorkPlan WP-P14-2026-07-15: the case supplies no direct relation for that use. Return missing-governor to the owner of Pump 14 planning relations, and do not infer that the problem caused W-P14-ADJUST-1010-1020. A.15.1 identifies that Work; A.3.4 identifies T-P14-PRESSURE-RISE as a bounded change of continuing HydraulicLoop_P14. Exact relation-declaration episteme P14-REL-2026, owned by Pump14OperationsRelations, declares AdjustmentWorkCausesPressureRise and MeasurementResultUsedByDecisionWork; separate case facts satisfy both predicates.

Keep four values separate: SetPointAdjustment@PlantOps-v3 is the selected U.Method; an A.3.2 U.MethodDescription episteme carries reusable claims about how that Method is done; WP-P14-2026-07-15 states intended Work; and W-P14-ADJUST-1010-1020 is the dated Work occurrence. Naming any of them neither identifies an additional relation nor makes one obtain, so the unsupported ProblemCard-to-plan guidance claim remains missing-governor.

P14-REL-2026 is available in the current case record. Independently, a separately stipulated world-side fact satisfies its actual-causation predicate, so write: W-P14-ADJUST-1010-1020 caused T-P14-PRESSURE-RISE. In the explicitly earlier case record, P14-REL-2026 is absent; at that epistemic stage, keep that Work and transformation separate, return missing-governor for their proposed connection, and route the missing declaration to Pump14OperationsRelations instead of asserting causation. Separately write: Decision Work D-P14 used measurement-result episteme MR-P14-AFTER as its declared basis. The loop continues; no entity begins, no production-completion criterion is current, and no transformation-composition claim follows. This case demonstrates work-caused change and later epistemic use without a production reading.

#Hair styling: a changed referent and an unresolved configuration

A salon record says, hair and gel were inputs; the hairstyle, photo, and satisfaction were outputs. A.15.1 identifies styling Work W-STYLE-27 with affected referent Hair_27; A.3.4 identifies T-HAIR-27 as the arrangement change of that continuing hair. Exact relation-declaration episteme SALON-RESOURCE-USE-2026, owned by SalonWorkRelations@Salon-27, declares StylingWorkConsumesResource and StylingWorkCausesHairArrangementChange; separate case facts support the work-change claim and, when known, the gel-consumption claim.

Write: A.15.1 returned W-STYLE-27 with affectedReferent Hair_27, and W-STYLE-27 caused T-HAIR-27 under StylingWorkCausesHairArrangementChange. When the separate consumption fact is present, also write: W-STYLE-27 consumed StylingGel_27 under StylingWorkConsumesResource. Do not yet write EveningArrangement_27 is the resulting configuration: the case has selected neither an A.22 structure, a characteristic-state fact, a relation occurrence, nor a description episteme and therefore has no direct configuration governor. Return that blocker. This case demonstrates a continuing changed entity plus a blocked attempt to turn result into an unnamed configuration kind.

Client_27 is the person receiving the service; Hair_27 is the continuing affected referent. A hair-to-person part claim, a service-recipient claim, or a person-level effect claim needs its own exact direct governor and case fact; naming the client beside the hair establishes none of them. Ordinary styling changes continuing Hair_27 and does not create a new entity. A separately individuated wig, extension, or other artifact may instead open its own identity-inception question under A.15.PROD when its identity rule and inception basis close.

For gel use, distinguish the three stops. With a current StylingWorkConsumesResource governor, a case fact that fails its predicate is factually unsupported, while an unavailable consumption fact is missing-information; an absent conforming declaration, applicability, or owner is missing-governor. A method-description ingredient field or appointment-plan row substitutes for none of those bases. Photo_27 remains separately identified: its identity, photography or record-forming Work, representation of Hair_27, and publication are separate questions. A measured satisfaction response, an evaluation verdict, and any downstream effect of the service likewise require separate predicates and owners; none constitutes the hairstyle or follows from the photo.

#Car 42: completion without inception

A finishing note says, the last nut was the input and completed Car 42 was the output. Car 42 already satisfies its identity rule before NutFasteningWork-42. Exact relation-declaration episteme CAR42-WORK-REL-2026, owned by Car42AssemblyRelations, declares FastenerParticipatesInFasteningWork and FasteningWorkCausesFastenerChange; separate case facts say that Nut-42-LAST participated and the Work caused the two independently identified fastening transformations.

Write: Nut-42-LAST participated in NutFasteningWork-42 under FastenerParticipatesInFasteningWork, and NutFasteningWork-42 caused the two named fastening transformations under FasteningWorkCausesFastenerChange. Do not open entity inception: the car continues.

For the narrowly bounded finishing use, NutFasteningWork-42 can be the whole Work selected by a local A.15.PROD production-work claim only when the fastening method's intended production effect and applicability, the exact work-to-change facts, and the current completion facts supply that narrow production basis. For the broader factory use, the same occurrence can be a proper operational part of CarProductionWork-42 only when an exact A.15.1 work-part relation obtains and the containing Work has its own separate production basis. Neither reading supplies the other, and neither proves that the two fastening transformations are parts of one composite transformation.

When completion is current, use exact completion-criterion episteme CAR-COMP-ED-42, its named applicability basis, exact boundary state, and production Work to ask A.15.PROD for the historically indexed completion claim. The suffix ED-42 and the criterion's publication establish no edition continuity. If a later criterion episteme continues an earlier one, state the separate C.2.1 EpistemeEditionRelation; otherwise treat it as a non-continuing replacement. If Car 42 had already completed earlier, classify the fastening separately as rework, repair, or maintenance. This case demonstrates completion distinct from inception and from automatic criterion lineage.

Production completion establishes neither delivery, acceptance, release, nor Car 42's present condition. Each current claim needs its own direct governor and facts.

#Authoring: changed episteme, publication, and review use

An authoring note says, research notes were inputs; the draft was the output handed off to review. First apply C.2.1. If claim content, exact EntityOfConcern, and effective U.ReferenceScheme are unchanged, keep DraftEpisteme_31 and state only the changed carrier, rendering, publication, evidence, or transfer relation. If a discriminator changes, identify distinct LaterDraftEpisteme_31; assert EpistemeEditionRelation(DraftEpisteme_31, LaterDraftEpisteme_31) only when C.2.1's historical-continuation predicate obtains.

Exact relation-declaration episteme AUTHORING-USE-REL-2026, owned by AuthoringUseRelations@Project-31, declares source-premise use and review-reference use. With separate case facts, write: Authoring Work W-AUTHOR-31 used SourceNotes_31 as a premise, and Review Work W-REVIEW-31 used DraftEpisteme_31 as a reference. A saved file, bibliography entry, or handoff record supplies neither fact.

DraftFile_31 is a separately identified form-bearing entity, not DraftEpisteme_31. Rendering work, changed bits, or adjacency to the draft establishes neither the file's first existence nor a new episteme. When either first-existence question matters, ask A.15.PROD separately for the inception of DraftFile_31 or of already distinct LaterDraftEpisteme_31 and consume its local claim or exact blocker. File inception neither creates nor replaces the claim-bearing episteme.

When publication is current, exact publication occurrence PUB-31 is governed by E.24.PUB only while its five fixed participants—the selected episteme edition, audience declaration, bounded-use declaration, exact publication form, and presentation carrier—satisfy its availability predicate. Those participants together with the maximal continuous availability interval identify the occurrence. E.17 instead governs the multi-view face or form; it does not identify PUB-31. Publication or availability proves none of delivery, acceptance, transfer, access, reliance, or use by review Work, and the owner-local phrase selected episteme edition creates no edition continuity.

If ordinary handed off wording already names one exact transfer relation, apply its direct pattern and stop. A transfer package or handoff record establishes neither that transfer nor use by the receiver. Apply E.10.MOVE only when the wording still hides an FPF-governed move, workflow, next action, or readiness claim; its recovery creates no process move, transfer, Work, permission, or receiving-use relation. This case demonstrates identity first, conditional edition continuity, direct source or review use, exact publication identity, and bounded transfer routing.

#Bias-Annotation

Lenses tested: Gov, Arch, Onto/Epist, Prag, Did. Scope: Limited to recovering one method-or-work boundary claim after A.6.P has isolated it; not Universal governance for all relation ambiguity, work identity, production, evidence, publication, transfer, or receiving use.

The pattern deliberately weights Onto/Epist toward exact entities, relation kinds, claim distinctions, and non-invention, and Prag toward the shortest usable result from the four-exit architecture. Did puts ordinary wording and heterogeneous cases before heavier assurance. The Arch cost is coordination with several direct owners rather than one convenient input, output, or result architecture. The Gov boundary is that the accountable subject owner supplies, rejects, or reframes a missing governor; WMR cannot admit it. Mitigation is the three-question ordinary core, two conditional assurance questions, four truthful exits, and independent factually unsupported, missing-information, and missing-governor reasons, with future-owner routing only for the last. The following domain-bias rows are informative risk cues; they add no duties beyond the checklist.

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

Informative misuse examples. The Repair column describes the outcome of applying the checklist; it creates no additional imperative or world-side fact.

#Consequences

• Practitioners retain short ordinary sentences while downstream users can recover the exact relation and its orthogonal claim dimensions.
• Method, plan, work, operation application, actual change, production, evaluation, delivery, acceptance, transfer, and receiving use remain independently inspectable.
• Local missing-governor blockers reveal where subject ontology is absent without forcing a new public kind.
• One compressed phrase may split into several claims; that is the cost of preserving different obtaining conditions and owners.

#Rationale

Boundary words describe a relation position only relative to an exact object. Treating them as entity kinds or universal relations erases the subject pattern that decides obtaining. The three-question ordinary route restores the thing, related object, and direct verb or stop first; two conditional assurance questions expose claim dimensions and the formal governor only when those distinctions can change or check the answer.

Mint vs reuse. A.6.P.WMR introduces only this pattern id and its Tech and Plain labels; it mints no U-kind, relation kind, boundary-word family, result record, or work occurrence. The worked-case RelationKind tokens are explicitly assumed to have been published by named project relation-declaration owners; naming them in a case neither admits them into FPF nor republishes their declarations. It reuses each exact subject kind, direct relation, local A.6.RCD claim, and blocker under its own governor. Any durable name for a recovered entity, relation, or performed-work occurrence starts under F.18 only after this recovery closes.

The lightest truthful exit is preferred. A direct relation is cheaper than a local compound claim; a local claim is cheaper than reusable predicate semantics; an exact non-assertability result is more truthful than an invented universal relation. This economy preserves expressive project language while keeping occurrence identity and ontology growth demand-driven.

#SoTA-Echoing

Informative source comparison. These rows classify source use and its effect on the Solution; they add no practitioner or modeled-world obligation.

These sources answer different practice questions. Provenance, metrology, and project-planning vocabularies expose useful distinctions and recurrent compression risks; none admits an FPF kind, makes a work or participant relation obtain, or replaces the three-question ordinary route and its two conditional assurance questions.

The three-question ordinary route, two conditional assurance questions, and four-exit architecture are an FPF-scoped synthesis hypothesis for one claim whose exact thing is known while its work or method boundary relation or one material claim distinction remains hidden. The cited traditions neither establish that architecture nor authorize it outside this boundary. The synthesis reopens if repeated subject practice yields a stable direct governor that replaces a branch, or if a trigger case cannot close through one of the four exits without new ontology.

For a practitioner encountering one of these standard vocabularies, the action is the same: preserve its bounded provenance, measurement, or planning meaning, then ask what exact thing is named, relative to what exact object, and what direct verb or stop is justified. Open the two assurance questions only when a material ambiguity or receiving use needs them. The standard term is evidence about likely interpretation, not the direct relation's governor.

Currentness checked on 2026-07-21. PMI version 5.0 is the January 2026 Lexicon; the current public PeopleCert page presents Foundation Version 7 and seven broad practices but no detailed product-planning semantics; the JCGM VIM3 2.9 entry remains the official online measurement-result definition; and the latest published PROV-DM remains the 2013 Recommendation, so it is used only as mature lineage. The adaptations reopen when PMI changes the relevant activity, work-package, output, result, or deliverable distinctions; when PeopleCert publishes or identifies an exact official locus for any detailed PRINCE2 product-planning distinction proposed as load-bearing here; when JCGM changes the measurement-result boundary; or when a successor provenance model changes usage or generation semantics for the declared comparison.

#Relations

• Specializes: A.6.P for the focused method-and-work boundary-word recovery case.
• Receives from: E.10 and E.10.ARCH only while their trigger and applicability checks leave the exact method-or-work boundary relation or a required claim dimension hidden; an already readable direct governor and complete claim dimensions bypass this pattern.
• Uses: A.6.RCD when exact participants are known but no direct relation closes the receiving claim; C.2.P for epistemic source expression and source-to-use recovery before the exact relation involving a Work occurrence is recovered.
• Coordinates with: A.3.1 method identity and generic participant meanings; A.3.2 method descriptions; A.6.1 actual operation applications and declaration-local bindings; A.15.1 dated work; A.15.2 intended work and plans; A.15.3 planned fillings; A.3.4 actual bounded change; and A.15.PROD production-work, entity-identity-inception, and production-completion recovery.
• Hands naming to: F.18 only after the exact governed value from a direct subject relation, exact A.6.1 application binding, or exact local A.15.PROD or A.6.RCD claim, together with its receiving use, is recovered. The fourth family—an exact non-assertability result independently reasoned as factually unsupported, missing-information, or missing-governor—does not authorize durable naming; only missing-governor is an ontology blocker that names the affected use and future owner. A durable performed-work name additionally requires the A.15.1 occurrence basis.
• Returns to: the direct measurement, evaluation, commitment, delivery, acceptance, transfer, resource, premise, source-use, transformation, evidence, assurance, publication, gate, decision, or receiving-work pattern that owns the recovered claim.
• Boundary: A.6.P.WMR owns the recovery method and ordinary direct sentence. It does not own direct subject ontics, create the work occurrence, make an operation binding obtain, admit a relation kind, supply evidence or warrant, or decide downstream reliance.

#A.6.P.WMR:End

Last Updated: 2026-07-22 — this section last modified in upstream FPF commit 6e7eeb93 (github.com/ailev/FPF)