A.6.P.WMR:5 - 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.

A.6.P.WMR:5.1 - Inspection and machining: one ordinary result, 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 current question is when exact Work first constituted the report, apply A.15.PROD. If neither relation is governed, return missing-governor naming R-17, the proposed application or Work participant, proposed predicate, affected use, and absent definition; name a future pattern or declaration need only when one is identifiable. 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:

• Applying A.15.1 identifies 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 missing machining-resource predicate and its defining pattern or declaration.

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 contains the defining ClaimGraph for these case-local predicates:

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.

A.6.P.WMR:5.2 - 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 contains the defining ClaimGraph for SourceDatasetParticipatesInETLWork and DestinationDatasetParticipatesInETLWork; separate case facts say that RawOrders_0811 and WarehouseOrders_0811 satisfy the declared source-dataset and destination-dataset participant meanings and predicates for 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 missing analytics-decision predicate and receiving use. 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 and predicate and cites the SubjectPatternLocator for their defining or constraining content.

A.6.P.WMR:5.3 - 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 contains the defining ClaimGraph for 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 the content that supplies that predicate or criterion; a measurement or diagnosis does not establish a verdict, and a verdict does not establish the patient’s later health effect.

A.6.P.WMR:5.4 - 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 naming the ProblemCard and WorkPlan participants, proposed planning-use predicate, affected planning use, and absent definition; name a future declaration need only if one is identifiable. 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 contains the defining ClaimGraph for 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 and return missing-governor naming both participants, the proposed causation predicate, the affected use, and the absent definition. No receiver or future declaration is required to state that blocker. 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.

A.6.P.WMR:5.5 - 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 contains the defining ClaimGraph for StylingWorkConsumesResource and StylingWorkCausesHairArrangementChange; separate case facts support the work-change claim and, when known, the gel-consumption claim.

Write: Applying A.15.1 identifies 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, predicate, or applicability condition 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 subject patterns; none constitutes the hairstyle or follows from the photo.

A.6.P.WMR:5.6 - 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 contains the defining ClaimGraph for 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.

A.6.P.WMR:5.7 - Authoring: a produced explanation, its continuing use, and the next missing fact

An authoring note says, research notes were inputs; the draft was the output handed off to review. The reader needs to decide whether to review an available explanation, finish its construction, or recover a missing basis. This constructed case first obtains a positive answer through the existing suppliers, then changes one fact.

Identify what the author obtained. Under C.2.1, DraftEpisteme_31 has ClaimGraph G31, exact EntityOfConcern PreparationMethodProposal_31, and effective ReferenceScheme StudioPreparation-2026. G31 explains a proposed timing-correction procedure, its independently supplied error bound, and different limits for analysis and viewing. It is an episteme about a proposed way; writing it does not establish that the proposal is an identified Method or that a recording was edited.

If a later rendering leaves all three identity discriminators 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.

Obtain the production claim from A.15.PROD. In the positive case, an engineer’s Work supplies the bounded technical argument and an author’s Work connects that argument to the procedure and its uses. A.15.1 has independently established both occurrences, with their A.13 performer bases and enacted Methods, and their exact work-part relations to composite W-AUTHOR-31. The applicable authoring Method intends constitution of the complete explanation. The following is the case’s supplied A.15.PROD basis, rather than an inference from the words draft output.

For the author-side replay, case substrate AuthoringInceptionClaims-31-v1 uses A.15.PROD:4.7’s time-indexed conjunction of these named governed facts. It retains the Work parts and change witnesses, uses the supplied ordered candidate boundaries 10:00, 10:10, 10:20 and 10:30, and selects the first boundary satisfying all inception conditions. These are all content-constitution boundaries in the complete case history, not samples of an otherwise unobserved interval. That history makes the identity test false at the two earlier boundaries and true at 10:20. Unavailable premises remain undecided; their absence supplies no negative fact. The replay yields the local inception claim with EntityOfConcern = DraftEpisteme_31, indexed by the exact specification and applicability basis. These case declarations supply no universal authoring, change or result relation kind.

The useful sentence is now: “W-AUTHOR-31 jointly produced this explanation at 10:20; review its proposed procedure and stated limits.” Work continues until 10:30, so the inception result is not its completion claim. Production completion, acceptance and publication each retain their separate question.

This reuses the same production meaning as Ship 27 in A.15.PROD:5.2. There the produced participant is a U.System under an applicable hull-identity rule; here it is a U.Episteme under the applicable content-identity rule. In both cases, first existence through the governed effects of the identified Work is the result meaning. Neither the ship’s hull rule nor the author’s content rule is substituted for the other. The practitioner reuses A.15.PROD and the applicable subject definitions, rather than inventing a result predicate for each noun.

Remove one essential fact. Keep the two work identities, their composition, the observed manuscript change, the content-identity specification, its applicability and the first-satisfaction history. In this variant, the facts establishing which Work’s editing operations targeted Manuscript_31 and effected those edits are unavailable. The definition of authoredContentChange remains known. The result is missing-information for W-AUTHOR-31’s asserted link to ManuscriptContentChange_31. Recover that operation-and-target history before claiming production by this Work in the variant. The available explanation can still be reviewed on its content; the unresolved production attribution does not erase it. If the corresponding subject predicate had never been defined, the different result would be missing-governor; repeated authoring uses would justify developing that definition under A.6.RCD, not guessing the missing case fact.

Use the explanation outside its producing Work. Exact relation-declaration episteme AUTHORING-USE-REL-2026 supplies the already established source-premise and review-reference relations for this case. Its premise-use condition requires actual use of identified source claims in the Work’s stated inference; its review-reference condition requires an actual bounded comparison using the identified reference content. Separate case facts support: Authoring Work W-AUTHOR-31 used SourceNotes_31 as a premise, and Review Work W-REVIEW-31 used DraftEpisteme_31 as a reference. The latter Work compares another proposal’s viewing limit against G31’s stated condition. It does not produce DraftEpisteme_31 again.

When only the content-basis question is current, A.6.RCD:4.5a’s derivedUsingRuleContent or evaluatedAgainstRuleContent may already state it: name the exact dependent and base ClaimGraphs and the derivation or criterion-selection fact. Those predicates do not replace the separate Work-use claim above. A saved file, bibliography entry, or handoff record supplies neither actual-use fact. The next action after a missing reference-use fact is to recover the bounded comparison, not to assert that the reviewer benefited from receiving a file.

Continue a useful condition without replacing the result. A Method engineer can continue using that same explanation while its source-based qualification remains applicable. Suppose a source revision changes only the analysis limit. The applicable qualification rule requires the source argument, the selected use’s limits and its dependencies to remain supported. The recovered dependency facts show that the viewing argument and its 8 ms condition are unchanged; the analysis claim depends on the revised argument. The engineer may continue the viewing use and return the analysis claim for requalification. A second description or a new production claim is unnecessary for that continuation.

Now remove the dependency information needed to bound the source change. Continued viewing use becomes unresolved too; absence of a visible edit cannot establish unaffectedness. Recover the affected dependencies or widen the recheck. This is a repeatable application of the qualification rule to a new situation. Claiming additionally that maintenance Work kept a condition true throughout an interval would require that Work’s own predicate and interval facts. The useful preservation of an applicable result does not supply that further attribution.

Keep availability and transfer at their own scope. DraftFile_31 is a separately identified form-bearing entity, not DraftEpisteme_31. File inception and episteme inception are separate A.15.PROD questions. Rendering work or changed bits alone settles neither. When publication is current, exact occurrence PUB-31 obtains under E.24.PUB while its five fixed participants—the selected episteme edition, audience declaration, bounded-use declaration, exact publication form and presentation carrier—satisfy its availability predicate. Together with the maximal continuous availability interval, they identify the occurrence. E.17 governs the multi-view face or form instead. The declaration-local phrase selected episteme edition creates no edition continuity.

Established availability lets the named audience obtain that content through that form and carrier. Actual access, delivery, acceptance, transfer, reliance and review use still need their own facts. If ordinary handed off wording already names one exact transfer relation, apply its direct pattern and stop. A package or handoff record establishes neither transfer nor receiving use. Apply E.10.MOVE only when the wording still hides an FPF-governed move, workflow, next action or readiness claim; its recovery creates none of those occurrences or permissions.