A.3.1:5 - Archetypal Grounding

Across the slices below, recognize a U.Method by a stable project answer to this question:

For these kinds of participants and conditions, what reusable way should a future enactment follow; what should it observe, compare, classify, decide, derive, change, produce, control, or preserve; what result or preserved condition is intended; and when should it stop?

Non-transformative method replay. DuplicateDefectReportComparison applies to two defect reports for the same product and release when both contain the required symptom and version data. An evaluator enacting it compares those fields and records same incident, different incidents, or insufficient information; missing version data is a stop. These facts identify the reusable comparison method.

Actual-transformation branch. The filled Etch_Al2O3 replay in 5.1 closes the reusable method without actual-change facts. If a later assertion says that Wafer-22 changed during Work W-143, identify the Work under A.15.1 and the actual transformation of Wafer-22 under A.3.4 separately; connect them only through a declared predicate or return missing-governor[work-to-change].

Manufacturing, optimization, proof, graph or query overread, and clinical triage differ in material, representation, and assurance needs, but they share the same method-identification question. The archetypal failure is also shared: a nearby description, plan, run, mechanism, formalism, or evidence relation takes the method name and silently changes what the project can rely on.

A.3.1:5.1 - Manufacturing recipe

Situation. A fab process engineer must decide whether two current SOP editions describe the same alumina-etch method before either description is cited in a work plan. The engineer needs a reusable method identification.

Reusable way and applicability. Etch_Al2O3 applies to alumina-coated silicon wafers whose substrate class and coating range satisfy RecipeWindow-Al2O3-3, using a qualified PE-4 plasma-etcher family and the gas-mixture range declared by that window. Its generic participants are the wafer surface, qualified etcher, admitted gas mixture, and target-depth parameter. A future enactment holds the admitted pressure and temperature envelopes, adjusts exposure until the declared target-depth stop, and preserves the substrate and maximum-temperature conditions.

Preconditions and stop. The method is applicable only when the wafer material and coating range are known, the selected PE-4 calibration is current for the planned use, the admitted gas mixture is available, and the safety interlocks required by RecipeWindow-Al2O3-3 are part of the intended setup. If the recipe fails to state the material/coating range, calibration requirement, gas mixture, target-depth stop, or preservation limits needed to identify the way, keep alumina etch as a method cue until that meaning is recovered. If a particular wafer or setup fails the stated range or calibration requirement, retain the identified Method and stop that planned use under its applicable admission or gate rule.

Visible identification result. Under effective FabProcessScheme-2026, where Al2O3, target depth, and substrate preservation have the local senses used above, the engineer can write:

MethodRef: Etch_Al2O3
SemanticBasisIfMeaningVaries: FabProcessScheme-2026 (`Al2O3`, `target depth`, and `substrate preservation`)
Applicability: alumina-coated silicon wafer; RecipeWindow-Al2O3-3; qualified PE-4 family
GenericParticipantMeanings: wafer surface; qualified etcher; admitted gas mixture; target-depth parameter
MethodConcern: remove the admitted alumina layer to the declared target-depth stop
Preconditions: material and coating range known; calibration current; gas and safety setup available
IntendedResultOrPreservedCondition: target depth reached; substrate and maximum-temperature bounds preserved

This result lets the engineer compare the two SOP claim sets against one method identity and lets a later work plan cite that method and the selected description edition. The SOP, PLC program, calibration recipe, and supplier note remain U.MethodDescription candidates when A.3.2 identifies what each episteme describes (EntityOfConcern) and the substantive claims it carries. For later work authorization or claims that Work W-143 occurred or Wafer-22 changed or passed metrology, use the relevant A.15.2, A.15.1, A.3.4, measurement, evidence, assurance, or gate pattern.

A.3.1:5.2 - Optimization model

Situation and reusable way. JS_Schedule_v4 applies when the jobs, eligible machines, durations, precedence constraints, feasibility rules, and optimization objective are all stated for the scheduling problem. A planner or solver system enacting it constructs candidate assignments, rejects infeasible candidates, compares the remainder by the declared objective, and records the selected schedule or no feasible schedule. Missing precedence data, an unstated objective, or incompatible machine eligibility is a stop rather than permission to guess a method variant.

This identification lets a planner compare two solver packages as descriptions of the same scheduling method. The MILP formulation and solver configuration are U.MethodDescription or formal-substrate candidates according to the claim. The selected production schedule is a U.WorkPlan; the dated solver run is Work; and its decision record is a separate result episteme.

A.3.1:5.3 - Proof or derivation

Gauss_Elimination applies to a matrix and right-hand side over a declared algebraic domain in which the required row operations and pivots are valid. A mathematician or proof system enacting it applies equivalence-preserving row operations until solved or echelon form is reached. A missing admissible pivot, unsupported division, or unspecified domain is a stop. The visible result here is a method identification that a later derivation may enact.

Recover the claim-bearing episteme expressed by a textbook explanation, proof-assistant script, or formal rule set; apply A.3.2’s membership test for Gauss_Elimination. A concrete proof-assistant run is Work, and the algebraic structure may be a formal substrate. Using the resulting proof for a project decision additionally needs an evidence or assurance relation.

A.3.1:5.4 - Graph or query overread

A graph path, SQL query, checklist predicate, or dashboard table may itself be the current direct object or may represent a relation, state, evidence structure, provenance structure, or publication face. It supports a method identification only when the project can separately state the reusable action, admissible inputs, branch criterion, intended result, and stop. A query text that returns rows is still a description or executable representation until that semantic way is stated.

Ordinary wording such as a graph “routes” or a query “calls” is usable when the operation and its participants are recoverable. Apply C.2.P.DR when a representation’s form or layout is treated as sufficient to establish method order, dated Work, gate passage, or authority.

A.3.1:5.5 - Clinical triage protocol

SepsisTriage_v3 applies to adult emergency-department presentations inside its declared population and assessment window. A clinician enacting it evaluates the stated signs and measurements, assigns an urgency class, and selects the next clinical response. Insufficient evidence, a patient outside the admitted population, or a presentation requiring another protocol is a stop. The visible result here is the reusable triage method and its boundary.

Recover the claim-bearing episteme expressed by the protocol PDF, order-set screen, or decision-support rule and apply A.3.2’s membership test for SepsisTriage_v3. Keep its carrier and publication form separate. A clinician’s dated assessment is Work. The physiological model or score formula may be a formal substrate or mathematical lens. Admission policy, treatment release, and evidence that triage reduced harm remain neighboring claims under their own patterns.