A.3.2:5 - Archetypal Grounding

Across the slices below, recognize the claim-bearing episteme before examining how it is represented or published. Ask in this order:

Which admitted U.Method is its exact EntityOfConcern?
Which claim says something substantive about that method as a way of doing?
Is anyone proposing a use beyond membership? If so, name the use, its subject pattern, and the claims it needs; if not, stop at membership.
When expression or availability matters, which C.29 representation corresponds to the claims, which publication occurrence makes the selected edition available, which publication form expresses it, and which U.PresentationCarrier bears that form?

A.3.2:5.1 - Industrial procedure

A procedure episteme about EtchAl2O3@FabA qualifies when its claims state how the etching Method is done: gas-feed participant meanings, temperature bounds, chamber preconditions, intended etch profile, failure conditions, operator system-role kind, calibration capability threshold, or admitted parameter ranges.

A PDF publication form may express one edition of those claims, and a PLC ladder representation may correspond to some of them. A U.WorkPlan states the planned maintenance-window preparation; tool run W-143 is Work. A metrology result supports another claim only through the evidence relation for that claim.

Named-use replay — preparing WP-Etch-MW-47. The maintenance planner needs four claims before drafting this A.15.2 U.WorkPlan: the chamber is empty, inert, and leak-check complete before gas feed; the method’s temperature range is 58–62 °C; calibration is no more than 24 hours old; and pressure above the stated bound stops the run. EtchAl2O3-Description-e7 passes A.3.2 membership because it concerns EtchAl2O3@FabA and says how that Method is done. It also states all four needed claims. To verify that this is the current edition, the planner checks its ClaimGraph against publication occurrence Pub-Etch-e7, publication form EtchAl2O3-SOP-e7, and carrier FabA-MethodRepository-2026, plus the source trace from EtchDescriptionReleaseWork-e7, performed under EtchDescriptionMaintainerAssignment-4 with method trace ClaimGraphReleaseCheck-v2. A.10 path EP-Etch-e7-Plan47 links those sources to claim C-Etch-e7-has-Plan47-claims. Its bounded use is citing e7 while drafting WP-Etch-MW-47; unsupported uses are gate passage, authorization, safe execution, and a claim that Work occurred. Its window reopens when e7, RecipeWindow-Al2O3-3, the calibration rule, or a source named in the path changes. RelianceDisposition=pass therefore supports citing e7 only for this drafting use.

EtchAl2O3-Description-brief-e7 still passes membership because it concerns the same Method and states the gas-feed and temperature procedure. It omits the 24-hour calibration condition and pressure stop. A.10 path EP-Etch-brief-e7-Plan47 points to that brief edition and cannot evidence the two missing claims, so RelianceDisposition=blocked-current-use applies to drafting WP-Etch-MW-47. Reopen after selecting an edition that states both claims; until then the planner stops or selects another edition. Membership is unchanged. If the result must persist, C.2.1 is the pattern for its result episteme and ClaimGraph, A.10 is the pattern for the evidence path and disposition, and A.15.2 is the pattern for the plan.

A.3.2:5.2 - Optimization model

A U.MethodDescription episteme for the scheduling Method qualifies when its exact EntityOfConcern is JSScheduleV4@Plant2026 and its claims state how a production schedule is produced or evaluated. A MILP representation and an explicitly recovered solver-configuration representation can stand in declared correspondence to those claims.

A separate formal-substrate episteme can make claims about variables, constraints, objective, admissible solution set, or invariants. A publication form expressing that episteme may be borne by the same presentation carrier. A timestamped solver run is work. A selector mechanism, if declared, is governed by A.6.1 and E.20. Solver search order does not by itself state the project work sequence.

A.3.2:5.3 - Proof script

An episteme about a reusable derivation or checking method qualifies when it identifies that U.Method exactly and makes a substantive claim about how the derivation or check is done. A proof-assistant script may represent those claims.

A concrete proof-checking session is work. Claims about a formal substrate, a theorem, or evidence for the theorem remain separately governed even when publication forms expressing those epistemes are borne by the same carrier. A publication occurrence makes a selected edition available to an audience for a bounded use.

A.3.2:5.4 - Clinical guideline

A guideline episteme qualifies when its exact EntityOfConcern is AcuteAppendicitisTriage@HospitalContext and its claims state the triage Method through patient-information and resource participant meanings, exclusions, decision criteria, relevant local system-role kinds and capabilities, intended effects, or failure response. A publication form expresses one selected edition, and a publication occurrence can make that edition available; approval status remains a separate claim.

Patient-specific dated enactment is a Work individual admitted under U.Work. If a causal claim relies on a triage disposition, diagnostic finding, or measurement result, name that premise and apply C.28. Merely using the guideline during Work establishes neither a causal effect nor a causal-use result.

A.3.2:5.5 - Workflow diagram

An episteme whose claims state one reusable method may qualify as U.MethodDescription; a BPMN or object-centric process model may represent those claims. A diagram can also represent a work plan, event-log model, or independently selected structure, so its notation does not settle the exact EntityOfConcern.

If readers treat the diagram as a route that tokens or workers must follow, compare that reading with the source claim. Keep an ordered sequence only when the method claim actually states one. When order comes only from layout, use C.2.P.DR and stop at the represented graph, constraints, objects, or events.