Part B - Trans-disciplinary Reasoning Cluster

B.1 - Holon Aggregation and Part-Whole Construction

Type: Part B holonic construction pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.1:0 - Use This When

Use this pattern when a project needs to say how several admitted objects are considered as a whole, or when a whole-level claim depends on parts, collection belonging under the collection’s own rule, component structure, constructional grounding, or a selected aggregation rule.

Typical moments:

• a product, plant, dataset, paper, model family, organization, fleet, batch, or research program is discussed as a whole;
• a dashboard rolls part measurements into a whole-level characteristic;
• a team says that a method, role, graph, or algebra “decomposes” something and may be smuggling part-whole claims;
• a collection needs whole-level characteristics without becoming an acting collective system;
• an aggregation claim is being used for architecture, assurance, evidence, or MHT reasoning.

First useful move. Recover the claim kind before choosing notation: part-whole construction, collection belonging under the collection’s own rule, collection-as-whole grounding, a relation among local system-role kinds, a direct participation or assignment relation, method relation structure, work occurrence holarchy, selected architecture structure, or mathematical description. If claim-bearing source wording still says only “role,” use E.10.ROLE before choosing one of these branches.

What goes wrong if missed. Γ, graph, algebra, decomposition, factor, component, step, phase, and collection wording become one universal composition language. Roles and methods become parts; work occurrence evidence is inferred from method structure; a graph is mistaken for the structure; a collection becomes an acting whole by label.

What this buys. B.1 gives one doorway into part-whole construction while keeping its neighbors clean: A.14 is the pattern for relation vocabulary, C.13 is the pattern for constructional grounding, B.3.5 is the pattern for Working-Model assurance grounding, A.15.1 is the pattern for work-occurrence holarchy, and C.29 is the pattern for mathematical-lens use.

Not this pattern when.

• If the question is the local relation word, use A.14.
• If the question is constructive part-whole grounding, use C.13.
• If the question is assurance grounding for a working model, use B.3.5.
• If the question is an exact relation among local system-role kinds, use A.2.7; if it is classification, assignment, or a direct participation relation, state that fact through its own pattern and predicate. Send unresolved claim-bearing “role” wording through E.10.ROLE. Use the Method patterns for method relation structure and C.29 when a mathematical lens is relied on for the current claim.
• If the question is performed-work occurrence parts, use A.15.1.
• If the question is whole reidentification or emergence-family wording, use B.2 or B.2.P.

B.1:1 - Problem Frame

B.1 is not a universal algebra pattern. It is the holonic construction doorway for part-whole and collection-as-whole claims.

The older Γ material remains useful only after the ontology-side claim has been recovered. Γ, graph, algebra, tuple, matrix, embedding, and neural representation can express or check a selected structure; they do not decide by spelling that the current object is a holon, that the relation is parthood, or that a role, method, step, or work occurrence is a part of a holon.

B.1:2 - Problem

Without B.1:

1. Mereology and notation collapse. A graph or algebra is treated as the part-whole structure itself.
2. Roles and methods become parts. Role factors, method parameters, guards, steps, and compositions are read as holonic parts because the same word “decomposition” appears.
3. Work occurrence is inferred from plan. A method decomposition or schedule is treated as evidence that performed work had those parts.
4. Collections become acting systems. A set, list, batch, fleet, or community is treated as an admitted acting System or responsibility bearer from plural naming, a system-role kind or assignment, a Method, or Work. Admission of the acting collective remains an A.1 question; responsibility also needs the predicate, participants, and pattern or rule that defines it.
5. Emergence becomes rhetoric. A whole-level gain is explained by “synergy” or “more than the sum” without checking existing-whole explanations or B.2 whole reidentification.

B.1:3 - Forces

B.1:4 - Solution

Use B.1 as a discriminator and construction frame.

B.1:4.1 - Holon Aggregation Claim Frame

When part-whole construction is current, recover:

HolonAggregationClaim@Context:
  candidateWholeRef: U.Holon
  candidatePartRefs:
  aggregationPolicyRef?
  claimScopeRef?: U.ClaimScope
  qualificationWindowRef?
  identityOrRecognitionRule:
  partRelationRefs:
  constructionBasisRef?
  selectedStructureRef?
  wholeLevelCharacteristicRefs?
  assuranceGroundingRef?
  neighboringNonPartRelationRefs?
  mathLensOrRepresentationRef?

This is a claim frame, not a U-kind and not an acting record. It says what must be named before the aggregation claim is relied on.

Use:

• A.14 for ComponentOf, ConstituentOf, PortionOf, PhaseOf, collection belonging under the collection’s own rule, aspect, and related vocabulary;
• C.13 for constructional grounding such as sum, set, slice, or another accepted construction;
• B.3.5 when a working model relies on the part-whole claim for assurance or evidence;
• C.16 when the current output is a whole-level characteristic;
• A.1 and A.15 when the whole is claimed to be an acting collective system.

B.1:4.2 - Didactic Firewall

B.1:4.3 - Work Occurrence Holarchy

Performed work is different from structural composition.

A dated Work may have independently admitted temporal or operational parts under A.15.1. C.27 governs temporal claims, and B.1.4 aggregates recovered order or temporal relations when that is the question. Resource roll-ups use B.1.6; composing effects needs the direct relation and composition rule for those effects. Neither kind of calculation establishes Work parthood or makes a Method or role expression a holonic part.

Use A.15.1 when the claim needs occurrence identity, temporal coverage, Gamma_time, Gamma_work, episode policy, overlap policy, resource aggregation, or performed-work evidence.

B.1:4.4 - Mathematical And Representation Apparatus

Use Γ, graph, algebra, tuple, matrix, embedding, or neural representation only after the object under concern and selected relation are named.

Acceptable uses:

• a mathematical lens for a selected structure;
• a constructional expression for a part-whole claim already admitted by A.14 and C.13;
• a representation of dependency relations;
• a checking apparatus for invariants or conservative bounds.

Blocked uses:

• graph wording as parthood admission;
• algebraic factorization as role, method, or work parthood admission;
• source notation as a new U-kind;
• one fold rule as a universal replacement for the subject pattern.

B.1:4.5 - Existing-Whole Before MHT

Before declaring B.2 whole reidentification, ask whether the whole-level gain can be explained inside the existing whole:

• better parts;
• corrected part relation;
• improved measurement;
• role or method relation repair;
• work occurrence evidence repair;
• functional or architecture selected-structure repair;
• source, publication, or representation correction.

Use B.2 only when the whole itself must be reidentified.

B.1:5 - Archetypal Grounding (Worked Cases)

B.1:5.1 - Pump Skid

A pump skid can be a U.System holon whose parts include pumps, valves, controller, frame, and connectors.

B.1 recovers the holon aggregation claim. A.14 names component or portion relations. C.13 gives constructional grounding. C.16 carries whole-level characteristics such as maximum flow or pressure envelope. If a graph is drawn, it represents a selected dependency or structure; the graph is not the skid.

B.1:5.2 - Evidence Corpus

A corpus can be a collection under its own inclusion rule and a C.13 set account. This alone does not make it a holon. Treat an integrated claim-bearing corpus as a whole only after all six A.1 matters pass, including constructive part relations, assembly, a composition-grounded whole characteristic, and possible participation in a larger assembly. Coverage, source freshness, bias exposure, or evidential diversity may be collection-level characteristics without settling that stronger question.

The corpus does not become an acting system. A review board, script, or research team may instead be admitted as a System. If the current claim says only that it takes part in ordinary review or analysis, state the direct participation relation and stop there. If it says that the System performed admitted U.Work, recover that performer’s A.13 core and independently admit the Work under A.15.1. Add F.6 afterward only when the B.1 claim also needs precise assignment-bound attribution. A short B.1 sentence may omit an unused assignment identifier only when every relation it consumes remains recoverable. A local kind and a separate System-classification judgment remain independently optional. The corpus may be an episteme or publication-side object under its subject patterns.

B.1:5.3 - Method With Steps

A machining method has ordered steps and parameters. Those steps are method relation or method-description material. They do not prove that a performed machining run occurred, nor that the run had the same parts.

If the current claim is the method structure, use Method patterns and C.29 when algebra is selected. If the current claim is the actual run, use A.15.1.

B.1:6 - Bias-Annotation

B.1:7 - Conformance Checklist

B.1:8 - Common Anti-Patterns and How to Avoid Them

B.1:9 - Consequences

Positive consequences:

• B.1 can still use useful aggregation apparatus without letting apparatus choose the ontology.
• Holonic part-whole claims become reviewable.
• Role, method, work, math-lens, and publication descriptions stop leaking into mereology.
• B.2 has a cleaner entry condition: whole reidentification, not ordinary improvement rhetoric.

Costs:

• Users must identify the claim kind before choosing a notation.
• Some Gamma-heavy examples require a subject pattern before the notation is used: work occurrence evidence uses A.15.1, work-resource aggregation uses B.1.6, mathematical-lens reliance uses C.29, and whole reidentification first uses B.2.P and then B.2 when the problem remains current.
• Work occurrence analysis requires evidence and timing, not just a method plan.

B.1:10 - Rationale

The practical force of B.1 is conservative. Whole-level reasoning is useful, but it must be grounded in accepted part-whole relations, constructional discipline, and use of the applicable direct patterns. This lets FPF speak across physical systems, epistemes, work occurrences, bounded contexts, disciplines, and collections without growing a new type for every composed expression.

Mathematical apparatus remains available. It becomes more useful after the governed object is known: graph for dependency representation, algebra for selected composition rules, tuple for slot relation expression, matrix or embedding for analysis, and C.29 when a mathematical lens is relied on for the current claim.

B.1:11 - SoTA-Echoing

B.1:12 - Relations

• Builds on: A.1 for holon admission, A.14 for relation vocabulary, C.13 for constructional grounding, and B.3.5 for Working-Model assurance grounding.
• Coordinates with: A.15 and A.15.1 for method and work, A.22 and C.30 for selected structure and architecture, C.16 for whole-level characteristics, C.29 for mathematical lenses, and B.2 for whole reidentification.
• Refined by: B.1.1, B.1.2, B.1.4, and B.1.6 for selected dependency, system aggregation, contextual-temporal aggregation, and work-resource aggregation cases.

B.1:End

B.1.1 - Dependency Structure and Relation Grounding

Type: Part B holonic construction pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.1.1:0 - Use This When

Use this pattern when an aggregation, architecture, assurance, or construction claim depends on how candidate parts, members, phases, portions, or external relations depend on each other.

Typical moments:

• a dependency diagram is used to justify a whole-level claim;
• a graph mixes parthood, mapping, order, time, resource, and boundary-crossing relations;
• a project needs to know whether a relation is part-whole, dependence, representation, influence, source use, publication use, or evidence relation;
• a selected dependency structure will be expressed with a graph, table, matrix, or another mathematical or representation lens.

First useful move. Name the dependency relation under concern before choosing graph notation. Then decide whether it is part-whole, boundary crossing, order, temporal phase, resource, representation, evidence, publication use, source use, or another direct relation defined or tested by the applicable pattern.

What goes wrong if missed. A graph becomes the ontology; an edge named “depends on” carries many relation kinds at once; external influence becomes parthood; order and time are encoded as structure; and mathematical checks look precise while the relation being checked remains unclear.

What this buys. B.1.1 lets dependency material bear on B.1 aggregation without letting graph notation decide relation kinds.

Not this pattern when.

• If the current relation word is a mereology question, use A.14.
• If the current part-whole claim needs constructional grounding, use C.13.
• If the current object is architecture selected structure, use A.22 and C.30.
• If the current expression is mathematical-lens choice, use C.29.
• If the current question is performed work, use A.15.1.

B.1.1:1 - Problem Frame

B.1.1 separates dependency structure from graph representation.

A dependency structure can be ontology-side when a direct pattern has selected the relation under concern. A dependency graph is a mathematical or representation description of that selected relation structure. The graph may be useful, but it is not the holon, not the part-whole relation, and not the constructional grounding by itself.

B.1.1:2 - Problem

Without B.1.1:

1. Edge drift spreads. ComponentOf, a collection’s belongs-to relation, PhaseOf, SerialStepOf, RepresentationOf, source use, evidence relation, and control relation all become generic graph edges.
2. Boundary crossing becomes parthood. A power grid, supplier, teacher, measuring instrument, model, or source record is drawn as a part because it affects the holon.
3. Design and run objects mix. Planned structure, design description, actual work occurrence, and telemetry are placed in one dependency expression without a DesignRunTag or a distinction among the patterns that define those claims.
4. Acyclic graph discipline overclaims. A graph check says something about the drawing, but the ontology-side relation remains ungrounded.
5. Mappings become parts. A digital twin, dashboard, diagram, or architecture description is treated as a constituent of the object it describes.

B.1.1:3 - Forces

B.1.1:4 - Solution

Use dependency structure first; use graph representation second.

B.1.1:4.1 - Dependency Structure Frame

DependencyStructure@Context:
  dependencyQuestion:
  intendedUse?:
  claimScopeRef?: U.ClaimScope
  qualificationWindowRef?
  candidateNodeRefs:
  selectedDependencyStructureRef?
  dependencyRelationRefs:
  relationParticipantRefs:
  relationGroundingRefs:
  partWholeRelationRefs?
  boundaryCrossingRelationRefs?
  orderRelationRefs?
  temporalRelationRefs?
  resourceRelationRefs?
  representationRelationRefs?
  evidenceRelationRefs?
  publicationOrSourceUseRefs?
  designRunTag?
  definingOrTestingPatternRefs:

This frame records independently grounded relation claims and their participants. It is not itself a U.Structure. When the receiving use needs one selected dependency structure, recover all four A.22 identity discriminators: exact constituents, obtaining relation occurrences, applied constraints and named selection/use frame. The record refers to that structure and to the patterns defining its relations.

B.1.1:4.2 - Graph Representation

Use graph language only when a graph is the selected mathematical or representation lens:

DependencyGraphRepresentation@Context:
  representedDependencyStructureRef:
  nodeExpression:
  edgeExpression:
  graphPropertyChecks?
  mathLensRef?
  publicationOrViewRef?

The graph may express acyclicity, reachability, cutsets, weak links, flow, or traceability. Those checks apply to the graph expression and bear on the selected relation only when the rule for that relation admits the mapping. Use C.29 to state the mathematical representation correspondence, preserved and lost distinctions, and validation boundary on which that inference depends.

B.1.1:4.3 - Relation Grounding Guide

B.1.1:4.4 - Graph Checks Are Conditional

Acyclicity, topological order, cutset, reachability, and flow checks are useful only after the graph is selected as a lens over a selected relation structure.

Do not infer:

• parthood from graph adjacency;
• independence from graph separation without a rule that makes the selected relation support that inference;
• performed work from a planned step graph;
• whole reidentification from a graph property without B.2;
• architecture from a graph without an exact described holon, selected structure, and architecture relation or claim.

B.1.1:5 - Archetypal Grounding (Worked Cases)

B.1.1:5.1 - Plant Supplier

Source graph: PowerGrid -> Plant.

If the edge means electricity supply, recover that exact supply relation. It establishes neither plant parthood nor its absence. Test a separate part-whole claim under the chosen whole’s identity and parthood rules; an independently admitted internal power subsystem can be both a supplier and a part.

B.1.1:5.2 - Digital Twin

Source graph: DigitalTwin -> Turbine.

If the edge means representation, recover the architecture-description, publication, source-use, evidence, or digital-twin relation. The digital twin is not a turbine component by graph adjacency.

B.1.1:5.3 - Work Plan And Work Occurrence

Source graph: Prep -> Weld -> Paint.

If the graph describes a method or process view, use the patterns that define the method, description, and order claims. If it describes performed Work, use A.15.1 with occurrence identity, timing, evidence, and the exact Work relation. Do not let the same graph do both jobs.

B.1.1:6 - Bias-Annotation

B.1.1:7 - Conformance Checklist

B.1.1:8 - Common Anti-Patterns and How to Avoid Them

B.1.1:9 - Consequences

Positive consequences:

• Dependency views become useful without becoming hidden ontology.
• External influences can be discussed without corrupting parthood.
• Graph checks keep their value and their limits.
• B.1 aggregation receives cleaner part-whole inputs.

Costs:

• A diagram alone is no longer enough; relation kinds and the patterns that define or test them must be named.
• Some compact dependency graphs need multiple relation layers or views.
• Graph-based checks may need C.29 when the mathematical lens is relied on.

B.1.1:10 - Rationale

Dependency language is useful exactly because it is broad. That breadth is also the danger. FPF keeps the breadth for recognition, then restores precision by separating relation kinds, selected structures, mathematical expressions, and publication forms.

B.1.1 therefore does not abolish dependency graphs. It makes them honest: a graph represents a selected relation structure; each direct relation is grounded by the facts and rule that make it obtain.

B.1.1:11 - SoTA-Echoing

B.1.1:12 - Relations

• Builds on: B.1, A.1, A.14, C.13, and A.6.5.
• Coordinates with: A.15.1 for work occurrence, B.1.4 for contextual and temporal aggregation, C.29 for graph as mathematical lens, A.22 and C.30 for selected structure and architecture, C.30.AD and C.30.AD.BA for architecture description and digital-twin cases.
• Can contribute evidence to: B.2 when dependency evidence bears on whole reidentification after existing-whole explanations fail.

B.1.1:End

B.1.2 - Coordinate Decisions About System Aggregation and Delimitation

Type: Part B holonic construction pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.1.2:0 - Use This When

Use this pattern when one exact entity recognized under the already admitted U.System kind, or one exact entity still being evaluated under A.1 for that kind, is being considered as a whole and an engineering decision depends on coordinating its independently governed part-whole, delimitation, crossing, function/bearer, and whole-characteristic claims.

Typical moments:

• a machine, plant, robot, vehicle, building asset, service organization, or operating unit is proposed as a whole assembled from exact constituents;
• a system-level characteristic is to be rolled up from constituent characteristics;
• a supply, signal, measurement, control, source, publication, evidence, or transformation relation is being mistaken for a part relation;
• a functional element must be distinguished from and allocated to physical, organizational, software, or operational bearers;
• a named decision needs one recoverable view of the system boundary, exact crossings, and compatibility choices without turning that view into the system.

First useful move. Name the exact whole and its A.1 recognition status, the decision being made, and each load-bearing claim. For every claim, select its subject pattern and either recover the exact result or state the exact missing governor or information. Only then ask whether their joint organization itself changes the named decision.

What goes wrong if missed. System aggregation becomes a drawing exercise. Ports, suppliers, documents, digital twins, dashboards, source records, and measuring instruments become components by placement. Functional elements become physical parts by label. External change or measurement is read as containment. One convenient record then appears to establish all those unrelated facts.

What this buys. B.1.2 coordinates one engineering aggregation decision while leaving system recognition, exact parthood, assembly, delimitation, crossing, function, bearer, characteristic, evidence, description, representation, and decision claims with their subject patterns.

Not this pattern when.

• If the exact entity has not yet been evaluated under the already admitted U.System kind, use A.1; do not promote the proposal into a durable kind-like label.
• If one exact part-whole relation is the question, use A.14 and its direct specialization.
• If constructive assembly grounding is the question, use C.13.
• If the question is a functional claim, use its direct behavior or realization predicate; use A.6.F when the function wording is unresolved and C.30.ASV when architecture-view conformance is needed.
• If bearer allocation or parthood is the question, use the direct allocation or part-relation pattern; use A.6.M only when module or interface wording needs repair.
• If a mathematical aggregation lens is the question, use C.29.
• If the question is project system-of-interest designation, system-role assignment, Work, transformation, service or access, evidence, description, or publication, use that subject pattern; B.1.2 neither identifies nor defines those relations.

B.1.2:1 - Problem Frame

B.1.2 specializes B.1 for system holons, but it is a coordination method rather than the source of one omnibus system-aggregation relation. The useful engineering question is which exact independently governed facts must be considered together for one aggregation or delimitation decision.

Keep five frequently collapsed objects distinct:

1. The exact system whole. It is independently recognized under A.1 and its direct identity rule.
2. Its environment. In this pattern, environment means the exact external referents and exact crossing relations made relevant by a stated delimitation and use. It is not a generic surrounding object; an exact medium is named separately when that medium is itself the subject.
3. An actual containing system. The larger system of which S is an admitted part exists for this claim only when an exact part-whole relation independently obtains. Interaction or spatial surrounding is not enough.
4. The project system-of-interest. Project designation or selection is a separate claim from U.System identity, environment, parthood, system-role kind or assignment, and architecture. B.1.2 does not derive it from a box or aggregation decision.
5. Use qualification and neighboring relations. Context is not one world-side container supplied by B.1.2. When claim scope, effective reference scheme, or a bounded model-use structure qualifies a use, recover that exact qualifier under its subject pattern. Recover any system-role assignment or other neighboring relation separately. None delimits the system, identifies its environment, or establishes containment by itself.

For a system-aggregation decision, use :4.1 to recover the system, parthood, delimitation, crossing, and whole-characteristic results or their blockers. Use :4.2 only when their joint organization changes that decision.

B.1.2:2 - Problem

Without B.1.2:

1. Boundary by drawing. A box in a diagram is accepted as system delimitation.
2. External relations become parts. Suppliers, grids, sensors, controllers, teachers, measuring instruments, or digital twins are placed inside the system because they interact with it.
3. Functional and physical structures collapse. A resistor symbol, control function, chassis function, or service label is treated as a physical component by name alone.
4. Whole-level characteristics lack grounding. Mass, capacity, reliability, safety, throughput, assurance, or agency-like characteristics are rolled up without saying which bearers, relations, and scales support the claim.
5. Transformation becomes containment. A tool, teacher, actuator, script, or controller changes a holon and is then treated as its part or containing whole.
6. Coordination record becomes ontology. One aggregate-shaped record silently creates systemhood, parts, boundary, crossings, allocation, evidence, and representation instead of pointing to independently governed facts.

B.1.2:3 - Forces

B.1.2:4 - Solution

Use B.1.2 to coordinate one named system-aggregation or delimitation decision across independently governed results. Do not introduce SystemAggregationRelation@Context, HolonDelimitationRelation@Context, HolonBoundaryCrossingRelation@Context, or another record-shaped relation merely to hold the answers together.

B.1.2:4.1 - Recover Each Direct Result Or Blocker

Naming those results together does not create a further world-side relation. Stop at the first direct blocker that prevents the named decision; do not weaken it into an aggregate-shaped placeholder.

B.1.2:4.2 - Select A Structure Only When The Joint Organization Matters

If the joint organization of several exact results itself changes the named decision, select one ordinary U.Structure under A.22. Recover all four identity discriminators: exact independently identified constituents, exact selected obtaining relation occurrences, exact constraints as applied, and one named selection-use frame with its admissible action or stop.

The selected structure is non-agentive. It creates no system, part, crossing, allocation, characteristic, evidence, or decision fact and does not become the system, its environment, or its containing whole. A box, list, graph, table, description, view, or publication can represent or describe the selected organization but supplies none of the four discriminators by form.

B.1.2:4.3 - Make Interface Choices About Exact Crossing Relations

When the aggregate exposes, namespaces, internalizes, excludes, or leaves a crossing with its subject pattern, make that choice about one exact crossing-relation occurrence and one named use. These words are ordinary decision options, not a closed FPF enumeration and not another relation kind.

Name the direct world facts, affected endpoints, exact crossing predicate and occurrence, preserved obligation or information, evidence if relied on, and the C.11 ChoiceResult or C.32.PAD ArchitectureDecisionRelation@Project that chooses among the ordinary interface options when its exact predicate applies. A different choice passes only after its exact subject assertion, predicate, and result are named; otherwise stop with the established missing-governor blocker, whose content identifies the absent exact predicate source. If a later use must inspect the choice, identify a separate C.2.1 episteme whose claim content describes it and cites that direct result; the episteme does not make the crossing, parthood, compatibility, or decision fact obtain. This preserves interface accountability without an omnibus compatibility-check object. Without that account, an apparent simplification can silently drop an external obligation or proliferate unmanaged endpoints.

B.1.2:4.4 - Whole-Level Characteristics

Roll up system-level characteristics only after the exact bearer, characteristic relation or assignment, scale, and aggregation or inference rule are selected under their subject patterns.

Useful families include:

• additive quantities such as mass, cost, energy stock, or material amount;
• limiting quantities such as pressure rating, weakest connector, safety class, or availability bottleneck;
• logical or capability claims such as emergency-stop availability or vulnerability exposure;
• architecture characteristics that depend on selected structure.

Use C.16, A.19, and C.29 when characteristic space, scale, threshold, or mathematical lens is relied on for the current claim. Use B.2 when redundancy, closure, or coordination creates or reveals a whole that must be reidentified.

B.1.2:4.5 - Functional Elements And Bearers

A functional element in a functional view is not automatically a system part. Recover the functional claim and its intended behavior, the exact bearer under its own kind and identity rule, the independently established realization or allocation relation, and any obtaining parthood relation. C.2.1 identifies a claim episteme when one must be cited; C.30.ASV qualifies an architecture structural view when that is the use.

Use A.6.F only to resolve an unclear function expression and A.6.M only to resolve module or interface wording. Neither pattern admits the bearer or establishes allocation or parthood. One bearer can realize several functions and one function can require several bearers when the direct domain relations support those claims.

B.1.2:5 - Archetypal Grounding (Worked Cases)

B.1.2:5.1 - Pump Skid

A pump skid may be one exact entity proposed for recognition under the already admitted U.System kind. Pumps, frame, valves, controller, and connectors become its components only when their exact A.14 part-relation occurrences obtain and C.13 grounds the assembly; the proposal, drawing, and component list establish none of those facts.

The power grid, maintenance crew, telemetry dashboard, and supplier are not skid components merely because the skid depends on them. Recover the exact systems or epistemes and their supply, work, telemetry, publication, source-use, or other direct relations. If a maintenance-isolation decision needs their joint organization, an A.22 selected structure may include the exact obtaining crossings without turning them into parts.

Concrete coordination result. In an illustrative component-inventory case, skid S is already recognized under A.1. Inspection and assembly evidence have established the A.14 component relations of pump P, frame F, valve V and controller C to S, with the C.13 assembly basis. The inventory is complete for this example. A documented electrical-supply relation has grid G as source and S as receiver; dashboard D is an episteme describing S. These independently supplied facts are the inputs to the decision, not conclusions inferred from the drawing.

For the question “Which of these objects belongs in S’s component inventory?”, B.1.2 returns P, F, V and C, retaining each part relation’s basis. G remains an external supply participant and D remains a description. The inventory establishes no total mass, reliability or safe-isolation conclusion: each would need its own characteristic rule or decision basis. If inspection instead leaves V’s part relation unresolved, return the three established components and that specific gap; do not present the inventory as complete. Changed assembly or supply facts reopen the affected result.

B.1.2:5.2 - Resistor In A Circuit

A resistor symbol in a circuit diagram is a functional or design-description element. The physical bearer may be a packaged resistor, a length of wire, a transistor region, or a module. Recover the exact function, bearer, allocation or correspondence, and any part relation separately; B.1.2 only coordinates them for the current circuit decision.

B.1.2:5.3 - Digital Twin Of A Building Asset

A BIM model, asset register, dashboard, or digital twin may describe the built asset and its systems. It is not the asset’s part by being linked in a model. Use architecture-description, publication, evidence, source-use, representation, and naming patterns for the description side; use exact part-relation patterns only for admitted system parts of the built asset.

B.1.2:5.4 - Lathe And Workpiece

The lathe can change the workpiece through a bounded transformation and work occurrence. Those facts do not make the workpiece a lathe component or make the lathe the larger whole containing it. Use A.3.4, A.15.1, A.12, and the exact crossing or participation pattern; use part-whole only when an exact relation independently obtains.

B.1.2:5.5 - Bias-Annotation

B.1.2:6 - Conformance Checklist

B.1.2:7 - Common Anti-Patterns and How to Avoid Them

B.1.2:8 - Consequences

Positive consequences:

• System aggregation remains practical for engineering systems and organizations.
• Boundary and interface concerns become explicit subject-pattern work without omnibus relation or check objects.
• Functional architecture, module allocation, and physical parthood stop collapsing into one diagram.
• Digital-twin and publication artifacts stay on the description side unless an exact stronger relation predicate is defined and current facts satisfy it.

Costs:

• Engineering diagrams used for decisions need annotations that name the exact relation and its defining pattern or declaration.
• Some familiar component lists must be split into physical parts, functional elements, external systems, sources, and descriptions.
• Whole-level characteristic claims need scale and relation discipline.

B.1.2:9 - Rationale

System aggregation is the place where holonic thinking is most tempting and most useful. It is also where false parthood is easy: anything connected, measured, represented, or controlled can be drawn inside a system box.

B.1.2 preserves the engineering payoff by coordinating exact subject-pattern results for recognition, parthood, assembly, delimitation, crossings, function, bearer, characteristic, evidence, and description. It selects one ordinary A.22 structure only when their joint organization changes the named decision.

B.1.2:10 - SoTA-Echoing

B.1.2:11 - Relations

• Builds on: B.1, A.1, A.14, C.13, A.22, and the direct relation patterns selected for the current decision.
• Coordinates with: A.6.F for function wording, A.6.M for module/interface wording, direct subject patterns for bearer identity and allocation, A.22 and C.30 for selected structure and architecture, C.16 and A.19 for characteristics, C.29 for mathematical lenses, A.3.4 and A.12 for transformation and acting-side externalization, and C.30.AD or C.30.AD.BA for architecture-description cases.
• Can contribute evidence to: B.2 when system aggregation no longer explains the whole-level claim and whole reidentification is needed.

B.1.2:End

B.1.3 - Knowledge Aggregation (Γ_epist): Synthesis and Target-Scheme Compilation

At a glance. Use B.1.3 to compose exact U.Episteme inputs into one knowledge aggregate while preserving provenance, conceptual fit, context, and the warrant each source actually contributes.

Use this when. Use this pattern when a named synthesis or compilation use depends on how claims, models, datasets, or arguments are combined, and the aggregation must keep source, mapping, conflict, order, and temporal qualifications inspectable.

Not this pattern when. Use C.2.1 for episteme identity and edition continuity, A.14 for a proper temporal restriction of one unchanged episteme, A.15.1 for Work parts or occurrences, B.1.4 for a bounded aggregation of already recovered order or temporal relations, and B.3 for the assurance claim that consumes the aggregate.

What changes in practice. Identify the target claim, each input’s support role and dependencies before combining them. Return a justified calculation or a reasoned synthesis with its limitations; preserve provenance and conflicts. Return identity, edition, temporal restriction, Work, publication, and assurance questions to their subject patterns.

► decided‑by: A.14 Advanced Mereology A.14/C.2.1 compliance — Use ConstituentOf for semantic parts and PortionOf only for quantitative splits of texts/data with declared μ. Use PhaseOf only for a proper interval of one unchanged C.2.1 episteme. When a MethodDescription or document episteme’s claim content, EntityOfConcern, or effective ReferenceScheme changes, identify another episteme and assert EpistemeEditionRelation only when its historical-continuation predicate obtains. Work segmentation uses A.15.1; no ComponentOf is used here.

Plain‑English headline. Γ_epist composes epistemic holons (claims, models, datasets, arguments) into a single episteme while preserving provenance and distinguishing the support, limitations, and conceptual mappings on which its conclusion depends. B.3 governs the meaning and model of any assurance calculation. This is a semantic and evidential composition, not a physical sum or a universal confidence fold.

B.1.3:1 - Problem frame

• Holonic foundation. In the FPF, a U.Episteme is a holon whose identity is knowledge-bearing (A.1). It can be a statement/claim, a model, a theory, a specification, a dataset with semantics, or a compiled claim-bearing synthesis.
• Strict Distinction (A.7). We separate: structure (what the episteme comprises), order (argument flow), identity and history (C.2.1 identities and edition relations), proper temporal restriction (A.14), work (what was spent to produce/validate it), and values (objectives/criteria). Γ_epist stays in the structure/semantics lane and calls out to Γ_ctx/Γ_time/Γ_work only after their direct inputs are recovered.
• Mereology (A.14). For knowledge composition we primarily use ConstituentOf (logical or semantic parts), UsageOf or ReferenceTo (external reliance), and each collection’s own belongs-to rule for collections such as anthologies or corpora. We do not use ComponentOf (physical) in Γ_epist. PhaseOf may restrict the same unchanged episteme to a proper interval when its complete C.2.1 identity triple remains fixed. Distinct labelled versions or revisions require distinct C.2.1 identities when a discriminator changes and an independently obtaining EpistemeEditionRelation for any claimed historical continuation. Knowledge does not act and acquires neither a work-facing local system-role kind nor an assignment. Ordinary prose may say, for example, “the researcher synthesized the sources”. If the receiving use does not identify that action as one particular dated U.Work occurrence, stop with the ordinary sentence. If it does, recover each actual performer’s A.13 core and independently admit the occurrence under A.15.1. Add F.6 only when the receiving use also needs precise assignment-bound attribution; a short local projection may omit an unused assignment identifier only when every consumed relation remains recoverable.
• Assurance (B.3). Keep F (Formality), G (ClaimScope), and R (Reliability) distinct. Identify the meaning, scale, and receiving use of each value before calculating with it. A mapping’s CL summarizes one relation’s fit; its ordinal rank is not a numerical loss of reliability. Preserve provenance and make any unsupported inference or semantic crossing visible. Formality or mode does not supply a missing warrant model.
• Order/time flavours. Argument sequences may need Γ_ctx (non-commutative ordering of premises to conclusion). Knowledge evolution first uses C.2.1 to identify exact epistemes and any obtaining edition relations; B.1.4/Γ_time may then aggregate already recovered temporal restrictions, relation order, deprecation, or update windows for a bounded use. The aggregation creates neither identity nor continuity. Open B.2 only if the synthesis leaves a genuine whole-reidentification question after the existing-whole explanation check and identifies an exact candidate new whole; new wording or explanatory gain alone is not MHT.

B.1.3:2 - Problem

Naive aggregation of knowledge holons causes recurring failures:

1. Unsupported confidence folds. Averaging incomparable scores can hide conflict; a compulsory minimum can discard useful complementary support or overstate the probability of several necessary conditions. Both violate B.3 when their inputs and dependency model are unjustified.
2. Provenance erasure. Merges that drop sources, methods, or links break A.10 Evidence Graph Referring and make results unauditable.
3. Semantic drift. Folding across mismatched concepts without explicit mappings (and their CL) yields incoherent composites that look formal but mean nothing.
4. Order blindness. Arguments with essential dependency order (premise ⇒ lemma ⇒ conclusion) are treated as sets; non‑commutativity is lost and results become non‑reproducible.
5. Semantic-context chimeras. Combining claims whose local senses or reference schemes differ, without exact mappings and—when meanings cross—an F.9 Bridge plus a separately warranted bounded-use claim, silently corrupts claims and inflates R.
6. Category errors. Applying a physical quantity’s addition rule to truth, or averaging ordinal formality, ignores the value’s meaning and scale. Use C.16 for admissible scale operations and B.3 for the warranted support inference.

B.1.3:3 - Forces

B.1.3:4 - Solution — Terms, operator family, invariant Standard, core rules

B.1.3:4.1 - Terms (didactic recap)

• U.Episteme — a claim-bearing knowledge holon. C.2.1 identifies it through the participant-determined EpistemeConstitutionRelation over <claim content, exact EntityOfConcern, effective ReferenceScheme>. ClaimGraphSlot, EntityOfConcernSlot, and ReferenceSchemeSlot name participant meanings only inside that relation’s reusable declaration; they are not internal slots of the episteme. Empirical grounding uses the separate EpistemeEmpiricalGroundingRelation, while text, code, figures, datasets, SCR/RSCR references, publication forms, and presentation carriers remain separately governed provenance, representation, publication, or carrier material.
• Evidence/Provenance Graph — an A.10 descriptive account whose edges cite independently established direct support, source, measurement or use relations. Display labels such as evidences do not create generic relation kinds.
• Semantic mapping — the exact correspondence rule used by this composition. When it crosses semantic contexts, identify the source and receiving F.17 SchemeSenseCell values and an obtaining F.9 Bridge; keep the proposed use, direction, use-specific rule, permitted loss, reliance, and CL evidence summary separate. F.9 does not require CL for every Bridge; B.1.3 requires the summary for a mapping used in its support account. CL alone neither grants the use nor supplies a numerical penalty.
• SCR — a U.SCR that lists all symbol carriers included in the aggregate; never dropped.
• Semantic context — Plain shorthand for the local interpretation basis recovered from one exact F.17 SchemeSenseCell as <ReferenceScheme, LocalSenseClaim>. It is not another operation argument or entity. Crossing between two such contexts uses F.9 and the separate bounded-use and reliance steps above.

Didactic reminders. • Knowledge does not act. A researcher or engineer may use it while performing Work. Recover the exact System and Work only when the receiving claim consumes them; use A.12 only when the acting-side distinction is itself current. • A collection’s own rule establishes which epistemes belong to it; belonging is not a semantic argument link and does not by itself make a holon. Use ConstituentOf for logical or evidential composition. • PhaseOf is only a proper temporal restriction of one unchanged episteme. Changed C.2.1 discriminators identify another episteme; test EpistemeEditionRelation separately. Use MHT only for a remaining whole-reidentification question, not as a substitute for C.2.1 identity.

B.1.3:4.2 - The operator family (companion flavours)

To keep design vs run clean (A.15), Γ_epist has two companion flavours that share the same algebra but answer different semantic questions. Their declarations contain only the values on which the result depends. A performer, local system-role kind, or assignment is therefore not an operator argument: the same fold can be specified before staffing and can be applied in Work performed by different Systems without changing its result semantics.

When one particular operation application matters, use A.6.1 for that application and its argument and result bindings. A practitioner sentence may still say “the engineer compiled the guidance”. If no particular dated U.Work claim is current, that ordinary sentence needs no classification or assignment apparatus. If one is current, recover every actual performer System’s A.13 core and independently admit the Work under A.15.1 from its performance history, enacted Method, temporal extent, and containing System. Add F.6 afterward only when precise assignment-bound attribution is current. A short B.1.3 projection may omit an assignment identifier unused by its receiver only when every relation it consumes remains recoverable. An operation result binding says which value the application returned; it establishes neither production nor first existence of that value, publication, release, acceptance, nor a carrier. Open A.15.PROD or the publication patterns only when one of those separate questions is current.

Synthesis (design-time semantic fold). Compose exact input epistemes into a draft aggregate.

Γ_epist^synth : ( D_know : DependencyGraph< U.Episteme > ) → U.Episteme

• Domain. D_know designates exact source epistemes and the governed ConstituentOf, UsageOf, ReferenceTo, evidences, derivesFrom, and collection-specific belongs-to relations that obtain among them, together with the mappings used by the fold. The graph represents those objects and relations; it does not make them obtain.
• Result. One synthesized episteme whose claim content, exact EntityOfConcern, and effective reference scheme satisfy C.2.1. Its ClaimGraph integrates the retained content; provenance and SCR keep contributing sources and carriers traceable. State its formal basis, scope, and supported conclusion with limitations. Calculate an aggregate R only where B.3 and C.2.2 establish the input meanings, scales, and dependency model. Otherwise keep support separate and return a bounded reasoned synthesis. Neither a higher formality level nor an axiomatic mode requires an invented numerical score or an irrelevant empirical study.

Compilation (target-scheme fold). Map one synthesized episteme into one exact target reference scheme.

Γ_epist^compile : ( E_synth    : U.Episteme,
                    TargetScheme : U.ReferenceScheme ) → U.Episteme

• Domain. One synthesized episteme and the exact target reference scheme used to read the compiled claims—for example, the scheme used by a journal, standard, or program specification. For every meaning that crosses semantic contexts, the fold also relies on exact source and receiving SchemeSenseCell values, an obtaining F.9 Bridge, and a separately stated bounded-use claim; any relied-on use must pass A.10 or B.3.
• Result. One compiled, target-scheme episteme with explicit mapping and loss information and a C.2.1 identity determined by its claim content, exact EntityOfConcern, and effective reference scheme. The result is not thereby a publication, release, carrier, or accepted artifact.

Relationship to Γ_ctx / Γ_time. If the knowledge fold explicitly depends on argument order (for example, a derivation), the internal fold uses Γ_ctx for the sequence. If a temporal storyline matters, first identify each exact episteme and any obtaining C.2.1 edition relation; then use B.1.4/Γ_time to aggregate only the recovered temporal restrictions, relation order, or applicability windows required by the use. Γ_epist composes exact selected episteme inputs, not a label-defined current slice. If the result changes claim content, EntityOfConcern, or effective reference scheme, C.2.1 identifies another episteme. Use B.2 only when exact construction facts leave a separate existing-whole versus candidate-new-whole question.

B.1.3:4.3 - Invariant Standard (how the Quintet applies)

• IDEM (singleton identity and source-repetition discipline). Folding a single episteme without a change of claim or scheme returns itself. Repeating the same source or data creates no additional evidence or accidental assurance upgrade.
• COMM/LOC (Local commutativity / locality). Reordering genuinely independent contributions does not change a result under its declared model. A derivation or other order-dependent argument uses Γ_ctx; source order does not establish statistical independence.
• WLNK (Weakest-link bound). An unsupported indispensable premise limits the conclusion that needs it. A numerical minimum is appropriate only when the named quantity and dependency model justify a bottleneck or lower-bound interpretation. WLNK does not impose minimum over every cited source or every argument.
• MONO (Monotonicity). A monotonicity claim names the support change and the model under which it holds. Duplicate data, a contrary result, a changed target population, or the failure of a necessary assumption is not simply “more support”.

No universal reliability fold. B.3 governs the quantity, scale, dependency assumptions, and calculation. For two necessary independent conditions with probabilities 0.9 each, the conjunction has probability 0.81, not 0.9. Without independence, use a warranted conditional model or leave that joint probability unresolved. A minimum or maximum can be useful under its own declared meaning; monotonicity and boundedness alone do not establish that meaning.

Formality and calculation. Ordinal comparisons remain ordinal. A quantitative calculation requires commensurate inputs and a model for the proposed operation, including any mapping loss; a table of numbers alone is insufficient. Formal derivations state their logic and assumptions, and constructive derivations their proof basis. When no common aggregate is justified, a qualitative synthesis can still give a complete, useful answer to a bounded question.

B.1.3:4.4 - Core rules for epistemic aggregation (design‑time synthesis)

When computing Γ_epist^synth(D_know):

1. Provenance preservation. The provenance/evidence graph is unioned with de‑duplication; every claim in the aggregate remains traceable to its sources and methods. No source, method, or dataset that supports a retained claim may be dropped.

2. SCR construction. Build a U.SCR that lists all symbol carriers (texts, code, figures, datasets) that materially participate in the aggregate. Provenance nodes must be mappable to SCR entries.

3. Object alignment. Identify the result’s one exact EntityOfConcern. Reuse the same already identified entity when the inputs concern it. A governed least common ancestor in a domain taxonomy may support that identification, but the calculation does not create the entity. If the claim requires a collection, relation occurrence, or other joint subject, identify that entity under its direct pattern and show that its identity rule obtains. A list, dependency graph, shared label, or mapping cannot create a joint subject; if none is governed, stop with the missing composition governor instead of inventing a generic composite entity. Record the semantic mappings and their CL evidence summaries without silently merging homonyms.

4. Recover the support relation before combining. For the exact claim and scope, distinguish:

• Indispensable premises: the conclusion requires each named premise. A missing or defeated premise blocks that inference, not every narrower conclusion.
• Alternative sufficient arguments: each actually sufficient argument can support the conclusion; expose shared premises, datasets, assumptions, and failure causes. Different argument names do not prove independence.
• Complementary evidence: a source may constrain a rival explanation, magnitude, uncertainty, or applicability without being a necessary premise. A limited additional study need not lower the existing support.
• Different scope slices: retain their populations, outcomes, conditions, and time extents separately unless an explicit transport or combination rule supports the joint claim.
• Counterevidence: retain credible results that conflict with the proposed conclusion. Weak support, absence of decisive support, an uninformative study, and evidence against a claim have different consequences.

Deduplicate actual evidence, not just citations. Account for overlapping data and shared biases before treating agreement as additional corroboration. State what each live limitation changes in the resulting claim.

5. Compose under the receiving model, or synthesize without a score. Keep F ordinal under C.2.3; any minimum for essential formal constituents concerns that formality claim, not R. Form G through the applicable C.2.2/A.2.6 scope rules; adding a study does not by itself extend applicability. For R, name the target quantity, compatible scales, dependencies, and warranted operation under B.3/C.2.2. This can justify a bottleneck minimum, a sufficient-argument choice, a probabilistic calculation, or a statistical synthesis; none is the universal default.

For a relied-on mapping, retain its CL summary and the actual limitation. A numerical loss function needs a receiving model that establishes its meaning, units, calibration or derivation, and assumptions. An ordinal CL rank, a monotone penalty table, or clipping to [0,1] supplies none of these. If no such calculation is justified, retain the separate support and mapping limitations in a reasoned synthesis; no penalty table or new study is required merely to return that result. A receiving assurance threshold applies only to the quantity and use for which it was justified.

6. Conflict detection and disposition. Detect contradictions, including overlapping-scope p and ¬p. Resolve a scope or interpretation difference only when the source facts establish it; do not explain away a credible contrary result by an invented subgroup story. Otherwise narrow, qualify, or withhold the affected conclusion and retain explicit conflict edges. A numerical synthesis may represent disagreement only under its justified model, not conceal it. Open B.2 only if exact construction facts leave a separate whole-reidentification question after the existing-whole explanation check.

7. Handling axiomatic and world-facing support. Retain each episteme’s declared mode and actual support:

• For an axiomatic input, empirical R may be N/A. Keep the proof, its conclusion under the stated axioms, and its formal validity; line=formal is a useful tag, not a conversion rule. Do not set R to F. An ordinal F-derived proxy describes only its declared ordinal meaning. Any value proposed for an R calculation needs a receiving model establishing meaning, scale, conversion, and assumptions; rescaling F into [0,1] is insufficient.
• For a postulative input, retain its actual warrant and empirical or other support as applicable. Apply a B.3.4 currentness or decay policy only to the support whose use consumes that policy; changing the mode creates neither evidence nor a conversion model.
• The aggregate declares its mode. If all its operative inputs are axiomatic, it is axiomatic; if an operative input is postulative, it is postulative. Keep any formal subclaim separately usable. A proof about a model supports a claim about a real system only with the needed model-to-world assumptions; evidence violating those assumptions remains visible.
• Constructive derivations. State the chosen proof basis and the correspondence needed by the conclusion. An induction proof may use its stated non-UF foundation. A UF-based equivalence claim supplies the required equivalence or isomorphism witness and the structure that the receiving theorem needs preserved. A lossy mapping cannot transport a theorem that depends on an erased distinction. If the required proof basis or correspondence is unavailable, leave that inference unresolved while retaining independently supported conclusions. A CL summary describes mapping evidence; it establishes neither equivalence nor theorem transport.

8. Order-aware arguments (optional). If the conclusion depends on premise or derivation order, identify the ordered relations and positions, declare the OrderSpec, and retain the branch, join and independence conditions needed by the argument. Use B.1.4:4 to check the bounded aggregation and its determinacy under those conditions.

9. No costs here. Any compute/collection effort is Γ_work; attach references but do not mix costs into epistemic aggregation.

B.1.3:4.5 - Core rules for target-scheme compilation

When computing Γ_epist^compile(E_synth, TargetScheme):

1. Reference-scheme bindings. Map every operative concept, unit, and claim into TargetScheme and record the exact mapping and its CL evidence summary. For a meaning that crosses semantic contexts, name the source and receiving SchemeSenseCell values, the obtaining F.9 Bridge, the proposed use, direction, use-specific rule, and permitted loss; establish reliance separately. C.2.1 identifies the compiled episteme from its resulting claims, exact EntityOfConcern, and target scheme. A changed identity discriminator identifies another episteme; it does not by itself open a whole-reidentification question.

2. Re-express the assurance basis. Re-express F, G, and the support account in TargetScheme. Preserve the formal conclusion and empirical limitations separately. Recalculate R or a mapping loss only if the target use has the required meanings, scales, and model under B.3/C.2.2; a change of vocabulary or increased formality is not additional warrant. Without a justified aggregate, carry the separate support and bounded synthesis. A quantitative or formal application proves the calculations or derivations it actually claims, not a fictitious tuple imposed by its mode.

3. Compilation trace. Produce the compiled episteme’s SCR and the carrier hashes needed to reconstruct this application. Require independent re-hash verification when the receiving claim needs independent carrier-integrity evidence under B.3 or an applicable B.3.3 assurance profile. A level label alone does not select that check. The trace establishes neither publication nor release. 4. Order/time hooks. If the compiled episteme includes an internal derivation, carry the OrderSpec. If it selects knowledge for a time-bounded use, name the exact C.2.1 episteme identity and link to the already recovered proper temporal restriction, edition relation order, applicability window, or B.1.4/Γ_time aggregation actually used.

B.1.3:5 - Archetypal grounding (worked, didactic)

B.1.3:5.1 - Episteme — Heterogeneous evidence into a guidance statement

This is a didactic evidence-composition case, not a clinical recommendation. The receiving question concerns a treatment’s pain outcome for an identified acute low-back-pain population within six weeks. The exact population and outcome, not a label or taxonomy operation, identify the subject.

• Inputs: E₁ is a randomized trial, E₂ an observational study, and E₃ a mechanistic model. Retain their designs, findings, uncertainty, assumptions, and scope. A bare “R=0.84/0.55/0.60” list has no declared common quantity here and cannot support a numerical aggregate. Likewise, “medium/wide/narrow” is not a substitute for actual ClaimScope.
• Synthesis: retain protocols, datasets, analysis scripts, and other participating carriers in the SCR. Establish any dosage or outcome mapping from its actual measurement basis; units named mg and IU do not themselves establish a conversion. Keep chronic cohorts and different outcomes separate unless a warranted transport relation supports the receiving claim.
• Necessary-premise case: if the proposed inference requires an outcome mapping that is unsupported, withhold that mapped inference. Retain the trial’s narrower source-scale conclusion rather than discard every source.
• Complementary case: a limited E₂ may help assess a confounding explanation left open by E₁; E₃ may constrain a mechanism without establishing the clinical effect size. Explain those contributions and their limits. The minimum of three unexplained scores neither captures them nor defeats the existing trial conclusion.
• Dependence case: if two reports reuse a cohort or share an outcome-measurement bias, do not count them as two independent confirmations. Different designs alone are insufficient to establish different biases.
• Contrary-result case: a credible E₂ result conflicts with E₁ in an overlapping subgroup. Keep the disagreement. Different baseline severity is a possible explanation only to the extent supported by the sources. Narrow or qualify the guidance claim; do not silently average the conflict away or call it an uninformative study.
• Completion: return the bounded guidance statement with its distinct supporting contributions, contrary result, scope, and unresolved interpretation. No common quantitative model has been supplied, so no aggregate R is returned. Whether another study is feasible and worth its total burden is a separate C.11/C.19.2 decision, not a condition for completing this synthesis.

Concrete completion of the case. Use the following invented findings only to illustrate the synthesis. P is the trial’s enrolled acute low-back-pain cohort; S is its identified high-baseline-severity subgroup. E₁ reports lower pain at six weeks with intervention X than with its comparator, both in P and in S. E₂ reports no such benefit in a separately observed cohort matching S; the sources have not resolved whether confounding or another difference explains the disagreement. E₃ supplies a mechanism compatible with benefit but no clinical effect estimate. No common quantitative support model is available.

The resulting guidance statement is: “The trial supports lower recorded pain at six weeks for X versus its comparator in P. The finding for S conflicts with the observational result and remains unresolved. The mechanism explains how benefit could occur but does not resolve that conflict or establish its magnitude. These sources support neither extrapolation beyond P and six weeks nor a combined reliability score.” The SCR retains all three contributions. A supported explanation of the disagreement or a corrected source result reopens the affected claim. A request for another population opens a separate question and synthesis. Identify the new claim, its subject and scope (C.2.1; A.2.6), and establish the evidence or warranted transport needed for that use. The request alone leaves the result for P unchanged. This is a completed bounded synthesis of the fictional findings, not advice to use X.

For Γ_epist^compile, map the retained claims into the journal’s scheme, carry the same limitations and any justified recalculation, and produce the compilation SCR and required hashes. C.2.1 identifies the target-scheme episteme “Guidance Statement v1.0”; later journal publication remains a separate occurrence.

B.1.3:5.2 - Episteme — Controller proof and a real protective function

• Inputs: a requirement specification, hazard analysis, test logs, and a proof of controller property P under assumptions A. Preserve each source’s actual formal basis and support. No common R scale follows from four labels or formality levels.
• Formal receiving question: “Does A entail P in the stated model?” Retain the valid proof and its assumptions as the useful result. An empirical study is not needed to turn that result into an invented empirical R; F describes checkability, not the probability that the actual controller is safe.
• World-facing receiving question: “Does the installed controller deliver the protective function in these operating conditions?” Expose the reliance on A, the implementation/model correspondence, and the actual operating scope. If A is unsupported for this use, the proof alone does not establish the world-facing claim. If logs show an edge case violating A, retain that counterevidence and withhold the stronger assurance while preserving the theorem A ⇒ P.
• Threshold case: a receiving acceptance clause requires a justified probability of at least 0.95 for the real protective function. Substituting a high F or its rescaled value cannot meet it. A declared ordinal checkability comparison remains usable as an ordinal comparison. A numerical acceptance result requires the model and evidence that warrant that particular probability; otherwise return the narrower formal conclusion and the unresolved actual-system assurance.
• Positive quantitative case: if a receiving model actually establishes two necessary independent conditions, each with probability 0.9, their conjunction is 0.81. A 0.85 threshold is not met by replacing 0.81 with min(0.9, 0.9). If independence is unavailable, the joint probability needs the actual conditional model or remains unresolved; the formal proof is unchanged.

For Γ_epist^compile, map the retained claims to the certification scheme. Where local meanings differ, identify exact source and receiving SchemeSenseCell values, test the F.9 Bridge, state the bounded certification use and permitted loss, and establish relied-on use separately. C.2.1 identifies the resulting episteme. Certification, authorization, a publication occurrence, and actual system protection remain separate claims.

B.1.3:5.3 - Contrast (didactic)

B.1.3:6 - Proof obligations (normative)

At synthesis (Γ_epist^synth):

1. PO‑SYN‑PROV. The provenance/evidence graph MUST be preserved (union with de‑duplication); every retained claim is traceable to sources/methods in the SCR.
2. PO-SYN-OBJ. The result MUST name one exact EntityOfConcern already identified under its direct pattern. If the synthesis depends on several inputs as a joint subject, its collection, relation, or whole identity MUST be independently governed; a list, graph, label, or mapping is insufficient. Every semantic mapping used by the fold MUST be declared with its CL evidence summary.
3. PO-SYN-CL. Every mapping used in the support account MUST retain its CL evidence summary and actual use limitation. A numerical loss MUST have a receiving model establishing its meaning, scale, derivation or calibration, and assumptions; ordinal ranks and monotonicity alone are insufficient. The summary neither establishes an F.9 Bridge nor grants use.
4. PO‑SYN‑R. The result MUST distinguish indispensable premises, sufficient alternatives, complementary support, scope slices, and counterevidence where present. An aggregate R MUST have warranted input meanings, scales, dependencies, and an operation under B.3/C.2.2. Otherwise retain separate support and a reasoned bounded synthesis. Neither F nor a mode tag supplies an R conversion.
5. PO-SYN-CONFLICT. The result MUST retain credible contrary evidence and distinguish an established scope or interpretation difference from an unresolved conflict. Narrow, qualify, or withhold the affected conclusion accordingly. B.2 applies only to a separately grounded whole-reidentification question.
6. PO-SYN-ORDER. If the conclusion depends on order, the ordered relations, positions and OrderSpec MUST be recorded. The aggregation MUST satisfy B.1.4:4 for its declared use, including applicable branch, join and independence conditions; determinacy is relative to those conditions.
7. PO‑SYN‑NOWORK. Resource spending, yields, and dissipation MUST NOT be computed here; instead, attach references to the aligned Γ_work composition.

At compilation (Γ_epist^compile):

1. PO-COMP-SCHEME. The exact target reference scheme MUST be declared. Every active concept and unit MUST have an explicit mapping; a cross-context meaning use MUST name the exact F.9 Bridge, separate bounded-use claim, permitted loss, and any relied-on A.10 or B.3 result.
2. PO-COMP-ASSUR. The formal basis, scope, and support account MUST be re-expressed in the target scheme without losing their limitations. Any recalculated R or loss MUST satisfy the receiving model; otherwise preserve the separate support and bounded conclusion.
3. PO-COMP-SCR. The compiled episteme MUST retain an SCR with the hashes, versions, and dates required to reconstruct the application. This obligation does not assert release or publication.
4. PO-COMP-ID. The output MUST be identified through its C.2.1 claim content, exact EntityOfConcern, and effective target scheme. A changed discriminator identifies another episteme. B.2 is opened only for an independently current existing-whole versus candidate-new-whole question, never as a substitute for this identity rule.
5. PO‑COMP‑ORDER/TIME. If derivational order is essential, the OrderSpec MUST be referenced. If temporal selection is essential, name the exact C.2.1 episteme identity and reference the already recovered proper restriction, edition-relation order, applicability window, and B.1.4/Γ_time aggregation actually consumed.

B.1.3:7 - Conformance Checklist (normative)

B.1.3:8 - Anti‑patterns & repairs

B.1.3:9 - Consequences

Benefits

• Auditability by construction. Every retained claim remains tied to its sources; SCR guarantees reconstructability.
• Qualified synthesis. Useful formal and complementary support is retained; dependency assumptions, contrary evidence, and mapping limitations constrain the resulting claim.
• Target-scheme results. Compiled epistemes are aligned with one declared reference scheme; any release or publication remains separately governed.
• Didactic clarity. Separates semantic folding (Γ_epist) from order (Γ_ctx), time (Γ_time), spend (Γ_work), and emergence (B.2).

Trade‑offs

• Mapping overhead. Declaring mappings and CL costs time; it prevents silent incoherence.
• No forced single score. Heterogeneous support may remain separate. This makes some comparisons less compact but avoids fictitious assurance and preserves a useful bounded conclusion. B.2 remains specific to a genuinely unresolved whole-reidentification question.

B.1.3:10 - Rationale (informative)

• Epistemic composition is not physical addition. A missing necessary premise, a complementary study, and a contrary result do different work. The receiving claim and dependency model determine their combination; minimum is not universally conservative.
• Provenance supports reliance. Losing a source or SCR link can defeat reconstruction or warranted use while the episteme keeps the same C.2.1 identity. Restore the missing provenance and reconsider the affected reliance. Identify another episteme only when claim content, EntityOfConcern or effective ReferenceScheme changes; source or method claims that form part of the claim content are subject to that same rule.
• Interpretation matters. Exact reference schemes and local senses prevent quiet reinterpretation. F.9 governs any cross-context Bridge; C.2.1 governs the resulting episteme identity.
• Parsimony with power. Provenance, support roles and dependencies, exact mappings, and order/time hooks suffice for a useful synthesis without imposing a common score. Gutierrez, Glymour and Davey Smith, Evidence triangulation in health research (2025) supports comparing design assumptions and shared biases, checking target-question comparability, and using qualitative comparison when quantitative pooling is unwarranted. This methodological contribution does not supply a universal R formula or make a further study mandatory.

B.1.3:11 - Relations

• Builds on: C.2.1 (episteme identity and independently obtaining edition relations), A.6.1 (semantic operation declarations and exact application bindings), A.14 (ConstituentOf, collection belonging under each collection’s own rule, and proper temporal restriction of one unchanged carrier), A.7 (Strict Distinction), and A.15/A.15.1 (Method/Work alignment and Work-temporal law). A.12 is used only when an acting-side distinction is current. An ordinary actor sentence needs no classification apparatus. Any particular dated synthesis or compilation U.Work first reuses each performer’s A.13 core and is independently admitted under A.15.1; F.6 follows only when the receiving claim also needs precise assignment-bound attribution. A short local projection may omit an assignment identifier unused by the receiver only when every consumed relation remains recoverable.
• Coordinates with: B.1.1 dependency-structure and relation-grounding checks, B.1.4 (Γ_ctx/Γ_time inside knowledge folds), B.1.6 (Γ_work for compute/collection spend).
• Coordinates with: F.9 for exact cross-context Bridges and bounded-use claims; A.10 or B.3 for reliance; A.15.PROD when production, first existence, or completion is current; and E.17/E.24.PUB for publication, form, and carrier. B.2 is used only when exact construction facts leave a separate whole-reidentification question after the existing-whole explanation check.
• Used by: B.3 assurance uses the aggregate’s exact formal basis, scope, and support account, including any justified R calculation and mapping limitations; C.11 and C.19.2 govern a separately selected inquiry or action decision.

One‑sentence takeaway. Γ_epist preserves provenance, distinguishes what each source contributes, and combines support only as its meanings and dependencies warrant—returning a useful bounded synthesis when no common score is justified.

B.1.3:End

B.1.4 - Specify Order-Sensitive or Temporal Aggregation (Γ_ctx, Γ_time)

Type: B-family aggregation pattern Status: Stable Normativity: Normative unless explicitly marked informative

Use this when. Use this pattern when the current claim aggregates already recovered relations over an exact set of ordered positions, phases, or a time window, and the question is not just ordinary part-whole construction. Typical cues are ordered steps, order-sensitive argument chains, asset histories, proper temporal restrictions of one enduring carrier, rolling windows, use-bounded roll-ups, time-sliced evidence, or a bounded chronology over exact C.2.1 episteme identities and already obtaining edition relations.

Not this pattern when. If the question is ordinary part-whole or collection admission, use B.1, A.14, and C.13. If it is episteme identity or historical edition continuity, use C.2.1 before any aggregation. If the question is the method as such, method description, work plan, dated work occurrence, or Work temporal part or episode, use A.3.1, A.3.2, A.15.2, or A.15.1. If the question is work-resource accounting, use B.1.6. If the question is changed identity, use the pattern that defines the subject’s identity or change; for a clear whole-reidentification question, use B.2 directly to test whether the existing whole suffices or a new whole must be reidentified. Use B.2.P first only when emergence-family wording hides the claim kind. If the question is temporal adequacy of a claim, use C.27.

What goes wrong if missed. Order, phase, context, or time-window wording becomes ordinary parthood, method order, performed work, evidence currentness, or whole reidentification by label.

What this buys. The practitioner can aggregate order-sensitive and temporal material while keeping method, work, transformation, work-resource, temporal-adequacy, and MHT claims with the patterns that define or test them.

B.1.4:1 - Problem Frame

Many useful aggregates are not simple unordered wholes. A manufacturing sequence changes meaning when steps are swapped. An argument chain depends on which premise is used before which lemma. A turbine or another enduring individual with a stated identity rule may be considered across proper temporal restrictions. An unchanged paper or dataset episteme may also be restricted to a proper interval only while its complete C.2.1 identity triple remains fixed; changed claim content, EntityOfConcern, or effective ReferenceScheme identifies another episteme, with edition continuity tested separately. In these cases the aggregation is about order or temporal coverage over already recovered relations, not about a new level, a generic boundary, or a hidden interaction kind.

B.1.4 defines the aggregation claim. It asks which EntityOfConcern is being aggregated, which positions or phases are included, which scope and time window qualify the claim, which ordered or phase relation is being used, what the aggregate may be used for, and which neighboring pattern carries any stronger claim.

B.1.4:1.1 - Problem

Without this pattern, four errors recur. First, SerialStepOf or another ordered relation is read as ordinary parthood, so changing the order looks harmless even when the aggregate meaning changes. Second, a phase label is read as a new holon level or a new whole, so identity change is hidden instead of handled by whole reidentification. Third, design-time plans, possible method order, run-time histories, and evidence windows are folded together as one sequence. Fourth, mathematical order, graph, or operator notation starts to stand for the in-life object instead of expressing a recovered relation for one bounded use.

The practical failure is not a missing diagram. It is an inadmissible aggregate: the user cannot tell which carrier is being followed, which positions or phases are included, which relation is ordered, which time window is covered, whether gaps or overlaps matter, or which pattern must carry a stronger work, resource, transformation, evidence, or whole-reidentification claim.

B.1.4:1.2 - Forces

B.1.4:2 - Solution

Recover a ContextTemporalAggregation@Context before using the aggregate:

ContextTemporalAggregation@Context:
  aggregationConcernRef
  aggregatedEntityOfConcernRef
  includedPositionRefs?
  includedPhaseRefs?
  claimScopeRef?: U.ClaimScope
  aggregationMode: contextualOrder | temporalPhase
  orderedRelationRefs?
  phaseRelationRefs?
  orderSpecRef?
  timeWindowRef?
  carrierIdentityRef?
  independenceOrJoinConditionRefs?
  coverageAndOverlapPolicyRefs?
  boundaryCrossingRelationRefs?
  relatedMethodRefs?
  relatedMethodDescriptionRefs?
  relatedWorkOccurrenceRefs?
  relatedWorkResourceAggregationRefs?
  relatedTransformationRefs?
  relatedWholeReidentificationRefs?
  evidenceOrSourceRefs
  admissibleUse
  stopOrReturnCondition
  nonAdmissibleOverread?
  strongerSourceReturnCondition

stopOrReturnCondition states when to stop aggregating or apply another pattern; strongerSourceReturnCondition states the condition for a stronger claim. Include nonAdmissibleOverread? only when it passes F.19’s plausible-reader test. groundedNonAdmissibleOverread? is an alias for that same optional value.

Use the record to describe the exact aggregation claim and its independently established relations. The record is not itself the relation or a new U.Level, U.Boundary, U.Interaction, or generic process object.

B.1.4:2.1 - Two Aggregation Modes

If one source phrase mixes both modes, split the record. A Method may have an ordered relation structure; the Work that enacts it may have exact A.15.1 temporal parts, episodes, operational parts, or separate occurrences, while C.27.TA supplies any independently declared overlap or other interval relation the receiving use aggregates. Those are different claims, and generic PhaseOf does not replace the Work or temporal relations.

B.1.4:2.2 - Where Stronger Claims Go

B.1.4:3 - Optional Operator Notation

Gamma_ctx and Gamma_time are optional notation for already recovered aggregation claims.

Gamma_ctx(contextualAggregationRecord, orderSpec, independenceAndJoinConditions)
  -> contextual aggregate record

Gamma_time(temporalAggregationRecord, timeWindow, coverageAndOverlapPolicy)
  -> temporal aggregate record

The notation does not create a holon, transformation, method, work occurrence, or whole reidentification by itself. It records how the selected relation set is combined for the current use.

Keep an ordinary statement about who prepared the aggregation ordinary. If the use asserts one exact dated sequencing, combining, measuring or auditing Work, recover the actual performer’s A.13 core and admit the Work independently under A.15.1. Use A.3.4 for a separate transformation claim, B.1.6 for resource aggregation, and A.10 to recover provenance and bounded reliance on independently established results. Writing the record does not identify its writer as the transformer of the EntityOfConcern.

B.1.4:4 - Admissible Checks

For contextual order aggregation:

• the ordered relation refs are named by value;
• the OrderSpec is declared as total order, partial order, or another named relation;
• independence, branch, or join conditions are named when parallel factors are used;
• the record names its included positions, ClaimScope when needed, and admissible use; any holon-boundary crossing is named by an exact relation;
• method, method-description, work, transformation, and resource claims use the patterns that define or test them.

For temporal phase aggregation:

• the carrier identity is recoverable;
• the time window is declared;
• the declared coverage and overlap policy holds; account for allowed overlaps and gaps without double counting, or narrow the use;
• identity change is not hidden as another phase;
• work-resource claims use B.1.6; temporal claims use C.27, currentness uses G.11, and A.10 recovers provenance and bounded reliance when needed.

B.1 invariant carry-through. Apply a B.1 algebraic law only when the recovered relation and declared operator justify it. Contextual aggregation is deterministic relative to the declared OrderSpec and join or independence conditions. Temporal aggregation depends on carrier identity and the declared coverage and overlap policy. A repeated designation creates no additional phase or relation by itself; retain distinct occurrences and ordered positions when the claim distinguishes them. State any singleton or idempotence law for the actual operator. Weakest-link and monotonicity claims name the characteristic and model being bounded or improved; an aggregation record alone establishes no performance, safety or assurance result.

B.1.4:4.1 - Compact Obligation Rows

B.1.4:5 - Archetypal Grounding (Worked Slices)

Manufacturing sequence. A frame is prepared, welded, inspected, painted, and packed. B.1.4 records the contextual order claim: selected steps, order specification, join conditions, and admissible use for planning or comparison. The actual shop-floor work occurrences use A.15.1; energy and material roll-ups use B.1.6; a changed frame state uses A.3.4.

Paper edition history. When draft, reviewed, and camera-ready texts change claim content, EntityOfConcern, or effective ReferenceScheme, C.2.1 identifies distinct epistemes and tests each claimed EpistemeEditionRelation independently. B.1.4 may record a bounded chronology over those already recovered identities, relations, applicability windows, or publication windows; it does not turn the editions into phases of one episteme. If one unchanged episteme is genuinely needed over a proper interval, A.14 PhaseOf may state only that restriction. Source-currentness and publication-use claims use A.10, G.11, and E.17; chronology establishes none of them.

Cross-regime evidence window. A dashboard aggregates observations from two operating regimes. B.1.4 records the exact observation sets, their subject populations or carriers, the aggregation window, and the admissible use. If the regimes use different measurement bases, use C.16 or C.29 for comparability before relying on the aggregate.

B.1.4:5.1 - Bias-Annotation

B.1.4:6 - Conformance Checklist

B.1.4:7 - Common Anti-Patterns and How to Avoid Them

B.1.4:8 - Consequences

This pattern makes ordered and temporal aggregation inspectable without turning every sequence, phase, or context label into a holon level. It also lets practitioners keep useful Gamma_ctx and Gamma_time notation while avoiding a category error: the notation is an apparatus over a recovered aggregation claim, not the in-life work, method, transformation, or whole.

The cost is that the practitioner must name the relation being aggregated. The gain is that contextual order, temporal coverage, work evidence, resource accounting, transformation, and whole reidentification stop interfering with one another.

B.1.4:8.1 - Rationale

B.1.4 exists because contextual order and temporal phase aggregation are neither ordinary part-whole construction nor generic process talk. One enduring carrier with a stated identity rule can be considered through proper temporal restrictions; a selected relation set can be order-sensitive; and both cases need admissible aggregation without inventing a new holon kind. The pattern therefore keeps relation discipline explicit: PhaseOf and the carrier’s identity rule for legitimate phase aggregation; C.2.1 identity and independently obtaining edition relations for distinct episteme history; A.15.1 relations for Work; ordered relation refs and OrderSpec for contextual aggregation; and separate patterns for resource, transformation, evidence, and whole reidentification.

The old DesignRunTag warning is preserved as a rule rather than a label: do not fold design-time possible order and run-time history into one aggregate. If both are needed, make two records and relate them by value.

B.1.4:8.2 - SoTA-Echoing

B.1.4:9 - Relations

• Builds on B.1, A.14, and C.13 for part-whole, phase, and constructive grounding discipline.
• Coordinates with C.2.1 for exact episteme identities and independently obtaining edition relations; with A.3.1, A.3.2, A.15.2, and A.15.1 for method, method description, work plan, dated work occurrence, and exact Work-temporal relations.
• Coordinates with B.1.6 for work-resource aggregation.
• Coordinates with A.3.4 for transformation. Use B.2 directly for a clear whole-reidentification question; use B.2.P first only when emergence-family wording hides the claim kind. The relevant subject pattern defines or constrains the recovered claim.
• Coordinates with C.27 for temporal-claim adequacy. When mathematical expression is selected, C.29 tests lens-use adequacy, E.18 defines the selected transformation-flow structure, and E.18.2 defines its mathematical description.

B.1.4:End

B.1.5 - Gamma_method - Order-Sensitive Method Composition and Work Enactment

Type: Part B composition and grounding pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.1.5:1 - Problem Frame

Use this pattern when a project must decide whether several recovered methods compose into one larger U.Method, and when order, guarded choice, parallel branches, typed joins, adapters, or method-interface exposure changes the identity of that whole method.

Typical moments:

• a procedure, workflow, algorithm, pipeline, proof route, clinical protocol, manufacturing recipe, inference pipeline, or operational playbook has named steps or branches;
• changing the order of two candidate submethods changes the result or the admissible conditions of use;
• a diagram or code file looks like a method, but it may be only a method description, a work plan, a dated work trace, a selector registry, or a mathematical lens;
• a larger method must expose some interactions at its boundary while hiding internal steps;
• assurance needs to know which joins, adapters, cutsets, or exposed interfaces make the composite method reliable enough to enact.
• a source presents Methods as a first–then list even though representative Work may also require several of them to contribute at the same time.

Primary EntityOfConcern. The EntityOfConcern is one exact candidate or composite U.Method, already identified under A.3.1. The proposition that exact part Methods and whole-forming facts qualify it as composite is separately governed claim content. A separately identified C.2.1 episteme may carry that proposition in its ClaimGraph; the episteme then has the exact candidate Method as its EntityOfConcern under its effective ReferenceScheme. The proposition does not become the episteme.

First useful move. For each apparent step or branch, recover the governed object before composing anything: U.Method, U.MethodDescription, U.WorkPlan, dated U.Work, an A.22-selected U.Structure, method-family registry or selector outcome, mathematical lens, mechanism, formal substrate, or quoted wording that does not yet carry a method claim.

What goes wrong if missed. A flowchart becomes the method, a plan item becomes a submethod, an event log becomes proof that a method was enacted, an order edge becomes a part, or a registry of alternatives is treated as one composed method. Then work starts from a description or label whose method identity, joins, interfaces, and failure conditions were never recovered.

What this buys. The project can test whether an already identified candidate U.Method is composite and can state the needed part, order, join, interface, and identity facts without turning every useful sentence into a relation kind. If that qualification fails, the project still has a useful lower object: an A.22-selected U.Structure, description, plan, work occurrence, lens, selector result, or A.15.4 appearance-based reliance repair request.

Not this pattern when.

• If the current claim is one semantic way of doing with no order-sensitive composition question, use A.3.1.
• If the current claim is a claim-bearing episteme that describes a method or relations among methods, use A.3.2 and C.2.1.
• If the current claim is intended work, use A.15.2.
• If the current claim is a dated occurrence, use A.15.1.
• If the current claim is structural component parthood, use A.14, C.13, and B.3.5.
• If the current claim is only a method-family registry, selector, fallback relation, or useful organization of already identified methods without one whole-method construction, use G.5 or select a U.Structure under A.22.

B.1.5:1.1 - Composition Question And Object Boundaries

U.Method is a non-agentive method holon kind. A method can have submethods and can participate as a submethod in a larger method. This does not mean every step-looking node, document section, file module, graph edge, work-plan item, or work occurrence is a method part.

Order-sensitive method composition is a narrow constructive question:

Given independently recovered U.Method parts,
which methodPartOf occurrences, exact whole-forming claims, and constraints qualify one already identified candidate as composite,
and what whole-level commitments let a practitioner identify, reidentify, and enact that method?

The whole method is not the diagram, code, schedule, event log, card, or work history that may describe, plan, record, or evidence it. Work enacts the method; the method does not perform work. An A.22-selected U.Structure may organize several methods and obtaining relations for one use without constructing another method.

Gamma_method is the name for this method-composition discipline. It is not a new root U-kind, not a workflow notation, not a generic container, not a resource-accounting operator, and not a substitute for U.Work.

B.1.5:2 - Problem

Without B.1.5:

1. Source-wording composition. “Step”, “stage”, “activity”, “task”, “procedure”, “workflow”, “pipeline”, or “algorithm” wording is accepted as method composition without recovering the actual objects.
2. Description-as-method. A workflow diagram, BPMN model, code repository, proof script, table, checklist, or graph path is treated as the composite method itself.
3. Order as mereology. SerialStepOf, ParallelFactorOf, guarded choice, or fallback relation is placed in a structural part-whole chain.
4. Typed joins disappear. One submethod’s intended result is assumed to satisfy the next submethod’s precondition without an adapter method, governed correspondence or equivalence, and an explicit failure route.
5. Interface exposure is hidden. Callers rely on internal interactions that should be encapsulated, or fail to see interactions that the composite method must expose.
6. Run-time leakage. Resources, timestamps, telemetry, performed values, and results are baked into the method instead of remaining occurrence-side facts and separately governed resource, result, and evidence relations.
7. False whole method. A method-family registry, fallback table, selector rule, or A.22-selected relation organization is treated as one whole method although no construction or whole identity has been recovered.
8. Sequence becomes level. A source list, vertical diagram, curriculum, or first–then account is treated as a subject hierarchy or level structure without an independently established level relation.
9. Simultaneous contributions become stages. Methods that contribute during the same bounded Work situation are forced into one before-after chain because the source, presentation, or review visits them one at a time.

B.1.5:3 - Forces

B.1.5:4 - Solution

A.3.1 first identifies the exact candidate U.Method and every exact part method. B.1.5 does not create their U.Method membership. It asks the narrower question: do these already identified methods, contributions, constraints, and boundary decisions warrant the claim that the candidate Method is composite?

Start with the smallest useful composition claim:

1. Name the same exact A.3.1 candidate Method and exact A.3.1 part methods.
2. In ordinary domain language, state the candidate’s reusable whole action, what each part contributes, and the order, guard, adapter, or join condition that the whole action actually needs.
3. For every whole-forming statement other than B.1.5’s narrow methodPartOf, use A.6.RCD’s lightest sufficient disposition: an existing direct predicate, a local compound claim, or a reusable predicate-definition episteme. A convenient edge label is not a relation-kind admission.
4. Add stable relation-occurrence identity, typed declarations, publication, or assurance only when a named dependent use consumes that extra result. Submit any relation-kind candidate to the exact E.24/E.24.UK admission predicates rather than admitting it here.
5. If the whole action, boundary, contribution, or reidentification rule is still missing, stop the composite claim and keep the useful lower object under its subject pattern.

Minimal positive. BuildAndVerifyPumpUnit is already an exact A.3.1 Method. Its construction rule requires frame assembly, motor installation, connector adaptation when the installed connector does not meet the test precondition, and functional testing; installation and any required adaptation must finish before testing, and adapter failure stops the whole before test. These plain claims, exact methodPartOf facts, and the whole identity rule can warrant the composite-method qualification without minting one relation kind per arrow.

Discriminating non-composite. AssessVitals, ClassifyUrgency, and RouteToCare can support readable result-to-precondition and guarded-dispatch claims while still lacking one reusable whole action, complete boundary, and whole reidentification rule. Keep those claims local and do not call their organization a composite Method. Select an A.22 U.Structure only if a real receiving use needs a load-bearing selected organization.

When a caller system, planner system, substituting-method selection use, auditor, or assurance use needs a reliance-bearing account, check the complete coordinates below. This is a reading checklist, not a schema, record, RelationSignature, or set of SlotSpecs.

Composite-method qualification:
  candidate whole method: one exact U.Method already identified under A.3.1
  part methods: a non-empty set of exact U.Method values already identified under A.3.1
  method-part occurrences defined in B.1.5: methodPartOf(part method, whole method)
  other whole-forming claims and constraints:
    exact order, independence, guard, iteration, fallback, adapter, and join meanings used here
    each closed at A.6.RCD's lightest sufficient disposition
  whole semantics:
    generic participants, applicability, preconditions,
    intended effects or preserved conditions, invariants, bounds,
    accepted inputs and outputs, failure and stop conditions
  boundary decisions:
    exposed, forwarded, and encapsulated interactions
  identity and reidentification:
    what keeps this whole the same and what identifies another method
  enactment boundary:
    exact U.Work may enact the method only through A.15.1 enactsMethod
  lower disposition if construction is incomplete:
    selected U.Structure | U.MethodDescription | U.WorkPlan | U.Work |
    G.5 selector | lens | A.15.4 appearance-based reliance repair request

B.1.5:4.1 - Recover Parts Before Composition

Do not start from the word “step”. Start from the object claim.

An apparent step can be:

• a U.Method submethod;
• a description constituent inside U.MethodDescription;
• a plan item inside U.WorkPlan;
• a dated U.Work occurrence or work part;
• an order, fallback, or selector claim among independently identified objects;
• a mathematical or representation lens over selected relations;
• mechanism or formal-substrate material;
• quoted wording that does not yet carry a method claim.

Only the first case can be a method part. Do not mint U.StepSpec, U.StepMethod, U.MethodStep, or U.MethodAlgebra for the others.

B.1.5 directly governs MethodPartOfRelation, expressed in Plain register as methodPartOf(partMethod, wholeMethod). Both participants are exact U.Method values already identified under A.3.1. The predicate obtains exactly when the whole Method’s stable construction rule names the part Method as a required contributor or as an admitted alternative for a required contribution, and that contribution participates in the whole’s reusable action. It establishes neither A.14 structural-component parthood, a work part, nor a transformation part.

One methodPartOf occurrence is determined by the ordered pair <part Method, whole Method>. Every bounded alternative already admitted by the whole’s construction rule can stand in methodPartOf at the same time; dated Work selecting one alternative does not start, end, or recur the other occurrences. For the same two exact Methods, the relation is atemporal: there is no silent cessation and later recurrence. If the construction rule changes so that a part is newly admitted or no longer admitted, the composite Method must be reidentified or the claim remains unresolved; reidentifying either participant gives another pair. This is why the participant pair is sufficient for the narrow family defined in B.1.5 even when actual enactments vary.

The same part Method may also stand in methodPartOf relations to several different whole Methods. Test every pair against the construction rule of its own whole. Each whole keeps its own reusable action, applicability, boundary, constraints, interfaces, accepted variations, and reidentification rule. One supported pair says nothing about another and creates no unique containing Method, discipline-wide whole, kind inheritance, transitivity, fusion, or common-whole closure.

A source label, list membership, diagram containment, shared name, registry entry, description membership, plan position, or work decomposition does not make methodPartOf obtain. When the test fails, keep the apparent step under its subject pattern and do not add a negative part merely to complete a diagram.

B.1.5:4.2 - Test The Composite-Method Qualification

First identify the exact candidate Method under A.3.1 from its reusable action, participant meanings, applicability, preconditions, intended result or preserved condition, bounds, and failure or stop conditions. If that Method cannot yet be identified, require A.3.1. B.1.5 then tests whether already identified part Methods and exact whole-forming facts justify calling that same candidate a composite Method; it does not create the candidate’s Method identity.

State each whole-forming fact in ordinary domain language before choosing its representational or ontological disposition. The words serial, parallel, guarded, iterative, fallback, adapter, and join do not settle the claim by themselves.

Before using a first–then or vertical list as Method architecture, make both checks.

1. Preserve real order. Ask what must finish or become true before another Method can start or continue. Name the Methods, the required result or condition, any join or adapter, and the failure or stop route. Keep a genuine first–then result as an unfolding or order claim; its position does not make it a subject level.
2. Test simultaneous contribution. Choose one bounded Work situation and ask whether several Methods contribute during it without all of them falling into one before-after chain. One Work whole may enact several Methods through separate A.15.1 relations. Alternatively, separately identified Work occurrences may overlap while enacting different Methods. State the Work identities and relations that actually obtain. Co-occurrence alone establishes no Method part, composite Method, Work part, or level.

Both answers may be true. A Method can contain a real ordered segment while other Methods contribute during the same broader Work. The source’s reading order and the fact that several Methods are used together decide neither which Methods are parts of one whole nor whether any level exists.

Then use A.6.RCD. Reuse an existing direct predicate when one already governs the needed claim. Otherwise stop at a local compound claim when it closes this use, or publish a reusable predicate-definition episteme when several uses need the same rule. Continue to a relation-kind candidate only when a named receiver needs stable occurrence semantics that claim content cannot supply; E.24 and E.24.UK decide admission. A label such as precedesInMethod is readable claim language, not admission evidence, and an ordinary composition claim needs no invented occurrence.

Keep definition, signature, kind, and edition distinct. A predicate-definition episteme may independently satisfy ordinary A.6.0 U.Signature membership. It is not a RelationSignature; that specialization opens only for an admitted relation kind. Changed predicate-definition or signature content identifies another episteme under C.2.1. Treat and connect the two epistemes as editions through EpistemeEditionRelation only when C.2.1’s historical-continuation test passes: exact source use and the applicable continuation rule identify which claim, EntityOfConcern, and scheme features must be preserved or may deliberately change, and the current facts satisfy that rule. Revision or supersession Work, Method, provenance, and change facts are evidence for this test; no label establishes continuity. Otherwise the later episteme is a non-continuing replacement. The changed content triggers review of dependent claims; it does not by itself prove another relation kind or relation occurrence. If a relation kind is independently admitted, its direct pattern or declaration defines applicability and occurrence identity, while current case facts establish obtaining, continuation, or cessation where relevant.

When several admitted order occurrences must be reviewed together, use B.1.4’s OrderSpec, exact ordered-relation designations, and join or independence conditions in a separate bounded-use aggregation record. The record and optional Gamma_ctx notation neither participate in Method identity nor make any relation obtain. When the order statements remain local claims rather than admitted relation occurrences, compare those claim contents directly and do not pretend that an OrderSpec has occurrences to aggregate.

The composite-method qualification holds only when the candidate Method also has its own reusable semantic action, generic participant meanings, applicability, preconditions, intended effects or preserved conditions, invariants, bounds, accepted inputs and outputs, failure and stop conditions, and interface decisions. Its identity includes the exact part Methods and construction architecture on which those semantics depend. Cite an effective reference scheme or claim scope only when its variation changes a Method meaning or the use of a claim about that Method; neither is a generic container.

State the reidentification rule with the qualification. The same exact candidate continues through only those parameter changes, reorderings, or part substitutions that its A.3.1 identity rule already permits while preserving the whole action, applicability, preconditions, intended result or preserved condition, bounds, required joins, and interface boundary. A change outside those permitted variations identifies another U.Method. Use B.2 when a separate higher-level reidentification or emergence claim is current; a B.2 label is not needed to state an ordinary B.1.5 rule.

B.1.5:4.3 - Keep Order Out Of Structural Mereology

Source cues such as SerialStepOf, ParallelFactorOf, guarded choice, iteration, fallback, adapter, and typed join call attention to possible whole-forming claims. They are not admission evidence, they need not become relation kinds, they are not A.14 component parthood, and they do not make methodPartOf obtain by themselves.

Use A.14, C.13, and B.3.5 when the claim is about structural parts of a holon. Use B.1.5 when the claim is about how reusable ways of doing construct a larger reusable way of doing. The same project may need both, but the relation occurrences and truth conditions remain separate.

Use B.1.4 when a receiving use needs an inspectable order aggregation, partial-order test, or join/independence account. Its OrderSpec and optional notation describe already recovered order occurrences; B.1.5 still decides whether those methods and relations construct one composite U.Method.

When the current claim is a proper temporal restriction of one unchanged non-Work carrier, apply that subject’s direct identity rule and A.14/B.1.4 rather than B.1.5. For MethodDescription history, compare the C.2.1 identity triples and assert EpistemeEditionRelation only when its historical-continuation predicate obtains. For Work intervals, episodes, performed parts, retries, resumptions, or later occurrences, apply A.15.1’s exact relations; generic PhaseOf is not their substitute. A temporal boundary becomes a B.2-family question only when a separate whole-reidentification, closure, or supervision claim remains. Order, temporal restriction, episteme edition, Work segmentation, structural parthood, method composition, and whole reidentification remain different claims even when one source diagram uses one line for all of them.

B.1.5:4.4 - Expose The Composite Method Interface

The candidate Method’s reusable action includes a boundary decision for each interaction:

• exposed: a caller system may rely on the interaction as part of the whole Method;
• forwarded: a caller system may address an internal submethod interaction through a declared designation or adapter;
• encapsulated: the interaction is internal and cannot be relied on from outside the whole Method.

An exposure decision contributes to Method identity whenever changing it changes the reusable action or its admissible boundary. That identity consequence does not wait for an outside party to rely on the Method. A named caller, planner, auditor, substituting-method selection use, or assurance use instead determines when the decision must be stated explicitly or published for reuse. Name the interaction, precondition, result or preserved condition, failure route, and any adapter needed for each exposed or forwarded case.

B.1.5:4.4.1 - Composite-Method Boundary Account and Publication Form

When a named receiver must reuse the boundary account, first identify one exact claim-bearing U.MethodDescription episteme under A.3.2 and C.2.1. Its claim content concerns the exact composite Method and states the exposed, forwarded, and encapsulated interactions. Then keep the publication-side objects and designation content below separate.

In B.1.5, composite-Method boundary account is the local Plain phrase for this MethodDescription claim content. A boundary-account form is the separately identified reusable arrangement used to present that content when publication is load-bearing. Neither phrase creates a new kind or acronym.

1. A bounded-use-declaration episteme states the operations or decisions supported by this publication, the conditions of that use, and the excluded stronger use.
2. An audience-declaration episteme states the audience criterion. The actual audience consists of entities admitted by that declaration; those entities are not substituted for the declaration episteme as a publication-relation participant.
3. An independently identified reusable boundary-account arrangement is a publication-form participant only while E.24.PUB PublicationFormExpressionRelation(description edition, boundary-account form, bounded-use declaration) obtains.
4. A paper card, poster, page, file, or screen must first be identified independently as a physical or digital U.PresentationCarrier; E.24.PUB PublicationFormBearingRelation(carrier, boundary-account form) then states which form it bears.
5. An actual system performs separate rendering, printing, uploading, indexing, or access-granting publication Work. That Work may establish or restore availability, but it is not the publication occurrence or one of its participants.
6. One EpistemePublicationRelation occurrence, with the exact five participants <description edition, audience-declaration episteme, bounded-use-declaration episteme, boundary-account form, carrier>, makes the edition available to the declared audience for the declared use throughout its maximal continuous interval of availability. The relation occurrence is not performed by the publishing system, and the boundary-account form does not publish itself.
7. Names, labels, and links that designate the Method or description edition remain separately governed designation content. Neither the form nor the carrier establishes designation merely by displaying similar words.

Reader-facing boundary-account prompts:
  described Method, exact MethodDescription edition, and effective reference scheme when its variation changes the Method meaning or claim use
  named audience criterion and bounded use, including any excluded stronger use, when publication is load-bearing
  exposed and forwarded interactions
  accepted input or call meaning
  preconditions and intended result or preserved condition
  failure and stop routes
  invariants
  exact B.1.4 order aggregation or OrderSpec only when the receiver relies on its order, join, or independence limits
  applicability, bounds, and quality or assurance envelope only when they limit the interaction on which the receiver relies
  adapter, typed-join, and assurance references only when the receiver uses them
  plain rationale for each encapsulated interaction on which misuse is likely

These prompts organize presentation; they are not direct-relation SlotSpecs, relation participants, Method parts, or a schema that creates a Method. None supplies the world-side methodPartOf facts or any other whole-forming claim. For a lightweight internal use, state the few boundary decisions in clear sentences and stop; do not create a description edition, declaration episteme, boundary-account form, carrier, publication Work, or publication occurrence by ritual.

B.1.5:4.5 - Keep Method Qualification And Work Occurrence Separate

B.1.5 evaluates and grounds the composite-method qualification of an exact U.Method already identified under A.3.1. A separately constituted U.MethodDescription may state that composition claim. Neither object creates performed Work.

One dated U.Work occurrence enacts one exact U.Method only when the A.15.1 method-enactment relation obtains. Recover each exact actual performer through A.13; A.15.1 then independently identifies the Work, time, containing System, and enacted Method. F.6 enters only when the Method-enactment account also consumes precise assignment-bound attribution through the same obtaining A.13 assignment; missing or failed F.6 leaves the Work and enactment intact. The System acts and the assignment does not. An assertion or occurrence description may cite those facts and the MethodDescription used; the Work occurrence does not store a card or record.

Parameter bindings, affected referents, resource use, telemetry, retries, results, actual transformations, production, evidence, evaluation, delivery, and acceptance remain separate objects and direct relations under their own governors. They do not become method parts, method identity fields, or generic Work outcomes merely because a report places them beside the Work.

The composition link is not one-to-one. A Work occurrence may enact the whole method without exposing every submethod as a separate work part. An exact A.15.1 TemporalPartOf_work may enact the same whole method during its selected interval. An A.15.1 episode may span several method factors, repeat one factor, or be split by evidence policy without changing the method identity. Conversely, a work part does not establish a submethod. A work part enacts a submethod only when that submethod is already an independently identified U.Method and a separate enactsMethod(workPart, submethod) occurrence obtains.

Reader check. Before saying that a work part enacts a submethod, name both sides:

• the occurrence-side object: parent U.Work, obtaining work-part relation, interval or boundary, and exact performer System recovered through A.13; only when this reader check expressly consumes precise assignment-bound attribution, also name the exact covering A.2.1 assignment and obtaining F.6 relation; add any separately obtaining resource or evidence relation only when used;
• the method-side object: exact A.3.1 submethod, methodPartOf occurrence, whole-forming claim at its A.6.RCD disposition, preconditions, intended result or preserved condition, interface boundary, and whole-Method identity;
• the cross-side fact: the exact enactsMethod(workPart, submethod) occurrence.

If any side is missing, lower only that side. Do not repair a missing submethod by inventing a work part, and do not repair a missing work part by inventing a submethod. Keep a method-description node, evidence segment, mechanism material, system-component behavior, or A.15.4 appearance-based reliance repair request under its subject pattern.

For an ordinary working question—what larger work is being done through this action now—use B.1.5.EW. It recovers the constitutive connections at the needed grain and shows how a changed encompassing condition changes the action. An ongoing whole need not be completed, and its constituents need not all act at once. When changing a constituent for use in one or several wholes, B.1.5.RS follows the change through their entry conditions, interactions and required results. The qualifications above still decide the corresponding Method and Work claims.

B.1.5:4.5.1 - Planning And Performed-Work Obligations

B.1.5 has three common use positions, but they are positions in use, not U-kinds:

• Planning or description-side use. A planner system performing planning Work recovers the exact Methods, methodPartOf occurrences, whole-forming claims at their A.6.RCD dispositions, any justified order aggregation, typed joins or adapters, interface boundary, invariants, and whole-level commitments. A resulting exact U.WorkPlan may cite the MethodDescription edition on which it relies; neither the planning Work nor the plan is the reader that defines Method identity.
• Performed-work use. Recover each exact actual performer through A.13, let A.15.1 independently admit the Work, and recover the exact enactsMethod occurrence for the whole Work. Add the exact covering A.2.1 assignment and F.6 relation only when this use expressly consumes precise assignment-bound attribution; missing or failed F.6 leaves the Work and enactment intact. Check capability fit or admission only when the work-entry decision consumes those claims; then check preconditions, order conformance, and exposed or forwarded interactions through their subject patterns. State resource use, evidence, and results only through their own obtaining relations. None becomes part of the method.
• Assurance use. Identify cutset submethods, fragile typed joins, adapter points, mapping congruence or CL-sensitive edges, and the envelope or scope in which the composite method is expected to hold. B.3 and related assurance patterns evaluate those hooks; B.1.5 only makes them visible.

Useful invariants remain: a single recovered submethod composed alone does not create a surprising new Method; order is deterministic only under the exact order claims and conditions at their selected A.6.RCD dispositions; any throughput or quality bound must name its characteristic, critical path, and weakest-link basis; strengthening a submethod, adapter, or typed join should not make the composite Method worse unless a stated side condition changes.

B.1.5:4.5.2 - Stop Before Transformation Composition

Method composition and Work decomposition establish no U.Transformation part, composite transformation, transformation atomism, or TransformationPartOfRelation. Even when several method parts address the same referent and one Work enacts the whole method, identify each actual transformation independently under A.3.4. If a claim needs transformation composition and no direct transformation-composition governor supplies its participants, obtaining rule, and occurrence identity, return missing-governor[transformation-composition] for the proposed whole and independently identified changes. Do not infer either composition or indivisibility from the gap.

B.1.5:4.6 - Select A Structure Below The Whole-Method Threshold

Use A.22 when independently identified Methods and already obtaining relations are useful to one question or action but do not construct one whole Method. For an actual load-bearing selection, first name the selecting system, selection Method, dated selection Work and bindings, and any result episteme needed to preserve the decision. Then name all four structure discriminators: exact constituents, exact selected obtaining relation occurrences, applied constraints, and the use frame. For a one-off hypothetical comparison, state the comparison and stop without asserting a selected U.Structure. MethodRelationStructure may be used as a local readable designator only for an actually selected structure; it is not a U-kind, relation kind, Method holon, or identity field.

Typical cases:

• a fallback registry selects among alternatives but supplies no whole method;
• a workflow diagram relates method descriptions but does not recover method parts;
• a method family has independently governed refinement, substitution, or dispatch relations;
• a graph or algebra represents selected method relations as a lens;
• the same method labels occur under different effective reference schemes, while the local senses have not been resolved and any F.9 Bridge would establish only sense correspondence, not method identity;
• a work plan orders tasks but does not define one reusable method.

The selected structure is a dependent organization for its named use. It does not create its constituents or relations, become a Method, or supply holonhood. Conversely, the internal construction of one exact Method whose composite qualification has been established does not become a second generic structure merely because a diagram can display it. Select a U.Structure only when that organization itself changes the next question or action.

This lower object is not a failure. It is the right governed object when relation organization is useful but whole-method construction is not current.

B.1.5:5 - Archetypal Grounding — Worked Slices

B.1.5:5.1 - Manufacturing Recipe

AssembleFrame, InstallMotor, AdaptMotorConnector, RunFunctionalTest, and BuildAndVerifyPumpUnit are exact U.Method values already identified under A.3.1; the last is now the candidate for a composite-method qualification. The four participant-determined occurrences methodPartOf(AssembleFrame, BuildAndVerifyPumpUnit), methodPartOf(InstallMotor, BuildAndVerifyPumpUnit), methodPartOf(AdaptMotorConnector, BuildAndVerifyPumpUnit), and methodPartOf(RunFunctionalTest, BuildAndVerifyPumpUnit) obtain because the stable whole construction rule names each contribution. Every already admitted connector-adapter alternative may stand in methodPartOf simultaneously; one Work occurrence selecting an alternative does not toggle those atemporal occurrences. Removing a contribution from the construction rule, adding a new admitted alternative, or changing a required order, join, whole result, or boundary outside the declared variations identifies another whole Method.

For the ordinary use, say: the installed motor must provide the harness-installed condition required by functional test; when the supplier connector does not provide it, AdaptMotorConnector must provide the conversion before test; adapter failure stops the whole before test. In this one use, PumpInstallBeforeTest and PumpConnectorAdapterJoin are readable labels for local compound claim content in the exact PumpBuildCompositionDescription-v1 : U.MethodDescription episteme under A.3.2 and C.2.1, not relation-kind names or occurrence designators. If several pump-family uses need the same parameterized rule, A.6.RCD can identify a reusable predicate-definition episteme. Only a later named receiver that needs stable occurrences can justify evaluating a derived-kind candidate under E.24 and E.24.UK.

The composite qualification additionally requires the candidate’s generic participants, applicability, preconditions, accepted inputs, final effect, preserved conditions, exposed start and abort interactions, encapsulated calibration interaction, failure routes, and reidentification rule. A list of the five names or an arrow diagram establishes none of these facts.

PumpUnitBuildWork-2026-07-29 may enact the whole through one exact enactsMethod occurrence without four corresponding work parts. If a separately admitted MotorInstallationWorkPart-2026-07-29 exists, it enacts InstallMotor only through its own enactsMethod occurrence. Resource use, test telemetry, the produced pump unit, acceptance, and evidence remain under their subject patterns.

B.1.5:5.2 - Emergency Intake

RegisterPatient, AssessVitals, ClassifyUrgency, and RouteToCare are independently identified Methods. For a one-off protocol review, the practitioner may state two local claims in ordinary language: the intended vital-sign result meaning of AssessVitals must satisfy the admitted input meaning of ClassifyUrgency; and the declared triage rule decides which admitted urgency category holds from the declared vital-sign conditions and, when the protocol uses them, the declared symptom conditions, then maps that category to one compatible RouteToCare. If no category or several incompatible categories hold, the practitioner stops the routing decision and returns the guard rule for repair. These are useful claim contents, not MethodResultPreconditionRelation or MethodDispatchRelation admissions.

This review is deliberately hypothetical and non-load-bearing. It compares the four Methods and the two claims but does not assert a persisted U.Structure or a selection judgment. If a later receiving use needs an A.22-selected structure, its selection must identify the exact selecting system, selection Method, dated selection Work and bindings, and—where the result must persist—the result episteme. The structure itself is then identified by all four A.22 discriminators: exact constituents, exact independently admitted obtaining relation occurrences, applied constraints, and use frame. The present local claims cannot be relabelled as such occurrences merely to fill that list.

The comparison still discriminates the non-composite case. No reusable whole action, complete precondition-to-result boundary, response to every guard conflict, or whole reidentification rule has been established. A wall poster may be a carrier bearing a publication form; an exact U.MethodDescription edition is a different claim-bearing episteme, and an actual publication occurrence is what makes that edition available to an audience. For intake Work, recover each actual performer through A.13 and admit the Work independently through A.15.1. Only if this comparison also consumes which assignment covered that Work should it separately check the A.2.1 occurrence and obtaining F.6 attribution; capability or admission claims consumed by entry remain separate. None of these facts is a Method part.

If a later hospital protocol first identifies an exact A.3.1 Method such as EmergencyIntakeMethod-v4 with the missing whole semantics, B.1.5 can test its composite-method qualification. Neither a poster, the one-off comparison, nor a later selected structure turns into that Method.

B.1.5:5.3 - Learned Model Pipeline

A neural-network pipeline may describe feature extraction, embedding, attention, retrieval, ranking, and explanation generation. Some blocks may be formal substrate or mechanism material, some may be constituents of a U.MethodDescription, and some may be recovered as U.Method values.

After the candidate whole represented by the pipeline and every claimed part have been independently identified as exact A.3.1 Methods, that candidate qualifies as composite only when exact methodPartOf occurrences, whole-forming claims at their A.6.RCD dispositions, accepted inputs and outputs, invariants or admissibility conditions, typed joins, fallback behavior, failure conditions, interface decisions, and reidentification rule are present. Otherwise keep the graph as a MethodDescription, mathematical lens, mechanism material, or—when an actual selection basis and receiving use exist—an A.22-selected U.Structure.

Suppose one dated training Work enacts the exact pipeline Method while three independently identified transformations occur: the feature store changes, model parameters change, and the ranking index changes. Common Work, shared data, Method order, and temporal adjacency do not establish transformation parts or one composite transformation. Without a direct transformation-composition governor, retain the three transformations and return missing-governor[transformation-composition] for the proposed three-change whole; do not call them atomic either.

B.1.5:5.4 - Evidence Synthesis And Publication

CollectDatasets, NormalizeSchemas, EstimateModel, CrossValidate, DraftManuscript, and EvidenceSynthesisAndPublication-v3 must first be exact A.3.1 Methods. B.1.5 can qualify the last as composite only when every claimed methodPartOf occurrence obtains and its whole-forming claims and constraints pass A.6.RCD’s lightest sufficient disposition. In ordinary language, the intended result of NormalizeSchemas must satisfy the admitted input meaning of EstimateModel; legacy datasets may require adapter Methods; CrossValidate may be a critical cutset for later assurance; and a provenance condition may be a precondition of DraftManuscript before publication Work begins.

A paper draft, workflow diagram, repository, or notebook may be a claim-bearing episteme, a representation, or a carrier; its form does not make it the Method. Publication Work is U.Work. Compute, storage, reviewer time, artifact production, release, and acceptance stay with their subject patterns.

EvidenceSynthesisInterfaceDescription-v3 : U.MethodDescription may state that the Method exposes Submit() and ReleaseArtifacts(), forwards CrossValidate.Folds(k), and encapsulates ad hoc scrubbing utilities. Identify SubmissionReleaseBoundaryAccountForm-v3 independently as the reusable arrangement entity selected as the boundary-account form. Identify EvidenceSynthesisMethodsPage-2026-07 : U.PresentationCarrier independently as the digital carrier. Identify SubmissionAndArtifactReleaseUse : U.Episteme as the bounded-use declaration whose claims state the supported submission and artifact-release operations, their conditions, and the excluded stronger use. Identify SubmittingResearchersAudienceDeclaration-v1 : U.Episteme as the audience declaration whose claims select the authorized submitting researchers; those researchers are the declared audience, not a participant substituted for the declaration episteme.

PublicationFormExpressionRelation(EvidenceSynthesisInterfaceDescription-v3, SubmissionReleaseBoundaryAccountForm-v3, SubmissionAndArtifactReleaseUse) must obtain for that form use, and PublicationFormBearingRelation(EvidenceSynthesisMethodsPage-2026-07, SubmissionReleaseBoundaryAccountForm-v3) must obtain for that bearing claim. ResearchPublicationSystem performs the separate EvidenceSynthesisInterfacePublicationWork-2026-07 : U.Work, which may establish or restore availability. The distinct EvidenceSynthesisInterfacePublication-2026-07 occurrence of EpistemePublicationRelation has the five fixed participants <EvidenceSynthesisInterfaceDescription-v3, SubmittingResearchersAudienceDeclaration-v1, SubmissionAndArtifactReleaseUse, SubmissionReleaseBoundaryAccountForm-v3, EvidenceSynthesisMethodsPage-2026-07> and carries the description edition’s enduring availability to the audience selected by the audience declaration for the bounded use. Publication Work is not a participant of that occurrence. None of these description, declaration, form, carrier, Work, or publication-relation objects creates an interaction, SlotSpec, Method part, or composition fact.

B.1.5:5.5 - Ordered Preparation And Simultaneous Performance

A music-and-dance performance can contain both kinds of fact. Venue setup, safety checks, and interface checks may need a real order before the public performance starts; a failed safety check may stop the unfolding. Preserve that order when the exact Methods and conditions support it. It is not a level structure.

During the performance, dancing, music making, sound mixing, lighting, and stage coordination may contribute at the same time. If the project identifies one performance Work whole, it may enact several exact Methods through separate relations. If it identifies several Work occurrences, state which overlap. Do not rewrite these contributions as five stages merely because a production plan or review lists them one by one. Conversely, do not erase real setup, cue, or handoff order merely because the overall performance is simultaneous.

The same two-way check applies elsewhere. In engineering Work, a lifecycle or product order does not prove that architecture, realization, integration, assurance, and feedback form one sequence. In operating Work, a workflow line does not serialize queues, commitments, resources, measures, and improvement. In capability development, preparation Work may precede the target Work while several target Methods contribute together during the transfer check. Preserve every real continuation condition, but do not invent order among concurrent contributions.

B.1.5:6 - Bias-Annotation

Lenses tested: Gov, Arch, Onto/Epist, Prag, Did. Scope: cross-domain order-sensitive composition of already identified U.Method values. It does not cover sole-Method identification, description-only organization, dated Work decomposition, structural mereology, or transformation composition without a direct governor.

• Gov: each methodPartOf occurrence and each other whole-forming claim stays with its direct governor; a named receiver changes how much of the boundary account must be stated or published, not whether a world-side fact obtains.
• Arch: the whole is qualified from exact part Methods and construction facts; order aggregation, a selected A.22 Structure, and a separate higher-level reidentification claim remain distinct architectural objects.
• Onto/Epist: Methods and obtaining relation occurrences remain distinct from MethodDescription claims, boundary-account presentation, carriers, publication Work, and publication occurrences.
• Prag: ordinary use may stop at readable local claims; reusable definitions, relation kinds, declarations, publication, and assurance are added only when a named receiving use needs them.
• Did: the manufacturing, emergency-intake, learned-pipeline, evidence-synthesis, and performance slices show positive composition, useful non-composite stopping results, and the difference between real order and simultaneous contribution across domains.

The pattern intentionally biases toward explicit construction and boundary accounts when joins or outside reliance are load-bearing. The lightweight local-claim lane and subject-pattern exits mitigate that bias so inspectability does not become ritual apparatus.

B.1.5:7 - Conformance Checklist

B.1.5:8 - Common Anti-Patterns and How to Avoid Them

B.1.5:9 - Consequences

B.1.5 buys inspectable Method composition without confusing the candidate Method, composition claim, MethodDescription, selected Structure, Work occurrence, resource use, and assurance argument. The practitioner can say which exact Methods are parts, which ordinary whole-forming claims and constraints qualify the candidate as composite, which interactions belong to its boundary, what exact Work enacts it, and where a stronger claim must stop.

The cost is proportionate explicitness: exact Methods, methodPartOf occurrences, whole-forming claim content, order and join conditions, interface decisions, whole semantics, and reidentification must be stated before the composite qualification can be relied on. Ordinary use can stop at readable local claims; reusable definitions, relation kinds, declarations, publication, and assurance are added only when a named receiver needs them.

B.1.5:10 - Rationale

The rationale is a strict object separation. Paying this explicitness cost exposes brittle joins and accidental external dependencies at Method boundaries before someone relies on the composite claim. Order is semantic but not structural parthood. A method can be a non-agentive holon, but a step label, graph node, phase, source section, description constituent, plan item, or work part is not a method part until the U.Method and methodPartOf occurrence are recovered. Gamma_method concerns ways of doing; Gamma_work supports occurrence-side resource analysis; B.3 evaluates assurance; A.22 selects useful relation organizations; B.2 handles a separately current higher-level reidentification claim. None of those neighboring objects replaces the direct B.1.5 construction facts.

B.1.5:11 - SoTA-Echoing

These rows answer the B.1.5 practice question: how to decide and expose order-sensitive Method composition without mistaking descriptions, Work, event records, or construction diagrams for the composite Method.

Currentness and reopen. These four decisions are qualified by the exact source selections cited above. Reopen only the affected row when a cited source or edition is superseded, or when newer practice changes the relied-on model/occurrence separation, order or join condition, interface or substitution boundary, or construction and reidentification test. Recheck that row’s B.1.5 adoption, refusal, and affected Solution, worked-case, checklist, and Relations loci; leave unaffected rows closed.

B.1.5:12 - Relations

• Uses A.1 for the general non-agentive-holon recognition boundary; A.1 does not supply Method-part or whole-forming facts.
• Uses A.3.1 to identify the exact candidate Method and every exact part Method before B.1.5 tests the composite-method qualification; B.1.5 directly governs only MethodPartOfRelation and the composite-construction test.
• Uses A.6.RCD for serial, parallel, guarded, iterative, fallback, adapter, join, substitution, and other whole-forming claims. Existing direct predicates, local compound claims, and reusable predicate definitions are valid stopping results; only a named occurrence-semantics need requires E.24 for a kind candidate and E.24.UK.
• Uses A.6.REL only when an independently admitted relation kind has an obtaining occurrence whose identity a receiver consumes. B.1.5 does not manufacture occurrence semantics for ordinary claim content.
• Uses C.2.1 to identify predicate-definition, signature, and MethodDescription epistemes and any later episteme with changed identity-bearing content. Uses EpistemeEditionRelation only when C.2.1’s exact historical-continuation predicate obtains; otherwise the later episteme is a non-continuing replacement. A predicate definition may satisfy ordinary A.6.0 U.Signature membership; only an admitted relation kind can have a RelationSignature.
• Uses B.1.4 only when a receiving use needs an explicit aggregation of already admitted, obtaining order relations, an OrderSpec, and join or independence conditions.
• Uses A.3.2 for each exact claim-bearing U.MethodDescription and E.24.PUB only when a named use requires publication detail: independently identified bounded-use- and audience-declaration epistemes, boundary-account form and U.PresentationCarrier; exact PublicationFormExpressionRelation and PublicationFormBearingRelation; separate publication Work performed by a system; and the five-participant EpistemePublicationRelation occurrence that makes the edition available. Raw audience and designation content remain separately governed.
• Uses A.22.CGUS when a real first–then, guarded, branching, or returning unfolding is the useful result; an unfolding position is not a subject level or evidence that all contributions are sequential.
• Uses A.15, A.15.1, and A.15.2 for exact dated U.Work, enactsMethod, and plans; uses A.2, A.2.1, and F.6 for local system-role-kind and Method alignment, separately declared assignment species, actual assignment occurrences, and obtaining Work–assignment attributions. The Method does not act, Work is not a relying reader, and neither a system-role kind nor an assignment performs Work.
• Uses B.1.6 and Gamma_work only for occurrence-side work-resource aggregation after the Work and resource relations are recovered.
• Uses B.3 for cutset, weakest-link, CL-sensitive mapping, and assurance claims; composition alone supplies no assurance verdict.
• Uses A.22 only for a real selected organization with its selection basis and four identity discriminators. A one-off hypothetical comparison and local whole-forming claims do not assert a selected U.Structure.
• Uses C.13 only after B.1.5 supplies exact Method parts, whole-forming facts and constraints, and the whole reidentification rule; C.13 consumes those facts but does not create them or require one relation kind per fact.
• Keeps A.14 structural-component parthood distinct from Method composition; coordinates with B.3.5 only when a published structural claim and its grounding are current.
• Uses B.2 when a separate higher-level reidentification or emergence-family explanation is current; ordinary composite-Method identity still needs its explicit B.1.5 rule.
• Uses G.5 when a Method-family registry, selector, fallback, or candidate-set decision is current but no whole construction is claimed.
• Uses C.29, A.6.1, and E.20 when a mathematical lens, formal substrate, mechanism, or representation-maintenance claim is current.
• Uses E.10 for method, step, process, workflow, ownership/stewardship, requirement, and source wording precision recovery.
• Stops before any positive transformation-composition or transformation-part claim until a direct governor supplies exact participants, obtaining semantics, and occurrence identity.

B.1.5:End

B.1.5.EW - Recover How Constituent Actions Enact Encompassing Work

Type: Method pattern Status: Stable

B.1.5.EW:1 - Problem frame

Use this pattern when you need to understand, perform, teach, divide or change a way of working and cannot yet explain how its constituent actions perform the encompassing work. A person knows each movement but loses the partnered dance. A team improves a calculation but no longer obtains a usable engineering answer. A description lists stages, yet the reader cannot tell what larger work is being done through the present action.

Start with one action and ask: “What am I doing through this action now, and what makes it part of that work?” Then recover the constituents needed to perform it and the conditions of the encompassing work that affect it.

The first useful result is an explanation you can use: the selected action, its relevant constituents and encompassing work, the connections that make the whole possible, and any difference that requires changing the action or its organization. A short demonstration can supply this result. A retained diagram or record is useful only when someone needs it later.

Use an already understood connection directly. This pattern does not require reanalysing every familiar act or finding the smallest possible action and largest conceivable whole. Stop where further detail would not change the present performance, learning, division of work or correction. Use B.1.5 when the separate question is whether identified Methods qualify as one composite Method; use C.32.MWA when several structures need to be synthesized into a practice architecture.

B.1.5.EW:2 - Problem

A sequence answers “what happens after what?”. It can leave out “what is being done through what?”. While a person adjusts a step to a partner, they can already be performing a coordinated figure and the phrase containing it. They do not first finish adjusting and only later start dancing the figure.

The relation matters for action. A step that is correct in a solo exercise may be wrong in this partnered phrase. Improving the isolated movement can reinforce the failure if the needed change concerns coordination or the encompassing intention.

The reverse mistake is to call every concurrent or indispensable activity a constituent. Music reproduction can support a dance without being part of the dancer’s Work as that Work is bounded. A planning decision made yesterday can still constrain today’s action without being performed again now.

B.1.5.EW:3 - Forces

• Familiar constituents make work possible, while their combination can introduce a difficulty absent from separate practice.
• Encompassing requirements constrain the parts; the parts’ actual capabilities limit what the whole can achieve.
• One action can serve several wholes, whose conditions can differ or conflict.
• A short account can guide action; unnecessary decomposition consumes the attention needed to act.
• The whole may be ongoing while only some of its constituents are active.
• A planned connection helps design work, but actual enactment needs the performed connection.

B.1.5.EW:4 - Solution

Recover the connection in both directions: what larger work is being performed through this action, and what constituent actions make it performable? Keep genuine before-and-after dependencies alongside these connections.

B.1.5.EW:4.1 - Choose an action and the work being explained

Name an action in a recognizable situation and the moment or interval under consideration. State whether you are explaining observed Work or proposing how future work could be done. Identify what is being attempted and what a useful result would be.

Use ordinary verbs first: adjusting a step, comparing a measurement, adding a value, questioning an assumption. If the description supplies only a noun such as “coordination”, recover what the participant actually does.

B.1.5.EW:4.2 - Recover an encompassing performance

Ask what larger action is being done through the selected action now. Explain the organizing connection: which part of that larger action this performs, how it combines with other contributions, and under which conditions.

For an actual occurrence, this connection must concern the performed work. Merely intending to obtain a later benefit is insufficient. A contribution can constitute part of an ongoing attempt even when that attempt fails; successful completion is a further question.

Distinguish three possibilities where they change your answer:

• The same Work enacts several Methods.
• An independently identifiable performed suboccurrence is an operational part of encompassing Work under A.15.1.
• One Work supports, overlaps or supplies a later result to another without being its constituent.

Choose the occurrence account that fits the work. Several descriptions do not require several Work occurrences. Identify a suboccurrence separately when its extent, performer, result, resource use or correction needs to be distinguished.

A useful test is to explain the positive connection, not just what would fail if the action disappeared. Removing an external power supply can stop a calculation; that fact alone does not make power generation part of the analyst’s Work.

B.1.5.EW:4.3 - Follow constituent and encompassing work

Continue through the constituent–whole connections in the selected Method or Work structure only while the next encompassing whole’s conditions change the action, its learning or its use. Explain each intervening connection. If an action serves two wholes, keep both uses and their different conditions visible.

Then ask what you must be able to do, or obtain from another participant, to perform the selected action. If a described construction remains unclear, use B.5.RC to recover its inputs, operations, conditions and a small execution. If you lack the domain know-how, obtain an explanation or demonstration. If you understand the operation but cannot perform it in the combination, practise with the encompassing conditions, obtain support or use another qualified contributor. Stop a branch at an understood operation or an available contribution sufficient for this use.

These moves need not end in one tree. Nor does following several connections establish an unrestricted transitive parthood rule. Carry the actual conditions through the intervening wholes. A move from an action to its enabling tool, or from a Method to a more general Method, changes the relation; describe it accordingly.

B.1.5.EW:4.4 - Examine the combination at a revealing moment

At the chosen moment, identify what must be coordinated and what can vary. Keep prior-result requirements: an operation can be a constituent of an ongoing whole and still have to wait for another constituent’s output.

Change one condition of the encompassing work in thought or in a suitable trial. Determine what must change in the constituent action. Then consider a limitation of that action and determine which encompassing performance it prevents or restricts. Use available knowledge when it answers these questions; a new experiment is not automatically required.

Where control is involved, first check whether the feedback concerns the response and interval being judged. Delayed or misleading feedback can make adequate execution look wrong. Then distinguish failure to follow the reference from accurate execution of a reference that is no longer feasible or useful. A reference may remain in force between updates; generating or revising it is separate work. C.30.LCA helps recover the control relations when those are unclear. Claims about dynamics, feasible response or timing need their subject-specific basis; a conflict requiring architecture change can continue through C.30.ILC.

B.1.5.EW:4.5 - Use the explanation to continue or correct the work

Choose the correction that the recovered connection supports:

A diagnosis may remain conditional when two explanations fit. Obtain further information only if it can change the next useful action and warrants its burden under C.11.DUA. More encompassing work does not automatically confer authority to override a participant’s constraints.

Return the explanation, any selected correction and the conditions that matter for using them. Recognition of a plausible connection is not assurance of successful performance. Establish a stronger composition, causal or performance claim only when the receiving use requires it.

B.1.5.EW:5 - Archetypal Grounding

B.1.5.EW:5.1 - A step within a partnered phrase

During one beat, a dancer transfers weight while adjusting the direction and size of the step to the partner’s movement. That adjustment is part of performing the coordinated turn; the turn is part of performing the phrase with its intended timing. The turn and phrase are ongoing through this action, although neither is yet complete.

A solo drill established that the dancer can make a large turn. In the partnered phrase, that amplitude pulls the partner off the shared line. The correction is to reduce the step and preserve the connection, not to repeat the large turn more accurately. A slower musical phrase changes when weight transfer must finish and how long the connection must remain available.

A different dancer has adequate strength and static axis control and knows the figure, but cannot maintain balance during its rotation. The missing performance lies between available muscular actions and the known figure. More strength practice or sequence recall need not repair this stipulated gap. Develop the rotational coordination in suitable practice, then return to the figure and vary the conditions that affect the combination. Keep already attained abilities; test the needed intermediate performance rather than assuming that mastery below and knowledge above fill it.

The selected Work structure here connects the performed movement, coordinated figure and phrase through their constituent–whole relations. Playing the recording is external support under this boundary. Practising these movements may later contribute to cultural transmission, but one beat does not establish that a cultural variant persists in a population.

B.1.5.EW:5.2 - An update within a running calculation

An analyst is totaling accepted observations as part of preparing a report. The algorithm maintains a running sum. On reading the next value, adding it to the accumulator is a constituent of computing the total; computing that total is part of the report preparation currently under way. The addition, computation and report preparation do not incur three copies of that minute of work.

The addition is correct over the supplied numbers. The report, however, requires excluding duplicate observations. If duplicate detection is missing, more precise addition cannot repair the report. Recover the accepted-observation rule and apply it before the affected update. The genuine order remains: the next update consumes the current accumulator, and the report cannot use the final total before the calculation finishes.

A scheduler running on the same machine overlaps the calculation. That overlap alone makes it neither an arithmetic constituent nor report-preparation Work.

B.1.5.EW:5.3 - Continuing operation between plan updates

A delivery team is following a route. Each driving action is part of progressing along that route and performing the delivery. Route planning was done earlier. Its result still constrains driving; the team is not performing the planning Work at every instant.

A newly closed road makes the old reference unusable. Better steering cannot restore feasibility. The team needs a revised route under the actual road and delivery constraints. If the road is open and the driver has merely missed a turn, execution correction may suffice. This distinction locates the useful intervention without imposing a fixed number of control levels.

B.1.5.EW:6 - Bias-Annotation

An observer can recognize their own specialist operation while missing the connection needed by another participant. Ask the receiver what the encompassing work requires. Equally, do not presume that a manager’s broad description supplies the constituent expertise. Actual constraints can invalidate the requested whole.

B.1.5.EW:7 - Conformance Checklist

• Can the reader identify the action and actual or proposed work being explained?
• Is each claimed encompassing connection explained through performed or proposed organization, rather than timing or importance alone?
• Are the needed constituents recoverable without indefinite decomposition?
• Does a consequential change in whole conditions produce an intelligible change in the action?
• Are genuine result dependencies and relevant external support retained?
• Does the result identify a useful continuation without claiming that recognition establishes success or assurance?

B.1.5.EW:8 - Common Anti-Patterns and How to Avoid Them

B.1.5.EW:9 - Consequences

The practitioner can locate a missing ability, combination condition or unworkable demand instead of treating every failure as poor execution. The account also makes division of work more useful: a contributor receives the conditions of the whole, not only an isolated task name.

Recovering these connections takes effort. Bound it by the action or explanation needed; reuse understood constituents and retain unresolved distinctions only when they affect that use.

B.1.5.EW:10 - Architectural Rationale

Work can be described at several grains without becoming several successive activities. Constitution explains why doing a part is already participating in doing the whole. Temporal order explains a different dependence, including order among those parts.

A practitioner can explain how one occurrence is performed without first establishing a reusable composite Method. Recovering that connection is enough when it answers the working question; synthesizing several practice structures is useful when their different organizations affect the decision.

B.1.5.EW:11 - SoTA-Echoing

Craver and Bechtel’s mechanistic account is a historical anchor for distinguishing constitutive organization from causal interaction. Weinberger’s critique shows why identifying intermediaries does not settle every explanatory question. This pattern adopts the need to explain organized participation; it imports no universal theory of causation or experimental test for parthood.

Matni, Ames and Doyle explain interacting control functions with different rates and recursively refinable organization. Their formal control constructions support the control example; they do not establish the constitution of every human practice. The practical recovery operation here is a methodological synthesis under FPF’s Method and Work distinctions.

For the practical question here—what larger work is being done through this action, and why must the action change—a lifecycle account is a serious but incomplete alternative. It usefully preserves preparation, delivery and other genuine precedence. It does not by itself explain why a smaller partnered step performs the figure better than a larger solo step at the same moment. Sections 4.2 and 4.4 therefore adopt organized-participation recovery and a changed-whole-condition comparison, retaining the lifecycle account where order matters. A short explanation can settle this question without building a full practice architecture.

A fixed control-layer diagram is another useful alternative when the problem already has a justified controller/reference/plant interpretation. The Matni–Ames–Doyle account helps interpret such a case and its differing rates. Section 4.4 retains the distinction between inadequate execution and an infeasible reference; section 4.2 requires the particular constituent connection rather than inferring it from diagram depth. For non-control work, the source’s formal constructions provide an analogy, not its ontology or a guarantee. Reopen this synthesis if a worked case requires causal influence to be mistaken for constitution, if its changed condition fails to discriminate the proposed connection, or if a simpler subject Method supplies the same useful correction. Where only an earlier-result dependency matters, keep that dependency account and stop.

B.1.5.EW:12 - Relations

• B.1.5 supplies Method-composition conditions; A.3.1 supplies Method identity.
• A.15.1 supplies Work enactment and operational parthood.
• B.5.RC helps recover an unfamiliar construction from its description. Missing domain knowledge or performing capability retains the separate returns in section 4.3.
• B.1.5.RS tests a proposed constituent replacement in its receiving wholes.
• C.30.LCA and C.30.ILC address control-specific interpretation and cross-scope architecture conflict.
• C.32.MWA handles synthesis when several practice structures must be considered together.
• C.11.DUA bounds further investigation by what it can change.

B.1.5.EW:End

B.1.5.RS - Evaluate a Constituent Method Replacement in Its Encompassing Uses

Type: Method pattern Status: Candidate

B.1.5.RS:1 - Problem frame

Use this pattern when a constituent Method could be replaced, simplified or implemented differently and you need to know which encompassing uses remain possible. A faster check returns the same answer on familiar inputs but no longer exposes information another part needs. An approximation is adequate for ranking options but unsuitable for deciding whether a limit is exceeded.

Start with the direction of replacement and the practical gain sought. Ask: “What do the receiving wholes rely on, and does this candidate still supply it under their conditions?”

The first useful result is a bounded substitution decision: the uses preserved, uses needing adaptation or restriction, and uses for which the replacement is incompatible or unresolved. One decisive comparison may be enough. Do not perform a new trial when an available argument or known counterexample settles the decision.

Use B.1.5.EW first if the constituent and its encompassing uses are unclear. If only the wording or diagram changes and the performed Method remains unchanged, check that representation’s correspondence instead. If the replacement supplies an entire standalone Method, use the relevant fit and choice Methods; this pattern contributes only the constituent-in-whole question.

B.1.5.RS:2 - Problem

Local adequacy does not establish substitutability. The whole can depend on output meaning, intermediate interactions, order, timing, recoverability or resource demand that a local comparison omitted. A shared constituent can satisfy one whole and fail another.

The opposite failure is to demand that every internal detail remain identical. This prevents useful replacement even when the receiving work does not depend on that detail. The preservation question must come from the actual use.

B.1.5.RS:3 - Forces

• A local gain can remove a contribution needed elsewhere.
• Several uses may require different guarantees from the same constituent.
• Simplification saves effort when its lost detail is irrelevant to the receiving action.
• Strong evidence can be expensive; a bounded argument or counterexample may already settle the next move.
• A common replacement reduces maintenance, while separate variants can preserve otherwise incompatible uses.
• Method identity, description correspondence and performance evidence answer different questions.

B.1.5.RS:4 - Solution

Compare the candidate against what the encompassing work needs, then carry the changed contribution through that work. State the direction and conditions of the result.

B.1.5.RS:4.1 - Name the proposed change

Identify the current constituent, its candidate replacement and the gain: for example, reduced delay, effort or dependence on a scarce specialist. State what changes in the operation, its inputs, outputs, interactions or realization.

Keep a proposed replacement separate from one already performed. Use A.3.1 to settle any needed identity claim: exposing a hidden step, changing an implementation within an admitted variation and proposing another Method need not have the same answer.

B.1.5.RS:4.2 - Recover the receiving wholes

Identify the encompassing Methods or work arrangements whose use can change. Follow an indirect use through the intermediate whole while it affects the decision. Include a second receiving use when the constituent is shared; local success in the first use is not evidence for the second.

This is a search bounded by the intended replacement. If the actual users cannot be recovered, restrict adoption to the known uses or return the missing use information that prevents a broader decision. Do not require an inventory of all imaginable uses.

For each relevant whole, recover:

• what it supplies or assumes at the constituent’s entry;
• what result or interaction it needs from the constituent;
• timing, ordering, coordination and resource conditions that affect this use;
• what variation or loss it can tolerate.

Plain statements are sufficient when they make the comparison executable. Use an existing interface or formal contract when it already states these conditions.

B.1.5.RS:4.3 - Compare the contribution under those conditions

Apply the proposed constituent to the receiving conditions. Follow what it supplies through the affected part of the whole, including an interaction before final output when the whole relies on it.

Choose an argument, available observations, calculation or trial that can discriminate the decision at proportionate cost. A known violation can reject a general replacement without testing every possible input. A successful example can reveal a usable construction but does not automatically support all inputs.

When an approximation is proposed, state the property preserved for the receiving use: a bound, ordering, feasible action, specified error or other needed consequence. Equal rounded answers on one example do not establish preservation of a different property.

If the same implementation must serve several wholes simultaneously, examine their joint demands. Separate success under incompatible settings is not one shared implementation. Compare retained variants or changed coordination where that is useful.

B.1.5.RS:4.4 - Classify the replacement by use

This is a directed conclusion. Replacing A by B in one use does not show that A can replace B, that they are the same Method, or that B is preferable in all uses.

B.1.5.RS:4.5 - Adopt or retain alternatives

Choose at the supported scope, accounting for adaptation, learning, operation and maintenance costs. Retain separate variants when their different strengths justify the burden; a single universal replacement is not required.

For an ongoing operation, use its ordinary rules for introducing change and retaining continuity. State the condition that would require reconsideration: changed inputs, another receiving whole, a tighter timing limit, lost support or a newly relevant result property. No separate certificate or trial is required merely to record that an existing basis was sufficient.

Return the decision in the form its receiver needs. Where the conclusion is only recognition of a plausible substitute, say so. A claim of guaranteed preservation needs the argument or assurance appropriate to that claim under B.3; a local decision under uncertainty uses C.11 and C.11.DUA.

B.1.5.RS:5 - Archetypal Grounding

B.1.5.RS:5.1 - Faster ordering in two encompassing uses

A team proposes replacing a stable sorting Method with a faster one that need not preserve the input order of equal keys.

One whole prepares a table showing how many records occur at each key. Internal order among equal keys does not affect those counts. Subject to the remaining input and performance conditions, the candidate can supply that contribution.

Another whole schedules requests by priority while retaining arrival order among requests of equal priority. Its method first orders records by arrival and then stably orders them by priority. Replacing the second sort with the candidate can reverse equal-priority requests. The earlier arrival ordering no longer survives the composition.

An allowed reversal of two equal-priority records with different arrival times exposes the incompatibility with the required guarantee. This is a counterexample to unrestricted replacement, not a prediction that this implementation reverses every such pair; repeated random benchmarks cannot restore the missing guarantee. Options include retaining the stable Method or sorting by an explicit compound key of priority and arrival. The compound-key candidate has changed the operation; compare its behavior and cost before using it. The same “sorted by priority” description concealed different requirements of the two wholes.

B.1.5.RS:5.2 - A bounded estimate and a threshold decision

A constituent estimates a quantity with absolute error at most 2. A receiving whole only needs to distinguish alternatives separated by more than 4; the bound can support their ordering when both estimates satisfy it.

Another whole must decide whether the quantity exceeds 100. An estimate of 99 is insufficient: the admitted interval is 97 to 101 and crosses the threshold. A more accurate estimate or another decision rule is needed for that case. At an estimate of 95, the same error bound puts the whole interval below 100 and can settle that particular decision.

The change from “estimate the quantity” to “support this decision” makes the scope of replacement explicit. The threshold is stipulated in this constructed example; the pattern does not supply a rule for choosing it.

B.1.5.RS:5.3 - A quicker observation during coordinated work

A group performs a movement sequence in response to a leader. A proposed observation Method uses occasional snapshots rather than continuous observation. It can suffice for an exercise in holding a static pose, but miss the cue that starts a coordinated transition.

Recover the timing actually needed by the encompassing sequence. If the snapshot interval exceeds the available response window, better interpretation of each snapshot cannot restore the missed cue. Keep more frequent observation, redesign the cue so it remains available, or change the coordinated sequence. Each proposal has a different burden and requires its own bounded comparison.

B.1.5.RS:6 - Bias-Annotation

The participant proposing a replacement often sees its local saving more clearly than the costs borne by other users. Recover the receiving requirements before choosing. A demand to preserve everything can conceal the opposite bias: treating familiar implementation detail as necessary even when no receiving use depends on it.

B.1.5.RS:7 - Conformance Checklist

• Are the constituent, candidate, replacement direction and intended gain clear?
• Have the relevant receiving wholes and their relied-on contributions been recovered?
• Does the comparison carry the changed contribution through each affected use?
• Are joint requirements examined when one realization must satisfy several uses together?
• Does the conclusion preserve its conditions and evidence reach?
• Are adaptation costs and a useful reconsideration condition included where they change adoption?

B.1.5.RS:8 - Common Anti-Patterns and How to Avoid Them

B.1.5.RS:9 - Consequences

Useful replacements can be adopted where they work without silently breaking other wholes. An incompatibility can also expose a better architecture: different variants, an explicit interface or a changed combination.

The method requires knowledge of receiving uses. Its cost grows with meaningful differences among them, not necessarily with the number of documents or callers. Reuse one comparison across uses only when their relevant conditions and relied-on contribution match.

B.1.5.RS:10 - Architectural Rationale

Substitution is a relation to a receiving use. A constituent’s attractive property does not establish that relation. Recovering the whole’s dependence avoids both unrestricted replacement and unnecessary preservation of detail.

When the receiving uses are already understood, the practitioner can begin with their requirements and compare the replacement directly. The result is a directed substitution decision across one or several uses, including a candidate that changes the whole to accommodate the new constituent.

B.1.5.RS:11 - SoTA-Echoing

Mazo, Compton, Cohen and Ames formulate compositional contracts for layered control systems. Their contribution supports checking what adjacent functions assume and supply, including their different signal and timing models. This pattern uses that conditional-composition idea beyond the paper’s system class; its formal guarantees are not generalized.

The stable-sort case illustrates contextual preservation by an elementary algorithmic counterexample. The bounded-estimate case applies ordinary interval reasoning. These are constructed cases of the common Method, not evidence that every constituent requires a formal contract or a numerical error bound.

For the practical question of substituting a constituent, a local performance benchmark is a serious alternative: it can reveal speed, cost and errors on its tested inputs. It does not establish that a replacement preserving totals also preserves arrival order, or that its error bound supports the required threshold decision. Sections 4.2–4.4 therefore select receiving-use conditions first, then derive or test only the preservation those uses need. The worked counterexample or an available bound can settle the stated question at less effort than an additional benchmark; an unresolved performance question can still justify a targeted trial.

Formal compositional contracts offer a stronger alternative where the constituent, interfaces and encompassing system fit their mathematical assumptions. The cited control theory makes those assumptions and guarantees explicit. This Method adapts that conditional comparison into ordinary statements of inputs, interactions, results and permitted losses; it keeps the formal proof when its additional assurance is useful and attainable. It does not treat every professional practice as a control-system instance. Reopen the selected comparison when an unmodeled interaction, shared realization, changed receiver or unsupported adaptation defeats the preservation claim. If one constituent cannot satisfy the relevant uses together, retain different variants or change the encompassing arrangement instead of declaring one universally better Method.

B.1.5.RS:12 - Relations

• B.1.5 and A.3.1 define Method composition, identity and replacement-claim distinctions.
• B.1.5.EW recovers constituent and encompassing work when those connections are not yet understood.
• B.5.RA and B.5.RR reconstruct and revise the argument on which preservation depends.
• C.29 governs a mathematical correspondence used in the comparison.
• C.30.LCA supplies control-specific conditions; C.30.ILC addresses resulting cross-scope architecture conflicts.
• C.11 and C.11.DUA govern the local decision and whether further investigation is useful.

B.1.5.RS:End

B.1.6 - Work-Resource Aggregation

Type: B-family aggregation pattern Status: Stable Normativity: Normative unless explicitly marked informative

Use this when. Use this pattern when the current claim aggregates resources, effort, time, energy, material, information, cost, or another measured resource over exact dated Work occurrences, A.15.1 temporal or operational Work parts, event-bounded episodes, non-Work carrier phases with an established identity and PhaseOf relation, boundary partitions, or comparable work-resource ledgers.

Not this pattern when. If the current question is the method as a way of doing, use A.3.1. If it is a method description, SOP, algorithm text, simulator configuration, or formal expression, use A.3.2. If it is a work plan, use A.15.2. If it is whether Work occurred or which Work temporal part, episode, operational part, retry, resumption, or later occurrence is current, use A.15.1. If it is work-entry readiness, full-kit condition, or resource readiness before work entry, use A.15.5. If it is bounded aggregation of already recovered temporal relations without resource accounting, use B.1.4. If it is a transformation claim, use A.3.4. If resource gain leaves whole identity in question, use B.2; use B.2.P only when emergence-family wording is unresolved.

What goes wrong if missed. Resource, effort, time, energy, or cost totals are read from methods, plans, dashboards, or phase labels without a dated work occurrence, resource ledger, and overlap policy.

What this buys. A replayable chain that keeps the resource Characteristic, measurement work/result episteme, aggregation work/result, exact policy, work parthood/overlap, and provenance separately recoverable while preventing double counting.

B.1.6:1 - Problem Frame

Practitioners need to roll up work-resource claims across runs, exact A.15.1 Work temporal parts or episodes, teams, devices, stations, model-training epochs, non-Work carrier phases with an established identity and PhaseOf relation, or evidence-production occurrences. The recurring error is to treat a method, method description, plan, phase label, dashboard, or expected efficiency as if it were measured performed Work or as if the label established a Work relation.

Use B.1.6 for the work-resource aggregation claim. Treat dated work occurrence, Method, MethodDescription, WorkPlan, resource ledger, holon delimitation, transformation, evidence, and whole reidentification as separate claims under their applicable patterns.

B.1.6:1.0 - Problem

Work-resource totals are often borrowed from plans, method descriptions, dashboards, or phase labels even when no performed-work evidence, resource-accounting basis, holon delimitation, time window, and overlap policy have been recovered. The failure is to treat a convenient total as a work-resource aggregation claim before the dated work occurrences and resource ledger are explicit.

B.1.6:1.1 - Forces

B.1.6:2 - Solution — separate measurement from aggregation

Start with one direct sentence:

Dated aggregation work W_agg applied policy P to the exact C.16 resource-result epistemes for work set W_set, under declared work-part/overlap relations and accounting boundary B, and obtained aggregation result R_agg; C.2.1 episteme E_agg states that result and A.10/G.6 record its provenance.

If any referenced resource value lacks its resource Characteristic, measurement work, result episteme, Scale/Unit, uncertainty when current, or provenance, it is not repaired by adding a ledger row.

WorkResourceAggregation@Context is a descriptive account for one aggregation claim:

WorkResourceAggregation@Context:
  aggregationConcernRef
  claimScopeRef?: U.ClaimScope
  accountingBoundaryRefs
  timeWindowRefs
  aggregatedWorkOccurrenceRefs
  resourceUseRelationRefs
  workPartOrOverlapRelationRefs
  nonWorkCarrierPhaseRelationRefs?
  resourceCharacteristicRefs
  measurementWorkRefs
  measurementResultEpistemeRefs
  aggregationMethodRef
  aggregationOperationDeclarationRef?
  aggregationPolicyRef
  conversionOrNormalizationRefs?
  aggregationWorkRef
  aggregationResultRef
  aggregationResultEpistemeRef
  provenancePathRefs
  admissibleUse
  stopOrReturnCondition
  nonAdmissibleOverread?

stopOrReturnCondition states when to stop or return to another pattern. Include nonAdmissibleOverread? only when it passes F.19’s plausible-reader test. groundedNonAdmissibleOverread? is an alias for that same optional value.

Recover each of these objects and claims independently:

• a resource Characteristic says which quantity or property is accounted for;
• measurement work and a C.16 measurement-result episteme supply each attributed resource value, Scale, Unit, uncertainty, model, calibration, and time stance;
• the aggregation policy declares inclusion, conversion, weighting, missing-value, partition, overlap, and deduplication rules;
• aggregation work has its actual performer identified through A.13 and is independently admitted as dated U.Work through A.15.1; if the aggregation account must also identify the assignment under which the Work was performed, F.6 checks that relation separately; Method, actual inputs through direct relations or A.6.1 bindings, resources, and temporal extent remain separate;
• the B.1.6 aggregation result is the typed total, vector, interval, or bounded estimate obtained under that policy and work set;
• a distinct C.2.1 aggregation-result episteme states the result, work set, policy, boundary, time window, qualifications, and uncertainty; and
• A.10/G.6 provenance makes the measurement sources, transformations, aggregation work, and result episteme replayable.

A ledger, dashboard, policy, profile, clause, citation, or graph edge may represent or cite this chain. None establishes work occurrence, actual participation, measurement, aggregation, or result identity by presence.

B.1.6:2.1 - Subject Pattern Map

B.1.6:3 - Optional Gamma_work Notation

Gamma_work is optional notation for a recovered WorkResourceAggregation@Context.

Gamma_work(workResourceAggregationRecord, resourceBasis, aggregationPolicy)
  -> aggregationResultRef, aggregationResultEpistemeRef

The notation applies only after the resource Characteristics, C.16 measurement Work and result epistemes, dated Work set, every A.15.1 Work-part relation used by the aggregation, any C.27.TA overlap fact used by it, any separately current non-Work carrier identity and PhaseOf relation, accounting boundary and time window, aggregation policy, and dated aggregation Work have been named. The notation then summarizes that recovered aggregation record.

B.1.6:4 - Ledger Discipline

The ledger is a replay surface, not the source of the aggregation claim. For every resource component it records:

• resource Characteristic, Scale, Unit, polarity when relevant, and accounting boundary;
• exact measured or estimated subject, time window, and work occurrence to which the value applies;
• C.16 measurement work and measurement-result episteme, including model, calibration, uncertainty, and provenance refs when current;
• every A.15.1 Work-part relation used by the ledger, every C.27.TA overlap fact used by it, and any separately current non-Work carrier PhaseOf, each independently established by its subject pattern;
• shared resource, meter, person, tool, stock, data, port, or time-window overlap and the exact deduplication rule;
• conversions, normalizations, imputations, and their declared method/policy refs;
• the aggregation policy edition and actual aggregation work occurrence;
• aggregation result and distinct C.2.1 result episteme; and
• A.10/G.6 source and provenance refs, G.11 currentness when current, admissible use, stop or reopen condition, and any guard justified by F.19’s plausible-reader test.

Measured, estimated, normalized, converted, allocated, and planned values remain visibly different. A planned value does not become a measurement result or performed-work resource use. A citation to a meter or invoice does not establish the measurement work; a ledger row does not establish work parthood or overlap.

Use PortionOf only for a resource portion with its A.14 measure and additivity basis. Use PhaseOf only for a proper temporal restriction of one unchanged non-Work carrier after its direct identity rule and interval conditions hold. For Work, use A.15.1 TemporalPartOf_work, EpisodeOf_work, OperationalPartOf_work, or another admitted Work-part relation only between independently admitted Work participants after its predicate passes. Route interval overlap through C.27.TA. Use retry or resumption only through a locally declared species with the needed participant meanings, predicate, identity, cardinality, and applicability; otherwise keep separately identified occurrences. Belonging to a collection, common timestamps, shared identifiers, a phase label, or co-listing in the ledger establishes none of those relations.

B.1.6:5 - Aggregation Rules

Typed resource basis. Aggregate only values whose resource Characteristic, Scale, Unit, subject, and accounting boundary are compatible under the declared policy. Joules, hours, kilograms, currency, bytes, and attention do not become one scalar by co-location.

Measurement before aggregation. Each measured input points to exact C.16 measurement work and one measurement-result episteme. Raw meter output, indication, resource stock, attributed value, aggregation input, and later efficiency verdict remain distinct.

Exact Work set. Name every dated Work occurrence included. Parent–child, TemporalPartOf_work, EpisodeOf_work, OperationalPartOf_work, and other admitted Work-part relations must already obtain between exact Work participants under A.15.1 or their direct subject patterns. Any overlap fact comes through its exact C.27.TA temporal declaration. A Method, plan, epoch or phase label, invoice period, or dashboard grouping does not establish the Work set.

Exact policy. The aggregation policy states inclusion/exclusion, conversion, normalization, weighting, missing-value treatment, boundary allocation, uncertainty treatment, overlap/deduplication, and output kind. A policy declaration is not aggregation work or a result.

Overlap and shared stocks. Addition is admissible only for disjoint partitions or after an exact policy handles overlap. Shared people, tools, meters, inventories, datasets, ports, and time windows require the direct shared-use/overlap fact and a justified allocation or deduplication rule.

Aggregation work and result. Use A.13 to identify the actual performer and A.15.1 to admit the dated aggregation Work independently. If the aggregation account must also identify the assignment under which the Work was performed, check that relation separately through F.6. Keep the Method, actual bindings, resources, and time separate. State the B.1.6 result as a typed total, vector, interval, or bounded estimate under the named policy and Work set; then state it in a distinct C.2.1 episteme.

Uncertainty and provenance. Propagate measurement uncertainty and model/conversion uncertainty according to the exact aggregation policy. Use A.10/G.6 paths to record the established work, measurements, policy application, transformations, result, and sources.

Plan/result separation. Keep expected use from a method description or WorkPlan as planned and resource readiness under A.15.5. Use A.15.1 and the measurement or aggregation predicates for performed Work and measured results.

Efficiency and yield. A ratio or yield claim names its input resource results, exact output/domain result, measurement bases, aggregation work, and comparison policy. It does not use a generic output-result relation. Apparent free gain remains a measurement, accounting-boundary, substitution, or whole-reidentification question until its subject pattern is recovered.

B.1.6:5.1 - Compact Obligation Rows

B.1.6:6 - Archetypal Grounding

Engine test programme. C.16 measurement Work attributes fuel mass, electrical energy, operator time, and emissions values to exact subjects under their Scales, models, calibration bases, windows, and uncertainties. Each has its own result episteme. Exact test-run occurrences and obtaining A.15.1 Work-part relations define the included Work set; independently declared C.27.TA overlap facts state shared timing. A test-cell or engine phase enters only through the carrier’s identity rule and proper phase relation. Shared warm-up energy is recorded under the exact temporal and resource-use facts. Dated aggregation Work applies ProgrammeResourcePolicy-v3, which allocates warm-up energy once and propagates input uncertainty. The B.1.6 result is a typed resource vector plus qualifications; a C.2.1 episteme states it. A later emissions verdict remains separate evaluation Work and result.

Manufacturing cell. Welding and painting are two dated work occurrences. Electricity, gas, consumables, and labor time are separate resource Characteristics with measurement-result epistemes. A shared extraction fan and overlapping operator time require direct shared-use facts and an allocation policy. The resource ledger represents those facts. Establish any separately claimed Work-part relation or frame transformation through its direct pattern.

Model training. Epoch labels alone do not establish work parts. Ground the training work and exact slices, then recover C.16 measurements for compute energy, storage traffic, and operator time. Aggregation work applies an edition-pinned policy to those result epistemes. The training Method, any algorithm text that qualifies as its MethodDescription, and the dated training Work remain distinct; trained-model identity, fairness result, provenance, assurance, and deployment decision stay with their subject patterns.

B.1.6:6.1 - Bias-Annotation

B.1.6:7 - Conformance Checklist

B.1.6:8 - Common Anti-Patterns and How to Avoid Them

B.1.6:9 - Consequences

This pattern defines a conservative predicate and result form for typed resource aggregation while keeping each input measurement, performed work occurrence, aggregation policy/application, result episteme, work relation, and provenance path distinct.

The cost is explicit accounting discipline. The gain is that resource roll-ups become comparable without claiming more than the evidence and boundary relation allow.

B.1.6:9.1 - Rationale

B.1.6 exists because a convenient total can hide several ontically different chains. Its result is obtained only after exact resource measurement, work-set and overlap grounding, an edition-pinned aggregation policy, and dated aggregation work. The ledger represents that recovered account.

The pattern keeps the useful old Gamma_work notation, but only as notation over a recovered aggregation record. It also preserves the old planned-versus-measured warning: a method description or work plan can declare expected yield or expected resource use, but measured aggregation depends on dated work evidence.

B.1.6:9.2 - SoTA-Echoing

Source qualification was checked against the publishers’ current surfaces on 2026-07-30. Because ISO and GHG Protocol announced active joint development of an updated product-accounting standard in 2026, these decisions remain qualified only through 2027-01-30 unless a new draft, amendment, confirmation status, or published replacement appears earlier. Internal FPF neighbour authority stays in Relations; it is not presented as an external source decision.

Source refresh is local: replay the row’s named rule, case, and checklist rows first. Widen only when that replay contradicts another current B.1.6 locus; a changed accounting source cannot by itself create work, overlap, measurement, result episteme, provenance, or a downstream verdict.

B.1.6:10 - Relations

• Builds on A.13 for actual performers, A.15.1 for independently admitted dated measurement or aggregation Work, F.6 when a result must also identify the assignment under which that Work was performed, and A.6.1 for declarations and actual bindings; C.2.1 governs measurement-result and aggregation-result epistemes.
• Coordinates with A.3.1, A.3.2, and A.15.2 for method, method description, and work plan.
• Coordinates with A.15.5 for work-entry readiness, full-kit condition, and resource readiness before work entry; B.1.6 may cite those refs but does not decide readiness.
• Coordinates with A.15.1 for exact Work temporal parts, episodes, operational parts, overlaps, retries, resumptions, and later occurrences; with B.1.4 only for bounded aggregation of already recovered temporal relations; and with C.27 for temporal-claim adequacy.
• Coordinates with A.1, B.1, A.14, and C.13 for holon delimitation, part-whole, proper temporal restriction and PhaseOf for a non-Work carrier, and constructive grounding.
• Coordinates with A.3.4 for transformation. Use B.2 for a remaining whole-identity question and B.2.P for unresolved emergence-family wording; the relevant B.2-family pattern defines or constrains the recovered claim.
• Coordinates with C.16 for resource Characteristics and measurement results; A.10 and G.6 for provenance; G.11 for currentness; C.29 for representation or mathematical-lens claims; A.15.1 for Work relations; A.14 and B.1.4 for non-Work part or phase relations and their bounded aggregation; E.17 for publication; and the applicable comparison, assurance, transformation, reidentification, or decision pattern when those uses are current.

B.1.6:End

B.2 - Meta-Holon Transition - Whole Reidentification

Type: Part B holonic construction pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.2:0 - Use This When

Use this pattern when changed facts raise the question whether the existing whole still carries the current claim or a new whole must be identified. The question may concern its delimitation, part relation, constitutive assembly, objective, supervision, capability envelope, agency threshold, or temporal consolidation.

Typical moments:

• a set of coordinated parts becomes a regulated system with its own objective and externally visible commitments;
• a commissioning history crosses into operation and the assurance claim must restart for the operational whole;
• a theory, model family, or knowledge body becomes an episteme whole recognized under the already admitted U.Episteme kind rather than remaining a loose catalogue;
• separately governed structure, functioning, method, and work facts support a capability envelope that the existing whole cannot explain; evidence separately supports the claim about those facts;
• an architecture residual cannot be explained inside the existing whole.

First useful move. Compare the observed gain or shift with explanations that preserve the existing whole. If better parts, corrected relations, improved measurement, Method or Work repair, richer phase coverage, or architecture-view repair is sufficient, stay with the existing whole and use that subject pattern. Proceed to a new-whole claim only when that comparison leaves whole reidentification necessary.

What goes wrong if missed. Emergence becomes rhetoric, ordinary improvement is overclaimed as a new whole, or a genuinely new whole remains hidden under old part, evidence, assurance, architecture, or responsibility claims.

What this buys. B.2 gives one accountable whole-reidentification move: recover the exact existing whole, the separately governed facts that challenge its identity, the exact candidate new whole, and decide whether the existing whole continues or the new whole must carry the claim before relying on evidence, a record, or a receiving-use decision.

Not this pattern when.

• If the claim is ordinary part-whole construction, use B.1, A.14, and C.13.
• If the claim is a whole-level characteristic change, use C.16 and the direct measurement or evaluation pattern.
• If the claim is capability without whole reidentification, use the direct capability and characteristic patterns.
• If the claim is transformation or work, use A.3.4 for the change and A.15.1 for the Work; use A.12 when the acting side needs recovery and A.15 when alignment across the neighboring objects is the question.
• If the claim is only wording repair for emergence-family language, use B.2.P first.
• If the claim is graph, RG-like, MSPD, or other mathematical expression, use C.29 unless whole reidentification is also current.

B.2:1 - Problem Frame

A Meta-Holon Transition is not a new root ontology, generic emergence label, or mathematical graph result. It is a whole-reidentification claim about an exact holon already recognized through A.1 construction, identity, part relations, whole-level characteristics, and a direct kind-specific pattern.

The B.2 comparison determines whether the old whole remains the right EntityOfConcern for the current claim; retain it when its identity rule accommodates the change. The candidate new whole can be recognized as a U.System, U.Episteme, U.Method, U.Work, U.Discipline, or another holon kind only after E.24.UK has admitted that public kind and the exact candidate satisfies A.1 plus the direct kind-specific criterion.

B.2:2 - Problem

Without B.2:

1. New whole is missed. A constructive assembly or coordinated closure changes the object, but evidence and architecture still point to old parts.
2. Ordinary improvement is overclaimed. A better component, stronger measurement, or corrected method is called emergence.
3. Record fields become ontology. A result field, trigger mnemonic, profile, or checklist is treated as a U-kind or actor.
4. Agency becomes binary. A threshold crossing is read as “agent or not agent” instead of a characteristic-space threshold for an admitted System. A local system-role kind, classification, or assignment is a separate optional fact and neither establishes nor is required for the agency characteristic.
5. Mathematics replaces ontology. A graph, RG-like flow, MSPD score, or benchmark jump is treated as MHT without recovering the holon claim.
6. Transformation becomes containment. A system changing another holon is treated as its part or the larger whole containing it without a separately obtaining part-whole relation.

B.2:3 - Forces

B.2:4 - Solution

Use B.2 as a world-side whole-reidentification pattern. Start with the actual wholes and the facts governed by their direct patterns; add records only when a receiving use needs them.

1. Name the exact existing whole, its admitted kind, and its identity or reidentification rule.
2. Recover each changed delimitation, constituent, constructive part relation, assembly, supervision, objective, capability, characteristic, or temporal fact under its direct pattern. A cue word, profile field, measurement, or graph edge does not make the fact obtain.
3. Test whether those facts can be explained as a change of the same whole. If repair, maintenance, changed characteristics, phase coverage, method or work correction, measurement, or architecture-view correction is enough under the existing reidentification rule, keep that whole and stop B.2.
4. If the existing whole is not enough, identify the exact candidate new whole and execute the complete A.1 criterion. Recover its constituents, obtaining constructive relations, assembly, reidentification rule, and composition-grounded whole characteristic. Also show that the candidate’s actual boundary, interfaces, relevant characteristics, and identity-preservation conditions satisfy the applicability and compatibility conditions of at least one governed larger-assembly construction method or rule under which it can remain a constituent. Then name its already admitted holon kind and satisfy the direct kind-specific criterion. If a required condition fails, the candidate fails A.1; if missing evidence or an unavailable dependency prevents a determination, evaluation returns unknown.
5. State the whole-reidentification claim: why the existing whole no longer carries the current subject claim and why the candidate new whole is the EntityOfConcern. This comparison does not itself create, admit, or classify either whole.
6. Materialize a trigger profile, optional explanation-result episteme, reidentification assertion, or record only when a named receiving use must inspect, cite, compare, or preserve that claim.

The optional MHTTriggerProfile, ExistingWholeExplanationResult, and HolonReidentificationRecord are ordinary C.2.1 epistemes. Their content can designate exact wholes, facts, claims, and relation occurrences; the content fields are not world-side participants and supply no substitute for the preceding move.

B.2:4.1 - MHTTriggerProfile

MHTTriggerProfile is a U.Episteme whose EntityOfConcern is the exact existing whole already recognized under an admitted holon kind. It collects exact current cues and support for asking whether whole reidentification is live. It is not MHT itself, and its content fields do not declare another relation.

The profile’s exact ClaimGraph and effective U.ReferenceScheme, together with its existing-whole EntityOfConcern, constitute its C.2.1 identity. Any current U.ClaimScope and an independently selected model-use structure can qualify this episteme when its receiving use needs them. These identity values and qualifications do not identify either whole, become MHT trigger facts, or make any referenced relation obtain. A single cue warrants attention; it does not establish whole reidentification.

B.2:4.2 - Existing-whole comparison and optional result

First perform an ordinary comparison: compare the observed change with direct explanations that preserve the existing whole. Consider better parts, corrected relations, improved measurement, method or Work repair, richer phase coverage, capability change, and architecture-view repair only when their direct patterns make those explanations current. If one explanation is sufficient for the receiving use, keep the existing whole, use that subject pattern, and stop B.2.

When another use must inspect or cite the outcome, identify an optional ExistingWholeExplanationResult episteme whose EntityOfConcern is the existing whole:

The comparison is an action a practitioner performs. The optional result records its claim-bearing outcome. Neither is a reusable checklist or Method unless an independent receiving use later requires and defines such an object. The episteme creates none of its referenced claims or relations.

B.2:4.3 - HolonReidentificationRecord

HolonReidentificationRecord is an optional U.Episteme whose EntityOfConcern is the exact new holon. Use it only when a person or system performing later work needs a durable account of why that new holon, rather than the prior whole, is the current EntityOfConcern. Candidate classification remains a separately governed judgment.

The record does not make the A.1 criterion true, admit a public kind, or create the candidate new holon. E.24.UK is the pattern for public-kind admission; A.1 is the pattern for world-side recognition; C.2.1 is the pattern for the optional classification assertion; its warrant requires exact evidence and assurance relations. Publication of the record is another relation under the publication patterns.

B.2:4.4 - Candidate New Whole Reference And Kind

Use one resultHolonRef : U.HolonRef for the candidate new whole and one resultHolonKindRef : U.KindRef for its kind. E.24.UK must already have admitted that public kind, and the candidate new whole must satisfy the A.1 constructive criterion plus any kind-specific membership condition. Neither the references nor the record establish those facts.

When a person or system performing downstream work must inspect or cite the classification judgment, add the optional resultHolonClassificationAssertionRef. That C.2.1 assertion may report a governed evaluation of true, false, or unknown; its evidence, warrant, and G.11 currentness stay separate from world-side criterion satisfaction. B.2 still asks a different question: whether the existing whole can continue to carry the subject claim or a new whole must be identified.

Do not use post* field names as live governed names. They hide the candidate new whole and its kind and invite temporal shorthand. Name that whole and its admitted public kind; cite a classification assertion only when the receiving use needs that episteme.

B.2:4.5 - Agency Threshold

An agency-characteristic threshold is a condition in a characteristic space, not a root kind or a substitute for the A.13 agency claim. State its exact System, predicate, claim scope, and qualification window.

Use A.13, A.19, and C.16 for the characteristic-space and threshold claim. Levin-line TAME work can discipline the multi-characteristic framing when agency evidence is relied on for the current claim. B.2 uses agency threshold only as one possible trigger in MHTTriggerProfile, and only when crossing the threshold changes closure, supervision, objective, or whole identity.

Recover the admitted System and its agency-relevant characteristic or threshold independently. A System may bear that characteristic while participating passively in the situation. A precise agency claim additionally requires the A.13 core, including the local agential system-role kind, System-classification judgment, and obtaining assignment; a characteristic-only claim does not acquire that additional scope. If claim-bearing source wording still says only “role,” use E.10.ROLE rather than presuming classification or assignment.

B.2:4.6 - Acting-System Participation

When a source describes a system changing another holon, recover acting-system participation and transformation separately.

Use A.12 for acting-side externalization, A.3.4 for bounded transformation, and A.15.1 for work occurrence. A system changing another holon does not thereby become its part or the larger whole containing it, and no U.Transformer kind is created.

B.2:4.7 - Mathematical-Lens Separation

Graph, algebra, RG-like, MSPD, benchmark, scaling, and morphism language can bear on MHT recognition only as mathematical or analytical expression.

Use C.29 when the mathematical lens is relied on for the current claim. Use B.2 only after the holon identity claim is recovered and the ordinary existing-whole comparison leaves a whole-reidentification question.

B.2:4.8 - Keep Whole Identity, Evidence, Currentness, And Reliance Separate

Keep these five distinctions explicit:

• the existing whole and candidate new whole, their constituents, obtaining constructive relations, assemblies, characteristics, and identity rules are world-side objects and facts under their direct patterns;
• a B.2 whole-reidentification assertion is a C.2.1 episteme about those objects;
• evidence and assurance relations support or warrant the assertion’s claim content but create neither whole and decide neither identity rule;
• use G.11 to determine whether the selected assertion or record edition is current for the receiving use;
• a person or system performing the receiving work decides whether to rely, decline to rely, defer, or reopen.

Evidence present or missing, and a current or stale record, can change what an evaluation returns and whether a person or system relies while performing receiving work. They cannot turn the same whole into a new whole or a new whole into the same one. Whether the existing whole continues or a new whole must be identified follows the direct identity and reidentification rules plus the actual construction facts. A.1 recognition of either candidate supplies no B.2 warrant and does not select B.2.

B.2:5 - Archetypal Grounding (Worked Cases)

B.2:5.1 - Closed-Loop Regulated System

Parts: plant, sensor, controller, actuator.

Existing-whole repair may be enough if only a sensor improved or a controller parameter changed. B.2 becomes current only when exact constructive relations and a governed assembly close the feedback and supervision around an objective, yielding one exact new whole proposed for recognition under the already admitted U.System kind, whose boundary, external commitments, and capability envelope are no longer explainable as changes of the existing whole. That proposed whole can satisfy A.1 only if its actual boundary, interfaces, relevant characteristics, and identity-preservation conditions also satisfy at least one applicable governed larger-assembly construction method or rule—for example, a rule under which the regulated system can remain one constituent of a larger plant or production system. If that compatibility condition does not hold, the proposed whole fails A.1; if the needed evidence or dependency is unavailable, evaluation remains unknown. Loop closure, a record, or a measurement supplies none of those facts.

MHTTriggerProfile@Control : U.Episteme
  entityOfConcernRef: plant-plus-devices configuration
  content:
    changedSupervisionRelationRefs: closed feedback relation
    changedObjectiveClaimRef: maintain output y near reference r
    changedCapabilityClaimRef: capability envelope after closure

HolonReidentificationRecord@Control : U.Episteme
  entityOfConcernRef: regulated control system
  content:
    existingWholeRef: plant-plus-devices configuration
    selectedTriggerProfileRef: MHTTriggerProfile@Control
    existingWholeExplanationResultRef: ClosedLoopExistingWholeResult
    resultHolonRef: regulated control system
    resultHolonKindRef: U.System
    resultHolonClassificationAssertionRef: RegulatedControlSystemClassificationAssertion
    wholeReidentificationClaimRef: ClosedLoopWholeReidentificationClaim
    changedClaimPatternLocators: A.1, B.1.2, B.2.2, C.30.LCA, A.2.2

The exact EntityOfConcern is an actual participant in the C.2.1 EpistemeConstitutionRelation; EntityOfConcernSlot is only the corresponding declaration-local participant meaning inside EpistemeConstitutionRelationSignature. The entityOfConcernRef field and indented content fields carry participant or claim designations in each episteme; they are not SlotKinds or participants of a new MHT relation. The feedback and capability relations retain their direct identities, while the optional classification assertion retains its own C.2.1 identity and does not establish world-side holonhood.

B.2:5.2 - Compendium Becomes Theory

A collection of results can remain a catalogue. B.2 becomes current only when the knowledge body is reidentified as an episteme whole with its own claim-bearing structure, explanatory objective, reference scheme, and evidence relations.

B.2.3 specializes this case when the exact candidate new holon named by the MHT claim is recognized under the already admitted U.Episteme kind. C.2.1 defines episteme constitution and identity; E.17 and E.24.PUB define publication occurrences, forms, and carriers; C.2.P recovers source-expression and source-to-use distinctions; use A.10 for bounded evidence reliance and G.6 for its evidence/provenance graph and ledger, retaining each relation’s direct governor.

B.2:5.3 - Capability Envelope Appears

Several systems, methods, and work occurrences align and a new capability envelope appears. Apply the direct capability, characteristic, function, transformation, method, work, evidence, and architecture patterns first.

Use B.2.4 only when separately governed capability or functioning facts make a whole-reidentification question live under B.2. Evidence can support the claim about those facts; it creates neither the facts nor the question.

B.2:5.4 - Lathe And Workpiece

A lathe transforms a workpiece. That is transformation and work, not MHT and not parthood. B.2 becomes current only if the manufacturing arrangement creates or reveals a new whole that must be reidentified, such as a production cell with exact constituents, obtaining coordination and supervision relations, a governed assembly, an objective, a whole-level capability, and a reidentification rule that the earlier arrangement lacks. A.1 recognition additionally requires the cell’s actual boundary, interfaces, relevant characteristics, and identity-preservation conditions to fit at least one applicable governed construction method or rule under which the cell can remain a constituent of a larger production system.

B.2:5.5 - Same Whole, New Whole, And Lost Evidence

Replacing Pump #37’s seal is an ordinary constituent change when the pump’s reidentification rule admits that maintenance phase. The same pump remains the EntityOfConcern; use the direct maintenance, part-relation, work, transformation, and characteristic patterns and stop B.2.

Closing a controller-sensor-actuator loop can yield a new regulated-system whole only when the exact candidate assembly, supervision and coordination relations, boundary, objective, whole-level capability, admitted U.System kind, and reidentification rule satisfy A.1 and the system criterion. Its actual boundary, interfaces, relevant characteristics, and identity-preservation conditions must also satisfy at least one applicable governed larger-assembly construction method or rule under which the regulated system can remain a constituent. If that condition fails, the candidate fails A.1; if the needed evidence or dependency is unavailable, evaluation returns unknown. A wiring diagram, commissioning record, loop closure, or capability measurement alone supplies none of those construction or compatibility facts.

If the support for the reidentification assertion is present and its edition is current, a person or system performing receiving work may rely on it. If the same evidence is unavailable, evaluation can return unknown; use G.11 to test whether the edition is current for this use; and the actor may decline, defer, or reopen. None of those branches changes whether the regulated-system whole actually exists or whether the prior configuration remains the same whole.

B.2:5.6 - Selected Structure And Transformation Stops

A selected BoundedModelUseStructure organizes exact model-use relations. It is not the new holon named by an MHT claim and gains no parts, agency, or whole identity from selection, naming, or a Context Map.

Several actual changes during assembly may each be exact U.Transformation occurrences. B.2 does not treat them as constituents of one composite transformation. If whole reidentification would require positive transformation composition, transformation parthood, or composite-transformation identity and no direct governor supplies contribution, compatibility, boundary, interfaces, and reidentification, retain the exact blocker and the independently identified changes. The missing composition facts do not show that any change is atomic.

B.2:6 - Bias-Annotation

B.2:7 - Conformance Checklist

B.2:8 - Common Anti-Patterns and How to Avoid Them

B.2:9 - Consequences

Positive consequences:

• MHT becomes a precise whole-reidentification move rather than a synonym for improvement.
• Cases involving a candidate new system, episteme, method, work occurrence, or discipline use the same B.2 whole-reidentification solution while retaining their subject patterns.
• Trigger language remains useful without becoming ontology.
• Mathematical and benchmark evidence can be used without replacing the holon claim.

Costs:

• Users must try existing-whole explanations before declaring MHT.
• MHT records require a reference to the exact candidate new whole, a reference to its already admitted public kind, A.1 recognition, and the evidence needed by any classification assertion used downstream.
• Some attractive emergence claims will return to ordinary characteristic, method, work, architecture, or measurement repair.

B.2:10 - Rationale

Holonic work needs a way to recognize when a whole has changed enough that the old EntityOfConcern no longer carries the current claim. B.2 provides that move without collapsing all novelty into “emergence” and without inventing record-field U-kinds.

The pattern is intentionally conservative: it applies repairs from subject patterns first, then supports whole reidentification only when the existing whole no longer explains the observed shift. This protects B.1 part-whole construction, A.15.1 work, A.3.4 transformation, C.16 characteristics, C.29 math-lens use, and episteme and publication discipline from being swallowed by MHT.

B.2:11 - Decision-bearing SoTA account

These sources answer different questions. None supplies a universal emergence detector. Popular modeling languages and generic architecture standards are not used as decision authority here because they do not decide when the same whole ends and another begins.

B.2:12 - Relations

• Builds on: A.1 for world-side holon recognition, B.1 for part-whole construction, A.14 and C.13 for relation and constructional grounding, and E.24.UK for one-time public-kind admission.
• Coordinates with: A.12 and A.3.4 for acting-side and transformation, A.3.1 and A.15.1 for Method and Work, A.15 when their alignment is the current question, C.16 and A.19 for characteristic space and threshold, C.2.1 for optional claim and record epistemes, A.10 and B.3 for evidence and warrant, G.11 for edition currentness, C.29 for mathematical lenses, and C.32.P2S when architecturing pressure becomes whole reidentification rather than local structure repair.
• Specialized by: B.2.2 when the candidate new whole is a system, B.2.3 when it is recognized under the admitted U.Episteme kind, and B.2.4 when capability or functioning facts require whole reidentification.
• Can use neighboring evidence from: B.2.5 when a supervisor-subholon feedback relation is part of the B.2 case evidence or neighboring structure; that does not make B.2.5 a specialization for the candidate new holon’s kind.
• Uses: B.2.P when emergence-family, MHT, MET, MFT, synergy, or metric-mirage wording hides which claim kind is current before B.2 is applied.

B.2:End

B.2.P - Clarify Emergence and Meta-Holon Transition (MHT) Claims

Type: Part B precision-restoration pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.2.P:0 - Use This When

Use this pattern when wording such as emergence, emergent, synergy, higher-level property, meta-system, meta-epistemic, meta-functional, MHT, MET, MFT, promotion, post*, or collection words mixed with those terms could be pointing to several different FPF objects.

The first useful move is:

Recover the claim kind before choosing replacement wording.

B.2.P is selected only when the source wording hides one of these recurring questions:

• Is this a B.2 whole-reidentification claim?
• Is the candidate new whole a system or episteme, or do capability and functioning facts make whole reidentification necessary?
• Is this only a characteristic, capability, functioning, architecture, evidence, measurement, or mathematical-lens claim?
• Is a collection, fleet, community, pool, or base being admitted as a whole, acting collective, whole-level characteristic bearer, or merely a membership set?
• Is a metric jump or benchmark result being overread as a new whole?

What goes wrong if missed. A word like “emergent” becomes a shortcut to a new U-kind, a collection receives agency by name, a metric jump becomes MHT, or source title mnemonics survive as if they were current pattern authority.

What this buys. B.2.P gives one local recovery profile for emergence-family and MHT wording. It keeps B.2-family subject patterns centered on whole reidentification while ordinary capability, characteristic, function, architecture, evidence, math-lens, publication, and collection claims remain with their subject patterns.

Not this pattern when.

• If the text already names the subject pattern and object by value, use that pattern directly.
• If the question is ordinary collection admission without emergence, synergy, MHT, metric mirage, or whole-reidentification wording, use A.14, C.13, B.3.5, A.1, A.15, A.2 patterns, or C.16 directly.
• If whole-span F.19 reading settles the wording without a remaining emergence-specific FPF question, stop there.
• If the question is general wording-use architecture, use E.10 and E.10.ARCH.

B.2.P:1 - Problem Frame

Emergence-family wording is overloaded. It can point to a new system whole, an episteme whole, a capability envelope, a characteristic crossing, an architecture residual, a mathematical scale expression, a benchmark artifact, a publication claim, or a collection-as-whole question.

It asks which exact EntityOfConcern, world-side or claim-side fact, and subject pattern are current, and whether the same whole still carries the claim.

B.2.P:2 - Problem

Without B.2.P:

1. Generic emergence becomes ontology. U.Emergence or an equivalent hidden kind appears even though no such root kind is selected.
2. Collections become systems by poetry. A fleet, community, pool, or base is treated as an acting system because the phrase sounds collective.
3. Capability becomes MHT. A new capability envelope or functioning relation is treated as a new whole without checking existing-whole explanations.
4. Mathematics becomes declaration. A graph, scaling law, RG-like expression, benchmark jump, or MSPD score is treated as whole reidentification.
5. Old mnemonic titles are mistaken for applicable PatternIDs. Source labels such as MET or MFT hide whether the claim concerns an episteme whole, capability or functioning facts, evidence for those facts, or something else.
6. Semio-bias returns. Publication, dashboard, model, or source interpretation claims displace the in-life holon or characteristic under concern.

B.2.P:3 - Forces

B.2.P:4 - Solution

Recover the claim kind and subject pattern before any wording replacement.

B.2.P:4.1 - Emergence Claim-Kind Recovery

Read the complete natural span with F.19 and E.10’s compact cues. If an emergence-specific FPF question remains, recover five things before choosing replacement wording:

1. Practical use. What decision, explanation, design move, or stop depends on the sentence?
2. Exact object. Is the concern an existing whole, candidate new whole, collection, characteristic, capability, functioning relation, structure, transformation, measurement result, assertion, or mathematical expression?
3. Concrete claim. What changed or obtains: construction, identity, capability, characteristic value, evidence, publication, representation, or only the wording?
4. Subject pattern. Which pattern defines or constrains that object and claim without using emergence as a substitute?
5. Disposition. Keep the exact direct claim, open B.2 only for a remaining whole-reidentification question, or stop with the exact missing object or governor.

A temporary author note may retain the source phrase, exact object, subject pattern, blocked overread, and replacement or stop. The note is not a U-kind, relation, result object, or required project record. Do not ask a practitioner to fill a generic emergence card before the direct object can be named.

B.2.P:4.2 - Claim-Kind Recovery and Subject-Pattern Selection Table

B.2.P:4.3 - Whole-Reidentification Recovery

When a whole-reidentification question remains after claim-kind recovery, do not create a second MHT schema. Use B.2 with this concrete account:

1. name the exact existing whole, admitted kind, and identity or reidentification rule;
2. name each changed delimitation, constituent, constructive relation, assembly, supervision, objective, capability, characteristic, or temporal fact and its subject pattern;
3. try the existing-whole explanation and state whether it preserves the existing whole;
4. if a new whole is still needed, require B.2 and execute the complete A.1 criterion: name the exact candidate, its constituents, obtaining constructive relations, assembly, reidentification rule, and composition-grounded whole characteristic; show that its actual boundary, interfaces, relevant characteristics, and identity-preservation conditions satisfy at least one applicable governed larger-assembly construction method or rule under which it can remain a constituent; then name its already admitted kind and satisfy the direct kind-specific criterion;
5. state whether the direct identity rules preserve the same whole or require a new whole for the current subject claim;
6. only when a specific downstream task must inspect or cite the decision, identify any separate assertion or record, supporting evidence and warrant, G.11 currentness result, and rely, decline, defer, or reopen decision.

Evidence availability, an evaluation value, a record field, and receiving reliance neither construct the candidate nor decide whether the existing whole continues or a new whole must be identified. If the exact candidate, one required constructive fact, or the larger-assembly compatibility condition has no governor, stop with that missing object or governor rather than writing candidateResultRef, resultKindRef, mhtWitnessRef, or a context-shaped placeholder.

B.2.P:4.4 - Collection Boundary

Collection words enter B.2.P only when they are entangled with emergence, synergy, MHT, metric mirage, or whole-reidentification wording.

If the claim is plain collection admission:

• use A.14 for membership and part-whole relation vocabulary;
• use C.13 for collection-as-whole constructional grounding;
• use B.3.5 for working-model assurance grounding;
• use A.1 for an acting collective admitted as U.System; use A.15 for a separate alignment question and A.2 patterns for the exact system-role-kind or assignment claim when either is current;
• use C.16 for a whole-level characteristic.

B.2.P may point to these subject patterns; it does not own their claims. An unassembled collection remains an unassembled collection even when a list, dashboard, or project card names it as one whole. A C.13 collection construction does not by itself establish an integrated assembly, acting system, or A.1 holon.

B.2.P:4.5 - Source Mnemonics and Result Fields

Treat source labels and short forms as recognition cues until the concrete thing or claim and its direct pattern are identified.

• MET may point to a claim that the candidate new whole is an episteme, source-title wording, episteme morphing, publication synthesis, or a source-only phrase. Identify the concrete claim before use.
• MFT may point to capability and functioning whole reidentification, a functional-structure view, function-like wording, method and work collapse, or source-only phrase. Recover before use.
• promotion may hide whole reidentification, status change, release, gate, publication, or project process wording. Recover before use.
• post* fields do not survive as generic governed names. When B.2 is current, name the exact candidate new whole and its already admitted holon kind directly; cite an optional classification assertion or reidentification record only when receiving work needs that episteme.

Do not treat the source label as a subject-pattern locator merely because it is recognizable.

B.2.P:5 - Archetypal Grounding (Worked Cases)

B.2.P:5.1 - “The Fleet Emerged As A New Actor”

Recover:

• Is “fleet” a membership set, collection-as-whole, acting collective system, or the candidate new system named by an MHT claim?
• Does the agency wording name an admitted System, an agency-relevant characteristic or threshold, a local system-role kind, a separate System-classification judgment, an obtaining assignment, or only ordinary prose? Recover these independently: the characteristic can obtain without an assignment and the System may participate passively. Send unresolved claim-bearing “role” wording through E.10.ROLE.
• Does the candidate new system have its own delimitation, objective, coordination, and capability envelope, and is the reidentification claim separately supported by evidence and assurance?

If the candidate new whole is an acting system, use B.2 and B.2.2. If the case is only a managed collection with a whole-level metric, use A.14, C.13, B.3.5, and C.16.

B.2.P:5.2 - “The Model Shows Emergent Robustness”

Recover:

• Which claims concern the model as a description episteme, and which concern its mathematical expression or lens use?
• Is robustness a characteristic-space claim?
• Is the result a benchmark artifact?
• Is there an in-life holon whole-reidentification question?

For those direct claims, use C.29, C.16, A.10, and source-use patterns as applicable. Use B.2 when the identity of the in-life whole remains the question.

B.2.P:5.3 - “A Meta-Functional Transition Happened”

Recover:

• Is there capability or functioning evidence?
• Do separately governed capability or functioning facts make a whole-reidentification question live, with evidence only supporting the claim about those facts?
• Is the concern function-like wording, a functional-structure view, a method-and-work relation, or a candidate new holon?

Use B.2.4 only for the B.2-facing whole-reidentification case. Otherwise use A.6.F, A.2.2, C.16, A.3.4, C.30.TFS-REL, A.15, or architecture patterns.

B.2.P:5.4 - “The Selected Context Became A Meta-System”

Recover the exact selected relation organization. If it is BoundedModelUseStructure, keep it as dependent U.Structure under A.1.1 and A.22. A context label, Context Map, diagram, or selection decision supplies no constituents, part relations, agency, holonhood, or MHT. If the source instead concerns an actual system whole, identify that system and its construction independently before B.2.

B.2.P:5.5 - “The Evidence For Emergence Was Lost”

Recover the exact whole-reidentification assertion, its evidence or assurance relation, the selected assertion edition, and the receiving work. Missing evidence can make a governed evaluation return unknown; a stale edition can fail G.11 currentness; a person or System performing the receiving work can decline reliance, defer, or reopen. None of those results reverses an actual construction or changes the direct rule that decides whether the existing whole continues or a new whole must be identified. Do not rewrite evidence loss as absence of the whole or as a new MHT.

B.2.P:5.6 - “The Assembly Changes Form One Higher-Level Change”

Identify each actual change independently under A.3.4. A shared work occurrence, flow, changed referent, time window, method decomposition, or C.13 construction trace does not make those changes parts of one transformation. If the use requires a composite transformation and no direct governor supplies constituent contribution, compatibility, boundary, interfaces, whole identity, and reidentification, return that exact blocker. Do not infer either composition or atomism.

B.2.P:5.7 - Bias-Annotation

B.2.P:6 - Conformance Checklist

B.2.P:7 - Common Anti-Patterns and How to Avoid Them

B.2.P:8 - Consequences

Positive consequences:

• B.2-family emergence language no longer creates hidden U-kinds.
• B.2, B.2.2, B.2.3, and B.2.4 stay centered on their subject claims instead of carrying repeated first-stage precision restoration.
• Collections, capabilities, functions, characteristics, architecture residuals, mathematical expressions, and publications keep their subject patterns.

Costs:

• Ambiguous emergence-family phrases take one recovery step before use.
• Some attractive umbrella claims become narrower subject-pattern claims.
• Old mnemonic labels may survive only as quoted source wording or reduced-use cues unless the concrete thing or claim and its direct pattern are identified.

B.2.P:9 - Rationale

Emergence-family wording is useful because it marks a possible explanatory concern. It is dangerous because it can hide the actual object: a holon, system, episteme, capability, characteristic, architecture structure, mathematical expression, evidence relation, source publication, or collection.

B.2.P follows F.19’s whole-span reading with compact E.10 cues; E.10.ARCH or a direct subject rule resolves only the remaining FPF ontology question, after which F.19 tests the repaired sentence. This prevents one word from creating several local ontologies.

B.2.P:10 - SoTA-Echoing

B.2.P:11 - Relations

• Builds on: F.19, E.10, E.10.ARCH, E.24, F.18, and B.2.
• Uses for whole reidentification: B.2, with B.2.2 and B.2.3 as kind-specific specializations and B.2.4 as the capability/functioning decision bridge.
• Keeps collection admission with: A.14, C.13, B.3.5, A.1, A.15, A.2 patterns, and C.16.
• Coordinates with: A.2.2, C.16, A.6.F, A.3.4, C.30, A.22, A.1.1, C.30.ASV, C.30.TFS-REL, C.30.ILC, C.32.P2S, C.29, A.10, B.3, C.2.1, G.11, E.17, and source-use patterns.

B.2.P:End

B.2.2 - Meta-System Transition: Test the Proposed New Whole as a System

Type: Part B holonic construction pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.2.2:0 - Use This When

Use this pattern when B.2 has identified one exact candidate new whole and that same individual must be recognized under the already admitted U.System kind: a swarm, production cell, cloud platform, regulated control system, organizational unit, or another physical or operational whole that can act in work or transformation while remaining itself.

The first useful question is not “is there emergence?” First test the exact candidate against A.1’s six common components. Then test whether its physical or operational organization makes it eligible to act in work or transformation while preserving its identity—the direct U.System criterion. After those two tests, recover only the additional facts used by the concrete case, such as delimitation, an objective or commitment, coordination, capability, system-role kind or assignment, method, work, transformation, functioning, architecture, evidence, assurance, or time. State each fact or claim through the pattern that defines its object or relation. Do not make an objective or commitment a condition for U.System recognition; require it only for the separate objective or commitment claim being made.

Use B.2 first to decide whether whole reidentification is needed and to identify the one candidate new whole. Use B.2.2 only when that candidate is to be tested under the already admitted U.System kind.

What goes wrong if missed. A real operating whole is still managed through old component claims, or a mere collection is declared a new system without establishing its A.1 basis and acting eligibility.

What this buys. The system MHT keeps the useful meta-system-transition intuition while preserving FPF’s subject patterns for system participation, architecture, capability, transformation, work, evidence, and assurance.

Not this pattern when.

• If the result whole is claim-bearing and non-agentive, use B.2.3 and the episteme family.
• If the evidence is only a capability or functioning gain without whole reidentification, use A.2.2, C.16, A.6.F, A.3.4, C.30.TFS-REL, and A.10.
• If the claim is ordinary system aggregation or delimitation, use B.1.2, A.1, A.14, and C.13.
• If the claim is a mathematical, simulation, graph, benchmark, or scaling expression, use C.29 and the relevant description or publication pattern before returning to B.2.
• If the claim is only supervisor-subholon feedback relation inside an already admitted system whole, use B.2.5.

B.2.2:1 - Problem Frame

B.2 is holon-general. B.2.2 is its U.System specialization.

A system-result MHT is current when B.2’s exact new whole proposed for recognition under the already admitted U.System kind is a physical or operational holon eligible to act and the case needs that same recognized whole to carry one or more separately governed system-level claims, such as delimitation, objective, coordination, capability, functioning, architecture, transformation, work, assurance, or time. The old constituent systems may remain parts, participants, resources, or interacting neighbors, but their claims do not automatically become claims about that recognized result system.

A collection of systems is not thereby a system MHT. B.2.2 carries B.2’s existing-whole/new-whole comparison through complete A.1 recognition and the direct U.System criterion; it does not create a system-specific result object or record schema.

B.2.2:2 - Problem

Without this specialization:

1. System identity stays on old parts. The project keeps component assurance, component responsibilities, and component interfaces after the operating whole has changed.
2. System claims become rhetoric. A group gets a collective name, but no delimitation, objective, obtaining coordination relation, or capability envelope is established for the exact new whole proposed for recognition under U.System.
3. Supervision is overread. A coordination mechanism is treated as a containing whole, safety warrant, or complete system recognition without the corresponding direct facts.
4. Transformation is confused with containment. One system changing another holon is treated as part-whole construction instead of transformation and work.
5. Architecture description replaces architecture. Dashboards, diagrams, simulations, bills, and digital twins are treated as the operating system rather than descriptions of it.

B.2.2:3 - Forces

B.2.2:4 - Solution

After B.2 leaves a whole-reidentification question open, continue with the same exact candidate new whole and direct facts. Add no system-specific result species or context-shaped slice.

B.2.2:4.1 - Reuse The B.2 Candidate And Complete System Recognition

Keep B.2’s one resultHolonRef for the exact candidate new whole and its one resultHolonKindRef, which here resolves to the already admitted U.System kind. The references may appear in B.2’s optional HolonReidentificationRecord when a receiving use needs a durable account; B.2.2 adds no second record.

Before calling the candidate a system result:

1. execute the complete A.1 criterion over the candidate’s exact constituents, obtaining constructive relations, governed assembly, reidentification rule, and composition-grounded whole characteristic;
2. show that its actual boundary, interfaces, relevant characteristics, and identity-preservation conditions satisfy at least one applicable governed larger-assembly construction method or rule under which it can remain a constituent;
3. apply the direct U.System criterion to that same individual: its actual physical or operational organization must make it eligible to act causally in work or transformation while preserving its identity;
4. recover only the additional system facts used by the concrete case—including any delimitation, objective, commitments, coordination, capability, system-role kind or assignment, method, work, transformation, functioning, architecture, evidence, assurance, or temporal claim—and state each through the pattern that defines its object or relation; and
5. keep the classification judgment, evidence or assurance, currentness, and receiving reliance separate from those world-side facts.

If a required A.1 component or the acting-eligibility criterion fails, do not identify the candidate as the system result. If an additional system fact needed for another claim is absent, withhold that claim rather than treating its absence as failure of the U.System criterion. If missing evidence or an unavailable dependency prevents a determination, report unknown; neither a filled reference nor an optional record changes that result.

B.2.2:4.2 - Carry Result-System Claims Through Subject Patterns

When the candidate is recognized as U.System, state every changed result-system fact or claim under its subject pattern:

• system-role assignments through A.2.1, relations among system-role kinds through A.2.7, and other relations through the patterns that define them;
• capabilities through A.2.2 and their measured-characteristic claims through C.16;
• methods through A.3.1, their descriptions through A.3.2, and mechanisms through A.6.1; use A.15 when their alignment with roles and work is the question;
• transformations through A.3.4;
• work occurrences through A.15.1;
• functioning and functional-structure wording through A.6.F to its direct subject pattern; selected transformation-flow structures through E.18 and their bounded architecture use through C.30.TFS-REL;
• architecture through C.30, A.22, and C.30.ASV;
• evidence and assurance through A.10, B.3, and B.3.5;
• temporal and dynamics claims through C.27, A.19, and the direct temporal patterns.

Do not reuse old component evidence as if it automatically covered the proposed new whole after recognition under U.System. Carry an unchanged component claim only through its exact continuing relation; establish each changed result-system fact under its subject pattern and support the associated claim through a separate evidence or assurance relation.

B.2.2:4.3 - System Trigger Interpretation

When a receiving use has materialized B.2’s optional MHTTriggerProfile, read its cues for a system case as follows:

No cue is enough by itself. Each row points to facts and claims to inspect; B.2’s direct existing-whole/new-whole comparison, complete A.1 recognition, and the system-kind criterion decide the result.

B.2.2:4.4 - Delimitation and External Acting Systems

For system-result MHT, distinguish:

• a part of the result system;
• an external acting system that changes the result system or a constituent;
• an environment or resource that participates in work;
• a description, dashboard, twin, model, diagram, or publication about the result system.

A lathe making a workpiece, a controller steering a plant, or a teacher changing a learner does not thereby become a part of the changed holon or the larger whole containing it. Use A.12, A.3.4, and A.15.1 for acting side, transformation, and work. Use part-whole patterns only when parthood itself is admitted.

B.2.2:4.5 - Assurance Re-Basing

When the exact candidate new whole is recognized as U.System, test old assurance against that system rather than transferring it by name.

Ask:

• Which component evidence still applies unchanged?
• Which evidence applies only through explicit correspondence or source-use relation?
• Which assurance claims must be rewritten for the result system?
• Which architecture, capability, functioning, work, temporal, or evidence claims now have different subject patterns?

A claim about the recognized result system may reuse component evidence only through an exact correspondence or source-use relation and a fresh evaluation of applicability. That system does not inherit safety, reliability, responsibility, or performance claims by label.

B.2.2:5 - Archetypal Grounding (Worked Cases)

B.2.2:5.1 - Search-And-Rescue Swarm

Before MHT, the project has individual drones with local navigation and maintenance records. After MHT, the current object may be one search-and-rescue swarm if the result whole has its own mission objective, coordination relation, external command relation, capability envelope, and swarm-level risks.

• Candidate new whole: the search-and-rescue swarm named by B.2.
• A.1 basis: exact drone constituents, obtaining formation and coverage-coordination relations, the governed swarm assembly, the swarm reidentification rule, and the whole-level area-search characteristic; its boundary, command and mission interfaces, operating characteristics, and identity-preservation conditions also fit the applicable larger rescue-system construction rule.
• System criterion: the swarm has acting eligibility. This case also has its own command-and-operating-area delimitation, mission objective, coordination relations, and external commitments.
• Assurance: swarm-level tests support claims about the candidate; individual drone certificates remain component evidence and do not establish the swarm facts.

The old drone evidence remains relevant, but it is not enough for the swarm-level assurance claim.

B.2.2:5.2 - Cloud Platform

Independent services become a platform only if the current claim concerns a result system: a shared control plane, system-level SLO, deployment and rollback coordination, platform-level evidence, and external commitments.

If the only change is a better dashboard or one more service, use architecture-description, publication, measurement, or component patterns. Use B.2.2 only when B.2 identifies the operating platform itself as the exact candidate new whole and that candidate passes A.1 plus the direct U.System criterion.

B.2.2:5.3 - Production Cell

A machine, robot, fixture, workpiece carrier, and inspection station can become a production cell when the cell has its own delimitation, objective, obtaining coordination relations, transformation structure, exact work occurrences, and capability envelope. Evidence separately supports the claims about those facts.

A fixture being manufactured as a workpiece is not part of the machine merely because the machine changes it. The production cell claim needs a result system; the manufacturing relation remains transformation and work.

B.2.2:5.4 - Bias-Annotation

B.2.2:6 - Conformance Checklist

B.2.2:7 - Common Anti-Patterns and How to Avoid Them

B.2.2:8 - Consequences

Positive consequences:

• Meta-system transition remains usable for engineering and organizational systems without making B.2 system-only.
• System ontic preservation becomes explicit: the same exact candidate is recognized under A.1 and U.System, while each system fact and claim stays with its subject pattern.
• Assurance, responsibility, architecture, work, and evidence claims are kept with their subject patterns.

Costs:

• A system-result MHT cannot be declared by name, diagram, dashboard, or metric jump alone.
• Teams must separate old component evidence from result-system evidence.
• Some apparent emergence claims return to ordinary system aggregation, capability, measurement, or architecture repair.

B.2.2:9 - Rationale

Valentin Turchin’s meta-system transition remains a useful intuition for the system case: components can become a higher operating whole when coordination and control create a new object of management and assurance. FPF generalizes that intuition in B.2, then uses B.2.2 to keep the classical system case precise.

The key distinction is ontological, not lexical. A whole proposed for recognition under the admitted U.System kind is not a trigger profile, coordination mechanism, graph, description, dashboard, or process label. It is one exact candidate new whole that satisfies A.1 and the direct U.System criterion; every changed system fact and claim stays with its subject pattern.

B.2.2:10 - SoTA-Echoing

B.2.2:11 - Relations

• Specializes: B.2 for one exact candidate new whole independently recognized under the already admitted U.System kind.
• Builds on: A.1, B.1.2, A.14, and C.13 for holon and system delimitation and part-whole grounding.
• Coordinates with: A.12, A.3.4, A.15, A.15.1, A.2.1, A.2.2, C.16, A.6.F, C.30, A.22, C.30.ASV, C.30.TFS-REL, A.10, B.3, and B.3.5.
• Uses: B.2.5 when supervisor-subholon feedback relation is part of the system-result evidence.
• Contrasts with: B.2.3 for MHT-result holons admitted as U.Episteme and B.2.4 for the capability and functioning decision bridge to whole reidentification.

B.2.2:End

B.2.3 - Meta-Holon Transition With Episteme Result

Type: Part B holonic construction pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.2.3:0 - Use This When

Use this pattern when B.2 has identified one exact candidate new whole and that same individual must be recognized under the already admitted U.Episteme kind: a theory, model family, standard, doctrine, specification body, research programme, field-level knowledge body, or other claim-bearing non-agentive holon.

Use B.2 first to decide whether whole reidentification is current and to identify the one candidate new whole. Use B.2.3 only when its resultHolonKindRef resolves to U.Episteme.

First useful move. For B.2’s exact candidate, identify one U.ClaimGraph, one exact EntityOfConcern, and one effective U.ReferenceScheme, then test whether their EpistemeConstitutionRelation obtains under C.2.1. Keep grounding, viewpoint, view, publication, source use, representation, evidence, and assurance in their neighboring direct relations.

What goes wrong if missed. A catalogue, literature review, dashboard, model repository, or vocabulary is called a new theory without claim-graph reidentification; or a real new episteme whole is treated as a pile of publications.

What this buys. The pattern preserves B.2 whole reidentification while keeping episteme ontology with C.2.1 and the episteme family. It prevents episteme-result MHT from becoming episteme agency, publication authority, generic emergence, or a second episteme ontology.

Not this pattern when.

• If the result whole is a physical or operational holon eligible to act, use B.2.2.
• If the question is episteme constitution, empirical grounding, publication, source use, view, viewpoint, ClaimGraph, reference scheme, or description use without MHT, use C.2.1, C.2.P, C.2.P.DR, E.17, and the direct episteme-family pattern.
• If the question is effect-free episteme morphing, viewing, retargeting, or controlled semantic coarsening, use A.6.2, A.6.3, A.6.4, or A.6.3.CSC.
• If the question is synthesis work, use A.15.1 for performed work and A.12 or A.3.4 for acting-side and transformation claims.
• If the wording is ambiguous emergence-family language, use B.2.P before selecting B.2.3.

B.2.3:1 - Problem Frame

A library is not a theory, and a theory is not its publication.

A group of papers, models, datasets, design notes, forecasts, standards, or local doctrines may remain a collection. B.2.3 becomes current only when B.2’s exact candidate new whole can be constructively recognized under A.1 and the current C.2.1 constitution criterion identifies that same individual as one claim-bearing episteme.

B.2.3 introduces no special episteme result object. It retains B.2’s one resultHolonRef and resultHolonKindRef, then requires C.2.1 for episteme constitution and each current neighboring relation’s own subject pattern.

B.2.3:2 - Problem

Without this specialization:

1. Catalogues become theories. Aggregated publications or dashboards are treated as a new episteme because they are stored together.
2. Theory becomes publication. The paper, report, standard document, model card, or dashboard is used as the episteme itself.
3. Episteme receives agency. The theory, standard, or doctrine is described as if it performs work or enforces behavior by itself.
4. Morphing becomes MHT. A view, retargeting, coarsening, translation, or model transformation is treated as a new episteme whole.
5. Assurance is inherited silently. Trust in constituent sources is treated as trust in the reidentified episteme whole.
6. Generic emergence replaces claim structure. “Emergent theory” hides the actual claim graph, reference scheme, and grounding relation.

B.2.3:3 - Forces

B.2.3:4 - Solution

Use B.2.3 as the U.Episteme specialization of B.2. Reuse B.2’s exact existing whole, exact candidate new whole, direct construction facts, and optional C.2.1 records; add no context-shaped slice or episteme-result schema.

B.2.3:4.1 - Reuse The B.2 Candidate And Complete Episteme Recognition

Keep B.2’s one resultHolonRef for the candidate and its one resultHolonKindRef, which here resolves to the already admitted U.Episteme kind. Execute the complete A.1 criterion over that candidate, including the larger-assembly applicability and compatibility condition. Then apply C.2.1 to the same individual:

1. identify its exact claim content as one U.ClaimGraph;
2. identify the exact independently governed U.Entity that those claims concern;
3. identify the effective U.ReferenceScheme under which the claims are read about that entity; and
4. test whether the direct EpistemeConstitutionRelation among those participants obtains and yields one interpretable claim-bearing whole.

The candidate and its constitution relation are distinct, even though C.2.1 reidentifies them from the same participant triple. A card, tuple, repository, publication set, graph representation, or filled reference does not make the relation obtain. If A.1 or C.2.1 fails, do not identify the candidate as the episteme result; if a required dependency cannot be evaluated, return unknown.

B.2.3:4.2 - Keep Constitution And Neighboring Relations Separate

The exact ClaimGraph, EntityOfConcern, and effective ReferenceScheme are the three participants of C.2.1’s EpistemeConstitutionRelation. That constitution relation does not by itself identify A.1 constituents or constructive part relations. When A.1 requires those facts, recover them from an exact direct episteme-part or claim-composition pattern. The EntityOfConcern remains an independently governed entity related through aboutness and reference. Keep all other current questions in their direct relations:

• empirical grounding uses EpistemeEmpiricalGroundingRelation only when designated empirical claims have current claim-to-world mappings involving the exact grounding holon;
• viewpoint selection for a describing use follows E.10.D2; U.View recognition requires E.17.0 conformance of the exact episteme to an exact viewpoint;
• publication occurrence, publication form, carrier, source use, and C.29 representation remain distinct from the episteme and its constitution;
• an exact acting System first has the A.13 core and A.15.1 independently admits its synthesis Work under a Method; F.6 enters only if the receiving transition account also consumes precise assignment-bound attribution through the same obtaining A.13 assignment, while any actual transformation remains a separate claim; and
• evidence and assurance support or challenge exact claims but do not enter episteme identity or establish constitution.

Add only the neighboring object or relation required by the receiving use. Do not infer any of them from a publication set, and do not turn them into extra identity positions.

B.2.3:4.3 - Episteme Trigger Interpretation

When a receiving use has materialized B.2’s optional MHTTriggerProfile, interpret its cues without giving agency to epistemes:

These cues identify claims and relations to inspect. They neither constitute the candidate episteme nor select B.2; the direct facts, complete A.1 criterion, C.2.1 constitution test, and B.2 existing-whole/new-whole comparison decide the result.

B.2.3:4.4 - Blocked Readings

Do not use B.2.3 as:

• a name for generic emergence;
• an authority claim for a publication;
• an agentive claim about a theory, standard, or doctrine;
• an effect-free episteme morphism, view, retargeting, or coarsening;
• a second episteme ontic beside C.2.1;
• a shortcut from source synthesis to high trust;
• a replacement for source-use, evidence, assurance, or publication patterns.

B.2.3:5 - Archetypal Grounding (Worked Cases)

B.2.3:5.1 - Reliability Doctrine

Before MHT, teams have local runbooks, incident reports, dashboards, and reliability definitions. They may be useful, but they are not yet one episteme.

After MHT, the exact candidate may be a reliability doctrine when it passes A.1 and its ClaimGraph, EntityOfConcern, and effective ReferenceScheme stand in an obtaining C.2.1 constitution relation. Add empirical grounding to operating services, handbook publication, and source-use relations for standards or training materials only when the receiving use needs them.

• Candidate new whole: the reliability doctrine named by B.2.
• A.1 basis: exact constituents and constructive relations established by an obtaining episteme-part or claim-composition predicate, a governed assembly and reidentification rule, a composition-grounded claim-bearing characteristic, and compatibility with an applicable larger knowledge-body construction rule.
• C.2.1 constitution: the doctrine’s exact ClaimGraph states its principles and definitions; its EntityOfConcern is user-visible service harm and reliability; its effective ReferenceScheme supplies the reliability designations and interpretation rules.
• Neighboring relations: empirical grounding to operating services, handbook publication, source use for standards and training materials, and evidence or assurance are added only for the receiving use and do not identify the doctrine.

Systems use and cite the doctrine, use it in training, and let its claims guide their work; any relevant local system-role kind and assignment remain separate claims.

B.2.3:5.2 - Model Family Becomes Theory

A model family can remain a toolbox. It becomes an episteme-result MHT only if B.2’s candidate passes A.1 and one exact ClaimGraph, EntityOfConcern, and effective ReferenceScheme stand in an obtaining C.2.1 constitution relation. Empirical grounding and explanatory or predictive use are checked through neighboring direct relations when the receiving use needs them; they are not extra identity constituents.

If the change is only a new model publication or benchmark score, use publication, source-use, measurement, evidence-use, and mathematical-lens patterns instead.

B.2.3:5.3 - Standard Body

A set of clauses, examples, and annexes can become a standard episteme only when the candidate passes A.1 and its exact ClaimGraph, EntityOfConcern, and effective ReferenceScheme satisfy C.2.1 constitution. Recover its terms, references, scope, and conformance claims under that constitution; identify publication forms separately.

The standard is not the committee, the PDF, or the Work of enforcement. The committee may be an acting System. If committee or enforcement Work is claimed, recover each exact performer through A.13 and admit the Work independently under A.15.1. Add F.6 only if the account expressly consumes precise assignment-bound attribution; a missing or failed relation leaves the Work intact. The PDF file is a presentation carrier; its layout may supply a publication form.

B.2.3:5.4 - Bias-Annotation

B.2.3:6 - Conformance Checklist

B.2.3:7 - Common Anti-Patterns and How to Avoid Them

B.2.3:8 - Consequences

Positive consequences:

• Episteme-result MHT becomes usable without preserving title mnemonics as ontology.
• C.2.1 remains the episteme identity pattern.
• Publications, source use, synthesis work, evidence, assurance, and acting systems remain separate.

Costs:

• A claimed synthesis must identify and test the current C.2.1 constitution, not only cite a portfolio.
• Result-episteme assurance requires a fresh applicability judgment for the exact result claim; existing relations may be reused where that judgment warrants it.
• Some “new theory” claims return to publication, source-use, morphism, benchmark, or evidence-use patterns.

B.2.3:9 - Rationale

Knowledge synthesis can create a new holon, but only when the result is a reidentified claim-bearing episteme. B.2.3 keeps that useful case and removes the drift toward episteme agency, publication authority, generic emergence, and duplicate episteme ontology.

This pattern is deliberately thin. B.2 is the pattern for whole reidentification; C.2.1 is the pattern for the ClaimGraph/EntityOfConcern/ReferenceScheme constitution relation and episteme identity; publication and source-use patterns contain the defining content for their relations; A.6 episteme-morphism patterns contain the defining content for morphing and retargeting; use A.15.1 for synthesis Work and A.12 for the acting-side split.

B.2.3:10 - SoTA-Echoing

B.2.3:11 - Relations

• Specializes: B.2 for an exact candidate new whole independently recognized under the already admitted U.Episteme kind.
• Builds on: B.2 for the exact candidate new whole and whole reidentification, A.1 for candidate recognition, C.2.1 for the obtaining ClaimGraph/EntityOfConcern/ReferenceScheme constitution relation, and E.24.UK for prior public-kind admission.
• Coordinates with: C.2.P, C.2.P.DR, E.17, E.17.*, A.6.2, A.6.3, A.6.4, A.6.3.CSC, A.10, B.3, B.3.5, C.29, F.18, and F.19.
• Uses: B.2.P when source wording such as emergence-family or title-mnemonic wording hides the claim kind.
• Contrasts with: B.2.2 for system-result MHT and B.2.4 for the capability and functioning decision bridge to whole reidentification.

B.2.3:End

B.2.4 - Do Capability or Functioning Changes Require Whole Reidentification?

Type: Part B holonic construction pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.2.4:0 - Use This When

Use this pattern when exact capability, functioning, or transformation-flow facts, already established under their subject patterns, make a B.2 whole-reidentification question live.

The first useful question is whether those facts can still be explained by the existing whole. If they can, keep that whole and use the direct pattern for the capability, functioning relation, transformation, Method, Work, module, characteristic, or architecture claim. If they cannot, use B.2 for the residual question. Evidence and measurement separately support, challenge, or leave unresolved the claims about those facts; they create neither the facts nor B.2 selection.

What goes wrong if missed. A genuine new whole is hidden under ordinary capability improvement; or every impressive capability, function, method chain, module allocation, or metric gain is overclaimed as emergence.

What this buys. The pattern keeps capability and functioning facts available to B.2 while preserving the separate evidence relation and preventing B.2.4 from becoming a generic capability, function, method, work, module, or emergence pattern.

Not this pattern when.

• If the claim is ordinary capability, use A.2.2; use C.16 for its measured-characteristic claims.
• If function-like wording hides the exact claim, use A.6.F to recover its direct subject pattern; an already precise functioning claim returns directly to that pattern.
• If the claim is transformation or transformation-flow structure, use A.3.4 or E.18 respectively; use C.30.TFS-REL for the selected structure’s bounded architecture use.
• If the claim is method, method relation, method description, work plan, or work occurrence, use A.15, A.3.1, A.3.2, A.15.2, and A.15.1.
• If bearer allocation is the question, use the direct allocation or parthood pattern. Use A.6.M only for unresolved module/interface wording, and C.30, A.22 or C.30.ASV only for the current architecture, selected-structure or architectural-view claim.
• If the claim is measurement, threshold, score, robustness, quality, or a whole-level characteristic, use C.16 and A.19 for that claim and A.10 only when evidence use is current.
• If the wording is ambiguous emergence, synergy, or title-mnemonic language, use B.2.P before selecting B.2.4.

B.2.4:1 - Problem Frame

A new capability is not automatically a new whole. A function-like relation is not automatically a part-whole relation. A transformation-flow structure is not automatically MHT.

B.2.4 is the narrow B.2 specialization for cases where exact capability, functioning, or transformation-flow facts defeat the existing-whole explanation and point to a candidate new holon. Evidence bears on claims about those facts; it does not make the explanation fail by itself.

B.2.4:2 - Problem

Without this specialization:

1. Capability becomes generic emergence. A threshold crossing or new envelope is treated as a new whole without B.2 checks.
2. Function becomes ontology. Function-like wording creates U.Function or a hidden peer kind.
3. Method and work collapse. The way of doing, description of doing, planned work, and performed work are compressed into one vague operational claim.
4. Module allocation becomes functional truth. A module label is treated as evidence for the required behavior or selected structure.
5. Transformation-flow description replaces in-life structure. A graph, diagram, or publication of a flow is treated as the flow structure or whole.
6. Whole reidentification is missed. A real result whole is left as “just a better capability”.

B.2.4:3 - Forces

B.2.4:4 - Solution

Use B.2.4 as a decision bridge from direct capability and functioning facts to B.2 whole reidentification. Add no generic slice, context placeholder, candidate-bearer list, or second B.2 record.

B.2.4:4.1 - Start From Exact Facts, Claims, And Support

1. Name the exact existing whole and its direct identity or reidentification rule.
2. Identify each exact capability envelope, obtaining functioning relation, or selected in-life transformation-flow structure under its subject pattern. Keep method, method description, work plan, work occurrence, module allocation, characteristic, and architecture facts separate when they are current.
3. State the exact claim made about those facts. Name evidence or measurement only as a separate relation that supports, challenges, or leaves that claim unresolved.
4. Perform B.2’s ordinary existing-whole comparison. Better measurement, component improvement, Method or Work repair, allocation repair, or architecture-view repair can leave the same whole in place.
5. If a residual whole-reidentification question remains, use B.2 for it. B.2 then identifies one exact candidate new whole, applies the complete A.1 and kind-specific criteria, and compares that candidate with the existing whole.

B.2.4 adds no result species. If a receiving use needs a durable account, use B.2’s optional C.2.1 epistemes; their content neither creates the direct facts nor selects the new whole.

B.2.4:4.2 - Subject-Pattern Test

Before applying B.2, test whether the exact facts are already explained under a subject pattern:

B.2.4:4.3 - Existing-Whole Explanation

Perform B.2’s ordinary existing-whole comparison before claiming whole reidentification. Materialize its optional ExistingWholeExplanationResult only when another use must inspect or cite the outcome.

Subject-pattern explanations that often stop B.2.4 include:

• better measurement or benchmark normalization;
• improved component capability;
• corrected function-like wording;
• a clearer method relation or method family selection;
• a new method description without corresponding in-life capability or work facts;
• better work coordination inside the same whole;
• module allocation repair;
• architecture-view or transformation-flow-structure repair;
• better evidence, measurement, or source currentness for an unchanged world-side claim.

If one of these explanations is sufficient, finish B.2.4 by retaining the existing whole and continue with the subject pattern.

B.2.4:4.4 - When B.2.4 Requires B.2

Use B.2 when the exact direct facts show that the existing whole cannot carry the current subject claim and an exact candidate new whole must be tested. Examples:

• a production cell has an exact capability envelope, obtaining coordination and functioning relations, a selected in-life transformation-flow structure, and external commitments that cannot be explained by individual machines or the old aggregate;
• a service platform has an obtaining functioning relation and external commitments that cannot be assigned to one service or module;
• exact coordination and work facts concerning a team, a toolchain, and the enacted Methods from a method family make a result-system candidate live; or
• a candidate episteme has exact constitution and explanatory-use facts that leave an episteme whole-reidentification question.

After the return, use B.2 for the existing-whole/new-whole comparison, its one exact candidate, and any optional record. B.2.4 adds no result record or evidence slice. The direct patterns still define and test the contributing facts, while evidence or measurement supports the associated claims.

B.2.4:5 - Archetypal Grounding (Worked Cases)

B.2.4:5.1 - Production Cell Capability

A milling machine, robot arm, fixture, and inspection station can remain a collection of assets even when a scheduling rule for their use is available. A new production-cell candidate becomes current only when exact capability, functioning, coordination, and transformation-flow facts cannot be explained by any single component or the old aggregate. Cell-level cycle time and tolerance measurements may support the claim; they do not create the candidate or those facts.

Use A.6.F for function-like wording, A.3.4 for transformations, E.18 for transformation-flow structure and C.30.TFS-REL for its bounded architecture use, A.15.1 for performed work, C.16 for cycle-time and tolerance characteristics, and B.2 only when the cell whole must be reidentified.

B.2.4:5.2 - CI/CD Capability

A team may have methods for coding, testing, and releasing. That does not by itself create a new whole. Use the direct Method and Work patterns for the method relations and performed release work.

B.2.4 becomes current only if exact capability, coordination, commitment, and work facts leave a result-holon question that the existing team or platform cannot explain. Evidence may support that claim; an automated delivery label or score does not decide the ontology.

B.2.4:5.3 - Theory Explains New Phenomena

A new theory may explain phenomena that the source portfolio did not explain. Use B.2.4 to bring the exact explanatory-use facts into B.2’s ordinary existing-whole comparison, while evidence separately supports or challenges the claim about that use. This does not assign an A.2.2 capability to the episteme. B.2.3 supplies the episteme-result specialization if the exact candidate is U.Episteme; C.2.1 defines its constitution; C.29 handles any mathematical-lens use.

B.2.4:5.4 - Bias-Annotation

B.2.4:6 - Conformance Checklist

B.2.4:7 - Common Anti-Patterns and How to Avoid Them

B.2.4:8 - Consequences

Positive consequences:

• Exact capability and functioning facts can make real whole reidentification current, while evidence bears only on the associated claims.
• Subject patterns remain visible, so local improvements are not overclaimed.
• Method, work, function, module, and architecture distinctions survive high-pressure capability language; each claim remains with its subject pattern.

Costs:

• Teams must do the subject-pattern test before using B.2.4.
• Many impressive capability claims will stay outside MHT.
• B.2.4 depends on B.2 for the whole-reidentification result and any durable record required by the receiving use.

B.2.4:9 - Rationale

Capabilities and functioning relations are often where a new-whole question first becomes visible. Their direct facts, not the availability of supporting evidence, determine whether the existing-whole explanation still works.

B.2.4 keeps this mixed situation disciplined. It does not rename the capability, functioning, transformation flow, method, work, allocation, measurement, or support as “meta-function”. It asks whether the exact direct facts defeat the existing-whole explanation and, only then, requires B.2 for the residual question.

B.2.4:10 - SoTA-Echoing

B.2.4:11 - Relations

• Specializes: B.2 for cases where exact capability, functioning, or selected in-life transformation-flow facts leave a whole-reidentification question after subject-pattern explanations are tested.
• Uses: B.2.P when emergence-family or title-mnemonic wording hides the claim kind.
• Coordinates with: A.2.2, C.16, A.6.F, A.3.4, E.18, C.30.TFS-REL, A.15, A.3.1, A.3.2, A.15.2, A.15.1, A.6.M, C.30, A.22, C.30.ASV, C.29, A.10, and source-use patterns.
• Contrasts with: B.2.2 for system-result MHT and B.2.3 for episteme-result MHT.

B.2.4:End

B.2.5 - Supervisor-Subholon Feedback Relation

Type: Part B holonic construction pattern Status: Stable Normativity: Normative unless a section is explicitly informative

B.2.5:0 - Use This When

Use this pattern when a holon is supervised, regulated, steered, corrected, constrained, or coordinated through a two-sided feedback relation between one supervising acting system and one or more supervised holons. If the supervision is conditioned by a local system-role kind or assignment, recover that classification and exact assignment separately.

The first useful move is to recover the facts supporting the feedback claim:

Which holons are supervised?
Which admitted system supervises these holons for this feedback use, under which policy and during which time window, and which local supervisor system-role kind and exact assignment obtain when that classification matters?
What observation, report, signal, publication, or source relation carries state?
What influence, constraint, objective, mode, or work change returns?
Which rule and case facts couple that return to the observation for each supervised holon?
Which transformation, work, architecture, evidence, assurance, timing,
or causal claim is being made in addition to the relation?

What goes wrong if missed. A control diagram, policy note, dashboard, publication channel, or supervisor word starts carrying part-whole, agency, safety, assurance, timing, gate, or architecture claims that belong elsewhere.

What this buys. B.2.5 gives a readable compound claim: for each named holon, this system receives the stated observation and returns an influence coupled to it under the applicable rule. The observation, influence and coupling facts remain separately governed; the assertion can support a control description without introducing a fused feedback occurrence.

Not this pattern when.

• If the question is a control-structure view, use C.30.LCA.
• If the question is architecture or selected structure, use C.30, A.22, and C.30.ASV.
• If the question is reusable dynamics, timing, rate, or temporal validity, use A.3.3 and C.27.
• If the question is causal use, use C.28.
• If the question is evidence, provenance, assurance, or a gate decision, use A.10, G.6, B.3, or A.21 respectively. Use A.20 for its internal-constraint test in a transformation-flow structure; other constraint claims need their direct pattern.
• If module or interface wording hides the exact claim, use A.6.M to recover it; use the direct pattern for an already precise allocation or commitment claim.
• If the question is whole reidentification, use B.2.

B.2.5:1 - Problem Frame

A supervisor-subholon feedback claim states observation or reporting, returned influence and their coupling for named participants in one use. It is a conjunction under A.6.RCD, expressed in a C.2.1 assertion. Each base relation retains its own participants, applicability and identity rule. A system-role kind or assignment may qualify the acting system when independently established.

Use B.2.5 for this compound description. A broader architecture, MHT, Work or evidence account may use it while retaining the direct rules for those additional claims.

B.2.5:2 - Problem

Without this pattern, three different structures collapse:

1. Part-whole structure. Which holons are parts of which wholes.
2. Supervisor-subholon feedback relation. Which admitted system supervises, what it observes, and what influence or constraint returns; add its system-role kind and assignment only when separately current.
3. Description or representation structure. Which diagram, dashboard, report, model, publication, or control-view description represents the relation.

When these are confused, a functional layer is treated as a physical part, a publication is treated as an acting system, a diagram is treated as evidence, or a supervisor label is treated as a gate or assurance result.

B.2.5:3 - Forces

B.2.5:4 - Solution

State the feedback claim in one C.2.1 episteme about the named controller and supervised holons. A sufficient ordinary reading is: “For every drone in this set during the stated interval, controller C receives the stated observations and returns commands coupled to those observations under rule R.” Use A.6.RCD’s compound-claim branch; the description does not require a new relation kind or one independently reidentifiable feedback occurrence.

For a nonempty set H and each h in H, recover three propositions under their direct domain definitions:

1. Observation: which state of h is observed or reported to the controller, through which obtaining observation, report, publication or source relation.
2. Return: which influence from the controller reaches h, under the applicable command, constraint, objective, mode or Work predicate.
3. Coupling: which rule applies to this observation and return, and which facts establish that this return depends on that observation under the rule.

The compound claim is true exactly when all three propositions hold for every member of H under common applicability: the same named use, participants, scope and temporal qualification. This is ordinary logical conjunction of those propositions, not a combination of probability scores or assurance results. Recover each direct definition and its applicable edition when the claim relies on it. A local use needs no separately published conjunction rule.

An optional note can retain the needed details:

SupervisorSubholonFeedbackClaim@Context:  // claim-bearing episteme, not U.Relation
  supervisingActingSystemRef: U.EntityRef resolving to one admitted U.System
  supervisedHolonRefs: FinSet(U.HolonRef)  // nonempty
  useAndTemporalQualification:
  pairClaims:  // one for every supervised holon
    supervisedHolonRef:
    observationClaimAndBaseRelationRefs:
    returnedInfluenceClaimAndBaseRelationRefs:
    applicableCouplingRuleAndEdition:
    couplingFacts:
  supervisorSystemRoleKindRef?:
  supervisorSystemRoleAssignmentRef?:
  evidenceRefs?:
  strongerClaimPatternRefs?:

Observation and influence references keep their own kinds; a report episteme, a signal occurrence and a source-use relation are not interchangeable occupants of one relation position. Evidence supports the assertion under A.10; its adequacy and the obtaining of the base facts remain separate questions. A local system-role kind and assignment are added only when they independently obtain and affect this use.

B.2.5:4.1 - Establish and qualify the conjunction

Co-present telemetry and commands are insufficient. For each pair, apply the coupling rule to the actual observation and return. An unrelated broadcast fails that condition; one-way reporting fails the two-sided predicate. If the rule is missing, return the missing governor. If the rule exists but a needed observation or dependency fact is unavailable, return missing information. Neither absence of proof alone nor an empty supervised set supports the affirmative assertion. A negative claim needs the rule’s non-obtaining test and facts that satisfy it.

Keep the base occurrences and their own extent and continuity rules. A communication break can make an interval-qualified feedback assertion fail without ending a supervisor assignment. Reconnection requires current observation, return and coupling facts. Apply a changed policy to the affected interval; adding a holon extends the asserted set only after its own pair is supported.

Reopen the dedicated relation-kind alternative only when a receiving use needs to identify a feedback occurrence independently across changes. That alternative must supply its obtaining, extent and continuity rules, including interruptions, under A.6.RCD and A.6.REL. A useful compound description can stop here.

B.2.5:4.2 - Part-Whole Boundary

A supervised holon may be part of a larger holon, but supervision and parthood are different relations. A controller, committee, platform-governance group, review board, or tool-mediated group can supervise when the exact acting entity is independently admitted as U.System; it may do so under an exact system-role assignment without being a physical part of the supervised holon. A method, policy, or review practice can structure the supervision work; it does not supervise by itself.

Use A.1 for holon recognition, A.14 for the exact mereological claim, and B.1 or C.13 for the applicable construction account. Use B.2.5 for the compound supervisor-subholon feedback claim.

B.2.5:4.3 - Acting-System Boundary

The supervising participant is an admitted acting system. When local classification matters, A.2 supplies the exact supervisor system-role kind and A.2.1 supplies the obtaining assignment; neither label nor assignment acts. Do not create U.TransformerRef or treat a publication, theory, dashboard, model, method description, or report as the acting system.

For acting-side externalization, use A.12. For transformation, use A.3.4. For Work, use A.15.1. For system-role kind and assignment, use A.2 and A.2.1.

B.2.5:4.4 - Control-Structure View Boundary

When feedback is drawn as planner, controller, observer, plant and supervisor structure, B.2.5 states the compound claim and C.30.LCA governs the control-structure view. The view can cite both the assertion and the independently obtaining base relations. Its arrows alone establish neither their obtaining nor the coupling.

B.2.5:4.5 - Neighboring Claim Boundary

B.2.5 does not certify stability, safety, assurance, evidence sufficiency, causal validity, gate passage, rate adequacy, or mathematical adequacy.

Use:

• A.3.3 for reusable dynamics or state-evolution claims;
• C.27 for temporal and rate adequacy;
• C.28 for causal-use claims;
• A.10 and G.6 for evidence and provenance;
• B.3 for assurance;
• A.20 for its internal-constraint test in a transformation-flow structure and A.21 for gate decisions;
• C.29 for mathematical-lens use.

B.2.5:5 - Archetypal Grounding (Worked Cases)

B.2.5:5.1 - Robotic Swarm

A fleet controller C supervises drone d1. In this illustrative protocol R1, each control tick requires a same-tick range report received by C and a returned command received by d1. The command is generated from that report: reduce speed when the reported obstacle distance is below 2 m; otherwise maintain speed. These protocol predicates govern reporting, command delivery and their coupling for this case; they do not establish sensor accuracy or safety.

If the tick-13 trace is unavailable, the corresponding conclusion is unresolved instead of negative. If R1 changes to R2, use R2’s actual coupling test for the new interval. Adding d2 requires d2’s own report, return and coupling facts before asserting feedback for {d1,d2}.

A C.30.LCA description consumes the report and command relation references plus the compound assertion. It need not invent a single feedback occurrence to draw the supported connection. Claims about convergence, delay tolerance, disturbance damping, evidence, assurance or safety use their subject patterns.

B.2.5:5.2 - Scientific Theory Revision

A theory is revised when labs publish findings and a research community reviews anomalies and accepted revisions.

B.2.5 can state feedback around review and revision when the reviewed object is independently admitted as a Holon and the report, returned revision influence and coupling rule are established. Otherwise retain the independently supported review or source-use claims. Recover the exact admitted System that performs the review or revision, whether it is a research community, standards body, lab, review board, or tool-mediated group; any local system-role kind and assignment are separate claims. The theory remains the reviewed or revised episteme.

For publication channels, journals, datasets, reports, and review records, keep each object’s identity distinct from its current publication or source-use relation; recover content, form, representation, or carrier only when the case depends on that distinction.

B.2.5:5.3 - Product Platform Policy

A product platform constrains component teams through interface rules and release gates. B.2.5 states the component reports, returned constraints and rule coupling those constraints to the reports for the admitted platform or governance system; a system-role kind or assignment is added only when separately current.

Work alignment uses A.15; a separate work-authority claim needs its own direct pattern. Gate passage uses A.21; A.6.M restores interface wording before the exact commitment claim returns to its direct pattern; architecture view uses C.30.LCA when the control structure is described.

B.2.5:5.4 - Bias-Annotation

B.2.5:6 - Conformance Checklist

B.2.5:7 - Common Anti-Patterns and How to Avoid Them

B.2.5:8 - Consequences

Positive consequences:

• Supervisor-subholon language stays useful without creating false acting objects or false part-whole claims.
• Control diagrams, publication channels, and feedback relations can be coordinated without being collapsed.
• Stability, safety, assurance, gate, timing, and evidence claims stay inspectable.

Costs:

• A compound feedback description is only the beginning of stronger analysis.
• Some control diagrams need qualification because their stronger claims remain unproven.
• Episteme examples require explicit acting systems for review and revision.

B.2.5:9 - Rationale

Supervisor-subholon feedback is a recurring relation in control, organization, architecture, and epistemic revision. It becomes precise only when separated from part-whole composition, control-structure views, publication and source-use relations, and stronger assurance claims.

The compound assertion supplies the present description use. A reusable feedback predicate or a dedicated relation kind is a further choice under A.6.RCD when a receiver needs it and the additional semantics are available. A mathematical loop remains a separately selected lens or structure.

B.2.5:10 - SoTA-Echoing — establish the feedback claimed for this interval

Practice question. What is enough to say that a named controller and holon participated in feedback during a specified interval? The selected line requires observation, returned influence and their rule-governed coupling. A serious cheaper alternative describes the intended controller, feedback channel and command channel in a functional control structure. That description can answer a design question before any operation occurs; it cannot alone settle an assertion about an actual interval.

Åström and Murray’s Feedback Systems, Chapter 1 summary supplies the selected control-theoretic line: feedback involves reciprocal influence, and sensing, computation and actuation form the basic control loop. The same source treats stability and useful closed-loop behavior as further design questions. Adapt reciprocal influence into the three propositions in §4, retaining each domain’s actual coupling rule. This supports a minimal descriptive assertion, not an import of continuous-time dynamics into organizational or episteme examples.

The STPA Handbook, MIT-STAMP-001, March 2018, Chapter 2, pp. 22–25 and 45–48 supplies the substantive control-structure comparator and failure analysis. It distinguishes a functional structure of possible information flow from physical structure, and examines missing, delayed or incorrectly used feedback. Adopt those distinctions for the view boundary in §4.4 and the interruption cases in §5.1. Reject using the diagram alone as an actual-interval witness; that shortcut is not a claim of the handbook. The handbook remains a source for analysis of control and unsafe scenarios, not a certificate that B.2.5’s assertion establishes safety.

The difference is visible at ticks 10–14 in §5.1. The intended diagram can stay unchanged while a delivered broadcast is unrelated to the observation, a command is absent, or the link is broken. Testing the three propositions distinguishes those cases and treats an unavailable trace as unresolved. The comparison therefore governs §4.1’s coupling and absence tests and CC-B2.5-2–3, while leaving C.30.LCA to describe the structure.

For an operational claim, both approaches can reuse the same controller rule and available trace; checking the relevant observation/return pair adds local work but closes a question the diagram leaves open. For an intended design, retain the cheaper structural description. A full dynamics model or STPA analysis costs more and answers stronger questions; it is needed only when those questions are selected. Reopen when the coupling rule, interval or member set changes, or a receiving use needs to reidentify one feedback occurrence across interruptions. These sources do not supply that new occurrence’s identity rule or establish the FPF Holon classification of an organizational example.

B.2.5:11 - Relations

• Builds on: A.6.RCD for the compound claim and C.2.1 for its assertion; A.1, A.2.1, A.12, A.3.4, A.15.1, B.1, A.14, and C.13.
• Coordinates with: B.2 when exact feedback facts leave a whole-reidentification question; evidence separately supports or challenges the claims about those facts.
• Coordinates with: C.30.LCA for control-structure view, A.3.3 for dynamics, C.27 for temporal and rate adequacy, C.28 for causal use, A.10 and G.6 for evidence, B.3 for assurance, A.20 for its internal-constraint test in a transformation-flow structure, A.21 for gate decisions, A.6.M for module-interface wording, and C.29 for mathematical-lens use.
• Uses: B.2.P when emergence or MHT wording hides the claim kind, including feedback or supervision invoked as an emergence claim. Ordinary feedback wording follows F.19/E.10 restoration and its direct subject pattern.

B.2.5:End

B.3 - Is This Claim Supported for This Use? — Trust and Assurance Calculus

Type: Foundational (B) Status: Stable Normativity: Normative when an FPF use makes an assurance claim about one exact target claim.

Plain-English headline. B.3 helps a practitioner state what an assurance claim is about, which argument and results support it, what use they support, what remains unsupported, and what would reopen the conclusion. It does not turn a badge, evidence item, calculation, record, publication, status, or decision into assurance by appearance.

Use this when. Use B.3 when an actual named assurance claim is current: for example, a claim that an exact model claim is credible for one decision, or that an exact safety claim is adequately supported for one release use.

First useful move. Write the target claim and the assurance use in one sentence. Then ask which direct results and argument make that use supportable. If there is no assurance claim, stop and use the pattern that defines or tests the actual evidence, status, gate, permission, safety, release, work, or domain-result claim.

What goes wrong if missed. A visible label or a convenient score starts raising trust without an exact target, argument, basis, limitation, and use. At the other extreme, a modest assurance question is forced through a universal score and a large record whose fields do not affect the decision.

What this buys. The user gets the smallest assurance result that changes the named use, with enough basis and limits to inspect or reopen it. Domain-specific characteristics and calculations remain usable without pretending that unlike measures share one scale.

Not this pattern when. Stay with A.2.4 for the classification of an episteme as evidence, A.10 and G.6 for source recovery and bounded reliance, G.11 for currentness, F.10 for a status value and its use, A.21 for a gate decision, and the direct domain pattern for safety, permission, access, responsibility, release, compliance, or controlled action. Consequence alone does not create an assurance claim. A direct domain rule may require one, but the claim must be stated before B.3 is applied.

First output. Produce either one bounded AssuranceResult claim or a plain statement that the available argument does not support the attempted assurance use. Do not create a B.3 result merely to record that another pattern is relevant.

B.3:1 - Problem frame

Assurance concerns a claim, not the world-side subject in isolation. Begin with one exact target claim, identified by its C.2.1 episteme or ClaimAddress as specified in §4.2, and one named use of an assurance conclusion. The claim’s EntityOfConcern remains the system, episteme, method, work occurrence, relation occurrence, or other exact subject identified by its direct pattern.

For example:

• a battery-pack safety fact and its direct test result remain under their safety, measurement, and test patterns;
• the episteme that states the safety claim remains under C.2.1;
• an assurance result states whether a named argument carries that claim for a named release use;
• a later gate, permission, or release decision remains a separate result.

The word calculus here means a disciplined way to select, combine, and interpret the inputs that the assurance argument actually consumes. B.3 defines no universal arithmetic across systems and epistemes.

B.3:2 - Problem

Five failures recur:

1. Assurance by appearance. A badge, dashboard, attestation, card, status, or publication is treated as the assurance conclusion.
2. One scale for unlike properties. Formality, reliability, coverage, congruence, and evidence quality are placed in one tuple even though they have different bearers and scales.
3. Unsupported aggregation. min, an average, a penalty, or another fold is called conservative without a dependency model and calibrated quantities.
4. Process burden by default. Every result is required to name dated Work, Method, assignment, bindings, and a reusable record even when the claim’s own basis closes the use.
5. Domain obligations absorbed into assurance. Safety, rights, access, responsibility, contest, redress, status, or controlled-action rules are replaced by a generic assurance record.

B.3:3 - Forces

B.3:4 - Solution

B.3:4.1 - Start from one assurance question

State these three things before choosing measures or a record:

1. the exact target claim;
2. the named assurance use;
3. the conclusion that must be supported, narrowed, or refused for that use.

Keep the following objects separate whenever they are current:

1. world-side facts and direct domain results;
2. the target-claim episteme;
3. evidence-use relations and source-provenance paths;
4. any assessment Work and the System that performed it;
5. formal, empirical, causal, measurement, conformance, or comparison input results;
6. the assurance-result episteme;
7. calculation traces, witnesses, and an optional note or publication that cites the result;
8. later reliance, status use, gate, permission, release, or action.

Evidence can support or challenge a claim. It does not make the target fact true. A favorable assurance result does not pass a gate, grant permission, or prove that later work relied on it.

B.3:4.2 - Use the smallest sufficient result

The compact result contains only facts every B.3 use needs:

AssuranceResult:
  targetClaimRef:
  assuranceUse:
  basisRefs:
  disposition: supported-for-use | narrowed | abstain | evidence-needed | reopen | blocked
  limitationsAndNotCarried:
  reopenCondition:

targetClaimRef identifies the exact C.2.1 episteme or one exact C.2.1 ClaimAddress when the use concerns one addressed claim inside a larger episteme. basisRefs cite the direct results, evidence-use relations, provenance paths, argument claims, or domain rules actually used. A compact result is complete when these fields decide the named use and another person can see why the stronger use is not carried.

Add a claim scope, condition set, interpretation scheme, audience, or time window only when changing it could change the conclusion. Keep design and run conclusions separate whenever their inputs or conditions differ.

Add assessment Work, performer, Method, application bindings, witnesses, or a reusable record only when the receiving use depends on competence, conflict of interest, timing, reproducibility, contest, redress, or later replay. These identities are never mandatory merely because B.3 is used.

An optional assurance note may cite the result and its basis. B.3 does not define a reusable RelianceSafetyCase, a safety authority, or a general contest-and-redress profile. If such a reusable object is needed, it requires its own problem, ontology, sources, minimum output, and direct domain boundaries.

B.3:4.3 - Name each characteristic by its bearer and scale

Include a characteristic result only when the assurance argument consumes it. State:

AssuranceCharacteristicResult:
  bearerRef:
  characteristic:
  scaleAndUnit:
  valueOrInterval:
  interpretationForThisUse:
  basisRef:

One characteristic name must not silently change meaning between subjects. System reliability, replication quality, evidential support, proof inspectability, and relation congruence are different characteristics even when a local source labels several of them R or CL.

The legacy letters F, G, R, and CL may appear inside a declared local scheme, but B.3 assigns them no universal cross-domain meaning:

• Formality or inspectability. Formal structure can make assumptions and inference steps easier to check. It raises assurance only when the named argument explains which uncertainty or verification need it closes. Making a wrong model proof-grade does not improve truth or empirical adequacy.
• Claim scope. U.ClaimScope stays an A.2.6 value. It is not a quality coordinate. Widening or narrowing scope changes the claim and its applicable use under the declared scope rules.
• Reliability-like characteristics. Use the exact domain definition, bearer, population or trials, conditions, scale, unit, and qualification window. A system reliability measure and an evidence-quality judgment are not interchangeable.
• Relation congruence. Characterize one exact mapping, calibration, interface, or other relation occurrence only under a declared scale and interpretation. The value neither changes the participants nor supplies a universal penalty.

Never average ordinal values. Do not subtract an ordinal value from a ratio quantity. Thresholds and order comparisons are valid only under the scale that defines them.

B.3:4.4 - Aggregate only under an applicable model

B.3 supplies no default fold. When the assurance argument combines quantitative or ordered inputs, cite:

1. the exact result claims being combined;
2. the dependency or alternative-path structure;
3. the domain aggregation rule or model;
4. independence, dependence, calibration, and unit assumptions;
5. the calculation or ordered comparison;
6. the rival rule that would matter if an assumption fails.

Use min only when the cited domain rule makes the weakest input a lower bound or bottleneck for the exact quantity. It is not universally conservative. If no applicable aggregation rule is available, report the inputs separately and return a bounded, non-positive, or unresolved disposition. Do not manufacture one score to make the result look complete.

Several independent evidence lines may strengthen an argument only through the rule that states how their dependence and coverage are handled. Claim-scope intersection or union follows A.2.6 and the relevant evidence model; it is not an assurance arithmetic shortcut.

B.3:4.5 - Choose one of three proof paths

Compact path. Use the six-field result in 4.2. Stop when it decides the named use.

Calculated or model-bearing path. Add the characteristic results, dependency structure, assumptions, aggregation rule, rival, calculation trace, and sensitivity or failure condition actually used.

Replay path. Add Work, performer, Method, application bindings, witnesses, and a reusable note only when those identities change the named assurance use. For any assessment Work, use A.13 to identify the actual performer and A.15.1 to admit the dated occurrence independently. Add F.6 only if the replay must also say exactly under which assignment the Work was performed. The Work, performer, Method, optional assignment check, result, witness, note, and publication remain separate.

Do not select the replay path merely because the use is important. Importance may make more basis necessary, but every added field must change inspectability, contestability, or the decision.

B.3:4.6 - Keep visible authority outside the result

A badge, score, dashboard tile, credential display, provenance mark, model card, datasheet, data card, assurance document, attestation, generated confidence phrase, or publication form can be a cue, source, evidence item, or representation. It contributes to assurance only through an exact claim and basis relation used by the argument.

If the visible item only reports a status, gate decision, permission, warning, or source location, use its direct pattern and produce no B.3 result. If an assurance claim is current, cite the item only for the property it actually establishes. A valid signature or provenance chain can establish origin and integrity without establishing safety, truth, compliance, or readiness.

B.3:4.7 - Leave domain obligations with their direct patterns

B.3 evaluates an assurance claim. It does not define safety duties, access rules, responsibility, affected-party disclosure, contest, redress, people or team status, resource allocation, release authority, or controlled action. Cite each applicable direct rule as a premise or limitation.

When a direct domain rule says a consequential use requires an assurance claim, state that claim and then apply B.3. When the direct rule requires a decision, permission, review, contest route, or redress relation instead, use that result directly. A display that affects behavior does not by itself open B.3.

B.3:4.8 - Preserve time, currentness, and design/run distinctions

State the exact window only when time changes the assurance conclusion. Monitoring, drift, incidents, evidence refresh, version change, policy change, gate change, or a newly discovered defeater can narrow, reopen, or withdraw a result while the target fact and target-claim identity remain unchanged.

Design evidence and run evidence may support different claims. Produce separate results when target use, conditions, scope, or evidence window differs; compare them instead of merging them into one score.

B.3:4.9 - Keep causal-use and method-structure branches direct

When an assurance argument depends on a causal-use claim, consume the exact C.28 result and its stated supported and unsupported uses. B.3 does not re-run causal identification. An unsupported causal-use result narrows, blocks, or leaves the assurance claim unresolved; it does not become a low universal reliability coordinate.

When Method composition, fallback, selection or family organization matters to the assurance argument, first use B.1.5, G.5 or the direct predicate for the relied-on fact. Use A.22 only when a separately selected organization itself changes the assurance question; then recover its selection basis and all four identity discriminators. MethodRelationStructure is a local designator for that selected structure, not a universal kind or a required record for every composition claim.

B.3:4.10 - Use Working-Model declarations only for what they state

An E.14 Working-Model assertion may contribute its declared validation posture and grounding links. A postulate still needs the empirical basis required by the current assurance use; an inferential claim needs its reasoning basis; an axiomatic or constructive claim needs the exact construction and identity basis it relies on. The declaration, grounding link, assessment Work, assurance result, and publication remain different objects.

B.3:5 - Proof obligations

B.3:5.1 - Common obligations

Every positive or narrowed B.3 result:

1. identifies the exact target claim and named assurance use;
2. cites only basis results and relations that actually bear on that use;
3. states assumptions, limitations, and unsupported stronger uses;
4. keeps target fact, claim, evidence, assessment, result, record, publication, and later use distinct;
5. names a reopen condition;
6. uses the direct domain rule for every safety, permission, access, status, release, responsibility, or controlled-action premise;
7. avoids aggregation unless its model and assumptions are explicit.

B.3:5.2 - Additional obligations for a calculated result

A calculated result also names every bearer, characteristic, scale, unit, dependency, calibrated mapping, aggregation rule, and calculation. It shows at least one assumption whose failure changes the result. If a rival rule is plausible at comparable effort, show why the selected rule fits the declared dependency structure.

B.3:5.3 - Additional obligations for replay

A replayable result adds only the Work and performance facts needed by the receiving use. Follow the §4.5 replay route for each assessment Work. Add its Method, application binding, witness, timing fact, or separate F.6 assignment check only when competence, independence, reproducibility, contest, or redress actually depends on that fact. No record field stands in for an obtaining relation.

B.3:6 - Worked cases

B.3:6.1 - Fully calculated case: two necessary independent conditions

Target claim: “The protection function succeeds on a demand.” Assurance use: a bounded reliability argument for a named design decision.

The domain model says that both independently tested conditions must succeed: sensor detection and actuator response. Each has estimated probability 0.9 under the same stated demand class and qualification window. Under the declared independence assumption, the joint probability is:

0.9 × 0.9 = 0.81

Using min(0.9, 0.9) = 0.9 would overstate this conjunction. If the conditions are dependent, even the product is not justified; the result must use the applicable conditional model or remain unresolved. The B.3 result therefore cites the two domain results, the series dependency structure, independence basis, product calculation, 0.81 conclusion, limitations, and the observation that reopens the independence assumption.

What changes in practice: the design decision is evaluated against 0.81, not a falsely “conservative” 0.9. No universal B.3 reliability formula is created.

B.3:6.2 - Routed-away case: dashboard status

Starting sentence: “The dashboard approves launch.”

The dashboard is a publication face. Suppose it displays GateDecision GD-17, which records that a named gate passed for release candidate R. The repaired sentence is: “The dashboard shows GateDecision GD-17 for release candidate R; the decision, not the display, records that the gate passed.”

Use A.21 and the release or permission pattern that consumes the gate decision. No assurance claim is present, so B.3 stops. If the dashboard does not resolve an exact gate decision, it is only a cue and launch approval remains unresolved.

B.3:6.3 - Episteme credibility with a compact result

Target claim: “Model edition M predicts response Y within the declared operating region.” Assurance use: whether an engineer may use that prediction as one input to a reversible design comparison.

The engineer cites the exact model claim, its empirical-validation result, A.2.4 first-use classification and the direct support relation actually used, the A.10 provenance path, the operating region, and the expiry condition. No combination of unlike characteristics is needed. The compact disposition is supported-for-use, limited to the reversible comparison; release, safety, and operation are expressly not carried. No dated assessment Work or reusable record is added because the use does not depend on who performed the already cited validation.

B.3:6.4 - Order-sensitive Method case

An assurance argument relies on a manufacturing sequence whose result changes when two steps are reversed. Recover the B.1.5 composition, order and join conditions and any actual A.15.1 Work the argument consumes. Those direct results may answer the assurance question. Use A.22 only if a separately selected organization contributes another needed premise; then identify its constituents, obtaining relations, applied constraints and use frame. The assurance result cites only the results and structure it actually relies on.

B.3:6.5 - Bias annotation

B.3:7 - Conformance checklist

B.3:8 - Common anti-patterns and repairs

B.3:9 - Consequences

Benefits

• Assurance remains explicit without forcing one cross-domain score.
• A small local claim can stop after six fields.
• Calculations become more trustworthy because assumptions and dependency structure are visible.
• Domain safety, access, responsibility, status, and decision rules retain their own meaning.
• Visible artifacts can contribute useful provenance or evidence without becoming authority.

Trade-offs

• B.3 supplies no convenient universal number. A project must use the domain model that gives its inputs meaning.
• Some assurance questions remain unresolved until a dependency model, calibrated mapping, or direct domain requirement is supplied.
• Reusable replay records cost more than a compact result and therefore require an actual receiver.

B.3:10 - Rationale

Assurance-case practice supports explicit claims, arguments, evidence, and maintenance. Reliability engineering supports calculations tied to dependency structure and assumptions. Neither supports one universal F-G-R-CL score across unlike subjects. B.3 therefore standardizes the boundaries and the minimum result while leaving characteristics and aggregation with the exact models that define them.

B.3:10.1 - Decision-bearing SoTA account

Older assurance-case editions and generic weakest-link slogans are lineage, not decision authority. Popularity, formal appearance, and publication recency do not establish the selected architecture.

B.3:11 - Relations

• Builds on: C.2.1 for target and assurance-result epistemes; A.2.4 for exact evidence-use classification; A.10 and G.6 for source-provenance paths and bounded reliance; A.2.6 for ClaimScope; C.16 and C.16.Q for characteristic and scale discipline; and the direct domain patterns for every input result.
• Coordinates with: A.15.1 and A.6.1 only when assessment Work and applications matter; G.11 for currentness; F.10 for status; A.21 for gates; permission, commitment, release, access, responsibility, contest, redress, safety, and controlled-action patterns for their own results; and E.17, E.24.PUB, and C.29 for publication and representation.
• Coordinates with: C.28 for causal-use results; B.1.5, G.5 or the direct pattern for the relied-on Method fact; A.22 only for an independently selected organization needed by the assurance argument.
• Used by: a pattern or project decision that consumes one exact assurance result. The consumer still applies its own decision, permission, gate, status, or work rule.

B.3:11a - Quantum-like claims

Quantum-like wording does not require assurance by itself. If the wording only prevents a local representation mistake, keep the note with C.26 and ordinary evidence. Apply B.3 only when an actual assurance claim about that exact quantum-like result and use is current. A comparative superiority claim must name the rival model, baseline, claimed mechanism, scope, evidence, and loss. Mathematical novelty or prestige supplies no assurance.

B.3:11b - Mathematical-lens use

When a C.29 mathematical-lens result is an input to an assurance claim, cite the exact lens-result claim, its interpretation and limits, the evidence-use and provenance relations relied on, and the named assurance use. Mathematical elegance or a structure-preserving mapping does not raise assurance by itself. Measurement construction and comparability remain with C.16.

B.3:End

B.3.3 — Assurance Subtypes & Levels

B.3.3:1 - Problem Frame

Use this when. A team must decide whether the available support is enough for a particular claim and receiving use, or what a published assurance level permits a recipient to conclude. Start with that claim, use, relevant conditions, and the warrant the conclusion needs.

A performance test, a proof and a terminology comparison answer different questions. Treating their presence as a maturity recipe can approve a poorly supported performance claim while demanding an irrelevant proof from a well-supported empirical result.

Practical gain. Choose the assurance contribution that can change the receiving judgement, and retain a sufficient qualified result without purchasing evidence merely to raise its label.

Ordinary boundary. A source locator, permission, status report or direct domain result that makes no assurance claim needs no B.3.3 classification. An ordinary assurance judgement can use B.3’s compact result without constructing a level scheme. A domain’s required proof, study or assurance profile applies when its actual claim and use require it.

B.3.3:2 - Problem

How can a recipient distinguish relevant conceptual, logical and empirical support without mistaking a link, evidence type, score or maturity label for an argument that the relied-on claim is adequately supported?

The tension is between comparable reporting and unlike assurance questions. Repeatable criteria help a shared use; a universal ladder hides differences in claim scope, consequences, assumptions and admissible evidence. Formal precision helps inspect an inference, but cannot compensate for an inapplicable premise.

B.3.3:3 - Solution

Use B.3 to identify the target claim and receiving assurance use. Determine which uncertainty or possible failure matters to that use, then examine the support that bears on it. State the supported or narrowed conclusion and the limitations that change reliance. A result need not carry an AssuranceLevel.

B.3.3:3.1 - Assurance subtypes answer different questions

Select the contributions needed by the claim, rather than demanding all three types for every judgement. A mathematical consequence may need a proof and no field trial. An engineering performance claim may have sufficient empirical support without an additional formal proof. A safety-related claim needs the actual protective argument and required evidence; neither FV ≥ threshold nor EV > 0 establishes that adequacy by itself.

Terms such as FV, EV or CL can be used only with the bearer, scale and interpretation the receiving argument consumes, as in B.3. A field called verifiedBy or validatedBy identifies a support relation to inspect, not a positive judgement by its mere presence.

B.3.3:3.2 - Use a level only through its justified profile

A domain may define an assurance profile or ordered levels when a recurring receiving decision benefits from that comparison. Its definition states the claim class and use, relevant conditions, meaning of each level, evidence rules, threshold basis and reconsideration conditions. Keep the measure and its scale explicit where a threshold is used. Establish the ordering from these meanings; the numerals in L0–L2 supply no ordering of trust across unlike uses.

Publish AssuranceLevel only with the applicable profile and a result showing why the target meets its criteria. The legacy names Unsubstantiated, Substantiated and Axiomatic do not supply default criteria. In particular, an axiomatic or constructive justification concerns a particular consequence or construction, not a universally higher assurance state than empirical support. A conjecture’s origin in abduction likewise does not assign it L0.

Examine whether a demanded threshold or evidence requirement protects the relevant quantity well enough to justify its cost, delay and displaced work. Keep that judgement distinct from the conditions presently binding the action. A recommendation to amend a requirement does not change it or confer amendment authority.

For a one-off receiving use, stop with the sufficient qualified assurance result. Do not create a profile, fill unused level fields or explain the omission of a level solely to complete this pattern.

B.3.3:3.3 - Preserve scope and inspect the actual grounding

Keep a design-time MethodDescription claim separate from a claim about performed Work or its Trace. Cite evidence with the appropriate conditions and scope. Evidence for a parent claim covers a child claim only through an argument establishing that coverage; a declaration of inheritance is insufficient.

State structural claims as readable Working-Model relations. When a publication choice or current requirement elects B.3.5’s CT2R-LOG profile, follow its relation-specific grounding: structural parthood uses the applicable C.13 sum or slice construction trace; collection belonging uses the collection’s set trace. These elected branches declare validationMode=axiomatic. Other permitted relation claims retain their applicable logical or empirical support. A level label alone does not elect this profile.

A grounding account and the author’s validationMode are inputs to inspect. Neither creates the relation, makes an empirical premise true, nor decides its currentness. Assurance publications remain downstream of the Working-Model surface under E.14.

B.3.3:3.4 - Worked case: a useful empirical result and an irrelevant fresh test

A team is deciding whether a converter can be used for non-safety-critical measurements within a declared temperature and input range. In this example, the receiving task’s justified tolerance is 2%. Calibration results covering that range, an adequate measurement-error account and applicable operating observations support error below that tolerance. The team can return “supported for this measurement use within the stated range,” with its actual limitations. A formal proof of unrelated program properties is unnecessary.

Now replace that basis with a newly passed boot test and a glossary mapping. These establish startup behaviour and the intended term correspondences, not measurement accuracy. The same requested measurement use remains unsupported. Neither fresh evidence nor one link of each required type repairs the missing performance basis.

If the recipient instead needs a mathematical invariant, inspect the proof under its assumptions. If the application introduces a protective function or a different operating range, reopen the affected assurance question under its own threshold and evidence rules. The earlier limited result remains an account of what it supported.

B.3.3:4 - Conformance Checklist

A Target of Assurance (ToA) denotes the claim being assessed for the named use, not an undifferentiated score for its whole system.

• CC-B3.3.1 (Relevant support): A positive assurance conclusion MUST identify the relied-on claim and use and explain how the cited basis supports it. A verifiedBy or validatedBy link alone is insufficient.
• CC-B3.3.2 (Needed correspondence): Where differing terms or participants can change the argument, the assessor MUST resolve the load-bearing correspondence through the applicable bridge. Other judgements have no general term-mapping prerequisite.
• CC-B3.3.3 (Qualified levels and thresholds): A published level MUST have an applicable profile, interpreted criteria and a supported assignment. Formal, empirical and constructive evidence requirements MUST follow the specific claim and receiving use. A generic score threshold or positive validation score cannot substitute for the required protective argument.
• CC-B3.3.4 (Bridge scope): A required bridge MUST cover the differences on which the conclusion depends. It SHALL NOT demand mapping every mechanism term to FPF as the price of an otherwise sufficient ordinary judgement.
• CC-B3.3.5 (Scope separation): Design-time and run-time assurance claims MUST retain their distinct subjects, evidence and conditions. A design result SHALL NOT be published as evidence that the corresponding Work performed successfully.
• CC-B3.3.6 (CT2R-LOG grounding): When B.3.5’s profile is elected, the structural and collection branches MUST retain their distinct current construction traces and declared modes. A level assignment SHALL NOT replace the required grounding or impose the profile on unrelated claims.
• CC-B3.3.7 (Downward-only dependence): Assurance publications or records SHALL NOT impose vocabulary or layout back onto the Working-Model surface.

B.3.3:5 - Common Anti-Patterns and How to Avoid Them

B.3.3:6 - Consequences

Recipients can inspect what an assurance result supports and why a stronger use remains open. Teams direct effort towards relevant gaps and can reuse genuinely covering evidence.

Comparability becomes profile-specific. Defining a useful shared profile takes judgement about consequences, criteria and evidence; routine uses avoid that overhead. Review remains fallible and contestable rather than becoming objective merely because a status is computed.

B.3.3:7 - Rationale

A claim, argument and evidence have different functions. Assurance improves when a contribution closes a relevant gap under applicable assumptions. Counting evidence types or increasing formality cannot guarantee that improvement.

B.3 supplies this claim-and-use structure and its source account. ISO/IEC/IEEE 15026-2:2022 concerns the structure and maintenance of assurance cases. This pattern adapts maintained, inspectable support to a receiving use; its subtype distinction and optional level profiles are FPF choices, not a level ladder attributed to that standard. Reconsider a local profile when its evidence model, receiving decision or threshold basis changes.

B.3.3:8 - Relations

• B.3, A.10 and C.2.1: define the assurance result, evidence-use references and target claim.
• B.5.3 and B.3.5/C.13: supply needed concept correspondence and the elected, relation-specific construction account.
• C.2.1 and E.14: keep the identified Working-Model claim distinct from its assurance publication. A.4 supplies a System design/operation comparison only when that is the actual claim being assured.
• B.3.4 and C.27.TA: qualify currentness by the relied-on use, conditions and temporal reference.
• C.11 and C.19.2: support the choice of worthwhile additional evidence when that decision is live.
• B.4 and Part D: may consume a qualified assurance result in their actual transition or decision rules; this pattern supplies neither an automatic evolution gate nor risk-acceptance authority.

B.3.3:End

B.3.4 - Can Earlier Evidence Still Support This Use? — Evidence Decay and Epistemic Debt

B.3.4:1 - Problem Frame

Use this when. An earlier result is being relied on now, and a changed condition or a due review may change whether it still supports the receiving claim. Begin with the relied-on use and the premise that may have changed.

A bridge’s earlier assessment may remain applicable to its unchanged bounded use, while a new traffic load defeats that assessment before its scheduled review. A library result can remain applicable to unchanged dependencies yet fail to address a newly discovered relevant vulnerability. The age of either report does not distinguish these cases.

Practical gain. Reconsider the affected support in time to change the decision, while retaining useful results whose relevant premises still hold.

Ordinary boundary. Do not open a new assurance procedure solely because a carrier is older. If available information already establishes applicability for the immediate use, continue on that basis without a renewal or skip-refresh certificate. A real licence deadline, calibration qualification or promised-use window remains a condition of the actual use.

B.3.4:2 - Problem

How can a team notice obsolete support without treating elapsed time as automatic loss of truth, measured risk growth or loss of every use of an evidence carrier?

Three failures matter: a changed load-bearing premise remains unnoticed; a fresh but irrelevant result creates false reassurance; or repeated checks of unchanged premises displace protective maintenance that could actually change the outcome.

B.3.4:3 - Forces

B.3.4:4 - Solution

Qualify currentness at the claim and receiving use. Reconsider only the dependency reach for which a changed premise or an applicable review rule can alter the conclusion.

B.3.4:4.1 - Locate the condition that can change reliance

Identify the earlier result being used and the relevant conditions: for example, its configuration, operating envelope, measurement qualification or dependency. Establish whether available information still supports those conditions. An unchanged file is not proof that its environment is unchanged; an older file is not proof that its support has failed.

Use time-based review when an applicable deterioration model or review policy warrants it. Use event-, dependency- or condition-based reconsideration when those define applicability. A newly discovered failure mode may reopen a result before a review date. A calendar reminder may instead find that the result remains applicable without a new experiment.

Keep three judgements distinct: whether the earlier evidence applies, whether it is sufficient for the present claim, and whether the proposed action satisfies its actual conditions. Currentness alone answers neither sufficiency nor permission.

B.3.4:4.2 - Give dates their actual meaning

A valid_until: ISO-8601-date | null field is used only when the receiving claim or applicable rule has a calendar boundary to convey. State what the date bounds. A review-due date requests reconsideration; a qualification, right or resource-use end date can terminate an allowed use. Do not merge these meanings into a global expiry of the carrier.

An absent or null date means that this field supplies no calendar boundary. It asserts neither perpetual validity nor invalidity and creates no mandatory justification for a missing date. Applicable event or condition limits still govern the use.

Where a required review period applies, follow it until it is changed by someone with the necessary authority. Evaluate its protective purpose, threshold basis and displaced cost separately when deciding whether to propose that change. Questioning the policy is not permission to ignore it.

B.3.4:4.3 - Treat epistemic debt as an optional planning indicator

A team may call its outstanding evidence-review or maintenance obligations epistemic debt (ED). If it needs a number, define the counted entities, dependency treatment, scale and unit, policy purpose, and meaning of the action threshold. An epistemic_debt_budget is then a named planning-policy limit, not a universal allowance of harm.

For example, a team may count distinct overdue review obligations to plan assessor capacity. Ten duplicate paths to one obligation do not create ten obligations. Separate obligations consuming the same source may still require different judgements for different uses.

Elapsed days can contribute to a justified priority rule or deterioration model. B.3.4 supplies no default rate, sum or automatic level downgrade. A planning count is not a probability of failure, and zero overdue reviews does not establish an adequate assurance case.

B.3.4:4.4 - Choose the feasible response to the actual change

Determine what the receiving use can support now. The following are possible responses, not a compulsory completion triad:

C.11 and C.19.2 supply the choice of worthwhile additional evidence. Rechecking available configuration or premise information need not be a new experiment. A possible experiment is not a Work commitment. If the desired check is unavailable, retain any independently warranted bounded action or limitation; do not fabricate an observation.

For an immediate unchanged use, stop with its usable result. When a later receiver needs a warning, limitation or retained reason to avoid unsupported reliance, keep that minimum content with the existing result or publication. A separate DeprecationNotice is useful when something is actually deprecated, not as proof that refresh was skipped.

B.3.4:4.5 - Follow affected dependencies and preserve real expiry

Trace a changed premise to the claims and uses that actually depend on it. Reopen those conclusions under their applicable evidence model. Shared paths do not multiply evidence or risk, and an unaffected use does not inherit a global downgrade from the carrier’s age.

Keep actual physical and institutional conditions intact. Expired calibration qualification, an unavailable configuration, ended resource support or an elapsed rights window can block the corresponding use even when the old report remains an accurate record of an earlier state. A justified deterioration model can make elapsed time material; cite that model rather than inferring universal decay.

A dashboard should distinguish a review due, a defeated premise and a restricted use. Its colour reports the declared indicator or disposition, not the truth of the underlying claim. A failing test is a potentially relevant adverse result to assess now, not merely another overdue date.

B.3.4:4.6 - Worked cases: the same age, different decisions

Bridge. An earlier structural assessment supports a specified load envelope, conditional on its stated condition and inspection regime. For an unchanged limited use, available load and condition information and satisfied required inspections can preserve that support. The assessment’s age alone adds no repeat assessment. In the paired case, proposed traffic exceeds the envelope: the earlier report does not support that use, however recent its cover date. Obtain the assessment or restriction needed for the changed load before relying on the stronger claim.

Suppose the available inspection team can either inspect a suspected load-bearing defect or repeat an already adequate check whose relevant conditions remain established. Examine the protected harm and the basis of the inspection requirement, what each result could change, and the cost of delay. Where the defect inspection can prevent that harm and the repeat adds no useful information, preserve the inspection capacity. If a currently binding repeat requirement prevents that choice, seek an authorized amendment; the resource conflict does not itself remove the requirement.

Library. The verified property of an unchanged library in its qualified configuration remains supported when the relevant assumptions and dependencies still hold. A new vulnerability affecting a dependency used by the security claim reopens that claim even before a review date. An unrelated vulnerability does not. Preserve unaffected functional results and any independently supported restricted service while addressing the security limitation. A release recipient who would otherwise assume the affected security property needs that limitation in the released result.

B.3.4:5 - Conformance Checklist

• CC-ED.1 (Use-qualified currentness): A currentness conclusion MUST identify the relied-on claim/use and the conditions or temporal boundary that change it. A carrier’s age or absent date SHALL NOT alone establish loss of support.
• CC-ED.2 (Interpreted planning measure): A numerical ED or debt budget MUST define its counted entities, dependency treatment, scale/unit, purpose and threshold meaning. No project has a default obligation to adopt one.
• CC-ED.3 (Affected reach): Reconsideration MUST follow the actual support dependencies. Any aggregation MUST use an applicable interpreted model and avoid counting duplicate paths as additional evidence or risk.
• CC-ED.4 (Qualified disposition): A trigger MUST be interpreted for the receiving use; it SHALL NOT automatically downgrade a level or require Refresh/Deprecate/Waive. Preserve a sufficient current result without a separate renewal or no-refresh certificate. Preserve real qualification, rights and resource-use expiry.
• CC-ED.5 (Actual exception authority): A waiver, when used, MUST have the authority and scope allowed by the applicable rule, a rationale, affected risk bearers and accountability, and its actual ending or reconsideration condition. Keep the auditable exception with the decision that uses it; a title or lowered assurance status does not confer risk-acceptance authority.

B.3.4:6 - Common Anti-Patterns and How to Avoid Them

B.3.4:7 - Consequences

Teams can retain applicable support and direct review towards changed premises, reducing needless repetition without losing actual maintenance obligations. Later recipients receive the warnings that change their decisions.

This requires judgement about dependency reach and review policy. An optional queue or dashboard helps allocate capacity but cannot replace that judgement. Sparse evidence about a relevant condition may leave the current use unresolved even when the carrier itself is unchanged.

B.3.4:8 - Rationale

An earlier result can remain valid for its earlier claim while no longer supporting a changed use. Conversely, elapsed time need not defeat an unchanged premise. Maintenance therefore follows the assurance argument and its conditions rather than a universal entropy metaphor.

B.3’s source account and ISO/IEC/IEEE 15026-2:2022 place maintenance with assurance cases. C.27.TA supplies the use-relative temporal qualification. This pattern adapts those distinctions to continued reliance and planning; it attributes no universal decay equation or mandatory expiry date to the standard. A validated domain deterioration model or an applicable review rule can justify a particular time-based policy and its reconsideration conditions.

B.3.4:9 - Relations

• B.3 and B.3.3: define the assurance claim, receiving use and any justified local level profile.
• A.10 and C.27.TA: supply evidence-use dependencies and qualified temporal claims.
• G.11: schedules justified reconsideration or refresh over the affected dependency slice and conveys needed limitations to later recipients.
• C.11 and C.19.2: support the choice of obtainable evidence work when its contribution can change the decision.
• B.4: uses actual transition conditions; a debt indicator does not constitute its evolution gate.
• Part D and applicable domain rules: govern protected interests, authority and exceptions; an assurance status change does not decide them.

B.3.4:End

B.3.5 - Assurance Grounding for Working-Model Relation Claims (CT2R-LOG)

Status: Stable Type: Pattern

At a glance. Use B.3.5 when a human-facing structural relation or a collection’s own belongs-to relation has been selected for an additional assurance account without exposing constructive machinery as the public vocabulary.

Use this when. Use this assurance profile only when a publication choice or named current requirement elects it for a direct relation claim. State the readable relation first. After election, structural parthood and collection belonging follow separate trace and validationMode obligations. The trace reports independently grounded facts for inspection; it creates neither the relation occurrence nor the entity it describes.

What goes wrong if missed. The readable relation and its assurance account collapse: authors either lose usable relation sentences, treat collection belonging as parthood, prohibit separately grounded parthood by label, or make a trace look like the cause of the claim.

What this buys. Working-Model relations stay readable, while an elected assurance branch supplies the right inspectable account without changing the direct relation kind.

Not this pattern when. Not this pattern when a direct relation claim is sufficient and no publication choice or current requirement elects this assurance profile. Also not this pattern when the current question is how to construct the trace (C.13), which mereology relation kind is intended (A.14), whether a whole must be reidentified (B.2), or whether a candidate name deserves durable U-kindhood (E.24.UK).

One‑line summary. CT2R-LOG keeps ComponentOf, ordinary belongs-to sentences, PortionOf, and AspectOf readable while respecting their different relation kinds. When this assurance profile is elected, structural parthood uses its applicable construction account; collection belonging uses a current C.13 set trace. Neither branch changes what makes the direct relation obtain, and neither trace decides whether a separate part relation is possible.

B.3.5:1 - Intent

Provide a single, human-facing family of Working-Model relations as the public relation layer, with explicit hooks for (G) grounding and (R) reliability, without exposing constructor jargon or overloading day-to-day authors.

What you get (manager/engineer view). The same relations you already know (e.g., ComponentOf) remain the public relation vocabulary.

What changes when the profile is elected (auditor/ontologist view).

• Each covered published edge carries two additional commitments:

  1. tv:groundedBy → points to the support required by the relation’s branch: the applicable sum or slice trace for structural parthood, one current C.13 set trace for the collection’s belongs-to relation, or an admissible argument or evidence object for another permitted claim.
  2. validationMode ∈ {axiomatic, inferential, postulate} → declares how the author justifies the assertion.

The pattern that defines the relation still decides when it obtains. CT2R-LOG records the public alias, the branch-specific support link, and the declared assurance posture; Lang-CHR supplies the labels.

B.3.5:2 - Problem Frame

B.3.5 exists where a readable Working-Model relation must remain usable by practitioners while assurance readers still need a grounding relation and declared validation stance. The EntityOfConcern is not a notation, trace file, or tool output. It is the relation-use discipline that keeps the public relation layer and assurance grounding layer distinct.

B.3.5:3 - Problem

Working-Model relations such as ComponentOf and an ordinary belongs-to sentence are easy to use but not self-justifying. Their declarations alone do not show which participants and occurrences obtain, which rule defines the relation, or what identifies the whole or collection. Conversely, exposing construction traces everywhere makes the graph unreadable to non-specialists.

We need: a stable public relation layer for relations and, where this profile is elected, a required, reconstructible grounding channel plus a visible validation intent that downstream assurance can reason about. The direct relation layer does not depend on electing the profile.

B.3.5:3.1 - Forces

• Two audiences, one dial. Project managers want one relation family and stable views; assurance readers want an inspectable construction account with explicit direct facts and identity conditions.
• Parsimony constraint. The Kernel stays minimal; construction is outside the Kernel.
• Unification inside FPF. We already unify external vocabularies; the same discipline is applied internally so patterns that publish structural claims can reuse one three-form construction-account discipline and one readable relation façade without making that account a second ontology.

B.3.5:4 - Solution (thumbnail)

CT2R‑LOG introduces a two‑link discipline and a validation flag around each canonical edge:

1. Alias link (concept‑level). Working-Model relations (e.g., ut:ComponentOf) are the public names for their exact direct relation principles. tv:AliasOf may point from the public relation kind to that principle for comparison and reuse; the alias defines neither an occurrence nor a whole.

2. Grounding link (assurance level). Each relation assertion covered by this elected profile carries tv:groundedBy according to its direct relation kind:

   • Structural parthood (ComponentOf, PortionOf, or AspectOf) requires one current C.2.1 construction-trace episteme in the applicable sum or slice form and validationMode=axiomatic. postulate is not available for this branch.
   • Collection belonging under the collection’s own rule requires one current C.2.1 C.13 set trace and validationMode=axiomatic. The trace reports the collection, the entity, the already established relation, the rule for belonging, and the identity conditions. It does not make the entity a constructive part, make belonging obtain, or prove that separately grounded parthood is impossible.
   • Other epistemic or constitutive edges may use an admissible evidence object or logical argument under validationMode ∈ {inferential, postulate} when no constructive trace is appropriate.

3. Validation flag (author intent). Every relation or aggregation rule covered by this profile carries tv:validationMode with one of:

   • postulate — pragmatic working claim backed by observations;
   • inferential — reasoned consequence with a followable argument; or
   • axiomatic — one inspectable construction account is the declared assurance basis.

The direct branch above selects which modes and grounding targets are allowed. The flag is an assurance posture, not a species of world-side relation and not an identity or timelessness guarantee.

F–G–R alignment. F (the published relation claim): :PumpA ut:ComponentOf :Skid12. G (its inspectable grounding account): the assertion links to :trace_Γm_sum_456, a C.2.1 episteme about the exact direct construction facts. Assurance posture: tv:validationMode=axiomatic is the author’s declaration. B.3.3 assesses the actual grounding for the receiving claim and use; a level is published only through an applicable justified profile. The declaration does not alter formality or establish empirical adequacy.

B.3.5:4.1 - Structural CT2R Typing-Grounding Unfolding Structure Block

When a constructive trace, working-model relation, and target kind or logical representation must be carried together across contexts, use this block or cite an equivalent A.22.CGUS specialization. The block is useful when the reader must see the passage from constructional material to a typed or logical claim without treating a readable relation label as proof.

StructuralCT2RTypingGroundingUnfoldingStructureBlock:
  unfoldingStructureRef: exact independently selected A.22 structure, when needed
  workingModelOrConstructiveRepresentationRef:
  targetKindOrLogicalRepresentationRef:
  bridgeRef?:
  constructiveTraceRef?:
  preservedStructure:
  lostOrCollapsedStructure:
  CL_or_CLk?:
  admissibleReuse:
  blockedSubstitution:
  evidenceOrProofLinkageRef?:

unfoldingStructureRef names an independently selected A.22 structure; this block is a record describing its use. Recover the exact constituents, obtaining relations, applied constraints and named selection/use frame. StructuralCT2RTypingGroundingUnfoldingStructure is a local designator for the selected structure used to inspect this construction-to-typed/logical projection. Any A.22.CGUS qualification is tested separately under its potential-continuation rule; a local name or record does not establish it. C.13 supplies constructive-trace content and C.3 the kind intent, extent and subkind content actually used. The record creates no proof, empirical evidence, Work plan or decision.

When an inadequate working account requires general diagnostic recovery of the exact subject construction, use A.7.1. That return may stop at a direct relation, system-role assignment, state or capability, Work occurrence, holon recognition, or the pattern for another subject without opening this structural CT2R specialization.

workingModelOrConstructiveRepresentationRef names the relation, trace, model, or representation being carried. targetKindOrLogicalRepresentationRef names the typed or logical target. bridgeRef is required when this use actually claims or consumes an obtaining semantic Bridge under F.9 or a kind correspondence under C.3.3. CL_or_CLk is required when the consumed assurance/calibration account requires that value. Entity, scheme, plane or notation changes alone establish no crossing; a same-sense unit conversion requires neither invented endpoints nor a Bridge. CL does not by itself authorize use. preservedStructure and lostOrCollapsedStructure state what survives the passage and what the published relation no longer carries. Evidence linkage remains with B.3 evidence and assurance subject patterns; proof linkage remains with the proof or mathematical subject pattern that is current. The unfolding block only makes the structure of the passage inspectable.

B.3.5:5 - Vocabulary & notation (normative)

• Working-Model relations (front‑stage). ut:ComponentOf, ut:PortionOf, and ut:AspectOf are publication-grade structural relations under their direct A.14 rules. A collection uses the belongs-to predicate defined by the pattern for that collection; FPF has no public generic ut:MemberOf relation. Belonging is not a sub-property of ut:PartOf, ut:StructPartOf, or ut:EpiPartOf, but the same entities may separately stand in a constructive part relation when its own rule and all six A.1 matters pass.

• Alias principle (lexical). tv:AliasOf links a public relation type to the exact direct relation principle whose reading it carries (for example, ComponentOf points to the direct structural-component principle). The alias supports comparison; it neither defines an occurrence nor says that a sum expression produced the relation.

• Grounding (per‑edge). When this profile is elected for structural parthood, tv:groundedBy points to the applicable current C.2.1 construction trace and validationMode=axiomatic. When elected for collection belonging, it points to one current C.13 set trace under the collection’s own rule and also uses validationMode=axiomatic. Other epistemic or constitutive claims may use a logical argument or evidence object under their permitted mode. Every target supports replay of the assertion’s basis; it creates neither the direct occurrence nor entity identity.

• Trace family. Γ_m.sum, Γ_m.set, and Γ_m.slice are the C.13 forms used by the covered branches. sum and slice report structural-parthood constructions; set reports an already grounded collection and the belongs-to occurrences established under its own rule. No form creates the facts it reports, and no temporal or workflow form is added.

• Validation flag. tv:validationMode ∈ {postulate, inferential, axiomatic} is required on every claim covered by this elected profile. Structural parthood and collection belonging use axiomatic with their branch-specific current trace. A direct relation outside the profile has no B.3.5 field obligation.

B.3.5:6 - Archetypal Grounding - Running example

Story. A refinery team publishes :PumpA ut:ComponentOf :Skid12.

• Publication — Working-Model relation layer. They publish one assertion using the Working-Model relation ComponentOf and declare its U.Formality (typically F≈F3, controlled narrative). Only the Working-Model relation is visible to readers.

• Constructive grounding (Γₘ). In the background, the published assertion links to :trace_Γₘ_sum_456, a C.2.1 episteme that names the exact pump and skid, the direct fastening, coupling, enclosure, terminal, flange, and seal occurrences that obtain, the applicable skid assembly rule, and the skid reidentification rule. An auditor replays that account to inspect the assertion’s basis. The same listed parts under a different assembly can form another whole, while a permitted pump replacement can preserve Skid12; the direct relations and reidentification rule, not the trace or input list, decide.

• Assurance stance & R-lane. Because the assertion is linked to the construction account required by its elected branch, authors set tv:validationMode=axiomatic. The account makes the relation’s basis inspectable; the declaration does not strengthen that relation, fix identity or make it timeless. B.3.3 considers the actual grounding and its currentness for the receiving claim and use.

• Contrast (epistemic). When the same team asserts :MassFlowRepresentation RepresentationOf :FlowModel, they declare validationMode=postulate and attach a calibration dataset instead of a Γₘ trace. Judge that empirical basis for the claimed representation and receiving use; the declared mode alone does not establish lower confidence. Under B.3.4, a changed configuration, calibration qualification or other relevant premise can reopen the claim. The dataset’s age alone does not defeat still-applicable support.

Result: one visible relation for engineers, a grounding reference and a validation-mode declaration for reviewers.

Collection case — Fleet North. First publish the ordinary sentence: “Vehicle 12 belongs to Fleet North under its registration rule.” Under that rule, the occurrence begins when Fleet North accepts the vehicle’s registration, ends on withdrawal or transfer, and a later accepted registration begins another occurrence. If no current publication choice or requirement elects this profile, the direct sentence is sufficient and the author stops.

Here the fleet publication elects the profile. It links the assertion to one current C.13 Γ_m.set trace that names Fleet North and its identity rule, Vehicle 12, the obtaining registration occurrence, the registration rule, and its ending and recurrence conditions; it declares validationMode=axiomatic. If a vehicle enters or leaves the fleet, or the rule changes, the earlier trace remains an account of its earlier state but is not current support for the later assertion. The register and trace report the relation; neither creates it. They prove neither ComponentOf nor that a separately grounded constructive part relation is impossible.

B.3.5:7 - Author Standard (at a glance)

When you add or import a relation edge:

1. Pick a Working-Model relation sentence such as “Impeller ComponentOf Pump” or “Vehicle 12 belongs to Fleet North under its registration rule”; avoid raw ut:PartOf unless you are drafting meta-level axioms. If no current publication choice or requirement elects CT2R-LOG, publish that direct claim and stop.

2. When CT2R-LOG is elected, attach tv:groundedBy:

   • Structural parthood → the applicable current construction trace and validationMode=axiomatic.
   • Collection belonging under the collection’s own rule → one current C.13 set trace and validationMode=axiomatic.
   • Another permitted epistemic or constitutive claim → the branch’s logical argument or evidence object and allowed mode.

3. Declare the selected tv:validationMode for every covered claim.

What managers see: nothing new in the graph picture. What auditors get: a reliable trail from every edge covered by the elected profile back to its inspectable construction or evidence account.

B.3.5:8 - Compatibility & cross‑references

• B.3 and the direct proof or mathematical pattern. CT2R-LOG makes the relied-on construction or support account inspectable; B.3 judges its contribution to the current assurance claim. State the actual logic and proof basis when a formal conclusion is used.
• B.3.3 (Assurance subtypes and levels). The declared validationMode and actual tv:groundedBy account contribute only what they establish for the receiving assurance claim. They do not compute a universal L0–L2 progression; a published level requires an applicable justified profile.
• B.3.4 (Evidence ageing and currentness). A relation assertion, its construction-trace episteme, and the warrants or evidence used for it retain their own editions and currentness. validationMode=axiomatic does not freeze a trace or make described world-side facts timeless; changed participants, relations, rules, or identity conditions require direct reinspection.

B.3.5:9 - Rule‑set — CT2R‑LOG (conceptual, human‑first)

Intent (one line). Make Working-Model relations the canonical relation vocabulary for authors, while providing a clean, purpose-selected bridge to assurance through aliasing and grounding semantics; the bridge is required only for the published assertions covered by an elected B.3.5 profile or named current requirement.

B.3.5:9.1 - Vocabulary and meanings in this pattern

• Working-Model relation. A human-oriented direct relation statement using a public name such as ut:ComponentOf, ut:PortionOf, or ut:AspectOf, or an ordinary sentence such as “this edition belongs to this product series.” It is the canonical public layer for readers; the direct pattern keeps the relation meaning fixed.

• Assurance Layer. Three complementary grounding modes an author MAY attach:

  • Constructive grounding: an inspectable account in one of the three C.13 forms (Γ_m.sum | Γ_m.set | Γ_m.slice). It names independently grounded participants, direct relation occurrences, the applicable construction rule, and identity or reidentification conditions. No formal notation is required, and the account does not create the relation it reports.
  • Logical grounding: a reasoned chain (think KD‑CAL style arguments) that shows why the relation follows from stated premises.
  • Mapping grounding: a relation-label alignment that shows the domain label truly denotes the intended Working-Model relation (Kind-CAL / Lang-CHR stance). These three grounding modes are complementary, not exclusive.

• Empirical Validation. How a published relation meets reality (observations, calibration scenarios). It lives beside, not inside, the relation. (See B.3 family.)

• Grounding vocabulary (tv:).

  • tv:AliasOf — declares that a Working‑Model relation is the canonical projection of a more general pattern (its “principle of use”).
  • tv:groundedBy — points to the author’s grounding account (Constructive, Logical, or Mapping, as applicable). When a construction trace is recorded, it is a C.2.1 episteme with its own edition and currentness. The tv: namespace is part of the Core conceptual lexicon; it is notation‑agnostic and tool‑agnostic.

• tv:validationMode ∈ {postulate, inferential, axiomatic}. A declaration by the author of the confidence stance for a relation instance: postulate — a pragmatic working claim; inferential — a reasoned consequence; axiomatic — the author declares that a constructive account is the assurance basis for this assertion. The mode does not classify the world-side relation and guarantees neither identity nor timelessness.

Authoring note. This pattern defines meanings, not formats. The words above SHALL be used consistently and without reference to any specific notations or execution environments (Guard‑Rails: Notational Independence).

B.3.5:9.2 - Normative rules (MUST/SHALL clauses for thinking‑and‑writing)

S‑1 (Working-Model first). Authors SHALL state each covered direct relation claim in Working-Model form. Assurance accounts remain below that public layer. Electing this profile adds branch-specific trace and mode obligations; it is not a precondition for direct use.

S‑2 (Alias declaration). If a Working‑Model relation follows a known general principle, the author SHOULD declare tv:AliasOf <Principle>, thereby making the intended use‑pattern explicit for reviewers and future readers. (This improves comparability without introducing extra formality.)

S‑3 (Grounding by mode). For every relation instance covered by an elected B.3.5 profile, the author MUST set validationMode and follow the corresponding grounding stance:

• S‑3.a postulate. For a branch that permits it, the author may omit constructive grounding, state the working scope, and give the empirical cues that would challenge the claim.

• S‑3.b inferential. For a branch that permits it, the author gives a short reasoned chain from admitted statements that a peer can follow.

• S‑3.c axiomatic. The author links the assertion to the current C.2.1 trace episteme required by its branch. A competent peer can recover the exact participants, direct relation occurrence, applicable rule, and identity or reidentification conditions. The account supports inspection; it creates none of those facts.

• S‑3.d Structural parthood. A covered ComponentOf, PortionOf, or AspectOf assertion requires validationMode=axiomatic and the applicable current C.13 construction account; postulate is not available.

• S‑3.e Collection belonging. A covered belongs-to assertion uses the rule defined for that collection and requires validationMode=axiomatic and one current C.13 set trace. The trace reports already established belonging and collection identity. A logical argument or evidence object may support the inclusion decision separately, but neither substitutes for the elected set trace, turns belonging into parthood, or prohibits a separately grounded part claim.

S-4 (Relation-kind sense-making).

• For structural ComponentOf, PortionOf, and AspectOf claims, the elected profile requires the applicable current construction account and validationMode=axiomatic.

• For collection belonging, the elected profile requires one current C.13 set trace and validationMode=axiomatic. The collection’s own rule still decides whether the occurrence obtains.

• For other epistemic or constitutive links, constructive grounding remains optional and the branch may prefer inferential or postulate reasoning with empirical cues.

S‑5 (Order and time do not establish parthood). Execution order, parallelism or interval inclusion alone SHALL NOT establish a part-whole relation. State Method composition under B.1.5 and temporal facts under C.27; use B.1.4 when those recovered relations must be aggregated. Independently established A.15.1 Work-part relations and A.14 proper-phase relations for unchanged non-Work carriers remain admissible under their own rules.

S‑6 (Unidirectional dependence). CT2R‑LOG may consume Compose‑CAL and KD‑CAL conceptually; it SHALL NOT redefine them. Meaning flows downward only (Kernel → Extension → Context → Instance).

S‑7 (Register discipline). When naming principles in tv:AliasOf, authors SHOULD use Tech/Plain twin labels where available and obey minimal‑generality and rewrite rules (LEX‑BUNDLE), so that aliases are recognisable across contexts of meaning.

S‑8 (No tool talk). Core prose MUST NOT introduce CI/CD terms, file formats, APIs, or machine‑oriented notations in place of concepts. If examples are needed, they MAY be plain‑language narratives or domain vignettes. (This pattern is conceptual by Standard.)

B.3.5:9.3 - Scope & Non‑Goals (to keep the plane clean)

• In scope. Canonical publication of relations for humans; alias‑to‑principle clarity; conceptual grounding stories; author‑declared validationMode; separation of structure vs order/time.

• Out of scope. Any machinery that executes checks; any binding to specific notations; any process/workflow mechanics; any discussion of file formats. (Those belong to tooling publications, pedagogy publications, and companion records; they SHALL NOT be imported by the Conceptual Core.)

• Edge placements. When a claim is chiefly about naming fit across Contexts, prefer Mapping grounding (Kind-CAL/Lang‑CHR stance). When it is chiefly about why it follows, prefer Logical grounding. When it is about what the whole is, from its parts, prefer Constructive grounding. (Authors MAY combine them.)

B.3.5:9.4 - Author’s working moves (micro‑playbook, notation‑free)

M‑1. State the relation in Working‑Model form (e.g., “Impeller ComponentOf Pump”). M‑2. If a publication choice or named current requirement elects this profile, pick validationMode; otherwise keep the direct relation claim and stop:

• For a permitted exploratory claim, choose postulate and state scope plus challenge cues.
• For a permitted conclusion from known statements, choose inferential and list the short argument.
• For structural parthood covered by the profile, choose axiomatic and link the applicable current construction account.
• For collection belonging covered by the profile, choose axiomatic and link one current C.13 set trace that reports the already established relation under the collection’s own rule.

M‑3. Add tv:AliasOf only when a named direct relation principle helps reviewers recognize the intended reading; do not alias the relation to a constructor result. M‑4. If assembly uses two parallel lines, state the actual Method/Work and temporal facts. Add any independently obtaining part relation under its own rule; parallelism alone does not establish it. M‑5. Stop when the selected readable relation and remaining non-use boundary are clear and, if this profile is elected, its validation mode and required current support are recoverable without guessing.

B.3.5:10 - Bias-Annotation (auditable, human-first)

The purpose of this section is to make typical cognitive slips visible and name the counter-moves an author or assurance reader should apply in thought—not with tools. These biases are generic; the remedies point to neighboring FPF guard-rails and patterns.