Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-22 12:18:55 UTC · snapshot created 2026-11-22 12:19:56 UTC · last check 2026-11-22 12:30:20 UTC

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 marked 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, research paper, or collection is discussed as a whole;
  • a dashboard rolls part measurements into a whole-level characteristic;
  • a team calls a role arrangement, method structure, or graph a decomposition, and its part-whole meaning is unclear;
  • 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. Start with the decision the recipient must make and the evidence already available about its subject. An accepted measurement of the identified whole can settle a question about its value. When the inference depends on constituents or their arrangement, identify whether the claim concerns part-whole construction, collection belonging under its own rule, or collection-as-whole grounding. For other meanings of composition, use the distinctions and supplying patterns in B.1:4.2. If claim-bearing source wording still says only “role,” use E.10.ROLE before choosing a branch.

What goes wrong if missed. Composition vocabulary and notation can conceal different relations. A role or Method may then be mistaken for a part, a Method structure for evidence of performed Work, a graph for the represented structure, or a collection for an acting whole.

What this buys. Use B.1 to identify a proposed whole and the relations and construction rule that ground a whole-level claim. Sections B.1:4.1–B.1:4.5 connect the required relations, evidence, and representations to their supplying patterns.

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 a publication choice or named current requirement elects the Working-Model assurance profile for the relation claim, use B.3.5.
  • If the question is a relation among local system-role kinds, use A.2.7; if it is classification, assignment, or a 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 separate mathematical representation-choice, transfer or reliance question remains unresolved.
  • 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

A claim about how a whole is constituted or what follows from that constitution needs the relevant part or collection relations. An observation or law applying to the identified whole can answer a question about its characteristic directly. Mathematical and computational representations can express or check a constitution once their correspondence with it is established.

B.1:2 - Problem

When these distinctions are missed:

  1. Mereology and notation collapse. A graph or algebra is treated as the part-whole structure itself.
  2. Decomposition by label. A parameter, guard or entry in a procedure is counted as a constituent Method. A Method can itself have constituent Methods when their contributions realize its purpose or maintain its required condition under their rule of combination.
  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

ForceTension
Part-whole usefulness vs ontology explosionFPF needs whole-level reasoning without minting a U-kind for every composed expression.
Constructional grounding vs math convenienceAlgebra and graphs can make checks precise, but only after the ontology-side object and relation are selected.
Collection value vs false collective agencyCollections can have useful whole-level characteristics without becoming acting systems.
Method planning vs performed workA method can guide expected decomposition; work occurrence parts require occurrence identity, timing, and evidence.
Emergence recognition vs ordinary repairSome whole-level gains require B.2; many are explained inside the existing whole by ordinary part, method, measurement, or architecture repair.

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.Entity
  candidatePartRefs:
  aggregationPolicyRef?
  claimScopeRef?: U.ClaimScope
  qualificationWindowRef?
  identityOrRecognitionRule:
  partRelationRefs:
  constructionBasisRef?
  selectedStructureRef?
  wholeLevelCharacteristicRefs?
  assuranceGroundingRef?
  neighboringNonPartRelationRefs?
  mathLensOrRepresentationRef?

This claim frame identifies the objects, relations, and qualifications needed to rely on the aggregation claim. Include optional fields when they change that claim or its use.

When the arrangement is yours to find, start with what could change the answer. Hold a constituent fixed and change where or how the whole uses it. Hold the reported whole result fixed and change how the constituents produced it. Follow a part or enclosing whole as far as one of those changes affects the requested decision or its grounds. Choose that extent separately for the system, Method, Work or episteme involved. Connect them through the actual relation the answer uses, such as a Work enacting a Method or a record about that Work. At each relevant scale, consider any admissible arrangements the proposed model treats alike. Recover a missing difference if they require different answers. An established rule that covers the remaining possibilities gives a stopping point.

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 through its sum, set or slice accounts;
  • B.3.5 when a publication choice or named current requirement elects its assurance profile for the relation claim;
  • 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 - Distinguish part-whole claims from other claims

Source claimOntology-side recoverySubject pattern
“This object is made of these parts.”Identify the candidate whole and constituents and establish the part relations and construction rule. When holonhood is claimed, apply all six A.1 components and the kind-specific conditions.A.1 for holon recognition, A.14, C.13; B.3.5 when a publication choice or named current requirement elects its assurance profile.
“These items belong to this collection.”The collection’s own belongs-to rule or collection-as-whole grounding; no ComponentOf inference.A.14, C.13, C.16 for a collection-level or whole-level characteristic.
“This role is combined from role factors.”Unresolved source wording. It may mean a relation among local system-role kinds, a classification or assignment, a participation relation, a naming question, or ordinary prose; none is holonic parthood by default.E.10.ROLE first; then A.2.7 only for the relation among local system-role kinds, or the pattern for the recovered classification, assignment, participation, or naming claim; use C.29 when a separate mathematical representation-choice, transfer or reliance question remains unresolved.
“This method has steps, parameters, guards, or variants.”Method relation structure, method family, method description, or work plan; not performed work by default.A.3.1 for Method identity and B.1.5 for composition. Use B.1.5.CM to construct a composite Method and C.29 when a mathematical representation-choice, transfer or reliance question remains.
“This run contained episodes or concurrent sub-runs.”Work occurrence holarchy with timing, evidence, occurrence identity, and work-part relation.A.15.1, temporal pattern, evidence-use pattern.
“This graph or algebraic notation represents the structure.”Mathematical or representation description of a selected structure.A.22 and the applicable architecture or description pattern; C.29 when a separate mathematical representation-choice, transfer or reliance question remains unresolved.
“The whole shows emergence.”Check applicable explanations within the existing whole first. Use B.2 when changed facts leave a consequential question about whether that whole remains sufficient or a new whole is required.B.2, B.2.P, or the characteristic, measurement, architecture, capability, or Work pattern.

B.1:4.3 - Work Occurrence Holarchy

A Method’s composition and the parts of a performed Work require different grounds.

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 relation and composition rule for those effects. Neither kind of calculation establishes Work parthood or makes a Method or role expression a holonic part.

B.1:4.4 - Use mathematical and other representations

Before using Γ notation or another aggregation representation, name the object and selected relation.

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.

Infer across the composition scales the question needs. Name the whole, the characteristic under investigation and the constituent conditions on which the answer depends. For an existing whole, use its established constitution. For a proposed assembly, identify the parts, their intended arrangement and the conditions stipulated in the design. Report the consequence as conditional until evidence of realization warrants an actual-system claim. For a system this can be an interaction between components. For an episteme, B.1.3 traces a joint conclusion to the claims, meanings and sources being combined. For a method, B.1.5 identifies which Methods are constituents, what they contribute and under which conditions their organization can achieve the intended result or maintain a required condition. One constituent may supply a result to the next. Several may jointly satisfy a requirement without a prescribed order. For an occurrence of work, A.15.1 and B.1.5.EW distinguish its actual constituent work from work elsewhere that supplies a result. C.20 identifies what joins reusable practice and knowledge in one discipline.

State the relation that carries the inference across the two scales. For a straightforward forward calculation, apply the established rule to the known values. For a sensitivity question, vary a consequential condition and check whether the whole can behave as before and whether it retains its identity. For an inverse question, the observed whole constrains which constituent configurations could account for it. For a design allocation question, the prescribed whole constrains the permitted designs. A mass budget leaves several allocations open until the designer chooses one. Across several scales, ground the composition on which the conclusion depends. A law covering the full range can carry the inference in one step. When the conclusion depends on an intermediate arrangement, establish what that arrangement contributes. Swapping the masses of two parts can preserve their total mass while changing their load distribution. A capability that arises from organized interaction needs grounds in that interaction. When you assert an actual encompassing whole, identify its obtaining part relation. A.1:4.2 gives the separate constructive test for possible participation in a larger assembly. A model of the complete assembly can be more or less abstract for the same question. Compare the feasible answers that each model admits under the same interpretation. Under B.5.MR a strict refinement preserves the earlier requirements, admits at least one answer and excludes at least one previously admitted answer. If models answer different questions, explain how their results fit together for the receiving use, such as the mass distribution of this skid and the loads its particular supports can carry.

B.1:4.5 - Consider explanations within the existing whole

To assess whether changed facts require a different whole for the receiving use, first consider applicable explanations within the existing whole, such as:

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

If a supported explanation is sufficient for the receiving use, keep the existing whole and stop. Use B.2 when changed facts leave a consequential question about whether that whole remains sufficient or a new whole is required; retain an unresolved comparison when its deciding grounds are missing.

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. A drawn graph represents the selected dependencies or other structure of the skid.

For dispatch under a specified mass limit for the assembled skid, its certified gross mass can settle that condition. A certified load or applicable bound for each lifting point can settle a question about those loads. To derive them from the assembly, account for the mass distribution, supports and loading conditions. Moving a pump can preserve gross mass while changing those loads. If the assignment is to design a lifting assessment for a range of layouts, start from the permitted support arrangements and required decisions, then choose the measurements or bounds that distinguish the consequential layouts.

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, running review tool, 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 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 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.

Use B.1.5 to establish Method composition. If the recipient needs to develop the composition from an intended use, B.1.5.CM explains how to choose the contributions and organize them. Use C.29 when a separate mathematical representation-choice, transfer or reliance question remains unresolved. If the current claim is the run, use A.15.1.

B.1:6 - Bias-Annotation

Bias riskFailureMitigation
Apparatus as ontologyA user infers the object kind from the form of a graph or other representation.Recover the holon, relation, selected structure, and mathematical-lens use separately.
Decomposition as parthoodSource “role” factors, method steps, phases, or work episodes are treated as holonic parts by label.Use E.10.ROLE when the role wording is unresolved, then the pattern for the recovered relation; use the Method, temporal, Work, or part-whole pattern for the other claims.
Collection as acting wholeA set, list, batch, fleet, or community receives agency or responsibility by plural naming.Recover who or what belongs under the collection’s own rule and the collection account, or admit the collective System under A.1. State responsibility separately by naming its predicate, participants, applicability, and occurrence identity; if no pattern or rule defines the needed claim, return that gap.
Emergence rhetoric“More than the sum” replaces existing-whole explanation.Check applicable existing-whole explanations; use B.2 only for a consequential question that remains about keeping or reidentifying that whole.

B.1:7 - Conformance Checklist

CheckRequirement
CC-B1-1The result answers the receiving question at its required scope. When choosing the composition or its model is part of the commission, the account explains which distinctions can change that answer and how the selected relations support it. The current claim identifies whether it is part-whole, collection belonging under the collection’s own rule, collection-as-whole, a relation among local system-role kinds, classification, assignment, participation, method relation, work occurrence holarchy, selected structure, or mathematical description; unresolved claim-bearing “role” wording is sent through E.10.ROLE.
CC-B1-2Part-whole claims name the whole and part participants, identity or recognition rule, part relation, constructional predicate and its defining pattern, plus any aggregation policy, selected structure, ClaimScope, or qualification window that changes the claim.
CC-B1-3A.14 defines the relation vocabulary used here; C.13 defines the construction accounts.
CC-B1-4Relations among local system-role kinds, classifications, assignments, participation relations, and Method relation structures are not treated as holonic parts merely because a label, graph, algebra, or naming convention composes them. A.2.7 is used only for the first of those branches.
CC-B1-5Performed work occurrence parts require A.15.1.
CC-B1-6Mathematical and representation apparatus is named as lens or expression, not as ontology by spelling.
CC-B1-7B.2 is selected when changed facts leave a consequential existing-whole versus new-whole question. A sufficient existing-whole explanation ends that inquiry; missing deciding grounds leave the comparison unresolved.

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

Anti-patternSymptomRepair
Gamma as head ontologyΓ is treated as the thing that makes all wholes.Recover the ontology-side claim first; use Γ only as constructional or mathematical apparatus when selected.
Graph as structureA diagram or graph is treated as the part-whole structure.Name the selected structure and relation pattern; keep the graph as representation or math lens.
Method as workA method decomposition is used as evidence that work occurred.Use A.15.1 for performed-work occurrence and evidence.
Collection as acting wholeA list or pool decides, acts, or bears responsibility.Recover who or what belongs under the collection’s own rule or its collection-as-whole account, or admit the collective System under A.1. A system-role kind, assignment, Method, or Work does not establish responsibility; name the predicate and the pattern or rule that defines it, or state that this is missing.
Emergence by narrative“More than the sum” replaces existing-whole analysis.Check applicable existing-whole explanations; stop when sufficient for the receiving use, or use B.2 for the consequential whole-identity question that remains.

B.1:9 - Consequences

Positive consequences:

  • Users can combine aggregation notation with an independently grounded account of the objects and relations.
  • Part-whole claims expose their objects, relations, and construction grounds for review.
  • Role, Method, Work, mathematical-lens, and publication descriptions remain distinguishable from part-whole claims.
  • Whole reidentification has an entry condition for B.2.

Costs:

  • Users must identify the claim kind before choosing a notation.
  • Further grounds depend on the claim: work occurrence evidence uses A.15.1; work-resource aggregation uses B.1.6; an unresolved mathematical representation-choice, transfer or reliance question uses C.29. Use B.2.P for unresolved emergence-family wording and B.2 when changed facts leave a consequential existing-whole versus new-whole question.

B.1:10 - Rationale

An inference from constituents to a whole relies on accepted part-whole relations, constructional grounding, and the applicable subject patterns. This supports reasoning across different kinds of objects while retaining their own admission and relation rules.

Mathematical apparatus remains available. Once the object is known, a graph can represent dependencies, an algebra can express selected composition rules, a tuple can express a slot relation, and a matrix or embedding can support analysis. Use C.29 when a separate mathematical representation-choice, transfer or reliance question remains unresolved.

B.1:11 - SoTA-Echoing

For the question “does a collection-level calculation warrant treating the collection as a holon?”, B.1 uses A.1:4.2’s recognition criterion, A.14:4’s distinction between belonging and parthood, and C.13:4.1’s construction accounts. A collection account and a holon account support different claims; use the lighter account when it supplies the receiving result.

The corpus in B.1:5.2 makes the comparison concrete. Its coverage or diversity can be assessed under the collection’s inclusion and characteristic rules while constructive part relations and assembly remain unestablished. Those same collection facts remain insufficient for a holon claim under A.1, even if the aggregate value is correct. B.1:4.1–4.2 therefore preserve the collection result and require the six constructive components and kind-specific conditions for the stronger holon claim. In the pump-skid case, independently grounded component relations and assembly supply the corresponding part-whole basis.

This conceptual comparison settles which account these FPF claims require and states the additional construction and recognition burden for a holon claim. It does not rank external ontology or engineering methods. Reopen the choice of account when the receiving claim, construction facts or applicable identity criterion changes.

B.1:12 - Relations

  • Builds on: A.1 for holon recognition, A.14 for relation vocabulary, and C.13 for constructional grounding. Use B.3.5 for Working-Model assurance grounding when a publication choice or named current requirement elects that profile.
  • 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 marked 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. Start with the decision and what would make its answer differ. Identify the participants and the relation that could transmit that difference before choosing graph notation. Use B.1.1:4.3 to distinguish common relation kinds, then follow the pattern that defines or tests the relation in question.

What goes wrong if missed. A generic “depends on” edge can conceal different relations. External influence, order, or temporal dependence may be mistaken for parthood, and mathematical checks may appear precise while the relation being checked remains unclear.

What this buys. The practitioner can use dependency evidence in a B.1 aggregation claim while keeping the relations distinct from their graph representation.

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.
  • For an architectural claim about a selected structure, use A.22 and C.30.
  • To choose a mathematical representation, 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 pattern has selected the relation under concern. A dependency graph describes that selected relation structure. The facts and rules governing the relations supply the grounds for the whole-level claim.

B.1.1:2 - Problem

When these distinctions are missed:

  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, 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 property is used to support a claim about the object without grounding the represented relation.
  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

ForceTension
Visual clarity vs relation precisionGraphs make dependencies visible but tempt one-edge-fits-all modeling.
Part-whole locality vs external influenceExternal systems can influence, measure, transform, or supply a holon without becoming its parts.
Mathematical checks vs ontology-side groundingAcyclicity, cutsets, reachability, and flow checks help only after relation kinds are selected.
Design view vs run evidenceDesign-time dependency descriptions and run-time evidence often share labels but concern different subjects and require separate claims.

B.1.1:4 - Solution

Work back from the proposed conclusion to the dependencies it uses. If one input changes, ask which result can change, by what interaction and under which conditions. Keep an external supplier in the account when its delivery matters. Follow a part into its own constituents when different internal arrangements can change the answer. For a proposed design, use the stipulated relations to reach a conditional conclusion. For a claim about the actual whole, establish which of those relations obtain. A diagram is useful when representing their organization helps the recipient decide.

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 the relations established about a subject or stipulated for a proposed arrangement. In a design comparison, the stipulated dependencies can warrant a conditional result before the design is realized. The frame can also refer to a selected U.Structure. When the receiving use needs one selected dependency structure, recover all four A.22 identity discriminators: 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?

Use the graph to examine properties such as acyclicity, reachability, cutsets, weak links, flow, or traceability. These checks concern the graph expression; their results bear on the selected relation only when its rule admits the mapping. State the mathematical representation correspondence, preserved and lost distinctions, and validation boundary on which that inference depends. Use C.29 when a mathematical representation-choice, transfer or reliance question remains unresolved.

B.1.1:4.3 - Relation Grounding Guide

If the edge means…Recover…Pattern that defines or tests the claim
part of the wholepart-whole relation over admitted holonsA.14, C.13, B.1
an entity belongs to a world-side collectionthe collection’s belongs-to occurrence, or a separately grounded collection-as-whole claimA.14, C.13, C.16, and the pattern that defines that collection’s rule
phase of the same carriertemporal phase relationthe carrier’s identity and phase rules and A.14; B.1.4 when the claim aggregates temporal phases
ordered step or branchmethod, process-view, Work, or order relationA.3.1, A.3.2, A.15.1, or the pattern that defines the order relation; B.1.4 for an order-sensitive or temporal aggregation claim; C.29 when a mathematical representation-choice, transfer or reliance question remains unresolved
performed work partwork occurrence relation with evidence and timingA.15.1
external influence, signal, supply, measurement, or controlthe obtaining relation and its participants, with the support required by the receiving claimA.3.4 for an actual transformation, C.16 for measurement, and the defining pattern for the supply or control relation; A.10 when the claim needs a source-to-use account for provenance or bounded reliance
representation, dashboard, digital twin, or architecture descriptiondescription or representation relation, not parthoodC.2.1, E.17, C.30.AD, C.30.AD.BA

B.1.1:4.4 - Graph Checks Are Conditional

Run graph checks only after selecting the graph as a lens over the dependency 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 a 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 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 Work relation. If one graph represents both, distinguish the Method or plan relations from the evidenced Work relations.

B.1.1:6 - Bias-Annotation

Bias riskFailureMitigation
Graph as ontologyA graph node or edge is treated as the represented object or relation.Recover the dependency structure and the relations, then use the patterns that define or test them before graph expression.
One-edge-fits-alldepends on carries parthood, order, representation, source use, evidence, and influence at once.Split the relation kinds and name the pattern that defines or tests each one.
External influence as parthoodSupply, measurement, teaching, source use, or control is drawn as a component relation.Use the boundary-crossing, evidence, source-use, publication-use, transformation, supply, or control relation and its defining pattern.
Design-description and run-occurrence collapseA planned dependency graph is treated as evidence of performed work.Separate design description, work occurrence, and evidence relations.

B.1.1:7 - Conformance Checklist

CheckRequirement
CC-B1.1-1The selected participants, relations and any transfer from a representation support the stated conclusion. For a proposed arrangement the result identifies its assumptions. For an actual-dependency claim the relevant relations are established.
CC-B1.1-2Graph, matrix, table and diagram wording distinguishes a representation from the organization it represents. When the receiving claim selects the representation’s organization as a U.Structure, identify that separate organization by the four A.22 discriminators.
CC-B1.1-3Part-whole edges use A.14 and C.13 discipline.
CC-B1.1-4Boundary-crossing, transformation, evidence, source-use, publication-use, and representation relations are not recast as parthood.
CC-B1.1-5Design description, run occurrence, and evidence are not mixed; the record names their separate patterns and uses a DesignRunTag or equivalent scope discipline when needed.
CC-B1.1-6Graph checks are interpreted only through the selected relation’s defining or testing rule. Use C.29 when a mathematical representation-choice, transfer or reliance question remains unresolved.

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

Anti-patternSymptomRepair
DependencyGraph as ontologyThe graph is treated as the thing being built.Name the dependency structure and relations first.
External supplier as partA supplier or infrastructure system is drawn inside the product.Use the boundary-crossing, supply, commitment, evidence, publication-use, source-use, or other relation; use parthood only for admitted parts. Use A.6.C only when the source’s contract wording must be unpacked.
Mapping as parthoodA model, dashboard, or digital twin is a node inside the asset.Use the representation, publication, architecture-description, or evidence relation.
Order as componentA subsequent step is represented as a component of an earlier step.Use the pattern that defines the order, method, description, or Work-occurrence claim.
Acyclicity as adequacyThe graph has no cycles, so the model is accepted.Check whether the selected relation is grounded and whether graph checks answer the current concern.

B.1.1:9 - Consequences

Positive consequences:

  • Dependency views expose the relations they represent.
  • External influence and parthood are assessed as separate claims.
  • Graph checks keep their value and their limits.
  • B.1 aggregation can rely on grounded part-whole inputs.

Costs:

  • Name the relation kinds and the patterns that define or test them, in the diagram or its accompanying explanation.
  • 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 is a useful starting term for several kinds of connection. To use it in a whole-level claim, distinguish the relation, the selected structure, and the mathematical or published expression. The facts and rules that make each relation obtain supply the grounds; a graph expresses the selected structure.

B.1.1:11 - SoTA-Echoing

For the question “what whole-level claim follows from this dependency graph?”, a generic graph can answer a reachability or cycle question about its edges. A claim about the represented system additionally needs the edge relation and its correspondence. A.14:4 and C.13:4.1 supply the part-whole and collection criteria used here; A.22:4.1 supplies the selected organization’s identity discriminators.

In B.1.1:5.1, the arrow PowerGrid -> Plant alone does not distinguish supply from parthood. Supply leaves parthood undecided; an independently grounded internal power subsystem can be both supplier and part. The generic edge account is sufficient for a graph property that does not depend on that distinction, but insufficient for a plant-parthood conclusion. Sections B.1.1:4.1–4.3 retain the graph calculation and add the relation facts, identity rule and correspondence required by the intended inference.

The additional work is to recover those facts and rules, using the diagram or an accompanying explanation when the receiving use needs them inspectable. This conceptual comparison supports the distinction in these cases; it does not establish superiority over named engineering notations. Reconsider the required account when the relation, correspondence or intended inference changes.

B.1.1:12 - Relations

  • Builds on: B.1, A.1, A.14, and C.13.
  • 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 a consequential question about retaining or reidentifying the whole.

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 marked informative

B.1.2:0 - Use This When

Use this pattern when an engineering decision about a system whole depends on several independently grounded claims: its part-whole relations, delimitation, boundary crossings, functions and their bearers, or whole-level characteristics. The entity may already be recognized under U.System or still be under evaluation through A.1.

Typical moments:

  • a machine, building asset, or organization is proposed as a whole assembled from identified 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, crossings, and compatibility choices without turning that view into the system.

First useful move. Start from the receiving decision and the system or proposed assembly it concerns. Follow its use outward when the enclosing arrangement can change that decision, and inward when two admissible internal arrangements give different answers. Identify the whole’s A.1 recognition status when systemhood matters to the claim. For each claim, use the applicable subject pattern to recover its result or identify the missing defining rule or information. Then ask whether considering the results’ joint organization changes the decision.

What goes wrong if missed. A reader may infer components and containment from placement in a diagram, treat a functional element as a physical part, or mistake an external transformation or measurement relation for parthood. A coordination record then appears to establish facts that each need grounds.

What this buys. The practitioner can combine the results needed for one engineering aggregation decision while retaining each claim’s grounds and use conditions.

Not this pattern when.

  • If the only open question is whether an entity qualifies as a U.System, use A.1.
  • If one part-whole relation is the question, use A.14 and its specialization.
  • If constructive assembly grounding is the question, use C.13.
  • If the question is a functional claim, use its 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 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.
  • For the system-of-interest role in an extended enterprise or the system-in-hand for local investigation or change, use A.1.STM and A.1.SCR. For a technical system-role assignment, Work, transformation, service or access, evidence, description, or publication, use its subject pattern.

B.1.2:1 - Problem Frame

B.1.2 specializes B.1 for system holons. It coordinates independently grounded facts for one aggregation or delimitation decision; each relation retains its defining pattern.

Keep the following meanings separate when identifying the whole:

  1. The system whole. For an existing system whose identity matters, establish it under A.1 and its identity rule. For a proposed design, identify the system to be built through its intended use, arrangement and assumptions.
  2. Its environment. In this pattern, environment means the external referents and crossing relations made relevant by a stated delimitation and use. It is not a generic surrounding object; a medium is named separately when that medium is the subject.
  3. A containing system. The larger system of which S is an admitted part exists for this claim only when a part-whole relation independently obtains. Interaction or spatial surrounding is not enough.
  4. System-of-interest and system-in-hand. The system-of-interest is the product System that a named extended enterprise is organized to create, change, sustain in use or retire. The system-in-hand is the system locally being investigated or changed. Use A.1.STM:4.1 and A.1.SCR:4.7 to establish the grounds for the designation or local focus. Neither establishes System identity, environment, parthood or architecture; any technical system-role classification and assignment also needs its own grounds.
  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 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 identity, part, boundary, crossing or characteristic results needed by that decision. Use :4.2 only when their joint organization changes that decision.

B.1.2:2 - Problem

When these distinctions are missed:

  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 creates systemhood, parts, boundary, crossings, allocation, evidence, and representation instead of pointing to independently governed facts.

B.1.2:3 - Forces

ForceTension
Engineering concreteness vs broad FPF holon scopeSystem aggregation must be practical for systems without making all holons systems.
Delimitation vs external dependencyA named use needs a system boundary while critical relations can cross it and remain external.
Component structure vs functional structurePhysical or organizational bearers may realize several functions, and one function may require several bearers.
Conservative roll-up vs redundancyWeakest-link and conservation checks are useful, but redundancy or substitution may require B.2 whole reidentification.
Description vs described systemA description must preserve the distinctions needed for the decision while remaining distinguishable from the system it describes.
Coordination vs ownershipOne decision may need many facts, but the coordinating pattern must not become the source of all those relations.

B.1.2:4 - Solution

Coordinate one named system-aggregation or delimitation decision using the independently grounded results below. A record can bring those results together; establishing any further relation requires grounds.

Use an established fact about the whole directly when it settles the decision. To compare proposed designs, hold their common requirements fixed and follow each proposed allocation or crossing to its consequence for the intended use. A model may group designs with the same relevant consequence and grounds. An inventory of existing components supports a different decision from choosing or realizing a new assembly. Read the questions below for the claims the result actually needs. For a proposal, identify its stipulated relations and conditions of use. Evidence that they obtain is needed for an as-built claim.

B.1.2:4.1 - Recover Each Result Or Blocker

Working questionSubject patternResult or stop
Which whole is being considered?A.1 and the kind-specific recognition patternFor a design comparison, the proposed whole, its intended use and the arrangement under consideration. For a claim about an existing U.System, a recognized entity or the A.1 evaluation of its six constructive components and kind-specific condition, including any unresolved basis.
Which constituents are parts, portions, phases, or members, and how do they assemble?A.14, the part-relation specialization, and C.13 for constructive assembly groundingFor an actual system, the obtaining part relations and assembly. For a design comparison, the proposed relations and their consequences under the stated assumptions; otherwise the missing governor, participant identity, obtaining fact, or assembly basis.
Which facts and selected boundary-use claim delimit the system for this decision?A.1 for system identity; A.14, the part-relation specialization, and C.13 for parthood and assembly; every crossing-relation pattern for external participants; C.11 for a local choice among already available boundary readings; C.32.PAD for a post-synthesis architecture decision concerning project Work; C.2.1 only for a separately persistent claimFirst identify the system and the parts, assembly or boundary crossings that affect this question. For a proposed option identify the corresponding design stipulations. For a claim about the actual system establish the relevant facts. If those facts answer the question, stop. If the named use additionally selects a boundary reading, return the C.11 ChoiceResult or C.32.PAD ArchitectureDecisionRelation@Project that makes its inclusion, exclusion, identity-preservation, and use claim current. Another choice branch passes only after its admitted decision predicate, source, and result are named; otherwise return the missing predicate or defining pattern, participant, obtaining fact, decision governor, or information blocker. When durable reliance is needed, one separate C.2.1 episteme states that claim and cites its basis; it creates none of the world facts. A selected U.Structure remains a separate B.1.2:4.2 branch.
Which relation crosses the selected boundary?The source, supply, flow, coupling, control, measurement, evidence, publication, transformation, commitment, or other relation pattern; F.9 only for a needed semantic correspondence or difference between two F.17 local senses from different semantic contextsFor an actual crossing, the obtaining relation with its participants and predicate. For a proposed crossing, the specified endpoints, relation and conditions; otherwise the missing governor, endpoint, binding, or obtaining fact.
Which function is realized by which bearer?The behavior, realization, allocation or parthood pattern; A.6.F or A.6.M only for unresolved wording; C.30.ASV only for architecture-view qualificationFor a current arrangement, recover the functional claim, bearer and obtaining realization or allocation relation. For a proposed allocation, establish what its bearer would have to do and whether the design supports that use. Establish parthood separately when it is claimed. If a relation required by the claim cannot be established, identify the missing predicate, participant or defining source.
Which whole-level characteristic is claimed?C.16 and A.19; C.29 when a mathematical representation-choice, transfer or reliance question remains unresolvedRecover the bearer, characteristic, assignment or value, and scale, together with any threshold, aggregation or inference rule, and lens-use boundary required by the claim; identify any missing basis needed for that claim.
Which evidence, description, representation, or publication supports inspection?C.2.1 for the account; A.2.4 for evidence-use or status-use classification. Use A.10 for an unresolved source-to-use account, B.3 for a requested assurance claim, C.29 for an unresolved mathematical-lens question, or E.17 for a needed publication face; use the applicable source or architecture-description pattern when that relation is the questionThe episteme and evidence, assurance, description, representation, source-use, or publication relation; otherwise the missing identity, relation, applicability, or reliance basis.

If grounds are missing, check whether the remaining possibilities support the same decision. Give that decision and its grounds when they do. Otherwise return the established contribution and identify the missing result that could change the answer.

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

When a decision depends on several results together, explain how they combine for that decision. In a design comparison, the relations and constraints stipulated for each option can warrant a conditional conclusion. When the claim selects a U.Structure under A.22, identify the subject whose organization is selected. Establish its independently identified constituents, the relation occurrences that obtain for that subject, the applied constraints and the named selection-use frame with its admissible action or stop. Relations between elements of a design can be present before the designed assembly exists.

The selected structure is non-agentive. Selecting it does not establish systemhood or the relations being selected. A diagram or other representation can express the selected organization; its form alone supplies none of the four discriminators.

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

When choosing an interface arrangement, identify the existing or proposed crossing and the use affected by the choice. Options include exposing the crossing, assigning it a namespace, internalizing it, excluding it, or leaving its treatment with its subject pattern. These are ordinary decision options.

Name the relevant world facts or design stipulations, affected endpoints, crossing predicate and any occurrence claimed, 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 predicate applies. A different choice passes only after its subject assertion, predicate, and result are named; otherwise stop with the established missing-governor blocker, whose content identifies the absent 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 result; the episteme does not make the crossing, parthood, compatibility, or decision fact obtain. This account lets the practitioner check whether an interface change loses an external obligation or leaves an endpoint unmanaged.

B.1.2:4.4 - Whole-Level Characteristics

Roll up system-level characteristics only after the 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 and A.19 for the characteristic, scale and aggregation rule. Retain the correspondence, assumptions and limits needed to rely on a mathematical lens; use C.29 when its choice, transfer or reliance remains unresolved. Use B.2 when changed facts leave a consequential question about whether the existing whole still supports the claim or a new whole is required. A sufficient existing-whole explanation ends that inquiry; missing deciding grounds leave the comparison unresolved.

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 bearer under its 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 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 entity proposed for recognition under the already admitted U.System kind. Pumps, frame, valves, controller, and connectors become its components only when their 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 systems or epistemes and their supply, work, telemetry, publication, source-use, or other relations. If a maintenance-isolation decision needs their joint organization, an A.22 selected structure may include the obtaining crossings without turning them into parts.

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 characteristic rule or decision basis. If inspection instead leaves V’s part relation unresolved, return the three established components and that 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 function, bearer, allocation or correspondence, and any part relation separately; B.1.2 only coordinates them for the 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. Identify what the model or account says about the asset; use C.2.1 if that description needs clarification. Follow the further questions in :4.1 only when the use depends on them. Establish any claimed parthood through its relation.

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 crossing or participation pattern; use part-whole only when a relation independently obtains.

B.1.2:5.5 - Bias-Annotation

Bias riskFailureMitigation
Box as ontologyA diagram boundary becomes system delimitation by appearance.Name the system and obtaining part and crossing relations. Stop if they answer the question. If a distinct use-relative boundary choice remains, name the C.11 ChoiceResult, C.32.PAD ArchitectureDecisionRelation@Project, or another admitted result; otherwise stop with the missing-governor blocker. Use an A.22 selected structure only when its four discriminators are independently grounded.
Interface as partSupply, signal, measurement, control, publication, or evidence relation becomes a component.Recover the crossing occurrence under its subject pattern and keep it separate from parthood.
Function as bearerA functional block or symbol is treated as a physical or organizational component.Recover function, bearer, allocation or correspondence, and any parthood claim separately.
Description as systemBIM model, dashboard, digital twin, register, or source record is treated as the system.Identify the description and the system it describes; use C.2.1 if that relation is unclear, and the applicable further pattern only for a remaining question.
Transformation as containmentA tool or teacher changes a holon and is read as its part or containing whole.Use A.3.4, A.15.1, A.12, and the participation or crossing pattern; require a separately obtaining part-whole relation for containment.
Coordination as ownershipA convenient B.1.2 record is treated as the source of all named facts.Use its subject pattern for each relation the conclusion needs; select an A.22 U.Structure only when the organization changes the decision.

B.1.2:6 - Conformance Checklist

CheckRequirement
CC-B1.2-1A design conclusion identifies the proposed whole and the stipulations on which the conclusion depends. When the conclusion needs an existing U.System, give its recognition under A.1 or identify the unresolved recognition question.
CC-B1.2-2The result identifies the system and the relations the named decision depends on. A design comparison states the assumed arrangements. Conclusions about as-built parts or actual crossings identify the obtaining relations under their subject patterns. When a distinct use-relative inclusion/exclusion choice is claimed, it cites the applicable C.11 ChoiceResult, C.32.PAD ArchitectureDecisionRelation@Project, or another admitted result; without that predicate, source, and result it returns a missing-governor blocker. Any durable C.2.1 episteme states but does not create those facts. An optional selected structure separately satisfies all four A.22 discriminators.
CC-B1.2-3External supply, signal, control, measurement, source, publication, evidence, transformation, or coupling claims retain participant bindings and relation patterns; none becomes parthood by crossing or importance.
CC-B1.2-4When a conclusion uses functional elements, their bearers, an allocation or a part relation, it identifies the grounds for each relation used.
CC-B1.2-5A whole-level characteristic names its bearer, characteristic relation or assignment, scale and supporting evidence. A roll-up or other inference identifies the rule and any mathematical-lens boundary it uses.
CC-B1.2-6Changing, controlling, teaching, measuring, or repairing another holon does not make that holon a part of the acting system; any containing-whole claim has its part-whole relation.
CC-B1.2-7Description artifacts, models, dashboards, digital twins, and registers remain distinct from the system holon and from any selected structure they describe.
CC-B1.2-8A claim to have selected a U.Structure identifies its subject and establishes the four A.22 discriminators for that subject. A conditional conclusion about a proposed design identifies the stipulated organization that warrants it.
CC-B1.2-9Environment, containing system, the system-of-interest role in a named extended enterprise, the local system-in-hand, and any claim or model-use qualifier remain separately identified; Context is not used as their common owner.

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

Anti-patternSymptomRepair
Box as boundaryA diagram rectangle determines system membership.Recover the identity, part and crossing facts needed for the boundary question. If they settle it, give the answer. If a distinct use-relative boundary choice remains, name the applicable C.11 ChoiceResult, C.32.PAD ArchitectureDecisionRelation@Project, or another admitted result; otherwise stop with the missing-governor blocker. Add a C.2.1 episteme only when that claim must persist; use an A.22 selected structure only when its four discriminators are independently grounded.
Supplier as componentExternal supplier or grid is treated as part of the system.Recover the supply, commitment, evidence, source-use, or other crossing relation under its subject pattern; infer no parthood.
Function block as moduleA functional block is treated as a physical component.Recover the functional element, proposed bearer, allocation or correspondence, and any obtaining part relation separately.
Digital twin as partA model or dashboard appears inside the system aggregate.Recover the description relation; add parthood only if its predicate independently obtains. Follow :4.1 for a further question about relying on or publishing the description.
Redundancy as arithmeticRedundancy is averaged into a better system score.Check the characteristic scale and applicable existing-whole explanations; use B.2 when the decision still depends on whether the existing whole is sufficient.

B.1.2:8 - Consequences

Positive consequences:

  • System aggregation remains practical for engineering systems and organizations.
  • Boundary and interface decisions expose the facts and rules they depend on.
  • Practitioners can distinguish functional architecture, module allocation, and physical parthood within a shared diagram.
  • The description remains distinct from the system it describes; any further claimed relation between them needs grounds.

Costs:

  • A decision diagram needs clarification when a relevant relation or its basis cannot be recovered from the diagram and its available explanation.
  • 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

An engineering decision may depend on several relations involving the same system. Drawing them inside one box can obscure which objects are parts and which participate through other relations. B.1.2 coordinates the independently grounded results and selects an A.22 structure only when their joint organization changes the decision.

B.1.2:10 - SoTA-Echoing

The coordination method uses A.1 for system recognition, A.14 and C.13 for parts and assembly, and the applicable characteristic or relation method for each further claim. In the pump-skid case (:5.1), assigning membership from diagram placement can include the external grid and the description. Keeping the independently established relations yields the component inventory and exposes an unresolved component relation while retaining the established ones. This is the bounded comparison the case supports. A comparative claim against a named systems-engineering or reliability-engineering method requires that method’s delimitation and inference rules, assessed on the same decision at comparable effort.

B.1.2:11 - Relations

  • Builds on: B.1, A.1, A.14, C.13, A.22, and the relation patterns selected for the decision.
  • Coordinates with: A.6.F for function wording, A.6.M for module/interface wording, 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 changed system facts raise a consequential question about continuing with the existing whole or identifying a new one.

B.1.2:End

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

Status: Stable

At a glance. Use B.1.3 to compose identified U.Episteme inputs into one knowledge aggregate while preserving their provenance, interpretation conditions, conceptual mappings, and contribution to its warrant.

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 claim the recipient needs. Use a sufficient existing argument directly when the commission asks for that conclusion. When asked to construct a synthesis, work back from its required conclusion to the premises, sources and dependencies to combine. 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.

Mereology and identity (A.14/C.2.1). Use ConstituentOf for semantic parts. Measure a text or data split on its selected expression or carrier under C.2.1 and E.24.PUB; use PortionOf only when those measured entities independently meet A.14:5.1. 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 composes the episteme’s structure and semantics. Use Γ_ctx, Γ_time, or Γ_work for the corresponding questions after recovering their required inputs.

  • Mereology (A.14). For knowledge composition we primarily use ConstituentOf (logical or semantic parts), UsageOf or ReferenceTo (external reliance), and each collection’s 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 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 dated U.Work occurrence, stop with the ordinary sentence. If it does, recover each performer’s A.13 core and independently admit the occurrence under A.15.1. Add F.6 only when the receiving use also needs 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 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 when the recovered facts leave a question about whether the existing whole still carries the current claim or a new whole must be identified; 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. Combining mismatched concepts without explicit mappings and their interpretation limits can change or obscure the resulting claim despite its formal appearance.
  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 mappings and—when meanings cross—an F.9 Bridge plus a separately warranted bounded-use claim, 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

ForceTension
Conservatism vs. SynthesisRefuse unsupported assurance gains ↔ retain the contribution of complementary and alternative support.
Universality vs. Domain nuanceA common composition account across domains ↔ domain-specific semantics and evidence patterns differ.
Provenance fidelity vs. Cognitive loadKeep the full trail of sources and methods ↔ avoid overwhelming authors with bookkeeping.
Order/time discipline vs. FlowRespect argument order, episteme identity and edition relations, and any proper temporal restriction ↔ keep composition usable for day-to-day synthesis.
Parsimony vs. FitSmall rule set (A.11) ↔ explicit mappings, use-specific limitations, and justified loss models where needed.

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

B.1.3:4.1 - Terms

  • U.Episteme — a claim-bearing knowledge holon. C.2.1 identifies it through the participant-determined EpistemeConstitutionRelation over <claim content, EntityOfConcern, effective ReferenceScheme>. These three participant identities determine its identity. Claim content and ReferenceScheme are epistemic constituents; EntityOfConcern is the independently governed subject related through aboutness.

    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.

  • Constitution participants and typed positions. When the receiving use needs a reusable designation of the EntityOfConcern, C.2.1:4.2.1 supplies EntityOfConcernSlot with ValueKind=U.Entity and refMode=U.EntityRef. It is a participant meaning in the relation declaration, not an internal slot of the episteme. Claim content and effective interpretation rules remain necessary constituents without being additional SlotKinds. A receiving relation declaration that needs ClaimGraphSlot or ReferenceSchemeSlot must supply each independently governed ValueKind and A.6.5 SlotSpec; the constituent name alone provides neither.

  • 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 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, and reliance separate. Retain a CL summary when the receiving rule uses one, including the applicable KD-CAL substitution or cross-notation reasoning rule in C.2. CL alone neither grants the use nor supplies a numerical penalty.

  • Source and carrier record (SCR) — a recoverable account of which sources and carriers materially contributed to one identified synthesis or compilation result, and what each contributed. Keep the source versions, methods and carrier information needed to reconstruct that aggregation. The account may be expressed as prose, a table or a graph.

    An account meeting C.2.1’s episteme criterion is one U.Episteme: its claim content records those participation facts, its EntityOfConcern is the aggregate, and its effective ReferenceScheme determines their interpretation. Apply C.2.1 to its identity: a corrected participation claim changes the episteme, while another layout can express the same claims. Working notes can precede that completed account.

  • Semantic context — Plain shorthand for the local interpretation basis recovered from one 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.

Collection membership. • A collection’s 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.

B.1.3:4.2 - The operator family

Γ_epist has two companion operations with different semantic questions and the composition conditions below. Their declarations contain the values on which the result depends. A performer, local system-role kind, or assignment is not an operator argument: the fold can be specified before staffing and applied in Work performed by different Systems without changing its result semantics. This preserves the design/run distinction under A.15.

When one 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 dated U.Work claim is current, that ordinary sentence needs no classification or assignment apparatus. If one is current, recover every 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 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 input epistemes into a draft aggregate. The displayed signature is a family template. An operation declaration states which receiving claim, use and composition rules are fixed and how varying values are supplied; it determines the result’s claim content, EntityOfConcern and interpretation basis from its admitted inputs. Its domain is restricted by the applicable conditions in :4.4. Ordinary bounded synthesis may state this basis in its explanation without a separate operation declaration.

Γ_epist^synth : ( D_know : DependencyGraph< U.Episteme > ) ⇀ U.Episteme
  • Domain. D_know designates source epistemes and the relations used in their composition: governed ConstituentOf, UsageOf and ReferenceTo relations; support and derivation relations under their predicates; and collection belonging under each collection’s rule. It also identifies the mappings used by the fold. Those relations must independently obtain; graph labels do not establish them.

  • Result. One synthesized episteme whose claim content, EntityOfConcern, and effective reference scheme satisfy C.2.1. Its ClaimGraph integrates the retained content. Keep material source contributions recoverable, adding the SCR when the receiving use requires reconstruction of the aggregation. 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 target reference scheme. Recover the operative target rules through C.2.1:4.1.1 and fix them as S for this compilation operation. A journal’s name or the document describing its rules does not by itself identify those rules.

Compare S with the source scheme by its interpreted rules, their domains and dependencies under C.2.1:4.1.1. A different spelling or encoding can express the same rules. A changed semantic rule or domain identifies a different target scheme even when a selected answer agrees; this compilation then identifies the result with that target S.

Γ_epist^{compile,S} : ( E_synth : U.Episteme ) ⇀ U.Episteme

S is fixed in the operation’s declaration. The declaration states how input claims are mapped into S and the conditions for admitting the result. The partial arrow means that an identified input episteme alone does not establish an admissible compilation: the mapping, preservation, and reliance conditions in :4.5 must hold. An unresolved interpretation or required mapping leaves the affected compilation unresolved.

  • Domain. One synthesized episteme whose retained claims can be interpreted in S under the declared mapping. For every meaning that crosses semantic contexts, the fold also relies on source and receiving SchemeSenseCell values, an obtaining F.9 Bridge, and a separately stated bounded-use claim. Reliance on that claim requires the A.10 evidence-provenance path and same-use RelianceDisposition under F.9:4.2: pass supports the named use; degrade supports only its named narrower use. A named assurance claim additionally requires a B.3 result supporting that same bounded assurance use.
  • Result. One compiled episteme with explicit mapping and loss information and a C.2.1 identity determined by its claim content, EntityOfConcern, and effective target scheme S. The result is not thereby a publication, release, carrier, or accepted artifact.

When the target must be replaceable. A receiving use that selects or substitutes a target scheme within one operation needs an independently governed range for that argument. Use C.3 to identify the candidate rules, their identity criterion, and the membership condition required by that use; then declare the argument and its binding conditions under A.6.1.

Range membership does not establish that the chosen scheme can express this input’s claims or that a proposed mapping preserves the required meaning. Those application conditions still need :4.5.

E.24.UK:4.2c supplies no admitted general U.ReferenceScheme range. Fixing one S permits the compilation above without claiming that general range; changing the fixed rules requires reconsidering the declaration, mappings, and affected results.

Relationship to Γ_ctx / Γ_time. If the knowledge fold depends on argument order (for example, a derivation), the internal fold uses Γ_ctx for the sequence. If a temporal storyline matters, first identify each 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 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 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 while preserving its claim content, EntityOfConcern and effective ReferenceScheme returns that same episteme. Repeating the same source or data creates no additional evidence or accidental assurance upgrade.
  • COMM/LOC (Local commutativity / locality). Reordering 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, these marginals alone bound the conjunction between 0.8 and 0.9. These bounds can settle thresholds on the conjunction itself. For another event whose occurrence requires both conditions, their joint probability supplies an upper bound. A lower bound on the conjunction also bounds success from below if their joint occurrence ensures success. More generally, let L be a lower bound on the probability of both conditions holding and d an upper bound on the probability that both hold and the function still fails. Success has probability at least max(0, L − d). A minimum or maximum can be useful under its 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.

To design the synthesis, first say what could count for or against the requested conclusion. Follow each needed inference to a premise, observation or rule that can supply it. Identify which contributions are semantic parts of the resulting argument and which sources establish or qualify a premise from outside it. A report about a component and a claim about the enclosing system can contribute together when the system’s use of that component warrants the inference. Try a different arrangement with the same local finding. If it changes the conclusion, retain the distinguishing condition or limit the inference. End a branch where an applicable source or general argument supplies the required ground. To supply a way of synthesizing future cases, explain how to choose these contributions when the sources or uses differ.

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. Preserve the material sources and methods on which each retained claim relies, including contrary evidence that bears on it. For a claim about all eligible contributions or about their absence, give the selection rule and establish why a missing contribution cannot change the result. A complete register, an applicable general argument or a sufficient bound can establish that coverage. A question about one documented contribution can be settled by that contribution.

2. SCR construction. Keep a recoverable account of every material source contribution, method, mapping and dependency. Include carriers and source versions where their identity, currentness, integrity or participation matters to the named use. When that use requires reconstruction of the aggregation, retain the SCR and the information needed for that reconstruction.

Use the developing record to expose a missing source, shared data or an unsupported inference. Keep contrary contributions visible under rule 4. Pass the recoverable account with the aggregate or through resolvable references. When a source changes, reconsider the retained claims that depended on it.

3. Object alignment. Identify the result’s one 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 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, their limitations, and any CL summary required by the receiving rule, without merging homonyms.

4. Recover the support relation before combining. For the 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 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 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. Assess F under C.2.3 from the expression properties of essential constituents and their connecting inferences. A minimum applies only under a justified composition rule on a shared local ordered scale; it concerns that expression assessment, 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 use limitations and any CL summary consumed by the receiving rule. 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 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 support and any mode declaration needed by the receiving use:

  • 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. A local ordinal formality summary describes only its declared ordinal meaning. Any value proposed for an R calculation needs a receiving model establishing meaning, scale, conversion, and assumptions; rescaling a formality rank into [0,1] is insufficient.
  • For a postulative input, retain its 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.
  • When the receiving use requires a mode classification, apply its rule to the support operative in the claimed conclusion. Under the axiomatic/postulative distinction, if all operative inputs are axiomatic, the conclusion is axiomatic; an operative postulative input makes that conclusion 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. Account for resource use separately. When the receiving question requires a resource account for computation or collection, use B.1.6/Γ_work and reference that account separately from the epistemic support.

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

When computing Γ_epist^{compile,S}(E_synth), retain the fixed rules S and the mapping used for this input:

1. Reference-scheme bindings. Map every operative concept, unit, and claim into S and record the mapping, its limitations and any CL summary required by the receiving rule. 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, 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 S. 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 result needs grounds for its claimed calculations or derivations; its mode alone requires no additional numerical tuple.

3. Compilation trace. Carry the recoverable source-contribution account with the compiled episteme or through resolvable references. Add carrier hashes or other reconstruction details when the receiving claim requires carrier integrity or replay of the compilation. 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 conclusion depends on derivational order, carry the ordered relations, positions and OrderSpec required by that use. If it selects knowledge for a time-bounded use, name the 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 used.

B.1.3:5 - Archetypal grounding

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

This is an 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 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 ClaimScope.
  • Synthesis: record the source findings and the protocol, dataset or analysis details on which the synthesis relies. Include carrier information when the receiving use needs it. Establish any dosage or outcome mapping from its 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 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.

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 source-contribution account 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 preserve the source-contribution account with any SCR or carrier-integrity details required by the receiving use. 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 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 the expression properties; the probability that the actual controller is safe needs its assurance basis.
  • 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 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, the theorem A ⇒ P still holds. Its proof leaves the real function in that case unresolved. Other evidence can settle the assurance question over its intended operating range.
  • 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. Acceptance can follow from a justified lower bound at or above the threshold. An upper bound strictly below it establishes failure to meet the clause. Where neither conclusion follows, return the narrower formal result and identify the unresolved system assurance.
  • Positive quantitative case: suppose the real protective function requires two conditions, each with probability 0.9. Under independence the probability of both is 0.81. The function can be present only when both hold, so its probability is at most 0.81. This rules out a 0.85 threshold. The probability of success equals that of the conjunction exactly when the probability of failure with both conditions present is zero. Without independence the probability of both lies between 0.8 and 0.9. Even one necessary condition with probability 0.9 rules out the 0.95 threshold. The formal proof remains available under its own assumptions.

For Γ_epist^compile, map the retained claims to the certification scheme. Where local meanings differ, identify 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 system protection remain separate claims.

To make the target choice explicit, fix S_cert with two interpretation rules: “proved under A” states A ⇒ P in the named model; “protection established in service” states that the installed system delivers the protective function in the named operating conditions. The proof input can be compiled into the first statement with A retained. It cannot supply the second statement without the model-to-world and assurance basis already identified above.

Reformatting the document that describes these two rules leaves S_cert unchanged. If another target reads “proved” as an unconditional claim about the installed system, that is a different scheme: the earlier mapping of the proof is inadmissible there, while the original theorem remains available.

Selecting that target within one replaceable-scheme argument also requires the declared range membership; matching its document format establishes neither membership nor an admissible mapping.

B.1.3:5.3 - Knowledge composition and system aggregation

AspectKnowledge composition (B.1.3:4)System aggregation decisions (B.1.2:4)
What is combined?Claims, models, datasets and arguments, with their provenance and semantic relationsEstablished component, material-portion and assembly facts for one engineering decision; each whole-characteristic claim uses its applicable aggregation rule
ConservatismSupport roles, dependence, and mapping limits under the named B.3 model; no invented aggregateWLNK for a quantity whose physical model justifies a weakest-part bound
FitSemantic mappings and their calibration evidence, with a separately warranted receiving useInterfaces, crossings and compatibility choices under B.1.2:4.3 and their relation rules
Order/timeArgument order; C.2.1 episteme identities and edition relations; A.14 proper temporal restrictions; B.1.4 aggregation of recovered order or temporal relationsA.15.1 for assembly Work and its temporal parts; A.14 for proper phases of enduring carriers; B.1.4 for aggregation of recovered order or temporal relations
Work/costResources spent in synthesis, compilation or validation Work, aggregated under B.1.6Resources spent in assembly or operation Work, aggregated under B.1.6

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 remains traceable to its material sources and methods. An SCR MUST be retained when required to reconstruct the aggregation for its named use.
  2. PO-SYN-OBJ. The result MUST name one EntityOfConcern already identified under its 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 limitations and any CL summary required by the receiving rule.
  3. PO-SYN-CL. Every mapping used in the support account MUST retain its use limitations and any CL summary consumed by the receiving rule. 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. When it makes a claim covering every eligible contribution, the grounds for coverage must support that claim. 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. When a resource account is required, use B.1.6 and reference its result separately; resource expenditure does not itself establish epistemic support.

At compilation (Γ_epist^compile):

  1. PO-COMP-SCHEME. The operative target rules MUST be identified and fixed in the compilation declaration. If the receiving operation instead accepts a replaceable scheme argument, its independently governed range and binding conditions MUST be declared and satisfied for that use. Every active concept and unit MUST have an explicit mapping; a cross-context meaning use MUST name the F.9 Bridge, separate bounded-use claim, permitted loss, and the A.10 path and same-use RelianceDisposition required by F.9:4.2. A named assurance claim additionally requires its B.3 result for that same bounded assurance use.
  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 keep its material source contributions recoverable. Retain the SCR and the hashes, versions or dates required by a named reconstruction, currentness or carrier-integrity use. This obligation does not assert release or publication.
  4. PO-COMP-ID. The output MUST be identified through its C.2.1 claim content, 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 C.2.1 episteme identity and reference the already recovered proper restriction, edition-relation order, applicability window, and B.1.4/Γ_time aggregation consumed.

B.1.3:7 - Conformance Checklist (normative)

IDRequirementPurpose
CC‑B1.3.1Every knowledge constituent supplied to Γ_epist MUST be a U.Episteme holon; ComponentOf is forbidden; use ConstituentOf, UsageOf, or ReferenceTo for their different claims; use a collection’s belongs-to predicate only for collections.Prevent category errors.
CC‑B1.3.2Material sources, methods and their contributions MUST remain recoverable with the aggregate. Preserve any SCR details required by the receiving use. A claim to complete coverage identifies which contributions qualify and what warrants its reach.Preserve source contributions and required reconstruction grounds.
CC‑B1.3.3Any aggregate R MUST follow the justified input meanings, scales, support dependencies, and receiving model. No default min, max, or F-to-R conversion is supplied; absent a common model, retain a bounded synthesis and separate support.Prevent unsupported assurance and preserve useful non-aggregate results.
CC-B1.3.4Contrary evidence MUST remain visible. An established scope or interpretation difference may separate claims; an unresolved conflict must qualify, narrow, or defeat the affected conclusion. Use B.2 only for a separately grounded whole-reidentification question.Keep the practical effect of disagreement visible.
CC‑B1.3.5Any mode declaration consumed by the receiving use MUST follow that use’s rule and the support operative in the claimed conclusion. Under the axiomatic/postulative distinction, an operative postulative input makes that conclusion postulative; separately supported formal subclaims remain usable.Preserve the relevant warrant distinction without substituting a tag for support.
CC-B1.3.6A cross-context meaning use names explicit mappings, source and receiving F.17 cells, an obtaining F.9 Bridge, a separate bounded-use claim and permitted loss, and the A.10 evidence-provenance path and same-use RelianceDisposition required by F.9:4.2. A named assurance claim additionally requires its B.3 result for that same bounded assurance use. CL alone never grants the use.Make semantic crossing inspectable.
CC-B1.3.7An order-dependent conclusion MUST meet PO-SYN-ORDER and B.1.4:4. If an episteme history matters, C.2.1 endpoint identities and any obtaining EpistemeEditionRelation MUST be named; any proper restriction or B.1.4/Γ_time aggregation MUST cite only already recovered temporal relations.Preserve order, identity, continuity, and temporal integrity.
CC-B1.3.8Keep design-time synthesis, target-scheme compilation, one operation application and its returned value, dated Work, performer and any relied-on assignment, production or first existence, publication, carrier, release, and acceptance separately governed.Preserve semantic and practical boundaries.

B.1.3:8 - Anti‑patterns & repairs

Anti‑patternSymptomRepair
Unsupported foldingIncomparable scores are averaged, minimized, maximized, or converted from FIdentify support roles, scales, dependencies, and the receiving model. If none warrants aggregation, retain separate support and a bounded synthesis; do not hide counterevidence.
Provenance amnesiaSources, methods or SCR links disappearRestore the provenance and reconsider affected reliance. Repeat the affected synthesis when its claims, mappings or support calculation depended on what was lost.
Homonym mergeDifferent concepts with the same name are mergedDeclare the mapping. For cross-context meanings, identify and test the F.9 Bridge, state the bounded use and permitted loss. Decide the proposed use under its applicable correspondence and reliance rules; leave it unresolved when required grounds are unresolved.
Unsupported semantic crossingLocal senses or schemes are mixed without a tested correspondence and use boundaryDeclare the mappings; for cross-context meanings identify the F.9 Bridge, separate bounded-use claim, permitted loss, and the A.10 path and same-use RelianceDisposition. Retain the additional B.3 result when a named assurance claim is current.
Version soupLabels or time slices mix unchanged epistemes, distinct epistemes, edition continuity, publication, and Work historyApply the C.2.1 identity triple first; test EpistemeEditionRelation separately; use A.14 only for a proper restriction of one unchanged episteme and A.15.1 for Work. Then aggregate only the recovered temporal relations the current use needs.
Work stuffingCompute/curation cost blended into reliabilityRemove the unsupported inference from resource expenditure to warrant. Use B.1.6/Γ_work only when a separate resource-aggregation claim is current.
Orderless proofDerivation steps treated as a setAdd OrderSpec; compose with Γ_ctx inside Γ_epist.
Synergy by narrativeA new theory or whole is claimed from explanatory gain aloneFirst identify the synthesized episteme through C.2.1. Open B.2 only if construction and identity facts leave an existing-whole versus candidate-new-whole question.

B.1.3:9 - Consequences

Benefits

  • Traceable composition. Every retained claim remains tied to its sources; the SCR identifies the carriers needed to reconstruct the aggregate.
  • 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.
  • Separate composition questions. Separates semantic folding (Γ_epist) from order (Γ_ctx), time (Γ_time), spend (Γ_work), and emergence (B.2).

Trade‑offs

  • Mapping overhead. Establishing correspondences and their limitations costs time and makes interpretation differences inspectable.
  • 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 applies only to an 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. Declared reference schemes and local senses let a reader identify reinterpretation. F.9 governs any cross-context Bridge; C.2.1 governs the resulting episteme identity.
  • Synthesis without a common score. Provenance, support roles and dependencies, 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 application bindings), A.14 (ConstituentOf, collection belonging under each collection’s 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 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 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 cross-context Bridges and bounded-use claims; A.10 for reliance accounts and the same-use RelianceDisposition required for relied-on Bridge use; B.3 additionally when a named assurance claim is current; 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 construction facts leave a separate whole-reidentification question after the existing-whole explanation check.

  • Used by: B.3 assurance uses the aggregate’s 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 marked informative

Use this when. Use this pattern when the claim aggregates already recovered relations over a 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 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. A reader may mistake an ordering for parthood, a planned sequence for performed work, a phase for a new whole, or temporal coverage for evidence currentness.

What this buys. The practitioner can specify or compute the order-sensitive or temporal aggregate needed by a receiving use, with its combining rule and limits. Method, Work, transformation, work-resource, temporal-adequacy and MHT claims retain 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 concerns order or temporal coverage over already recovered relations.

B.1.4 asks what result the receiving use needs, which inputs and independently established relations it uses, and which operation combines them. Order, temporal reference, window, coverage and overlap qualify that operation when they affect its result. A stronger claim keeps its subject grounds.

B.1.4:1.1 - Problem

Confusing these relations produces four recurring errors. 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, a user treats mathematical notation as the represented object or relation, without establishing the correspondence needed for the bounded use.

The resulting aggregate is unusable for the proposed claim: 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

ForceTension
Order sensitivity vs. ordinary parthoodOrdered positions must remain reviewable without recasting them as parts of one physical whole.
Temporal coverage vs. carrier identityA phase aggregate needs useful time windows, but it must not hide that the carrier changed identity.
Design-time relation vs. run-time historyMethod order, work plan, and performed work often share labels, but they are different claims.
Compact notation vs. ontologyGamma_ctx, Gamma_time, graph, or algebra notation can make a relation easy to use, but cannot create a holon, method, work occurrence, or transformation.
Local aggregation vs. related claimsThe aggregation account should remain compact while retaining links to the independent grounds for resource, evidence-currentness, transformation, and MHT claims.

B.1.4:2 - Solution

Start with the receiving question and the result it needs. An already adequate aggregation rule and ordinary explanation can be used directly.

  1. Recover the inputs and relations. Identify the included positions, values, intervals or phases and the objects they concern. Keep their identity and relations grounded in the subject facts and applicable rules. For a temporal input, recover its bearer, temporal reference and interval; relate different references only through a justified conversion.
  2. Choose the combining rule and result. State the operation and what it returns: for example, an ordered relation structure, a combined value, the union of covered intervals or their elapsed span. When the rule is yours to design, change a possible history while holding the proposed summary fixed. Moving a gap can preserve total coverage while moving the last completion beyond a deadline. Use the events, intervals or joint conditions that distinguish the answers the recipient needs. Supply the order, join, independence, coverage and overlap conditions that this operation uses. If the rule needed by the question is missing, retain that gap rather than naming an unsupported aggregate.
  3. Obtain the requested result. A specification can be sufficient when the task asks how the aggregation is to be performed. When a computed result is needed, apply the selected operation and interpret its result under those conditions. Distinguish an order structure from the result of applying the operations it represents. Section :5 shows why the same inputs can support different warranted results.
  4. Bound the use and stop. State the supported use and any condition whose failure or uncertainty changes it. Narrow the result or leave the affected conclusion unresolved when its required basis is missing. Use another pattern when a distinct claim needs that pattern’s contribution. Stop with the sufficient ordinary answer.

When the receiving use needs an inspectable account, reuse an adequate account or materialize a ContextTemporalAggregation@Context record. It describes the independently established inputs, rule and result; it does not establish their subject facts:

ContextTemporalAggregation@Context:
  aggregationConcernRef
  aggregatedEntityOfConcernRef
  aggregationMode: contextualOrder | temporalAggregation
  combiningRuleOrOperator
  resultOrResultSpecification
  includedPositionRefs?
  includedIntervalRefs?
  includedPhaseRefs?
  claimScopeRef?: U.ClaimScope
  orderedRelationRefs?
  temporalRelationRefs?
  phaseRelationRefs?
  orderSpecRef?
  temporalReference?
  timeWindowRef?
  carrierIdentityRefs?
  independenceOrJoinConditionRefs?
  coverageAndOverlapPolicyRefs?
  boundaryCrossingRelationRefs?
  relatedMethodRefs?
  relatedMethodDescriptionRefs?
  relatedWorkOccurrenceRefs?
  relatedWorkResourceAggregationRefs?
  relatedTransformationRefs?
  relatedWholeReidentificationRefs?
  evidenceOrSourceRefs?
  admissibleUse
  stopOrReturnCondition?
  nonAdmissibleOverread?
  strongerSourceReturnCondition?

The aggregation concern is the receiving question; the EntityOfConcern is the independently identified subject of the aggregation claim. Included inputs retain their bearers and identities. Add each optional value when it changes that claim or its use. Facts and evidence needed to warrant the result remain necessary whether or not a reference field is written.

stopOrReturnCondition? states an action-changing limit; strongerSourceReturnCondition? is used only for a distinct stronger claim that the receiving work needs. Include nonAdmissibleOverread? only when it passes F.19’s plausible-reader test; groundedNonAdmissibleOverread? is an alias for that same optional value.

B.1.4:2.1 - Two Aggregation Modes

ModeObjectRequired relation disciplineTypical use
Contextual order aggregationPositions and relation facts whose order, partial order or join structure matters to the stated use.Included inputs, combining rule and required result, OrderSpec, ordered relation refs, join or independence conditions when used, and ClaimScope when needed.Ordered method relation, order-bound argument chain, staged construction description, controlled sequence.
Temporal aggregationInterval or time-indexed facts about named bearers or occurrences.Input identities and temporal relations, temporal reference or justified conversion, TimeWindow, combining rule, coverage and overlap policy. The proper-phase profile additionally requires one continuing carrier and the phase relation.Work-interval union or elapsed span, asset phases, observation windows, or chronology over episteme identities. For proper phases of one episteme, its complete C.2.1 identity triple stays fixed; distinct editions require their identities and any claimed edition relation.

When a use combines order and temporal claims, distinguish what each contributes and state the correspondence on which the joint result relies; one sufficient account may contain both. A Method may have an ordered relation structure. Work that enacts it may have A.15.1 temporal parts, episodes, operational parts or separate occurrences, while C.27.TA supplies any independently declared overlap or other interval relation. Aggregate those inputs under the chosen rule. Use PhaseOf only for the proper-phase profile of one enduring carrier, not as a substitute for Work or temporal relations.

B.1.4:2.2 - Where Stronger Claims Go

ClaimPattern to use
Method as semantic way of doingA.3.1
Method-description membership or a description-use questionA.3.2 defines membership and description boundaries. For SOPs, code or simulator configurations, use A.3.2 when the question is whether the identified episteme has an admitted Method as its exact EntityOfConcern and makes a substantive claim about it as a way of doing; representation form alone does not select the branch. Use the applicable subject or publication pattern for another claim.
Work planA.15.2
Dated work occurrence, performed episode, or evidence that work happenedA.15.1
Work-resource roll-up, spent resource, cost, effort, energy, material, or comparable ledgerB.1.6
Episteme identity and historical continuity between distinct epistemesC.2.1; aggregate only identities and an already obtaining EpistemeEditionRelation when the bounded use needs their chronology
Proper PhaseOf, portion, membership, or other parthood relation for a non-Work carrierA.14, B.1, and C.13 as appropriate; Work temporal and part relations remain with A.15.1
Holon delimitation or boundary-crossing relationA.1, B.1, A.12, A.3.4, or the pattern that defines the relation
Bounded change under conditionsA.3.4
Whole reidentification, emergence-family wording, MHT, MET, MFT, synergy, or metric-mirage wordingUse B.2.P when emergence-family wording hides the claim kind. If a whole-reidentification question remains, including one raised by an autonomy or capability change, use B.2; B.2.2 and B.2.3 handle System and Episteme result recognition, and B.2.4 is the capability/functioning decision bridge. Use B.2.5 separately for a two-sided supervisor-subholon feedback claim, whether or not whole reidentification is current.
Architecture structural view or selected structureC.30.ASV, A.22, or the pattern that defines or tests the architecture claim
Mathematical order, graph, algebraic notation, graph path or morphism used as expressionUse the applicable mathematical or subject rule directly when it supplies the result. Use C.29 for a separate unresolved representation-choice, transfer or reliance question. Use E.18 when its selected transformation-flow structure is the subject, and E.18.2 for a mathematical description of that TFS or a selected TFS network.

B.1.4:3 - Optional Operator Notation

Gamma_ctx and Gamma_time are optional notation for a selected aggregation operation and its result. A specification may state such an application without claiming that its result has already been computed.

Gamma_ctx(selectedInputs, combiningRule, orderSpec, joinOrIndependenceConditions?)
  -> contextual aggregation result

Gamma_time(selectedTemporalInputs, combiningRule, temporalReference, timeWindow, coverageAndOverlapPolicy)
  -> temporal aggregation result

The notation expresses the selected operation; it supplies no default combining rule. Temporal inputs retain the values and temporal facts consumed by that rule. An optional account can provide the argument values and describe the result. Establish the represented objects and relations under their patterns, and check the operation’s conditions before relying on that result.

Keep an ordinary statement about who prepared the aggregation ordinary. If the use asserts one dated sequencing, combining, measuring or auditing Work, recover the 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 claim identifies its included inputs, combining rule, result or result specification, ClaimScope when needed, and admissible use; any holon-boundary crossing it uses has its relation basis;
  • method, method-description, work, transformation, and resource claims use the patterns that define or test them.

For temporal aggregation:

  • each input interval and its bearer or occurrence are identified; a proper-phase claim additionally preserves the one carrier’s identity under its rule;
  • the temporal reference, any required conversion and the selected time window are established;
  • the selected combining rule and coverage/overlap policy hold; handle allowed overlaps and gaps as that rule requires, or narrow the use;
  • a changed identity is represented as a distinct input when appropriate, rather than hidden as another phase of the same carrier;
  • work-resource claims use B.1.6; positive temporal-aspect claims use C.27.TA, while a separate temporal-claim adequacy question uses C.27. Currentness uses G.11, and A.10 recovers provenance and bounded reliance when needed.

B.1 invariant carry-through. Apply an algebraic law only when the recovered relation and selected operator justify it. A unique computed contextual result requires the operation, permitted order and join or independence conditions to determine that result. Before promising an execution or its result, establish that the applicable constraints admit an execution. When admissible orders give different values, check the requested conclusion across them. A bound on all returned values can establish a condition on those values. For a promise to deliver the result by a deadline, also establish timely completion under the choices the promise covers, using a feasible decision rule if those choices are entrusted to the performer. To refute a guarantee with an adverse order, establish that the order can occur. For an exact value, retain the supported alternatives or establish the additional ordering or selection that determines it. An order structure can be a sufficient aggregate without asserting a unique execution outcome.

Temporal aggregation follows its selected rule, temporal reference, coverage and overlap policy; one-carrier continuity is additionally required by the proper-phase profile.

A repeated designation creates no additional occurrence or relation by itself; retain distinct occurrences and ordered positions when the claim distinguishes them. State any singleton or idempotence law for the 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 - Aggregation obligations

ObligationWhat must be namedWhy it matters
Independence and joinsFor branches used in the aggregate, name their relation refs, any join refs and the condition under which they may be combined.Prevents an ordered aggregate from treating dependent branches as independent evidence or work.
Order specificationTotal order, partial order, precedence relation, or another named relation over the selected positions.Keeps order-sensitive claims from being read as unordered collection claims.
Decisive dependency relationFor a weakest-link claim, name the relation that makes one position, delay or missing step decisive for the aggregate use.Keeps that claim dependent on its model and relation.
Bearer identity and phase continuityIdentify each temporal input’s bearer. For the proper-phase profile, state which carrier remains the same and under which identity rule.Keeps separate occurrences distinguishable and prevents a phase account from hiding identity change.
Temporal coverageTemporal reference, time window, intervals or phase refs, combining rule and coverage/overlap policy.Distinguishes covered time from elapsed span and exposes how gaps and overlaps affect the result.
Chronological disciplineState whether the claim uses chronological, logical, publication or performed-work order, and the correspondence needed when more than one is used.Keeps a document sequence, argument sequence and work occurrence sequence from substituting for one another.
Monotone characteristicFor a monotonicity claim, name the characteristic, comparison and model under which adding inputs preserves or improves the result.Blocks generic monotonicity claims over an unspecified aggregate.

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

Manufacturing sequence. A frame is prepared, welded, inspected, painted and packed. For a planning or comparison question, specify the selected steps, precedence, any joins used and the required result. That order specification can be the sufficient B.1.4 result. 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 can return a bounded chronology over those identities, obtaining relations and relevant applicability or publication windows. The editions retain their distinct identities. If one unchanged episteme is needed over a proper interval, A.14 PhaseOf states that restriction. Source-currentness and publication-use claims use A.10, G.11 and E.17 as applicable; chronology establishes none of them.

Cross-regime evidence window. A dashboard combines observations from two operating regimes. Identify the observation sets, their subject populations or carriers, temporal reference and aggregation window. Choose the operation and the claim it is meant to support. Under C.16, establish the measurement meanings, specification, scale and unit semantics, model/calibration conditions and population or time basis needed for direct comparability.

Any cross-basis conversion or comparison retains its operation rule and loss or uncertainty conditions. Use C.29 when a separate mathematical correspondence or reliance question remains. If the required compatibility is unestablished, retain separate results or narrow the claim rather than pool them as one supported aggregate.

Order-dependent calculation. In this constructed case, start with x = 1 and combine f(x) = x + 1 and g(x) = 2x by sequential application. Applying f then g gives g(f(1)) = 4; applying g then f gives f(g(1)) = 3. An OrderSpec permitting both orders does not establish one numerical answer or the independence needed to ignore order. For a unique prediction, establish which order applies or that every permitted order gives the same value on the input in question. In this example the two attainable values establish that the result is at least 3. A trusted observation of the final value can answer a question about an actual run even if its order is unknown. To explain how that value arose, establish the facts on which that explanation depends. If the task needs only the partial-order specification, that specification already answers it.

Work-interval aggregate. In this constructed case, independently admitted Work occurrences W1 and W2 occupy [0,2) and [3,5) hours under one declared clock reference, within window [0,5). For covered time, take the union [0,2) ∪ [3,5): its duration is 4 hours. For elapsed span from first start to last end, take the convex hull [0,5): its duration is 5 hours, including the gap. These are different warranted answers to different questions, following the A.15.1:9.1 Work-interval profile.

Union counts a shared instant once when intervals overlap. Its set-based policy and the hull policy are idempotent for duplicate input and independent of input order; another operator needs its laws. The two occurrences keep their separate identities and require no invented common Work or PhaseOf relation.

B.1.4:5.1 - Bias-Annotation

Bias riskFailureMitigation
Notation becomes ontologyGamma_ctx, Gamma_time, graph, or algebra wording is treated as the in-life object or relation.Recover the ordered or temporal relation first, then treat notation as a selected expression.
Sequence becomes workA method order, plan order, document order, or performed-work history is treated as the same thing.Name the claim and use the applicable method, description, work-plan, dated-Work, or evidence pattern.
Phase becomes levelA phase label is used as a new system level or a new whole.Recover the subject first: C.2.1 identity/edition law for an episteme, A.15.1 for Work, or the carrier’s identity rule and proper PhaseOf for another enduring individual. Open whole reidentification only when that question remains current.
Coverage becomes authorityA complete-looking timeline is treated as sufficient evidence or currentness.Use the applicable evidence, source-currentness, and temporal-adequacy patterns when those claims are current.

B.1.4:6 - Conformance Checklist

IDRequirementPurpose
CC-B1.4-1The aggregation claim identifies its subject, included inputs and relations, combining rule, required result, aggregation mode, ClaimScope when needed, temporal reference/window when relevant, and admissible use.Makes the aggregation usable without requiring a separate record when an ordinary answer suffices.
CC-B1.4-2Contextual aggregation identifies its ordered relations and OrderSpec. Temporal aggregation identifies its intervals, bearers, temporal reference and TimeWindow; the proper-phase profile also establishes one-carrier identity and the phase relations.Keeps order, temporal aggregation and proper-phase claims distinguishable.
CC-B1.4-3Independence, join, coverage, and overlap-policy conditions are present when the claim uses them.Keeps local composition reviewable.
CC-B1.4-4Method, method-description, work-plan, work-occurrence, work-resource, transformation, and whole-reidentification claims use the patterns that define or test them.Prevents B.1.4 from absorbing neighboring objects.
CC-B1.4-5Mathematical notation is treated as a selected lens or expression, not as the in-life object or relation.Keeps Gamma_ctx, Gamma_time, graph, and algebra language bounded.
CC-B1.4-6Use stays within the established operation, identity and coverage conditions. For an execution claim, establish the feasibility it requires. A guarantee of delivery also covers timely completion under the promised conditions. When a condition remains open, give any requested conclusion warranted across the admitted cases. Narrow or withhold the part that depends on the missing distinction; use the subject pattern for a distinct identity, change or whole-reidentification question.Preserves stops without requiring a stronger claim merely to finish an ordinary aggregate.

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

OverreadRepair
A sequence is treated as physical parthood.Recover ordered relation refs and use contextual aggregation; use part-whole patterns only for part-whole claims.
A phase label is treated as a new system level.Recover the carrier identity and phase relation. If a clear whole-reidentification question remains, use B.2 directly; use B.2.P first only when emergence-family wording hides the claim kind.
A planning order is treated as performed work.Use A.15.2 for work plan and A.15.1 for dated work occurrence.
A resource total is inferred from temporal coverage without its resource-accounting rule.Establish the resource claim under B.1.6. One account may state both the independently supported temporal and resource results.
A diagram or table substitutes for the independently represented object or relation.Establish that subject and the representation correspondence. A diagram or table may present or return the aggregate result; its form alone establishes neither the represented facts nor their identity.

B.1.4:8 - Consequences

The practitioner obtains the aggregation specification or result needed by the receiving use, with its rule and conditions recoverable in a sufficient ordinary explanation or an inspectable account. Gamma_ctx and Gamma_time remain optional expressions. Recovering the inputs and conditions takes work, but makes the result distinguishable from claims about performed Work, resources, transformation and whole reidentification.

B.1.4:8.1 - Rationale

Order-sensitive and temporal aggregation combine already grounded inputs under a selected operation. One continuing carrier may be considered through proper phases; separate Work occurrences or observations may supply intervals for a different temporal aggregate; and an order structure may be the desired result or an input to a further calculation.

Each case keeps its grounds: carrier identity and PhaseOf for proper phases, C.2.1 identity and obtaining edition relations for episteme history, A.15.1 for Work, C.27.TA for temporal facts, and the ordered relations, operation and conditions for the aggregate. Resource, transformation, evidence and whole-reidentification claims retain their rules.

Distinguish design-time possible order from run-time history. When both contribute to one use, state the correspondence between their claims; keep one or several accounts according to what that use needs.

B.1.4:8.2 - SoTA-Echoing

For the question “which aggregate answers this receiving use?”, B.1.4 adopts A.15.1:9.1’s Work-interval distinction: union answers covered time, while convex hull answers elapsed span. C.27.TA:0 and :4.2 explain how to state the bearer, temporal reference and interval on which either calculation relies. The operation and its conditions, rather than a generic total or operator label, decide the result.

In the Work-interval case above, the same inputs give a justified 4-hour covered duration and a justified 5-hour elapsed span. Either can be sufficient for its question; using an unqualified total would hide which question was answered. The order-dependent calculation similarly distinguishes a usable partial-order specification from a unique numerical result that its permitted orders do not yet determine. Sections :2-:4 therefore require the rule, result kind and applicable conditions while allowing the ordinary sufficient answer.

The additional burden is recovering those inputs, rules and conditions; an inspectable record is needed only for a receiving use that consumes it. These constructed comparisons support the stated mathematical and subject distinctions. They do not establish empirical effectiveness or a ranking of external engineering notations. Reopen the operation or result choice when the receiving question, input identities, temporal reference, relation facts or applicable operation law changes.

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 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 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.TA for positive temporal-aspect facts and C.27 for a separate temporal-claim adequacy question. Use C.29 when mathematical representation-choice, transfer or reliance remains unresolved. E.18 governs a selected transformation-flow structure; E.18.2 governs its mathematical description or that of a selected TFS network.

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 marked informative

B.1.5:1 - Problem Frame

Use this pattern when the question is whether identified Methods constitute one reusable Method. Their contributions may depend on order, guards, joins, shared constraints or simply satisfying distinct requirements of the whole. If the recipient must devise the arrangement, begin with B.1.5.CM and use the qualification below on the resulting proposal.

Typical moments:

  • a procedure, algorithm, or protocol 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 candidate or composite U.Method, already identified under A.3.1. The proposition that 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 candidate Method as its EntityOfConcern under its effective ReferenceScheme.

First useful move. Identify the reusable result or condition the recipient needs and whether the task is to qualify a proposed arrangement or to construct one. For each apparent step or branch, distinguish the object it denotes: 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 state the part, order, join, interface, and identity facts needed for that claim. If qualification fails, another useful result may remain, such as a description, plan, selected structure, or selector result, under its pattern. Use A.15.4 when the failed qualification reveals reliance on appearance.

Not this pattern when.

  • If the claim concerns one semantic way of doing and its composition is outside the question, use A.3.1.
  • If the claim is a claim-bearing episteme that describes a method or relations among methods, use A.3.2 and C.2.1.
  • If the claim is intended work, use A.15.2.
  • If the claim is a dated occurrence, use A.15.1.
  • If the claim is structural component parthood, use A.14; use C.13 for a needed construction account and B.3.5 only when its additional assurance profile is elected.
  • If the 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.

For a proposed composition, ask:

Given independently recovered U.Method parts,
which methodPartOf occurrences, 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 names this method-composition discipline. Use the patterns above for related objects and B.1.6 for resource accounting.

B.1.5:2 - Problem

When the objects and composition grounds are left unclear:

  1. Source-wording composition. A label such as “step”, “workflow”, or “algorithm” is accepted as method composition without recovering the 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.
  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 checking their compatibility, any needed adapter Method or governed correspondence, and the 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. The resource use, timestamps, telemetry and results of a particular execution are attributed to the Method itself. A reusable Method may stipulate a resource or time limit. Its use in a particular Work and the values actually observed need their own grounds.
  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

ForceTension
Method reuse vs source examplesTeams need a reusable way of doing, while sources often show only one description, run, or plan.
Order fidelity vs compact modelingImportant sequences and joins must remain explicit without turning every diagram edge into ontology.
Order vs simultaneous contributionA first–then condition must survive, while Methods that contribute together must not be invented as stages merely because they are described in sequence.
Whole-method identity vs relation usefulnessSome method-side relations are useful without asserting one composite method whole.
Interface exposure vs encapsulationA composite method must state which interactions callers may rely on and which remain internal.
Assurance vs executionAssurance needs joins, adapters, cutsets, and failure conditions; dated enactment, result, and evidence-use claims stay with their subject patterns.

B.1.5:4 - Solution

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

If the parts and arrangement are still yours to choose, use B.1.5.CM:4.1 to work from the whole result to the contributions and their conditions. Return here to test the resulting composition claim:

  1. Name the same A.3.1 candidate Method and 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 needs.
  3. For every whole-forming statement other than B.1.5’s 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 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. Retain any independently supported description, plan, structure, or other result under its subject pattern.

Minimal positive. BuildAndVerifyPumpUnit is already an 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, 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 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 receiving use needs a selected organization.

When a receiving use relies on the composition account—for example, planning, Method substitution, or assurance—check the questions below. They guide reading; they do not declare a schema or relation signature.

Composite-method qualification:
  candidate whole method: one U.Method already identified under A.3.1
  part methods: a non-empty set of 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:
    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:
    U.Work may enact the method only through A.15.1 enactsMethod
  other independently supported results if composition is incomplete:
    for example, a description, plan, selected structure, selector result, or Work claim
    use A.15.4 when reliance on appearance needs repair

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 an independently identified U.Method can be a method part; keep the other objects under their patterns.

B.1.5 governs MethodPartOfRelation, expressed in Plain register as methodPartOf(partMethod, wholeMethod). Both participants are 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 Methods, the relation is atemporal: there is no 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 family defined in B.1.5 even when enactments vary.

The same part Method may also stand in methodPartOf relations to several whole Methods. Test every pair against the construction rule of its whole. Each whole keeps its 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 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 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.

Composition cueWhat the claim must let a practitioner decide
serialwhich part Methods belong to the whole, what requires their order, and what permits the later Method to start. If it consumes a result of the earlier Method, establish how that result meets its precondition
parallelwhich branches have no prescribed mutual order, which contributions the whole needs and which conditions they must meet together. Where continuation depends on combining results, establish that they can be combined. Account for shared resources across the permitted executions, including simultaneous access when required
guarded choicewhich alternative Method is selected, the selection condition, what happens when no guard or several guards hold, and which whole contains that choice
iterationwhich part Method repeats, what establishes another iteration, and the stop or failure condition
Method refinement or substitutionwhich Method may replace which other Method, for which use, and which whole semantics, joins, and exposed interactions must remain invariant
fallback or dispatchwhich primary and alternative Methods are involved, the trigger for using the alternative, and whether the statement belongs to this whole or only to a selector registry
adapter or typed joinwhich upstream result meaning satisfies which downstream precondition, which adapter Method or governed correspondence is needed when those meanings differ, and which condition or failure route governs continuation

Use B.5.MR for refinement or abstraction between models of Methods. Establish a comparison between the Methods themselves through A.3.1’s identity and relation conditions. The model comparison alone replaces no constituent Method.

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

  1. Preserve order. Ask what must finish or become true before another Method can start or continue. Identify the source of the order. A protocol can require two independent assessments in sequence with the first assessment sealed until both finish. Other Methods need an actual handover. For those, identify the result, any join or adapter, and what happens when the receiving conditions fail. Keep a first–then result as an unfolding or order claim; its position does not make it a subject level.
  2. Test independent and simultaneous contributions. Recover which contributions the whole requires, which can occur in either order, and which must overlap or use a shared resource. A construction rule can settle those questions for the allowed executions before any Work occurs. Where a working situation exposes a dependency, establish how far it applies. For a claim about dated occurrences, identify those Work individuals and their obtaining A.15.1 enactment relations.

Both answers may be true. A Method can contain an 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.

A functional layer can name a responsibility, such as supervising a process. Recover the Methods that realize it and the systems that perform them when those relations matter. Several Methods can serve the same layer while belonging to different encompassing Methods. For a proposed model of one Method, check which admissible executions it groups together. It must distinguish those requiring different caller actions, results or grounds for the promised use. If comparing models for refinement, keep the Method and the question fixed under B.5.MR.

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 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: source use and the continuation rule identify which claim, EntityOfConcern, and scheme features must be preserved or may deliberately change, and the 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 pattern or declaration defines applicability and occurrence identity, while case facts establish obtaining, continuation, or cessation where relevant.

When the receiving use needs to combine order information, apply B.1.4 to the selected inputs, combining rule, and required order, join or independence conditions. State the OrderSpec, the required ordering over the identified positions, in adequate prose or the representation consumed by the receiver; identify each claimed relation occurrence under its predicate.

An adequate explanation or existing account may suffice. Materialize a separate aggregation record only when the receiver needs it. The account and optional notation describe the composition facts; they add no Method identity discriminator and make no relation obtain.

The composite-method qualification holds only when the candidate Method also has its 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 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 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 a 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 for structural parts of a holon, C.13 for their construction account when needed, and B.3.5 when the additional assurance profile is elected. Use B.1.5 for the contribution of reusable ways of doing to a larger reusable way. A project may need both claims; each retains its participants and truth conditions.

B.1.4 can supply an order aggregation, partial-order test, or join/independence account. Recover the selected inputs and combining rule, including the required ordering specified by OrderSpec; B.1.5 still decides whether the Methods and their construction facts constitute one composite U.Method.

When the claim is a proper temporal restriction of one unchanged non-Work carrier, apply that subject’s 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 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 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

State the boundary decisions in sentences: what a caller may request, what it must supply, what result or preserved condition it may rely on, and what stops the interaction. Name any needed adapter, order condition, bound, or assurance limit. Explain an encapsulated interaction when a plausible caller could otherwise rely on it. This can complete an internal boundary account.

When a receiver needs the published account, say which MethodDescription edition is available, to which declared audience, for which bounded use, through which expression and carrier. A.3.2 and C.2.1 identify the description; E.24.PUB supplies the publication relations and their progressive explicitness. Name a reusable boundary-account form only when its arrangement rules matter. The form, its conforming expression and the carrier retain separate identities.

For disputed availability or publication identity, recover E.24.PUB’s five participants <description edition, audience declaration, bounded-use declaration, expression, carrier>, its supporting expression and bearing relations, and the maximal continuous availability interval. If form conformance is used, the same expression must support the form-mediated claims. Publication activity is separate; identify dated publication Work only when that occurrence is asserted. Names and links retain their designation meaning.

Optional prompts for the receiving account:

  • the described Method and the description edition used;
  • exposed and forwarded interactions, accepted input meanings, preconditions, intended results or preserved conditions;
  • required invariants, failure routes and stops;
  • order or join conditions, adapters and applicable bounds that affect the receiver’s use;
  • the audience and bounded use when the account is published.

Use an existing adequate account without adding a form. These presentation prompts supply no Method parts or composition facts.

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

B.1.5 evaluates and grounds the composite-method qualification of a 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 U.Method only when the A.15.1 method-enactment relation obtains. Recover each 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 assignment-bound attribution through the same obtaining A.13 assignment; missing or failed F.6 alone leaves independently grounded Work and enactment intact. If the same finding invalidates a premise consumed by A.13 or A.15.1 admission, recheck that premise and its dependent conclusions while preserving independently grounded history and relations.

The performing System acts under the recovered relations. An assertion or occurrence description may cite those facts and the MethodDescription used.

Parameter bindings, affected referents, resource use, telemetry, retries, results, transformations, production, evidence, evaluation, delivery, and acceptance remain separate objects and relations under their 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 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 performer System recovered through A.13; only when this reader check consumes assignment-bound attribution, also name the 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: 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 enactsMethod(workPart, submethod) occurrence.

If one of these grounds is missing, leave that claim unresolved while retaining the independently supported claims. A Work part and a submethod each need their grounds. 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 a 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. To plan enactment, recover the Methods, methodPartOf facts, other whole-forming claims at their A.6.RCD dispositions, needed order and joins, interface boundary, invariants, and whole-level commitments. A resulting U.WorkPlan uses A.15.2 and may cite the MethodDescription edition on which it relies. Identify dated planning Work under A.13 and A.15.1 only when that occurrence is asserted; planning and its product remain separate from Method identity.

  • Performed-work use. Recover each performer through A.13, let A.15.1 independently admit the Work, and recover the enactsMethod occurrence for the whole Work. Add the covering A.2.1 assignment and F.6 relation only when this use consumes assignment-bound attribution; missing or failed F.6 alone leaves independently grounded Work and enactment intact. If the same finding invalidates a premise consumed by A.13 or A.15.1 admission, recheck that premise and its dependent conclusions while preserving independently grounded history and relations.

    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 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 order claims and conditions at their selected A.6.RCD dispositions.
  • A throughput or quality bound identifies its characteristic, the conditions it covers and the rule that warrants the bound. A critical path, a bottleneck, parallel capacity or a bound on the combined result may supply those grounds.
  • A claim that improving a submethod, adapter, or typed join improves the composite must name the characteristic and conditions under which that improvement transfers.
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 transformation independently under A.3.4. If a claim needs transformation composition and no 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

When the organization itself answers a needed question, use A.22 to select a U.Structure over independently identified Methods and obtaining relations. State its four identity discriminators: constituents, selected relation occurrences, applied constraints, and use frame. Ordinary prose or an existing adequate description can supply them.

An asserted dated selection Work needs its A.13/A.15.1 grounds; add an operation binding or result episteme when the receiving claim needs one. A local comparison can also suffice without selecting a structure. MethodRelationStructure is a local designator for a selected structure, not a new U-kind.

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

A selected structure is useful when the question concerns relation organization and does not require a composite Method.

B.1.5:5 - Archetypal Grounding — Worked Slices

B.1.5:5.1 - Manufacturing Recipe

AssembleFrame, InstallMotor, AdaptMotorConnector, RunFunctionalTest, and BuildAndVerifyPumpUnit are 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 this 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 labels for local compound claim content in the 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 enactsMethod occurrence without four corresponding work parts. If a separately admitted MotorInstallationWorkPart-2026-07-29 exists, it enacts InstallMotor only through its 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.

The two claims can finish this protocol comparison. If the receiving question instead needs a selected U.Structure, recover all four A.22 discriminators: constituents, independently obtaining relation occurrences, applied constraints, and use frame. The local claims cannot be relabelled as relation occurrences. Identify dated selection Work only when that occurrence is asserted, and a separate result episteme when the judgment must persist.

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 an expression that conforms to a publication form. A U.MethodDescription edition is the claim-bearing episteme conveyed by the expression; a publication occurrence makes that edition available to an audience for a bounded use.

For intake Work, recover each 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 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 A.3.1 Methods, that candidate qualifies as composite only when methodPartOf occurrences, whole-forming claims at their A.6.RCD dispositions, an account of the accepted inputs and outputs, and a rule identifying the Method across its admissible variations are established. Include the joins, fallback routes, stops and interface decisions on which this particular pipeline depends. Where the grounds for Method composition are missing, identify what the graph does supply. It may be a MethodDescription, a mathematical lens, or an account of the mechanism. A claimed A.22-selected U.Structure needs its selection basis and receiving use.

Suppose one dated training Work enacts the 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 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 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 states that the Method exposes Submit() and ReleaseArtifacts(), forwards CrossValidate.Folds(k), and encapsulates ad hoc scrubbing utilities. A submitting researcher can use this boundary account to distinguish supported calls from internal operations.

For the published account, EvidenceSynthesisMethodsPage-2026-07 is the digital carrier of an ordered-text expression of that edition. SubmittingResearchersAudienceDeclaration-v1 identifies the authorized submitting researchers; SubmissionAndArtifactReleaseUse states the supported submission and artifact-release operations, their conditions and any needed stronger-use boundary. If the selected SubmissionReleaseBoundaryAccountForm-v3 constrains the arrangement, check that this expression conforms to it.

E.24.PUB tests whether the same expression conveys the required claims, is recoverable from that carrier, and is available to the declared audience for that use. Its five participants and maximal continuous availability interval identify the publication occurrence. Uploading or granting access may establish that availability; an assertion of publication Work has separate A.13/A.15.1 grounds. Availability alone establishes neither actual use nor the Method’s composition facts.

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 an order before the public performance starts; a failed safety check may stop the unfolding. Preserve that order when the 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 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 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 continuation condition, but do not invent order among concurrent contributions.

B.1.5:6 - Bias-Annotation

The following risks concern cross-domain order-sensitive composition of already identified U.Method values. B.1.5 does not cover sole-Method identification, description-only organization, dated Work decomposition, structural mereology, or transformation composition without a governor.

  • Gov: each methodPartOf occurrence and each other whole-forming claim stays with its 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 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 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 order and simultaneous contribution across domains.

Construction and boundary accounts are useful when a join or outside reliance depends on them. Keep a local claim when it supplies the needed result, and use another pattern for a different object or relation.

B.1.5:7 - Conformance Checklist

CheckRequirement
CC-B1.5-1The candidate whole and every claimed Method part are independently identified as U.Method values under A.3.1 before B.1.5 tests the composite-method qualification.
CC-B1.5-2Step wording, description nodes, plan items, Work occurrences, file modules, graph edges, registries, source wording, mechanism material, formal substrates, mathematical lenses, and evidence or publication-use claims are not Method parts by position or label. Keep each with its governor unless it is independently identified as a U.Method and methodPartOf separately obtains.
CC-B1.5-3Every methodPartOf(partMethod, wholeMethod) occurrence passes the required-contribution or admitted-alternative test. Its identity is determined by the ordered pair; all bounded alternatives may obtain simultaneously, Work selection does not toggle them, and a changed admitted-part set reidentifies the whole Method or leaves the claim open. One part Method may have several whole Methods only through separately supported pairs and separately qualified whole constructions; no unique parent or closure property follows.
CC-B1.5-4Every serial, parallel, guarded, iterative, fallback, adapter, substitution, or typed-join use states a decidable claim and selects A.6.RCD’s lightest sufficient disposition. A relation kind and occurrence are required only after independent admission for a named occurrence-semantics use.
CC-B1.5-5The already identified candidate Method states whole-level participant meanings, applicability, preconditions, intended effects or preserved conditions, invariants, bounds, accepted inputs and outputs, failure and stop conditions, interface decisions, and reidentification rule before its composite qualification is accepted.
CC-B1.5-6Exposed, forwarded, and encapsulated interactions are distinguished because changing the reusable action or admissible boundary changes Method identity. A named caller system, planner system, auditor, substituting-method selection use, or assurance use determines whether the boundary account must be explicit or published; reliance does not create its identity effect.
CC-B1.5-7A boundary account states the interactions and conditions needed by its receiver. For publication, distinguish the MethodDescription edition, audience declaration, bounded-use declaration, expression and carrier; add a reusable form when its conformance matters. E.24.PUB supplies expression/bearing predicates and availability identity when needed. Publication Work and designation content remain separate claims.
CC-B1.5-8A selected A.22 structure has its four identity discriminators: constituents, obtaining relation occurrences, applied constraints, and use frame. Dated selection Work, an operation binding, or a persisted result episteme has separate grounds when that claim is needed. A sufficient local comparison requires no selected U.Structure.
CC-B1.5-9When the composite method needs a separate higher-level reidentification or emergence explanation, use B.2 in addition to the B.1.5 method reidentification rule.
CC-B1.5-10A temporal slice, episode, event-log segment, telemetry interval, engine stroke, detector component, or U.WorkPlan item is neither a Work part nor a Method part by appearance. Keep each with its subject pattern. A Work part enacts a submethod only through a separate A.15.1 enactsMethod occurrence; whole Work may enact the whole Method without mirrored Work parts.
CC-B1.5-11A needed order aggregation preserves B.1.4’s selected inputs, combining rule, order relations and required join or independence conditions. The OrderSpec may be stated in ordinary prose; use a separate record when the receiver needs it; neither adds Method identity nor establishes relation facts.
CC-B1.5-12Typed joins name the upstream intended-result meaning and downstream precondition, plus an adapter or governed correspondence when those meanings differ, and a failure route; signatures do not establish the holder’s ability.
CC-B1.5-13Dated Work, performing Systems, separately declared assignment species, assignment occurrences, obtaining F.6 attributions, resource use and costs, yields, dissipation, telemetry, results, and production, together with separate evidence-, publication-use-, evaluation-, delivery-, and acceptance claims, use their subject patterns and do not become Method identity fields.
CC-B1.5-14Assurance hooks identify the dependencies and scope the B.3 claim uses, including cutsets, fragile joins, adapter points or CL-sensitive mappings when relevant; no performance or quality claim follows from composition alone.
CC-B1.5-15A method-composition claim establishes no A.14 structural-component relation, work-part relation, or selected-structure identity unless the corresponding predicate separately obtains.
CC-B1.5-16Method parts, Work parts, common referents, method order, and temporal adjacency establish neither transformation parthood nor a composite transformation; missing transformation-composition governance returns missing-governor[transformation-composition] for the proposed whole and independently identified changes, without an atomism inference.
CC-B1.5-17A composition inferred from a first–then or vertical account preserves its continuation conditions and identifies whether contributions are serial, unordered or required together. The Method’s construction can establish this organization. A claim about how the work actually proceeded has its own occurrence grounds. Source order creates no level; simultaneous use creates no Method part, composite Method, Work part, or level.

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

Anti-patternRepair
“The workflow diagram is the composite Method.”First govern the diagram as U.MethodDescription or another representation; identify the candidate and part Methods under A.3.1, then test methodPartOf, whole-forming claims at their A.6.RCD dispositions, whole semantics, boundary, and reidentification.
“Step A is part of the Method because it is a box.”Recover whether the box denotes a U.Method, description node, plan item, Work occurrence, claim, or lens expression; test methodPartOf only for an independently identified Method.
“Parallel branches can join because the picture rejoins.”State which branches may proceed in either order, what the receiver needs from them and which combinations satisfy that need. If the Method requires a join, specify its condition, any necessary correspondence and what becomes possible or remains blocked when it fails. Use A.6.RCD’s lightest sufficient disposition.
“The production plan lists five Methods, so the practice has five stages.”Preserve any setup, handoff, or continuation order. Recover any required joint contribution from the arrangement. Use the occurrence evidence when the question concerns a performed case. The plan’s row order establishes neither a total sequence nor a subject level.
“The selector table is the Method.”Use G.5 for the selector. Select an A.22 structure when the receiving use needs that organization and all four discriminators are established; otherwise retain the sufficient local comparison. A composite Method needs its construction and whole-level commitments.
“The run proved the method structure.”Record the run as U.Work; relate it to the method through enactsMethod and use evidence only through its governing relation. A successful run neither creates method parts nor settles reidentification.
“The phase is a method step.”Recover the subject: use the carrier’s identity rule plus proper A.14 PhaseOf for one unchanged non-Work individual, C.2.1 for distinct MethodDescription epistemes and any obtaining edition relation, or A.15.1 for Work temporal parts and occurrences. None is a Method part unless a U.Method and methodPartOf independently obtain; use B.2 only for a separately current whole-reidentification, supervision, or closure claim.
“The join improves throughput, so the method has emergence.”Identify the characteristic and the dependencies that govern the claimed gain, such as a bottleneck when one is decisive. Then open B.2 only when a separate whole-level reidentification claim remains.
“The boundary-account prompts define the Method.”Recover the Method and its construction facts first. The account describes those facts; a selected form constrains eligible expressions. Use E.24.PUB when the publication relation or form conformance matters.
“The boundary account is a nice diagram.”State the interactions and their conditions. If a receiver depends on publication, identify which description edition is available to which declared audience and use through which expression and carrier. Open E.24.PUB’s further predicates for the unresolved publication question.
“The same Work and referent make the transformations one composite.”Identify each transformation under A.3.4. Without a transformation-composition governor, return missing-governor[transformation-composition] for the proposed whole and independently identified changes; infer neither composition nor atomism.

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 Methods are parts, which ordinary whole-forming claims and constraints qualify the candidate as composite, which interactions belong to its boundary, what Work enacts it, and where a stronger claim must stop.

The cost is proportionate explicitness: 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 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 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 B.1.5 construction facts.

B.1.5:11 - SoTA-Echoing

The following published treatments provide bounded comparisons for Method composition. Their models illuminate distinctions; applying those distinctions to FPF Methods uses the construction and identity tests above.

Published treatment and its contributionUse in B.1.5Applicability limit
Case and decision models in CMMN 1.1 (2016) and DMN 1.5 (2024), object/event records in OCEL 2.0, and traces in OpenTelemetry 1.58.0 describe different objects. These named editions supply historical comparison examples; A.15 and A.15.1 govern the Work claims.Distinguish a reusable composition account from records about its enactment. Recover the Methods and construction facts, then use the Work or evidence predicates for what happened.A model or telemetry representation can support a claim without itself being the Method or establishing Method parts.
Bosman et al., “A Calculus for Scoped Effects & Handlers” (2024) separates syntax from handling semantics and provides explicit forwarding of scoped operations. Matache et al., “Scoped Effects as Parameterized Algebraic Theories” (2024) develops equational reasoning for scoped operations.Use these software examples to examine scope, typed joins, forwarding and boundary behavior. Explain the preconditions, result meanings and failure routes of the proposed Method composition in its domain.These calculi supply no general Method identity for manufacturing, clinical or organizational work. An FPF boundary change affects identity when it changes the reusable action or admissible boundary under A.3.1.
Gogioso et al., “Constructor Theory as Process Theory” (2023) connects abstract tasks to physical processes through a compositional formal treatment. A.3.1 develops the Method-side comparison.Retain the distinction between a specified task and a process that realizes it when examining composition and enactment.The formal bridge does not by itself identify an FPF Method part or dated Work; use their predicates.
Borgo and Righetti, “Towards Applied Constructional Ontology” (2025) examines choices and difficulties in applying constructional approaches to foundational ontologies. A.1 develops the construction-sensitive comparison.State constituents, construction facts and identity choices instead of treating a diagram or label as a constructed whole.Method composition retains its predicate. Its order is not structural parthood, and the source’s exploratory ontology comparison supplies no ready-made Method composition rule.

B.1.5:12 - Relations

B.1.5.CM constructs the prospective whole, constituent contributions, joins and boundary account that this qualification consumes. C.32.MWA.PP separately compares performance and provision arrangements. Useful cooperation or a shared provider does not supply a missing Method whole.

  • 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 candidate Method and every part Method before B.1.5 tests the composite-method qualification; B.1.5 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 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 when the receiving question needs order aggregation or its specification, with the selected inputs, combining rule, order relations and required join or independence conditions. OrderSpec states the required ordering; it needs no separate record when ordinary prose suffices.
  • Uses A.3.2 and C.2.1 for MethodDescription claims and identity. Uses E.24.PUB when publication affects the receiving use: start with the edition, audience, bounded use, expression and carrier; recover further expression, bearing, form-conformance or availability predicates for the question that remains. Publication Work and designation remain separate.
  • Uses A.22.CGUS when a 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 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, assignment occurrences, and obtaining Work–assignment attributions. The Method does not act, and neither a system-role kind nor an assignment performs Work.
  • Uses B.1.6 to construct a resource-accounting rule for prospective Works, derive a conditional bound from a proposed arrangement, or aggregate actual use through Gamma_work. A report of actual consumption relies on the relevant Work and resource relations.
  • Uses B.3 for cutset, weakest-link, CL-sensitive mapping, and assurance claims; composition alone supplies no assurance verdict.
  • Uses A.22 when the receiving use needs a selected organization and its four identity discriminators are established. Ordinary comparisons can finish without that claim; a dated selection occurrence has its separate Work grounds.
  • Uses C.13 only after B.1.5 supplies 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; uses B.3.5 only when its additional assurance profile is elected for the structural claim.
  • Uses B.2 when a separate higher-level reidentification or emergence-family explanation is current; ordinary composite-Method identity still needs its 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.
  • Use C.29 for an unresolved mathematical representation, correspondence or transfer question; an adequate local calculation can suffice. Use A.6.1 for a needed law-governed operation declaration or application binding, and E.20 when a proposed change affects mechanism meaning, suite semantics, wiring, governing-definition assignment or citeable-token meaning.
  • 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 governor supplies 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 from the work the recipient needs to explain, carry out or change. If the question starts from an action, ask what encompassing work is being done through it and how. If it starts from a delivery, an ongoing service or a shared performance, work back to the actions that constitute it and to the contributions it receives from elsewhere.

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. 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’ 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 enactment needs the performed connection.

B.1.5.EW:4 - Solution

Trace the constituent–whole connection in the direction needed for this question. From an action, recover what larger work is performed through it. From an encompassing performance, recover how the actions together constitute it. Preserve before-and-after dependencies wherever they affect that inference.

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

Identify the action or encompassing work the recipient asks about and the interval relevant to its use. For an actual occurrence, ground the account in the performance. For a proposal, say what would occur under its conditions. When the assignment is to teach someone to perform the analysis, leave that person the choice of a relevant action or whole from the working situation, unless the commission supplies it.

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

Follow the constituent–whole connections needed for the action, decision or explanation entrusted to the reader. Different work arrangements can produce the same output. Recover which one occurred when it matters who performed the work or how the participants coordinated. A known organizing rule can justify a connection across several scales. Inspect an intermediate whole where its arrangement could change that connection. If the action serves several wholes, include those whose conditions or outcomes bear on the question.

For a decision about who will perform the action or what the performer needs to learn, determine what they must be able to do and which contributions others may supply. A question about whether an action formed part of a completed Work can already be settled by the organizing rule and evidence about that occurrence. 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 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

When the question concerns coordination at a particular 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.

Follow the direction of dependence the question asks you to explain. To determine what a change in the encompassing work requires of a constituent, vary the relevant whole condition and trace it to the action or its coordination. To determine what a constituent permits the encompassing work to achieve, carry its constraint into the proposed organization. Apply an established rule directly when it answers the question. A comparison or trial is useful when a consequential dependency remains open.

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

Where correction is needed, choose the correction that the recovered connection supports:

What prevents the encompassing performance?Useful continuation
A needed operation is unknown or cannot be performed.Recover, learn or obtain that contribution; retain the whole conditions while doing so.
The operation is understood but this execution violates its conditions.Correct the execution and inspect the affected encompassing result.
Individually adequate operations do not fit together.Change their coordination, order, shared conditions or allocation; examine the burden moved elsewhere.
The reference or requested result cannot be met under current conditions.Reconsider that reference, demand or available means with the participant who can change it.
The description assigns a connection that the work does not support.Repair the account; do not change the work merely to fit the diagram.
A constituent could be replaced.Use B.1.5.RS to preserve the requirements of its receiving wholes.

A diagnosis may remain conditional when two explanations fit. For a discretionary inquiry, obtain further information where it can change the action or explanation the recipient needs and warrants its burden under C.11.DUA. Complete any separately commissioned observation under its own conditions. 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.

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. If every intermediate sum must count only accepted observations, apply the eligibility rule before each affected update. If the report promises a final total, documented reconciliation of duplicates before delivery can also give the required result. In the running-sum algorithm each new addition consumes the previous accumulator.

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

B.1.5.EW:6 - Bias-Annotation

An observer can recognize their 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. 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?
  • Do the selected actions, enclosing work and any external contributions explain the result at the scope requested? A common organizing rule may cover several connections.
  • Where the question involves a change, does the account explain the dependency in the required direction between constituent action, coordination and encompassing Work?
  • Are 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

FailureRepair
Three level names stand in for an explanation.Show what the selected action does in each encompassing performance at the chosen moment.
A stage list conceals current constitution.Explain both what is done through the action now and which result must become available later.
Every description creates another Work and another time charge.Use the performed history and the receiving accounting question to identify occurrences and parts.
All constituents must run at once.Identify the active constituent and preserve the other constituents’ timing conditions.
Successful isolated practice is treated as mastery of the combination.Practise the relevant whole and vary a condition that changes coordination.

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 how the conditions of that work affect the action—a lifecycle account is a serious but incomplete alternative. It usefully preserves preparation and delivery, and the precedence relations between activities. 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 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. Reconsider the proposed connection if its explanation rests only on causal influence or if the comparison contradicts the claimed dependence. Use a simpler subject Method when it supplies the same useful result. 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 Method Replacement in Its Encompassing Uses

Type: Method pattern Status: Stable

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 error bound can preserve the order of well-separated options while leaving a value near a decision threshold unresolved. The same bound can settle a threshold when the entire interval falls on one side of it.

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?”

An assessment identifies the uses preserved, uses needing adaptation or restriction, and uses for which the replacement is incompatible or unresolved. This can finish a request for a compatibility judgement. Choosing and introducing a replacement can be a further assignment. One decisive comparison may be enough. Use an available argument or counterexample when it decides compatibility. A trial commissioned as a separate deliverable remains due on its agreed terms.

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 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 can reduce 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 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

Follow the proposed change to each receiving use covered by the decision. An indirect use can matter even if an intermediate whole returns the same value, for instance when its timing or explanation changes. For a change restricted to one use, establish any consequences for others through resources, commitments or interfaces shared with it. For a wider adoption claim, establish which uses are covered and why the argument applies throughout that scope.

Bound the search by the proposed adoption and its conditions. An interface rule that guarantees every required contribution can cover a class of unnamed users. If an uncovered use could alter the decision, restrict the adoption to the supported scope or obtain the missing condition.

For each 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 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.

When one replacement must support several uses, follow their permitted combinations over the relevant period. Two uses can exhaust the same finite supply even in succession. A single configuration may work for all of them, or a choice by the authorized participant may depend on information available before the commitment. Establish that the proposed arrangement meets the shared and individual requirements under those conditions. If only one specified use is commissioned, test the dependencies needed for that use.

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

Comparison resultWhat can follow
The needed contribution and conditions are preserved.Report that the replacement is compatible with that use under the established conditions.
Preservation holds only under a narrower condition.Identify the condition of compatibility and the uses requiring another solution.
An adapter or changed combination can restore the needed contribution.Treat that adaptation as part of the candidate and check its burden and behavior.
A required contribution is lost.Reject the replacement for that whole, change the requirement through the relevant decision, or choose another candidate.
Information does not distinguish compatibility from failure.State what the supplied evidence establishes and which condition would decide compatibility. Seek further evidence when the decision warrants that inquiry or when obtaining the evidence is itself commissioned.

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

If you are commissioned to recommend or choose an alternative, compare the compatible options at the supported scope, including adaptation, learning, operation and maintenance costs. Separate variants can be worthwhile when their different strengths justify their cost. The person with authority over adoption decides whether and when to introduce the chosen replacement.

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.

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 an argument appropriate to that claim. Use B.3 when a named assurance claim about its support is current; 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 a 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 can establish a strict ordering between two alternatives when their estimated values differ by more than 4 and both estimates satisfy that bound.

Another whole must decide whether the quantity exceeds 100. At an estimate of 99 the error bound alone gives the enclosing interval [97, 101]. It leaves the decision open. A separate bound on admissible values may settle the threshold even without a more accurate estimate. At an estimate of 95, the same error bound puts the whole interval below 100 and can settle that 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 needed by the encompassing sequence. If an allowed cue can arrive and its response window can close between successive snapshots, the snapshots alone cannot guarantee a timely response. Known synchronization or another timely source may still guarantee it. 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 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?
  • Does the comparison cover the receiving uses claimed, by their individual conditions or by a rule that applies throughout the proposed scope?
  • Does the comparison carry the changed contribution through each affected use?
  • When one realization must serve several uses, does the design cover their permitted combinations and shared constraints over the promised interval?
  • Does the conclusion preserve its conditions and evidence reach?
  • Are adaptation costs and a reconsideration condition included where they change adoption?

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

FailureRepair
One matching output stands in for preserved behavior.Recover the timing, interaction or property used by the whole and test that contribution.
Compatibility in one whole is exported to every user.Separate receiving uses and restrict the conclusion accordingly.
Every implementation detail must remain unchanged.Preserve what the declared use relies on; permit changes outside that dependence.
An adapter is omitted from the candidate’s cost or failure analysis.Include the adapter in the candidate arrangement and follow the combined behavior.
A successful trial becomes an unconditional guarantee.State its supported scope and establish stronger claims only when required.

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. A common argument may cover differing conditions and contributions when its bounds establish each required result.

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. 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 an 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 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.
  • Use C.29 when a separate question about mathematical representation, result transfer or unsupported reliance remains 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.5.CM - Construct and Qualify a Composite Method

Type: Method pattern Status: Stable

Primary working result: a bounded composition result whose whole, participants, and load-bearing relations are independently supported; a prospective candidate Method account; or a useful narrower claim. Include the proposed relation sets, conditions and unresolved questions needed by the receiving use. Writing the account creates neither the Method nor an obtaining architecture.

B.1.5.CM:0 - Use This When

Use this pattern when someone needs a reusable way to achieve a result or maintain a condition through several contributions, or when a decision depends on a proposed Method’s constitution. The designer may have a working problem and no list of constituent Methods yet.

Begin with what the recipient must be able to do or rely on, the circumstances covered and the choices entrusted to the designer. If an arrangement is already proposed, recover its semantics and the relations that carry its contributions. If construction is commissioned, use §4.1 to choose those contributions and organize them into a candidate.

The first useful result is two-branched. If the whole and participant Methods are identified and the required relations are shown to obtain, record the bounded composition result. Otherwise return the prospective account or partial claim supported by the evidence. That account can finish a present design comparison while whole identity or relation truth remains unresolved. For a discretionary trial, compare its attainable contribution with its burden and feasibility. A separately commissioned realization or trial remains due on the agreed terms.

Do not require prior performance of C.32.MWA.PP when equivalent proposal content is already available. Do not treat a coherent description, selected architecture, WorkPlan, tool implementation, or successful first trial as Method construction or identification by itself.

B.1.5.CM:0.1 - Working Distinctions

Name used hereMeaning
proposed Method wholeA claim that several contributions form one reusable Method for a stated use. It may be no more than a candidate account.
whole semanticsIntended result or preserved condition, reusable procedure or invariant, applicability, participants, permitted variation, bounds, and reidentification rule.
participant statusWhether each named participant is an identified Method, candidate account, other kind, or unresolved subject.
obtaining composition resultA result about an identified whole and identified participant Methods whose required B.1.5 relations are independently shown to obtain for the bounded claim.
prospective candidate accountAn episteme proposing a possible reusable whole while identity or relation conditions remain unresolved.
relation setNamed proposed or obtaining composition, order, result-use, allocation, support, authority, or other relations. Their truth statuses remain explicit.
realization/test WorkPlanA plan for later Work that could implement the proposal and return observations. It is not performed Work and does not by itself establish that the Method exists.

B.1.5.CM:1 - Problem Frame

Method Engineering often produces coherent proposals before the proposed practice exists. Situational Method Engineering and design-Method research offer useful construction and adaptation moves, while FPF keeps the proposed account, world-side Method, MethodDescription, WorkPlan, performed Work, and obtaining relations distinct.

A proposal can state an invariant, guards, variants, participant contributions, stops, and a bounded trial when one is selected. The error is reporting possible-future content as already obtaining.

B.1.5.CM:2 - Problem

One failure declares a whole whenever a document gives several steps a shared name. Another refuses to state anything useful until a mature Method has already been identified. A third treats participant co-use, Work order, or a successful tool integration as sufficient evidence for methodPartOf.

The first error overclaims, the second prevents learning, and the third confuses several relation structures. A prospective or partial account can support present comparison or later realization while keeping uncertainty explicit.

B.1.5.CM:3 - Forces

ForceTension
Useful proposalA project needs a coherent possible-future account, while coherence does not identify a Method.
Composition evidenceParticipant Methods and relations may be supported unevenly, while one missing load-bearing relation can defeat the whole claim.
VariationA reusable Method permits bounded variation, while unlimited adaptation destroys reidentification.
TrialabilityA WorkPlan can make uncertainty testable, while planned or performed Work does not backdate Method existence.
Useful partial resultA partial result must support its receiving use while keeping unresolved identity or relation claims explicit.

B.1.5.CM:4 - Solution

B.1.5 supplies the composition test. This construction supplies the candidate whole, constituent contributions, interfaces and grounds to which that test applies; it can also return a useful relation account below the whole-Method threshold. Use an already complete B.1.5 result directly rather than reconstructing it.

From the required result, construct the missing arrangement or recover the arrangement to be assessed. Test whole and participant identity separately from whether their proposed relations obtain. Return the design or the judgement the recipient needs under the conditions established.

B.1.5.CM:4.1 - Pattern-Use Unfolding

  1. Name the receiving use. State the result or preserved condition, situation family, intended users or performers, and consuming decision. Identify the configuration or edition and time window when they change the claim or its use.

  2. Develop the whole action. For each admissible use, ask what must be achieved, preserved or available by the next decision. Work back to what must be done within the Method and what the caller or another provider may supply. A needed input can be obtained externally. When obtaining or checking it is itself part of the promised way of working, provide an operation for it. Combine or separate candidate Methods where their variation changes the whole action, an interface or a condition the caller relies on. Identify the entry and exit conditions, permitted variations, bounds, stops and reidentification rule the claim needs. Use an existing construction or invariant where it supplies these grounds. State which conditions are proposed and which are independently established.

  3. Preserve participant statuses. Identify each Method under A.3.1 where supported. Keep candidate accounts and other subjects at their existing statuses.

  4. Name the relation sets. State every load-bearing proposed or obtaining relation, including Method composition, Work order or overlap, result use, allocation, support/provider access, authority, and description correspondence as applicable. Do not infer one relation from another.

    Carry a permitted situation through the proposed arrangement. Can its participants deliver the required result together under the available information, resources and authority? Hold the result of one part fixed and vary its timing, its use or another part’s choice if that can change the whole result. Follow such a difference into the constituent or enclosing Method that governs it. Keep model distinctions needed for the caller’s action and for explaining why it is supported. An argument covering the permitted variations can establish this fit for the design before any enactment.

  5. Test the positive branch. Record an obtaining composition only when the whole and parts are identified as Methods and the required B.1.5 relations are shown to obtain within the bounded claim.

  6. Return the prospective branch when needed. State the candidate whole, participant statuses, proposed relation sets, guards, adapters, alternatives, recovery, variation points, burdens and unresolved conditions needed for the receiving use. For a design commission, supply how the chosen contributions work together and under what variation the proposed Method will still serve the caller. For an evaluation, an identified incompatibility may itself decide the question.

  7. Settle the commission at the supported scope. A grounded fragment or an incompatibility can complete a question about that relation or about the feasibility of a proposed arrangement. If a required contribution or connection is still yours to design, construct it. Where a necessary condition cannot be provided, state what the supported part delivers and what prevents completion.

  8. Choose a useful continuation when needed. For a discretionary implementation or trial, use C.11.DUA to compare its attainable contribution with access, allocation, authority, time and other burdens. If the commission requires that performance, carry it out under its conditions or identify what prevents it and who can resolve the obstacle. When that Work is selected, name its observations, acceptance and failure conditions, any required authority, and the reconsideration rule; prepare a WorkPlan where coordination needs one. Otherwise finish with the supported account or partial result and the limitation that matters to its recipient.

B.1.5.CM:4.2 - Record the Result

Result positionRequired content
use and whole semanticsIntended result or preserved condition and receiving use; the whole semantics needed for the returned claim, including operations or invariant, applicability, participants and any relevant variation, bounds or reidentification conditions. A prospective or partial result keeps missing identity or relation grounds explicit.
participant accountEach subject, kind or status, identity basis or open condition, and proposed contribution.
relation setsEach load-bearing relation, its participants, truth status, grounds and any guard required for its receiving use.
branch verdictObtaining composition result, prospective candidate account, or partial result with decisive reason.
prospective contentThe guards, adapters, alternatives, recovery, stops, burdens, variation points and unresolved conditions that change the intended contribution or receiving use.
continuation, when selectedLater Work and observations, any required authority, acceptance/failure and reconsideration condition; a realization/test WorkPlan where its coordination needs one.

B.1.5.CM:4.3 - What Changes in Practice

Practitioners can write and test a coherent proposed Method without pretending that documentation created it. A positive composition claim becomes stronger because its identity and relation evidence are explicit; a prospective account remains useful for comparison through its guards, variation, recovery and stated limits. A selected implementation or trial adds the continuation needed to learn more.

B.1.5.CM:5 - Archetypal Grounding — C-EC-Release-v2

The EC-417 project proposes C-EC-Release-v2 as a whole for safety-relevant release coordination.

Under A, the team waits for signed supplier evidence before integrating the software. Under B2, it integrates from a versioned provisional edition, reconciles it with signed evidence before safety closure, and assigns most preparation of the changes between the editions to the supplier-configuration role to keep the safety engineer within the peak limit. C.32.MWA.PP §5.3 gives the timing and capacity comparison. A can be selected only before integration; recovery R is used when closure fails after early B2 integration.

The proposed account states:

Whole positionProposed content
intended resulta release-authorizable evidence and integration state for one safety-relevant change
situation familyinternal or supplier-originated hardware/software changes with versioned provisional or signed pinout evidence
invariantprovisional evidence may support reversible early integration, but signed evidence and repeated checks are required before safety closure and release authorization
participantsidentified M-HW-Verify, M-SW-Integrate, M-Supplier-Approve, and M-Release-Authorize; candidate reconciliation accounts remain separate
permitted variationpre-entry A when signed evidence or B2 entry conditions differ; B2 for bounded early integration; post-entry recovery R after a failed B2 closure
bounds and stopsconfidentiality, human authority, D-8 safety peak at or below 0.40, signed evidence before closure, and reversibility until D-1
reidentificationpreserve the intended result, invariant, participant-status boundary, evidence-version guard, authority, and A/B2/R branch meanings

The four participant Methods are identified, but the proposed whole is not. Their co-use and the proposed order do not establish that they are Method parts. The relation sets therefore remain proposed:

  • provisional-evidence integration at D-21 and signed-evidence reconciliation at D-8;
  • signed evidence and accepted safety result before release authorization;
  • supplier preparation responsibility for 1.60 h under B2;
  • separate safety and release authority;
  • PLM, rig, and provider-access conditions; and
  • description correspondences from evidence version through integration bundle and verification result.

For this selected trial, B.1.5.CM returns a prospective candidate account with a WorkPlan covering at most three B2 releases. The whole and relation claims remain proposed.

At each proposed release’s D-21 entry checkpoint, SafetyReviewer-17 accepts or rejects the entry evidence under ASG-SafetyReview-17 and AUTH-SafetyEvidence-17; ReleaseDecider-17 then decides branch entry under ASG-ReleaseDecision-17 and AUTH-ReleaseDecision-17. The filled entry case identifies these decisions as W-SafetyEvidenceDecision-17 and W-ReleaseDecision-17.

For closure or recovery, the two decision-makers use the evidence then available to decide safety-evidence acceptance and release, withhold, or next-slot disposition under the applicable assignments and authorities. Each performed later or repeated decision is a distinct dated Work occurrence with its inputs and result. Neither decision or authority relation substitutes for the other.

In B2, TraceReviewer-17 accepts or rejects each AI trace suggestion used by the release branch under ASG-TraceReview-17 and PERM-TraceAcceptReject-17. The full EC-417 application, §16.9.5 records the one permission grant and the dated Work W-TraceAcceptReject-17-01 that returns acceptance in the filled case. The separate relation PEX-TraceAcceptReject-17-01 connects that dated Work to the permission it exercised. EV-PEX-TraceAcceptReject-17-01 supplies evidence about this exercise.

Each additional used suggestion requires its own dated decision Work and result, confirmation that the permission applies at that time, and its own Work-to-permission exercise relation.

If signed evidence is missing at the D-8 closure checkpoint, withhold release and enter recovery R. In R, preserve the performed-integration record and evidence history. Repeat the evidence comparison and affected verification when evidence arrives by D0 while the existing evidence and reversibility guards still hold. Record whether early integration is retained, rolled back, or repeated, and the added burden. If closure remains unresolved at D0, the release result is withhold/next-slot and this R occurrence ends as a failed B2 trial.

ASG-TraceReview-17 and PERM-TraceAcceptReject-17 end at D0; continuing safety or release relations extend neither. This trial provides no post-D0 AI-supported continuation and asserts no later Work or recovery WorkPlan. Unresolved R may motivate separate later planning.

When later non-AI recovery needs coordination, the project may create a new A.15.2 WorkPlan; A.15.2 does not require planning before every otherwise valid later Work. Planned or unplanned Work would still need its separate qualification/currentness, readiness, assignment, permission/authority, and A.15.1 occurrence as applicable. These stops preserve all earlier Work and evidence history. A is only a pre-entry alternative.

Acceptance observations include whether each trial respects confidentiality and authority, remains at or below the D-8 capacity bound, preserves evidence/version correspondence, and reaches a release or recovery result by D0. An attempted post-D0 AI-supported continuation, or an assertion of later Work without a separately admitted A.15.1 dated Work occurrence, is a stop and failed trial observation.

The withhold/next-slot result preserves earlier Work and may motivate later planning. Those observations may support, narrow, split, or reject the account. They do not by themselves identify the whole; A.3.1 remains the identity owner.

For this series, a release counts once as a failed trial if it has a capacity or supplier-pinout/integration-bundle mismatch failure or enters R, even if recovery later succeeds; keep all failure reasons.

After two distinct failed trials, ReleaseDecider-17, within AUTH-ReleaseDecision-17, returns B2 for revision or rejects further use. That disposition retains the separate safety decision and grants no authority to revise the account. The immediate confidentiality, assignment, permission and authority stops still apply to the first breach. The existing decision covers at most three trials; a further release needs a new applicable decision.

B.1.5.CM:5.1 - Finish a Design Comparison Before a Trial Is Available

Suppose an earlier design use asks whether this release-coordination proposal preserves signed-before-closure, confidentiality and the A/B2/R distinctions well enough to compare with another proposal. The sources support that account, but whole identity and composition relations remain unresolved, and the team has no rig access, allocated effort or trial window. Return the traceable prospective account with those identity and relation limits. The receiving designer can compare the proposals and finish that question on the available content.

If the assignment is instead to devise a release procedure, start from what the release decider must establish at closure. Early integration from provisional information leaves a possible difference from the signed edition. Work back to the need to detect that difference, determine which checks it affects and supply their results before authorization. Waiting for signed evidence can remove the provisional-to-signed comparison while changing the time available for integration. Choose an arrangement that satisfies the applicable time, access and authority conditions. State which evidence can be supplied from outside the Method and which verification the proposed rule requires within it.

A later opportunity with useful obtainable observations can warrant implementation or a trial and its coordination plan. The already selected three-release case above retains its WorkPlan, observations and stops.

B.1.5.CM:6 - Bias-Annotation

Recurring biasLikely driftRepair
document-whole biasShared title and ordered sections become one world-side Method.Recover whole semantics, identity, and relations independently.
co-use biasSeveral Methods used in one project become participant parts of a composite.Require identified whole/parts and obtaining B.1.5 relations.
trial-success biasOne successful Work occurrence identifies a reusable Method whole.Use trial observations as later evidence and keep A.3.1 separate.
unlimited-adaptation biasEvery changed proposal keeps the same identity.State permitted variation, bounds, and reidentification rule.
architecture-decision biasSelecting a proposed relation set makes it obtain.Preserve proposal truth until realization and evidence support a stronger claim.

B.1.5.CM:7 - Conformance Checklist

  • The returned claim states the whole semantics it needs: intended result or preserved condition, situation, reusable operations/invariant, applicability, participants and relevant variation, bounds and reidentification conditions. When construction was commissioned, the proposed arrangement shows how the designer selected and connected the required contributions for the admitted uses. A supplied list of participants supports only the choices actually made from it. Missing grounds remain explicit in a prospective or partial result.
  • Whole and participant identification are judged separately; candidate and unresolved statuses remain explicit.
  • Method composition, Work order/overlap, result use, allocation, support, authority, and description relations are not inferred from one another.
  • The positive branch requires identified whole and parts plus obtaining B.1.5 relations.
  • The prospective branch preserves proposed truth and includes the guards, adapters, alternatives, recovery, stops, burdens and unresolved conditions needed by the receiving use.
  • WorkPlan, performed Work, observations, MethodDescription, and Method identity remain distinct.
  • A partial account states which receiving question it settles. Any part still required for the commissioned design is supplied or identified with the condition preventing it.
  • A supported account or partial result can complete its receiving use. A discretionary continuation has a worthwhile feasible contribution. Separately commissioned realization or observation is accounted for under its own performance, authority and acceptance conditions.

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

Anti-patternRepair
“We wrote the method.”Say that a candidate account or MethodDescription was written; identify the Method separately.
“The architecture was selected, so its relations obtain.”Keep the decision and proposed relations separate from realization evidence.
“All participants passed A.3.1.QM, so they form a whole.”Test whole identity and B.1.5 composition independently.
“A failed trial falls back into the earlier history.”Preserve performed Work and define a separate recovery branch.
“Wait for perfect proof before saying anything.”Return the supported prospective account or partial claim with the limits needed for its use; select further testing when its obtainable contribution warrants it.

B.1.5.CM:9 - Consequences

Projects can move from architecture proposal to realization and learning under identity and relation conditions. An established composition and a supported proposal remain distinguishable, and either can support the use for which its grounds are sufficient.

The cost is a visible open identity or relation question. Some proposed methodologies will remain candidate accounts after useful trials, and some will split into several Methods or a relation structure instead of maturing as one whole.

B.1.5.CM:10 - Rationale

Construction and description can change epistemes and WorkPlans immediately; they do not create a reusable way of doing in the world by assertion. The two-branch result preserves this difference while letting possible-future content guide real Work.

B.1.5.CM does not depend on applying C.32.MWA.PP first. C.32.MWA.PP is one common source of proposed relation sets, but any equivalent content can enter B.1.5.CM directly.

B.1.5.CM:11 - SoTA-Echoing

SourceRetained contributionUse boundary
Henderson-Sellers and Ralyté, Situational Method Engineering reviewConstruction and adaptation of Methods for situations.Source-local fragment, process, role, and assembly concepts do not establish FPF identity or composition.
Gericke, Eckert, and Stacey, Elements of a design methodIntended use, procedure, representation, tool, ecosystem, and adaptation conditions for a coherent proposal.Conceptual completeness does not prove world-side Method existence or relations.
Current FPF A.3.1, A.22, B.1.5, and C.32.MWAMethod identification, selected structures, Method composition, and several-structure synthesis.B.1.5.CM adds the whole-versus-prospective-account resolution and realization continuation.

Reconsider the account when its content fits none of these supported results, when variation defeats its reidentification rule, or when the claimed composition depends only on Work order or co-use.

B.1.5.CM:12 - Relations

  • A.3.1 governs whole and participant Method identification; B.1.5 governs any Method-composition claim.
  • C.32.MWA.PP commonly supplies proposed relation sets and architecture alternatives, but it is not a compulsory predecessor.
  • A.3.1.QM supplies individual qualifications without whole identity or compatibility.
  • Later realization, identification, description, support, trial, and assurance patterns consume only the branch and truth status returned here.
  • A prospective account, WorkPlan, selected architecture, or trial result supplies no obtaining ArchitectureRelation or methodPartOf fact by itself.

B.1.5.CM:End

B.1.6 - Work-Resource Aggregation

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

Use this when. Use this pattern when a recipient needs to design or apply an account that combines measured or estimated resource use, such as effort, time, energy, material, information or cost, across identified accounting subjects. These may include 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, or boundary partitions with the relations needed for their resource account.

Not this pattern when. If the question is the Method as a way of doing, use A.3.1. If it concerns whether an episteme is a MethodDescription, or the use of its claims about a Method as a way of doing, 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. A convenient resource total is taken from a method description, plan, dashboard or phase label without warranted input values, identified accounting subjects and a combination rule that handles any overlap.

What this buys. The practitioner can specify an appropriate resource account or justify its typed total, vector, interval or bounded estimate from its input values, included subjects, accounting scope, time basis and operative rules, and check whether the same resource contribution has been counted more than once.

B.1.6:1 - Problem Frame

Practitioners need resource totals across identified Work occurrences and their A.15.1 temporal parts or episodes. A non-Work carrier phase can enter the account when its identity and PhaseOf relation are established. 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

A convenient total becomes an unsupported resource claim when its input values, included subjects, accounting scope, time basis or combination rule are missing. Claims about performed Work also need evidence for those occurrences and their resource use; accounts that depend on holon delimitation, boundary crossing or stock relations need those relations established.

B.1.6:1.1 - Forces

ForceTension
Measured work vs. planned workExpected yield, duration, or resource use helps planning, but cannot prove performed-work resource use.
Typed resources vs. convenient totalsEnergy, mass, time, cost, data volume and attention need compatible accounting bases and any conversion required for the proposed comparison.
Boundary accounting vs. local convenienceResource values need an accounting scope and time basis, together with any holon-delimitation, boundary-crossing or stock relations on which that account depends.
Additivity vs. shared contributionsDisjoint resource contributions can be added; repeated inclusion of the same use, stock portion or contribution requires a justified allocation or deduplication rule.
Efficiency vs. whole reidentificationApparent free gain may be measurement, changed accounting basis, substitution, or a new whole; B.1.6 cannot decide that by resource wording alone.

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

First identify whose resource, which use or availability, and what period the decision concerns. A reading for the entire agreed boundary or a warranted bound can answer directly. If the answer depends on combining contributions, use the following form.

Under rule P, the resource values attributed to the included subjects S within accounting boundary B and time window T yield typed result R, with the stated qualifications. The result statement identifies those inputs and grounds.

When the boundary and units are yours to choose, work back from the action. What expenditure, stock, peak demand or right to draw would change it? Follow that quantity through the relevant Work, participants and transfers. Select a smaller unit only where its attribution, timing or interaction with another use can change the answer. Try shifting the same total between two users or two periods. If a limit can be met in one arrangement and missed in the other, retain that distinction and any restriction on which demands can occur together. An existing rule for the whole class of jobs can establish coverage without a separate entry for each job.

For a commission to design an accounting rule, specify the inputs and how they determine the required output across the admitted jobs. Give a computed result when the commission includes applying the rule. An ordinary sentence or table may suffice for either result. Stop when it answers the receiving resource question with the required basis. If an input or relation is unknown, carry the admissible possibilities through the rule. Give a supported answer, including a threshold decision from a sufficient bound, and identify any separately requested quantity or attribution still open.

For each input, retain its subject, resource Characteristic, Scale, applicable Unit, attribution basis and uncertainty relevant to the use. A claimed performed measurement retains its C.16 Work and result; an estimated or derived value retains the source values, model and conditions that warrant it. A ledger row supplies no missing basis merely by displaying the value.

WorkResourceAggregation@Context is one possible descriptive outline for the aggregation claim. Use it when that organization helps the receiving use; ordinary prose or another adequate representation can carry the same content. Fields marked ? are included when the corresponding claim or use needs them; the conditions below govern their required content:

WorkResourceAggregation@Context:
  aggregationConcernRef
  claimScopeRef?: U.ClaimScope
  accountingBoundaryRefs
  timeWindowRefs
  includedSubjectRefs
  aggregatedWorkOccurrenceRefs?
  resourceUseRelationRefs?
  workPartOrOverlapRelationRefs?
  nonWorkCarrierPhaseRelationRefs?
  resourceCharacteristicRefs
  resourceValueBasisRefs
  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 the following content for the claims made and the use being proposed:

  • a resource Characteristic says which quantity or property is accounted for;
  • each resource value retains its attribution basis: a claimed performed measurement has C.16 measurement Work and a measurement-result episteme; an estimated or derived value keeps its source values, model and conditions. Retain Scale, applicable Unit, time stance, and the calibration and uncertainty basis needed for the use;
  • the aggregation policy states the inclusion rule and output kind, together with the conversion, normalization, weighting, missing-value, allocation, uncertainty and overlap rules needed to interpret or justify this result. Identify the policy edition when the result or its use depends on that edition;
  • when the claim asserts dated aggregation Work, or the receiving use needs that occurrence, A.13 identifies its performer and A.15.1 independently admits it as U.Work. If assignment-bound attribution is also needed, F.6 checks that relation separately. The Method, inputs through direct relations or A.6.1 bindings, resources and temporal extent retain their grounds;
  • an application of the aggregation rule returns the typed total, vector, interval or bounded estimate warranted by the input values, included accounting subjects and operative rules. A design for later applications specifies how the result will be obtained;
  • the result statement conveys the result, included subjects, rule, boundary, time basis, qualifications and relevant uncertainty. When the receiving claim or use needs a claim-bearing episteme, identify it through C.2.1 by its claim content, EntityOfConcern and effective ReferenceScheme. Keep the resource value, claim content, episteme and expression distinct; and
  • keep the source basis recoverable: the measurement or estimate sources, operative rules and derivations needed to justify the result. Use A.10 when source-to-use reliance must be replayable, and G.6 when that chain needs a stable address for citation, replay, audit or refresh. Apply G.11 when currentness affects the use.

A ledger or other representation may describe this account. Establish each Work, participation, measurement, part/overlap or result-identity claim on which the proposed use depends under its predicate; an adequate existing representation can then carry the warranted result.

B.1.6:2.1 - Subject Pattern Map

ClaimSubject pattern
Resource Characteristic, Scale, applicable Unit and value-attribution basisC.16 for measurement and derived value attribution; for a claimed measurement Work, A.13 identifies its performer and A.15.1 independently admits the occurrence. Add F.6 when assignment-bound attribution is needed, and A.6.1 for bindings when used.
Dated aggregation Work and performerA.13 identifies the performer, then A.15.1 independently admits the Work. Add F.6 only if the result must also identify the assignment under which the Work was performed. Method enactment and inputs remain separately governed, including A.6.1 bindings when used.
Work temporal part, episode, operational part, partition, overlap, retry, resumption, or later occurrenceA.15.1 and the Work relation pattern; use B.1.4 only to aggregate already recovered temporal relations
Proper temporal restriction of another enduring carrierthat carrier’s identity pattern plus A.14 PhaseOf; never a substitute for Work relations
Overlap, shared-stock, boundary, and deduplication factsC.27.TA for interval overlap; the stock, resource-use, boundary, or accounting relation pattern for the other fact
Aggregation policy and typed aggregation resultB.1.6
Measurement-result and aggregation-result epistemesC.2.1; A.15.PROD only when their inception through work matters
Source recovery, replayable reliance, provenance or publicationRecover the sources needed for the claim. Use A.10 for a needed replayable source-to-use reliance account, G.6 for a needed stable address of that chain, and E.17 for a publication question.
Edition currentnessG.11
Planned work or resource readinessA.15.2 or A.15.5, never a measured aggregation result
Transformation, whole reidentification, assurance, comparison, or decisionthe applicable A.3.4, B.2, B.3, A.19, C.11, or other pattern for that claim

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 when required by the receiving claim or use]

The notation summarizes an aggregation whose required basis has been recovered: resource Characteristics and input-value grounds; included accounting subjects and any Work-part, temporal-overlap, resource-use or stock relations used by the account; a non-Work carrier phase’s identity and PhaseOf grounds when that phase is included; accounting scope, time basis and operative rules; and the typed result with its qualifications. Any asserted measurement or aggregation Work keeps its independent occurrence grounds. The notation adds none of those facts.

B.1.6:4 - Ledger Discipline

A ledger can organize the grounds needed to reconstruct the aggregation. Whether using a ledger or another representation, retain for each resource component:

  • resource Characteristic, Scale, applicable Unit, polarity when relevant, and accounting boundary;
  • the measured or estimated subject, time window, and included Work occurrence, non-Work carrier phase or other admitted accounting subject to which the value applies;
  • the attribution basis: C.16 measurement Work and its result episteme for a claimed performed measurement, or the source values, model and conditions for an estimated or derived value, including the calibration and uncertainty basis needed for its use;
  • every A.15.1 Work-part relation used by the ledger, every C.27.TA overlap fact used by it, and any current non-Work carrier PhaseOf, each independently established by its subject pattern;
  • which overlaps matter to the result: an exact total may require identification and deduplication, while a threshold can sometimes be decided by a bound that holds for every possible overlap;
  • any conversions, normalizations or imputations used, with the operative methods and rules;
  • the operative aggregation rule, its edition when the result or use depends on it, and the aggregation Work occurrence when that dated occurrence is asserted or required;
  • the typed aggregation result and its statement, with a separately identified C.2.1 result episteme when the receiving claim or use needs one; and
  • sources and derivations needed to justify the result; A.10/G.6 accounts under the conditions in §2; G.11 currentness when it affects use; and the admissible use, stop or reopen condition, with any guard justified by F.19’s plausible-reader test.

Keep visible which values are measured, estimated or planned, and which normalization, conversion or allocation has been applied. These descriptions can overlap: an estimated value may result from an indirect measurement. Its basis determines the claim.

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 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, applicable Unit, subject and accounting boundary are compatible under the operative rule. Joules, hours, kilograms, currency, bytes and attention do not become one scalar by co-location.

Measurement before aggregation. Each measured input points to 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.

Included accounting subjects. Establish which subjects the account covers, individually or through a rule that covers the whole requested scope. Identify an individual Work occurrence or phase when its resource use, identity or part relation is used in the inference or requested as a result. Parent–child, TemporalPartOf_work, EpisodeOf_work, OperationalPartOf_work and other admitted Work-part relations must already obtain between independently admitted Work participants under A.15.1 or their subject patterns. A non-Work phase keeps its carrier’s identity and PhaseOf grounds. For temporal overlap, recover the participants, temporal reference and interval facts under C.27.TA; establish resource-use or stock overlap under its accounting rule. A Method, plan, epoch or phase label, invoice period or dashboard grouping does not establish these subjects or relations.

Operative policy. State inclusion and output kind, and the conversion, normalization, weighting, missing-value, boundary-allocation, uncertainty and overlap/deduplication rules needed to interpret or justify the result. Identify the edition when the result or use depends on it. A policy declaration remains distinct from its application and result.

Overlap and shared stocks. For an exact total, establish disjoint contributions or justify how any overlap is handled. For a bound, establish the direction in which overlap can affect the requested quantity. For example, the sum of the hours in two complete groups is an upper bound on the hours in their union if repeated contributions have nonnegative values and are measured on the same basis. That bound can settle a ceiling without identifying every shared contribution. For allocation among works, use the assignment rule for the resources in question. Reuse of one person, tool or meter across distinct resource contributions does not by itself duplicate those contributions.

Aggregation result and any asserted Work. For a requested application, return the typed total, vector, interval or bounded estimate warranted by the input values, included subjects and rule, with its qualifications. A design for a class of jobs identifies how to select those inputs in each permitted case and why the rule will answer the receiving question. An ordinary statement or table can convey that result. When a claim-bearing result episteme is needed, identify it through C.2.1 as in §2, retaining the distinction between resource value, claim content and expression.

When a dated aggregation occurrence is asserted or required, use A.13 to identify the performer and A.15.1 to admit that Work independently. Add F.6 when assignment-bound attribution is needed. The Method, bindings, resources and time retain their separate grounds.

Uncertainty and provenance. Propagate measurement, model and conversion uncertainty under the operative rule where it affects the result or use. Keep the necessary sources and derivations recoverable. Use A.10 for needed replayable source-to-use reliance and G.6 for a needed stable address of that chain, preserving any Work, measurement, policy-application and transformation facts the use requires.

Estimates, plans and performed use. An estimated or derived resource value retains its source values, model and conditions; a planned amount retains its planning basis. The same value may serve both uses. Keep 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, output or domain result, attribution bases and applicable comparison rule. Any asserted dated aggregation Work retains its independent grounds. Explain a claimed gain through the measurement, accounting and domain-result grounds on which it depends; use B.2 when whole identity remains the question.

B.1.6:5.1 - Aggregation obligations

ObligationWhat must be named
Resource inputCharacteristic, Scale, applicable Unit, subject, time basis, attribution grounds and uncertainty relevant to the use. A claimed performed measurement retains its C.16 Work/result; an estimate or derived value retains its sources, model and conditions.
Included subjectsGrounded coverage of the accounting subjects, and the identity of every individual occurrence whose attribution the conclusion uses or supplies; every Work-part, temporal-overlap, resource-use or stock relation used by this aggregation; and the identity and PhaseOf grounds for any included non-Work carrier phase.
PolicyInclusion and output kind; every conversion, weighting, missing-value, allocation, uncertainty or overlap rule needed for the result or use; and an edition when either depends on it.
Dated aggregation Work, when asserted or requiredPerformer identified through A.13; dated U.Work independently admitted through A.15.1; a separate F.6 check when assignment-bound attribution is needed; separate Method, resources and direct/A.6.1 bindings.
Aggregation resultFor an application, the typed result, included subjects, rule, boundary, time basis and qualifications. For a design, the input selection and rule that will supply the required output under the stated conditions. When the receiving claim or use needs a result episteme, identify it through C.2.1 as in §2.
Source basis and currentnessRecoverable sources and derivations; A.10 when source-to-use reliance must be replayable, G.6 when that chain needs a stable address, and G.11 when currentness affects use.
Later useThe receiving claim, action or judgement and any premise, reference, argument or decision-use relation it requires.

B.1.6:6 - Archetypal Grounding

Ordinary operator-time total. Two existing records, with their value-attribution grounds, attribute one hour each to two admitted Work occurrences by the same operator. Their participant and time facts establish that these are distinct, disjoint resource contributions within the chosen accounting period. Addition yields two operator-hours; an existing table can state that result and its basis. This answer need not assert a separate dated occurrence of aggregation Work. If both entries instead copy the same one-hour contribution, adding them would double-count it: recover the common contribution and count it once, or leave the affected total unresolved until that identity is established.

If the two one-hour entries may be copies or distinct contributions, and the records exhaust the stated scope, total operator time lies between one and two hours. This settles a two-hour upper limit, even while exact utilization remains open. A roster showing two planned hours would answer a scheduling question. Establishing how much time the operator actually spent uses the resource records for the period.

Engine test programme. C.16 measurement Work attributes fuel mass, electrical energy, operator time, and emissions values to subjects under their Scales, models, calibration bases, windows, and uncertainties. Each has its result episteme. 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 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. Recover what each component includes: the same fan-energy contribution or operator-time contribution must not be counted twice. For a combined cell total, count a shared contribution once; if the question allocates it to individual jobs, apply a justified allocation rule. Distinct, disjoint uses of the same fan or operator remain separately countable. The resource ledger represents those facts. Establish any separately claimed Work-part relation or frame transformation through its pattern.

Model training. Epoch labels alone do not establish work parts. Ground the training work and 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

Bias riskFailureMitigation
Plan becomes evidence of actual useExpected resource use is presented as evidence of performed resource use.Keep the plan, any claimed dated Work, the value-attribution basis and the B.1.6 result distinct.
Boundary or phase word carries accountingA port, interface, team, device, epoch or phase label is used as Work parthood, overlap or accounting boundary.Establish the accounting scope, time basis and operative rule, together with any delimitation, Work relation, carrier identity/PhaseOf, crossing or stock relation on which the account depends.
Untyped total hides conversionHours, energy, material, money, and data are added as one number.Keep resource vectors typed until a conversion relation or model is declared admissible under the applicable measurement or mathematical-lens pattern.
A resource contribution is double-countedThe same resource use, stock portion or attributed contribution is counted more than once.For an exact total, account for the repeated contribution. For a threshold decision, use a sufficient bound valid for all overlaps still possible. Use the applicable allocation rule if shares are requested.
Efficiency becomes proof of a new wholeReduced resource use is treated as proof of a new whole.Use measurement and evidence-use patterns for the gain; use B.2 when whole identity remains the question and B.2.P for unresolved emergence-family wording.

B.1.6:7 - Conformance Checklist

IDRequirement
CC-B1.6-1Every resource component names its Characteristic, Scale, applicable Unit, subject, time stance and attribution basis, with uncertainty relevant to use. A claimed performed measurement retains its C.16 Work and result; an estimated or derived value retains its sources, model and conditions.
CC-B1.6-2Included accounting subjects and each relation used by the aggregation are independently grounded. A class or boundary rule may establish coverage. Each individual occurrence attribution or A.15.1 Work-part relation used has its basis; temporal overlap follows C.27.TA, resource-use or stock overlap follows its rule, and an included non-Work phase satisfies its carrier’s identity and PhaseOf conditions.
CC-B1.6-3The operative policy names inclusion and output kind, every additional rule needed to interpret or justify the result, and an edition when the result or use depends on it.
CC-B1.6-4For dated aggregation Work, A.13 identifies the performer and A.15.1 independently admits the occurrence. F.6 is present only when the result must also identify the assignment under which that Work was performed. The Method, direct/A.6.1 bindings, resources, and temporal extent remain separate.
CC-B1.6-5A design explains input selection and the warranted output for the requested class. A claimed application supplies its typed aggregation result and grounds. When a claim-bearing result episteme is needed, its claim content, EntityOfConcern and effective ReferenceScheme are identified through C.2.1. The resource value, claim content, episteme and expression remain distinct.
CC-B1.6-6Sources and derivations needed for the result are recoverable. Any required A.10/G.6 provenance account or G.11 currentness result remains separate from the measurement and aggregation results.
CC-B1.6-7Planned values and A.15.5 resource readiness are not presented as measured performed-work aggregation.
CC-B1.6-9Any yield, efficiency, comparison, assurance, transformation, whole-reidentification or decision claim names its applicable subject pattern.

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

OverreadRepair
A method or algorithm is treated as the work-resource roll-up.Recover the resource claim and its grounds through B.1.6. Use A.3.1 for a separate Method question, or A.3.2 for a MethodDescription membership or description-use question.
A work plan is treated as measured work.Use A.15.2 for the plan and A.15.1 for performed work evidence.
A phase label or timeline is treated as a resource ledger or as proof of a Work relation.Recover the subject first: A.15.1 for Work temporal parts or occurrences, the carrier’s identity pattern plus A.14 for proper non-Work PhaseOf, and B.1.4 only for bounded aggregation of already recovered temporal relations. Add B.1.6 only when typed resource values are being aggregated.
A resource gain is treated as emergence.Use measurement and evidence-use patterns first; use B.2 when whole identity remains the question; use B.2.P for unresolved emergence-family wording.
A ledger, dashboard or report total is relied on without the grounds its use requires.Identify what establishes the value for the required boundary and period. A warranted whole-boundary reading can settle a total. Recover component records, relations and combining rules where the result or its required explanation depends on them. Preserve an adequate account; obtain only missing grounds under §§4–5. An asserted dated aggregation Work or a needed replayable provenance account retains its requirements.

B.1.6:9 - Consequences

This pattern grounds typed resource aggregation in attributed input values, identified accounting subjects, operative rules and the conditions of the receiving use. Measurement, performed Work, aggregation policy/application, result episteme, subject relations and provenance retain their separate grounds whenever claimed or needed.

The cost is establishing the accounting basis. A comparison can then use totals whose value-attribution bases, boundaries and aggregation rules are compatible, within the limits of their evidence.

B.1.6:9.1 - Rationale

B.1.6 exists because a convenient total can hide different subjects, repeated contributions or incompatible value bases. A warranted result requires the input-value grounds, included subjects and relations, accounting scope, time basis and combination rule needed for that claim. Policy editions, dated aggregation Work and provenance accounts are added when the claim or receiving use depends on them. An adequate ledger or other expression can state this account.

Gamma_work denotes the aggregation described by that account. A MethodDescription or WorkPlan can state expected yield or resource use; a claim about actual use needs evidence for the included subjects and their attributed resource contributions. Any claimed performed Work retains its independent occurrence grounds.

B.1.6:9.2 - SoTA-Echoing

The following contributions are adapted from the cited editions for work-resource aggregation.

SourceContribution to the methodUse boundary
ISO 14040:2006 with Amendment 1:2020 and ISO 14044:2006 with Amendments 1:2017 and 2:2020Adapt goal/scope, system-boundary, inventory, allocation, reporting and intended-use discipline. Recover the boundary, included subjects, output kind, intended use and any allocation or overlap rules required by the account before relying on the total.An LCA boundary or reported total does not establish FPF Work parthood, measurement, aggregation Work, result identity or admissibility for every later use.
GHG Protocol, Product Life Cycle Accounting and Reporting Standard (2011)Adapt process subdivision or system expansion before allocation, physical or other justified allocation, and double-count control for shared processes and stocks. Recover which resource contributions overlap and apply justified allocation or deduplication where needed.A common meter or convenient allocation key does not establish disjointness, Work structure or a universal resource share.
JCGM GUM-6:2020, Developing and using measurement modelsAdapt input-quantity, model-adequacy, covariance, and uncertainty-propagation discipline. Retain input uncertainties, correlations and conversions, the propagation method, and qualified output uncertainty separately from provenance.Source references and point totals do not propagate uncertainty; aggregation does not make incompatible models or quantities commensurable.
ISO 80000-1:2022, Quantities and units — Part 1: GeneralAdapt the distinctions among quantity kind, unit, quantity value, and dimension, and the use of coherent units, for typed inputs and outputs. Keep resource quantities distinct unless a conversion or normalization and output kind are justified.A shared numeral, unit label, normalized score, or vector position does not justify cross-kind addition, scalarization, efficiency, or comparability.

B.1.6:10 - Relations

  • For claims about dated measurement or aggregation Work, A.13 identifies performers and A.15.1 independently admits the occurrences. F.6 applies when assignment-bound attribution is needed; A.6.1 governs declarations and bindings when used. C.2.1 governs the 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 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 marked informative

B.2:0 - Use This When

Use this pattern when a decision depends on whether an existing whole can carry a claim through an actual or proposed change, or requires identifying a different whole. The question may concern its delimitation, constituents, assembly, objective, supervision, capability envelope, agency threshold or continuity across time.

The question can also arise when a whole is first constituted or first recognized. If no prior holon has been established, use A.1 and the applicable construction and kind-specific patterns to recognize the candidate. B.2’s comparison begins only when there is an established prior whole to compare with it.

Typical moments:

  • a set of coordinated parts becomes a regulated system with its objective and externally visible commitments;
  • an installation enters operation and its users must determine which commissioning evidence supports a claim about it in service;
  • 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. What decision depends on the identity of which whole? Establish whether the question concerns an actual change, what would follow under a proposed arrangement, or a design still to be made. Use an established continuity condition directly when it decides the question. For an actual gain or shift, compare explanations that preserve the existing whole. A constituent repair, different measurement, change of Method or Work, wider phase coverage or a corrected architecture view may suffice. For a design, start from the required use and the choices it leaves open in :4. A disputed identity criterion belongs in :4.0.

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

What this buys. The practitioner can decide whether the claim concerns the existing whole or a new one, using the changed facts and each whole’s identity grounds. The result guides subsequent records and reliance decisions.

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 measurement or evaluation pattern.
  • If the claim is capability without whole reidentification, use the 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 concerns a graph, RG-like, MSPD or other mathematical expression, use its mathematical or subject pattern, with C.29 for an unresolved representation-choice, transfer or reliance question. B.2 applies separately when whole reidentification is also current.

B.2:1 - Problem Frame

A Meta-Holon Transition is a whole-reidentification claim about a holon recognized through A.1 construction, identity, part relations, whole-level characteristics, and a kind-specific pattern.

The B.2 comparison determines whether the receiving use can continue with the old whole or requires a newly identified whole; retain the old whole when its identity rule accommodates the change and it meets that use. 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 candidate satisfies A.1 plus the kind-specific criterion.

B.2:2 - Problem

When whole identity and its grounds are unclear:

  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 user treats the organization or labels of a record as grounds for recognizing the whole or its kind.
  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

ForceTension
Parsimony vs noveltyFPF should not mint new wholes for every improvement, but some closures change the EntityOfConcern.
Continuity vs reidentificationHistory and phase continuity matter, but some transitions require identification of a new whole.
Trigger recognition vs trigger inflationDelimitation, part-relation, objective, supervision, capability, agency-threshold, and temporal cues help recognition but do not declare MHT by themselves.
System-facing emergence vs broader holonsHolonic systems literature is system-facing, while FPF also needs cases in which the candidate new whole is an episteme, method, work occurrence, or discipline.
Math-lens power vs ontology disciplineRG-like, graph, algebraic, or benchmark expressions can bear on a claim only after the holon and relation are named.

B.2:4 - Solution

B.2 concerns the constitution and continuity of wholes. Distinguish what already obtains from what the recipient wants to design. Add records only when a receiving use needs them.

Start from what someone must decide and what the answer has to establish. For a maintenance decision this might be whether a repair belongs in the history of this installation. For a repeatable service it might be which participants must act together and which rights can remain with independent providers. Establish the unit and interval for each claim. Keep the installation and its assemblies, the Method and its constituent operations, the actual job and its performances, and the episteme that warrants an identity claim distinct wherever their differences could change the answer. Changes in any one can matter to the others through use, enactment, authority or evidence. If the claimed whole is a discipline, trace which practices and knowledge its practitioners organize and which they simply draw on. Follow the relation that carries the consequence for the decision.

When the boundaries have been left to you, keep one constituent fixed and vary the organization or use of the whole. Then keep the reported whole result fixed and vary which constituents produced it or how they were connected. Would the recipient act differently or need a different explanation? At each relevant scale preserve the distinction that makes the difference. An aggregate may establish a whole’s output and leave open which assembly or Work produced it. Stop at the established rule, observation or bound that decides the question. Use C.39.SA:4 when choosing those ranges is itself part of the work.

Establish which prior whole, if any, is being compared. For a first constitution, obtain the construction facts under the applicable subject pattern and then apply A.1. For a first recognition of an existing whole, apply A.1 to the facts already obtaining; the recognition date does not establish when the whole came into existence.

When the prior identity grounds are unavailable or disputed, use :4.0 to recover or compare their basis if this could change the result. A decision common to the supported identity alternatives can go ahead. An assertion naming the continuing individual still needs grounds that distinguish it. First constitution, recognition and a prospective design supply no prior holon for existingWholeRef by themselves.

If an arrangement is to be designed, begin with the result its users must be able to obtain or maintain. Check first what the present arrangement can already supply. If its continued use meets the commission, that can settle the design decision. For an unmet condition or an expressly commissioned alternative, trace the required result to the contribution, connection or authority needed at the time of use. Consider whether an allowed change inside the existing whole, an external service or a differently constituted whole could supply it. Choose the constituents and relations the proposed result depends on and test them together under the applicable construction and identity conditions. A sufficient shared constraint can exclude a family of proposals. An unsuccessful trial excludes only the arrangements its result covers. Return the feasible proposal, conditional comparison or established limit requested. Evidence that a proposal was realized belongs to a claim about actual constitution or performance.

For a claim of actual whole reidentification, compare an established prior whole with the proposed successor:

  1. Name the receiving claim or use, the existing whole, its admitted kind, and its identity or reidentification rule.

  2. Establish the changed facts needed by this comparison under their subject patterns. A change of the bearer, its Method, an occurrence of Work or the episteme reporting it can have different consequences for continuity. Establish any connection used to carry a conclusion between them. A cue word, profile field, measurement or graph edge alone leaves that connection open.

  3. Test whether those facts can be explained as a change of the same whole using :4.2. A same-whole explanation can show that continuity was possible. To establish actual continuity, identify the relevant history or show that all histories compatible with the evidence preserve identity under the applicable rule. If the comparison is unresolved, identify the deciding fact or rule still needed instead of declaring a new whole necessary.

  4. When the comparison establishes that the existing whole is insufficient, designate the proposed new whole as a U.Entity and execute the A.1 criterion. Recover its constituents, obtaining constructive relations, assembly, reidentification rule, and composition-grounded whole characteristic.

    Also show that the candidate’s 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 kind-specific criterion.

    If a required condition fails, the candidate fails the corresponding recognition test; if missing evidence or an unavailable dependency prevents a determination, evaluation returns unknown.

  5. State the whole-reidentification claim: why the receiving use cannot retain the existing whole and how the recognized new whole meets that use. A positive classification alone does not establish this comparison. The prior whole may continue to exist and retain a narrower use; reidentification does not require its destruction.

    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 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.0 - Establish the identity grounds for the comparison

Use this branch when the comparison needs an identity criterion that is unavailable or contested. A sufficient criterion already supplied by the admitted kind and subject practice can be used in :4.2. Here the useful result is a justified rule for the whole being compared, or the missing ground that prevents choosing one.

Recover the subject of the identity claim. State what continuing whole the receiving question concerns and which construction makes it that whole. A commissioned installation, the resources currently performing an order and a supervisor’s jurisdiction can overlap materially while answering different questions. Recover their constituents, organizing relations and relevant occasions before treating their descriptions as rival accounts of one individual. Use A.1 and the kind-specific pattern for the corresponding recognition question. When two accounts concern different subjects, keep each subject and its continuity conditions.

Recover what warrants each proposed rule. Find the domain account that makes the proposed conditions relevant to this whole: for example, the constitutive organization described by a design, an established lifecycle practice, or a theory of the object’s persistence. Follow its reasons into what may change and what ends the individual. Distinguish a condition sufficient for continuity from one merely necessary for it. An identifier, observation or test can help recognize that condition; recover the connection that gives it identifying force. For an institutionally constituted object, the applicable constituting rule can itself supply identity conditions. For a physical organization, a proposed rule also has to fit the organization and changes. A convenient model boundary answers only the questions warranted by its correspondence to that subject.

Compare the consequential alternatives through B.5.TC. Give each proposed account the same identity question and corresponding facts; recover its reasoning, then vary the condition on which the accounts disagree. Choose variations from the disputed claim. Replacement can expose whether the criterion preserves an organization or requires a fixed collection of parts. A temporary loss of functioning tests whether incapacity has been confused with the end of its bearer. A transfer of control tests whether the question follows the installation or a control relationship. Two independently constituted systems with the same output test whether a proposed condition distinguishes individuals or only capability. Division, merger or reconstruction matters when one of those events changes the receiving decision. For an episteme, compare its ClaimGraph, EntityOfConcern and effective ReferenceScheme under C.2.1 even when its carriers differ.

Locate the first reason for disagreement, as B.5.TC:4.4 explains. It may be a different subject, an incompatible domain premise or a missing fact about one continuing whole. A counterexample can defeat a proposed criterion; the surviving proposal needs the positive domain grounds that license its continuity claims. When a theory’s application is unclear, B.5.TU supplies that recovery. Obtain a specialist result or further inquiry only for the consequential ground still missing, using C.11.DUA to judge its attainable contribution and burden.

Return the criterion to the identity comparison. State the selected subject, the rule and its grounds, the changes it permits, and the event or condition that would end continuity. Keep a qualified or partial rule at the strength supported. Feed those results into :4.2 and use A.1.RI when observations still need to be associated under the rule.

A commission to set a future continuity rule gives the practitioner a further choice. Compare which substitutions, divisions or transfers each rule would allow for the intended use, and who or what could give the rule effect. A rule adopted for future maintenance governs from the occasion covered by its terms. To decide what happened at an earlier repair, use the conditions that governed that repair.

Complementary accounts keep their different subjects; unresolved competing criteria for the same subject retain their conditional answers and the fact or domain commitment needed to decide between them. If their difference cannot affect the receiving work, continue that work at its supported scope. A broader identity conclusion remains open.

B.2:4.1 - MHTTriggerProfile

MHTTriggerProfile is a U.Episteme whose EntityOfConcern is the existing whole already recognized under an admitted holon kind. It collects 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.

Content fieldValue kind and use
existingWholeRefU.HolonRef resolving to the existing whole already recognized under an admitted holon kind.
existingWholeIdentityRuleRefU.EpistemeRef resolving to the current identity-rule episteme.
currentPartRelationRefs[]U.EntityRef values, each resolving to one individuated current part-relation occurrence.
changedDelimitationRelationRefs[]References to changed delimitation relation occurrences under their patterns.
changedPartRelationRefs[]References to changed part-relation occurrences.
changedSupervisionRelationRefs[]References to changed supervision relation occurrences.
changedFeedbackClaimRef?U.EpistemeRef resolving to a B.2.5 compound feedback assertion when the receiving use needs that claim. Its observation and return-influence relations and coupling grounds remain with the assertion.
changedCoordinationRelationRefs[]References to changed coordination relation occurrences.
changedObjectiveClaimRef?U.EpistemeRef resolving to the objective-change claim.
changedCapabilityClaimRef?U.EpistemeRef resolving to the capability-change claim.
agencyThresholdClaimRef?U.EpistemeRef resolving to a current characteristic-space threshold claim.
temporalConsolidationClaimRef?U.EpistemeRef resolving to the temporal-consolidation claim.
evidenceRelationRefs[]References to evidence relation occurrences supporting the trigger claims.
sourceUseRelationRefs[]References to source-use relation occurrences when a source is relied on.

The profile’s complete interpreted claim content and effective reference scheme, 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 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 patterns make those explanations current. For a feasibility question, a supported way of meeting the use while preserving the existing whole can suffice. For a question about what actually happened, establish the identity conclusion for the history that occurred. If both continuity and replacement are compatible with the evidence, state what can be decided under both and leave their historical identity open. Use the subject pattern for any remaining question.

For each material explanation, test three things together: whether it covers the change needed by the receiving use, whether the old identity rule permits it, and whether it is compatible with the established facts. When continuity across observations is uncertain, use A.1.RI to construct the possible connections and test them against the subject constraints. A changed part may preserve one whole’s identity and defeat another’s; the applicable identity rule decides.

Comparison resultGrounds and next move
sufficientFor a possible continuation, an admissible identity-preserving arrangement meets the use. For actual continuity, the known history or every history still compatible with the evidence preserves identity. Retain the whole for the conclusion established.
insufficientAn established condition necessary for the receiving use cannot be met while preserving the prior identity; or the governing facts and rules justify a closed set of applicable alternatives and every alternative fails. Proceed to the candidate’s A.1 and kind-specific tests.
unknownA deciding fact or rule is unavailable, or material alternatives remain that would change whether a new whole is needed. Obtain that missing basis or retain the unresolved comparison.

An unsuccessful search for an explanation does not establish insufficient. A closed comparison needs a reason why its alternatives cover the named question, not an inventory of every imaginable explanation. If all remaining identity alternatives permit the same needed continuation, A.1.RI allows that continuation without settling the unused identity distinction; this does not establish an MHT claim.

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

Content fieldValue kind and use
observedChangeClaimRefU.EpistemeRef resolving to the observed-gain or observed-shift claim.
candidateExplanationClaimRefs[]Claims under their subject patterns.
explanationEvidenceRelationRefs[]Evidence relations used to assess those explanations.
existingWholeSufficiencyVerdictsufficient, insufficient, or unknown for the named receiving use.
remainingWholeReidentificationQuestionRef?The residual question when the result is insufficient or unknown.

The practitioner performs the comparison; the optional episteme records its outcome. Identity and relation claims depend on the facts and rules used in that comparison.

B.2:4.3 - HolonReidentificationRecord

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

Content fieldValue kind and use
existingWholeRefU.HolonRef resolving to the prior whole already recognized under an admitted holon kind.
selectedTriggerProfileRef?U.EpistemeRef resolving to the selected MHTTriggerProfile, when one was used and the receiving account needs it.
existingWholeExplanationResultRef?U.EpistemeRef resolving to the optional ExistingWholeExplanationResult; omit it when the ordinary comparison sentence is enough.
resultHolonRefU.HolonRef resolving to the established new whole.
resultHolonKindRefU.KindRef resolving to its admitted holon kind.
resultHolonClassificationAssertionRef?U.EpistemeRef resolving, only when a person or system performing later work must inspect or cite the judgment, to a C.2.1 classification judgment about whether the candidate new whole satisfies the A.1 criterion under the stated admitted holon kind.
wholeReidentificationClaimRefU.EpistemeRef resolving to the claim that the candidate new whole, rather than the prior whole, now carries the subject claim.
changedClaimPatternLocators[]U.EpistemeRef values resolving to the patterns for each changed claim used in the rationale.
evidenceRelationRefs[]References to evidence relation occurrences supporting the reidentification claim.
sourceUseRelationRefs[]References to source-use relation occurrences when sources are relied on.
mathLensUseOutputRefs[]?MathLensUseOutputRef values resolving to C.29 outputs whose mathematical results bear on the claim.

A referenced C.29 output retains its correspondence, assumptions, omitted detail or loss, and limits on reliance. Select the output under C.29:4.4: a conditional explanation or diagnosis may remain a MiniCard, while reliance on the result as an adequate model of the phenomenon requires the FullCard account. Reuse an adequate existing account.

Ordinary local mathematics need not produce a C.29 output, and an output reference does not assert a lens-use relation occurrence.

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. Recognition requires the relevant construction and identity grounds. When evidence is relied on, retain the evidence relations supporting the claim.

Use B.3 when the receiving question asks whether support is adequate for a named claim and use, or when a binding requirement calls for that assurance. Supply B.3’s minimum qualified result, adding Work, performer, or replay information only when that use requires it. Storing an optional classification assertion alone creates no separate assurance duty. Check whether existing support applies to the result claim; adequate support can be reused, while assurance for parts does not automatically transfer to the whole. Publication of the record is another relation under the publication patterns.

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

Before recognition, designate the candidate as a U.Entity and name the admitted kind under which it is being tested. A known failure of a necessary A.1 or kind-specific condition yields false; unavailable deciding grounds yield unknown. Neither result proves that the prior whole is sufficient for the receiving use.

For the established result, use one resultHolonRef : U.HolonRef 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 a preliminary, failed, or unresolved evaluation, use the optional classification assertion or result episteme governed by A.1 and C.2.1. Its EntityOfConcern is the candidate being evaluated. After establishing the new holon, a needed HolonReidentificationRecord may cite the classification judgment through 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. A false or unresolved assertion does not become a positive result by being cited in a record.

A historical record can be preserved when support later becomes unavailable; present reliance must reflect that loss, which alone does not change the object’s historical identity. B.2 asks a different question: whether the existing whole can continue to carry the subject claim or a new whole must be identified.

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 System and predicate, with any claim scope and qualification window required by the receiving use.

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 claim. B.2 uses agency threshold only as one possible trigger in MHTTriggerProfile, when crossing it raises a whole-reidentification question about closure, supervision, objective, or 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 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. Changing another holon does not establish a part-whole relation between that holon and the acting System.

B.2:4.7 - Mathematical-Lens Separation

A mathematical or analytical result, such as an MSPD measure or graph analysis, can contribute to an MHT claim through a justified correspondence with the objects and relations concerned. Compare models on the question the recipient is asking. Suppose a summary retains total output but omits which installation produced it. It can still establish a production threshold. To identify the installation, see whether its construction and history can be recovered or whether every history compatible with the summary gives the same identity answer under the governing rule. A history admitted only by the summary is insufficient to identify an actual producer. Carry the conclusion back in the direction supported by the correspondence. Use B.5.MR when the relation between the models themselves is at issue.

Use C.29 when a separate representation-choice, transfer or reliance question remains unresolved. Use B.2 for the consequential whole-reidentification question, beginning with the ordinary existing-whole comparison.

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 patterns;
  • a B.2 whole-reidentification assertion is a C.2.1 episteme about those objects;
  • evidence and assurance relations support or warrant claims about construction and identity grounds, including the reasoned choice of an applicable criterion in :4.0;
  • 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 identity and reidentification rules plus the construction facts. A.1 recognition alone does not establish a B.2 whole-reidentification claim or 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. When feedback and supervision around an objective change, use B.2 if the receiving claim leaves a consequential question about retaining or reidentifying the existing whole.

A positive new-whole claim requires constructive relations and a governed assembly, with its boundary, external commitments, and capability envelope no longer sufficiently explained as changes of the existing whole. Designate that proposed whole and test it under the already admitted U.System kind.

It can satisfy A.1 only if its 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.

The optional accounts below apply when the plant-plus-devices configuration is already an established holon under its identity rule and the regulated system has passed the comparison and recognition tests. If this is the first constitution of a whole from a collection of devices, use the A.1 construction-and-recognition route in :4 instead.

MHTTriggerProfile@Control : U.Episteme
  entityOfConcernRef: plant-plus-devices configuration
  content:
    changedFeedbackClaimRef: FeedbackClosureClaim under B.2.5
    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 EntityOfConcern is a 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 assertion keeps its observation and return-influence relations and its coupling grounds under B.2.5. Any supervision or capability relations retain their identities, while the optional classification assertion retains its 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. For a first episteme constitution, establish its claim-bearing structure and interpretation under C.2.1 and apply A.1. When an established prior whole is available, compare the changed claim-bearing structure, explanatory use, and reference scheme with its identity rule through :4.2. Evidence supports the comparison; a change in evidence alone does not reidentify the episteme.

B.2.3:5.1 shows a complete constructed comparison: an existing episteme supports a narrower deployment claim, while the required conclusion needs a changed ClaimGraph and ReferenceScheme and hence a different episteme under C.2.1. The prior episteme remains usable for its narrower claim.

B.2.3 specializes this case when the candidate new holon is to be tested under the already admitted U.Episteme kind. C.2.1 defines episteme constitution and identity. Use E.24.PUB when publication availability, form or carrier matters, and E.17 when a reader needs a publication face of the accepted account. Use C.2.P for unresolved source-expression or source-to-use distinctions and A.10 when a source-to-use account is needed for bounded reliance. Use G.6 when a later user must cite or replay a provenance chain, retaining the established facts, direct relations and their governors.

B.2:5.3 - Capability Envelope Appears

Several systems, methods, and work occurrences align and a new capability envelope appears. Establish the capability claim and the contributing facts under their patterns.

Use B.2.4 when capability or functioning changes raise a whole-reidentification question. Evidence supports the claim about those changes; the B.2 identity comparison determines whether the existing whole still suffices.

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 when changes in the manufacturing arrangement raise a consequential question about retaining or reidentifying the existing whole.

If the comparison establishes that a new whole is needed, recover the proposed candidate—for example, a production cell with constituents, obtaining coordination and supervision relations, a governed assembly, an objective, a whole-level capability, and its reidentification rule—and show why the earlier arrangement cannot meet the receiving use while retaining its identity.

A.1 recognition additionally requires the cell’s 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 maintenance, part-relation, work, transformation, and characteristic patterns and stop B.2.

In the closed-loop case in :5.1, the claim concerns a regulated system with a stated objective. To identify an actual new system, establish why the prior configuration no longer carries that claim and how the organized sensor, controller, actuator and plant together satisfy A.1 and the U.System criterion. Ground the objective, the supervision and the capability required by this case under their own predicates.

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

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 exists or whether the prior configuration remains the same whole.

B.2:5.6 - Selected Structure And Transformation Stops

A selected BoundedModelUseStructure organizes 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 changes during assembly may each be 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 governor supplies contribution, compatibility, boundary, interfaces, and reidentification, retain the blocker and the independently identified changes. The missing composition facts do not show that any change is atomic.

B.2:5.7 - Obtain a criterion before judging a production-cell change

In this constructed case, a maintenance engineer must decide whether replacing a robot and transferring supervision continues the commissioned production cell or requires identifying another whole. Three proposed accounts track the listed components, the achieved output and the installed organization. The receiving question concerns the maintained installation; scheduling separately needs the resources currently assigned to an order.

The available engineering material provides grounds for comparison. The design makes the robot exchangeable through specified mechanical, safety and control connections to the retained base, guards and fixtures. The maintenance procedure isolates the installation, replaces that module and tests those connections before return to service. The control arrangement permits supervision to be reassigned through the same interface. Separately commissioning another installation gives it its construction and maintenance history. The practitioner must turn these commitments and the construction facts into a continuity rule for the installation.

Apply B.5.TC to the three proposals. Requiring the same component individuals throughout conflicts with the design’s exchangeable-module construction: it would terminate the cell’s identity at the substitution that the maintenance operation performs within the retained organization. Preserved output is also inadequate as an identity criterion. The isolated cell temporarily produces nothing, and a second independently assembled cell can produce the same output at the same time. A named supervisor identifies a control participant; the design permits that participant to change while retaining the installation and its control interface.

The supported criterion therefore follows continuity of the installed assembly and its organizing connections, allowing the component substitutions those connections and the maintenance practice support. Its grounds are the design’s organization and the lifecycle operations on that organization. Component serial numbers, production measurements and supervisor assignments supply different facts needed by that account; none of the three alone identifies the continuing installation.

Now inspect the change. The base, guards and fixtures remain; the replacement robot fits the specified connections; the required connection checks pass; supervision transfers through the retained interface. Under the recovered criterion, the replacement is an admitted constituent change of the same cell. In :4.2, that supported maintenance explanation is sufficient, so keep the cell and update the changed component and responsibility claims under their subject patterns. The scheduling account can separately change its resource membership.

Change the conditions. If the governing criterion requires continuity of the installed assembly, and that assembly was dismantled, it no longer continues under that criterion. Another installation achieving the same output can meet a production target. For a claim about which installation supplied it, establish the new assembly and its link to the production history. For a proposal to preserve output after dismantling, the engineer can instead design the new arrangement and show what it would supply under its stated conditions. Realization and production remain separate claims.

If only output logs are available and the construction and maintenance grounds cannot be recovered, state the missing connection: whether the change preserves the installed organization under an applicable lifecycle rule. Retain the conditional identity alternatives. The logs can still support their bounded production claims.

B.2:6 - Bias-Annotation

Bias riskFailureMitigation
Emergence rhetoricA gain, surprise, or synergy label declares a new whole.Perform B.2’s existing-whole comparison before declaring a new whole.
Record as ontologyTrigger profiles, result fields, or checklist labels become U-kinds.Keep the trigger profile, optional explanation result, and reidentification record as U.Episteme values; keep the ordinary comparison as an action. Let E.24.UK handle public-kind admission and A.1 recognize the candidate new whole.
Math as MHTGraph, RG-like, MSPD, benchmark, scaling, or morphism expression declares whole reidentification.Recover the holon identity claim and its grounds; use C.29 for a remaining representation-choice, transfer or reliance question. Begin B.2 with the existing-whole comparison.
Binary agencyAgency threshold crossing is treated as a root kind or binary status.Use the characteristic-space and threshold patterns; use B.2 when the threshold claim raises a consequential whole-reidentification question.
Transformation as containmentA system changes another holon and is treated as its part or containing whole without a separately obtaining part-whole relation.Use A.12, A.3.4, A.15.1, and the crossing relation pattern; apply B.2 only when separately grounded facts make whole reidentification current.

B.2:7 - Conformance Checklist

CheckConformance condition
CC-B2-1A B.2 use names the receiving claim or use, the existing whole already recognized under an admitted holon kind, its identity rule, current part relations, and kind-specific pattern before declaring whole reidentification. Without an established prior whole, first constitution or recognition returns to A.1 and the applicable subject pattern.
CC-B2-2MHTTriggerProfile is a U.Episteme with the existing whole as EntityOfConcern and typed content references.
CC-B2-3A prospective comparison states the conditions under which the proposed arrangement would preserve or change whole identity. An actual MHT claim requires the prior and resulting whole and their grounds. The ordinary existing-whole comparison precedes that claim and distinguishes a supported same-whole explanation, established insufficiency, and an unresolved comparison as in :4.2. An optional ExistingWholeExplanationResult episteme is created only when a receiving use must inspect or cite its explanations, evidence, and sufficiency verdict.
CC-B2-4HolonReidentificationRecord is a U.Episteme with one resultHolonRef for the established new whole, one reference to its admitted public kind, the whole-reidentification claim, direct evidence and subject-pattern references, and only an optional C.2.1 classification-assertion reference when a person or system performing later work needs to inspect or cite that judgment.
CC-B2-5Agency-threshold claims use the characteristic-space and threshold patterns; B.2 uses them when they raise a consequential whole-reidentification question. The admitted System and characteristic are recovered independently of any optional local system-role classification or assignment, including when the System participates passively.
CC-B2-6Acting-system participation and transformation use A.12 and A.3.4.
CC-B2-7Mathematical expressions can bear on but do not replace the holon reidentification claim.
CC-B2-8The candidate new whole reference and its kind reference remain separate.
CC-B2-9A candidate new episteme, system, method, work occurrence, or discipline uses A.1 recognition plus its kind-specific pattern; a dependent U.Structure is not the new holon named by an MHT claim.
CC-B2-10Whether the existing whole continues or a new whole must be identified follows construction and reidentification facts; evidence availability, evaluation value, record currentness, and receiving reliance remain separate results.
CC-B2-11B.2 does not infer transformation composition, transformation parthood, composite identity, holonhood, or atomism from several changes, one work episode, one selected structure, or missing part facts.

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

Anti-patternSymptomRepair
Emergence by adjectiveA capability or property is called emergent without reidentifying the whole.Use B.2.P to recover claim kind, then B.2 only if whole reidentification is current.
Record as ontologyTrigger profile, result field, or record name is treated as a world-side kind.Keep the trigger profile, optional explanation result, and reidentification record as U.Episteme values; keep the ordinary comparison as an action. Let E.24.UK handle the candidate new whole’s public kind and A.1 recognize that candidate.
Content field as relation slotA reference field inside a profile or record is treated as a participant SlotKind or as evidence that the referenced relation obtains.Keep the field in episteme content, resolve its reference to the occurrence, and use that occurrence’s subject pattern for obtaining and identity.
KPI jump as MHTA metric improves and MHT is declared.Perform the ordinary existing-whole comparison; use the measurement, characteristic, Method, Work, or architecture pattern when it explains the change.
Agency shortcutAgency threshold crossing creates a new root kind.Use the characteristic-space and threshold patterns; apply B.2 when the crossing raises a whole-reidentification question about closure, supervision, objective, or identity.
Math result as MHTGraph, RG-like, MSPD, or benchmark expression declares new whole.Recover the holon identity claim and its grounds; use C.29 for a remaining representation-choice, transfer or reliance question. Use B.2 for the whole-reidentification question.
Transformation as containmentA system changes another holon and is treated as its part or containing whole without a separately obtaining part-whole relation.Use A.12, A.3.4, A.15.1, and the crossing relation pattern; use parthood only when a grounded part relation independently obtains.

B.2:9 - Consequences

Positive consequences:

  • MHT becomes a 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 helps locate the changed facts that need examination.
  • 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 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 the prior EntityOfConcern no longer carries the claim. First test whether the existing identity rule accommodates the changed facts, including any sufficient repair under a subject pattern. Whole reidentification is needed only when the existing whole no longer supports the explanation. Part-whole, Work, transformation, characteristic, representation, and publication claims retain their grounds throughout that comparison.

B.2:11 - Decision-bearing SoTA account

Practical questionPrimary sourceAdopt, adapt, or reject in B.2Effect in this pattern
When may a configured production arrangement be treated as a distinct operating whole?Bartels et al., Dependable Cyber-Physical Matrix Production Systems Utilizing Holonic Multi-agent Systems (2025), and Macherki et al., QHAR: Q-Holonic-Based Architecture for Self-Configuration of Cyber-Physical Production Systems (2021), with a production-system case illustrating how the architecture could support reconfiguration.Adopt the practical need to recover entities, flows, coordination, dynamic interdependence, control organization, and reconfiguration purpose. Reject a named holonic architecture, control layer, or reconfiguration event as sufficient whole identity.Section 4 requires the A.1 and applicable kind-specific criteria for a positive new-whole claim. Section 5.1 adds the objective, feedback and supervision grounds used by its regulated-system case.
What separates inputs, construction, and the resulting whole?Florio and Linnebo, Introduction to Constructional Ontology (2024), and Borgo and Righetti, Towards Applied Constructional Ontology (2025).Adopt the separation among accepted inputs, constitutive organization, and resulting identity. Adapt it to FPF’s direct part relations, assembly, reidentification rule, and admitted holon kinds. Reject a trigger profile, record, tuple, or Method label as the constructor that makes the whole exist.Sections 1, 4, 4.3, and 5 distinguish world-side construction from comparison and record epistemes.
How should agency bear on whole reidentification?Michael Levin, Technological Approach to Mind Everywhere (2022).Adopt non-binary, multi-characteristic, empirically tested agency and multi-scale competency as possible evidence about a system. Reject an agency label or threshold as a root kind or automatic new-whole result.Section 4.5 treats an agency threshold as a possible trigger when it raises a consequential question about retaining or reidentifying the whole.
What can a multiscale mathematical signal contribute?Akhtyrchenko, Katsnelson, and Ustyuzhanin, Directing Open-Ended Evolution in Artificial Life via Multi-Scale Path Divergence (v2, 3 August 2026), defines MSPD over realized trajectories as a multiscale analytical and optimization measure.Adopt MSPD as a possible analytical input when its trajectory assumptions match the case. Reject a high MSPD, RG-like score, graph pattern, or benchmark jump as whole reidentification.Sections 0, 4.7, and 8 use C.29 for a remaining representation-choice, transfer or reliance question and retain the B.2 identity comparison.

Constructional ontology makes the identity consequences of inputs and organizing relations inspectable. Its applied use depends on the intended ontology and domain commitments; those grounds determine which proposed construction answers the identity question. Section :4.0 connects their recovery with B.5.TC’s comparison of competing accounts.

The manufacturing studies contribute reasons for control organization and reconfiguration; a production or recovery result supports the corresponding behavioral claim. Identifying the continuing individual additionally needs its construction and continuity grounds. The case in :5.7 develops that connection under engineering premises.

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 to be tested under U.System, B.2.3 when it is to be tested under the admitted U.Episteme kind, and B.2.4 when capability or functioning facts raise a whole-reidentification question.
  • 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 for disputed identity grounds: B.5.TC for the comparison and B.5.TU when an application of a proposed account must first be constructed; :4.0 explains the identity-specific return.
  • 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 marked 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.

First useful move. Recover what the speaker means to establish and what the recipient needs to do with it. Write the claim in terms of its subject, the change or relation at issue, and the conditions under which it would hold. One phrase may join several claims. Preserve the connection between them when the recipient needs it.

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. The practitioner can replace ambiguous emergence wording with the claim and the pattern that supplies its grounds. Whole reidentification stays distinguishable from the neighboring claims in :4.2.

Not this pattern when.

  • If the text already names the subject pattern and object by value, use that pattern.
  • 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.
  • 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.

Recover the EntityOfConcern, the fact or assertion being discussed, its subject pattern, and whether the same whole still carries the claim.

B.2.P:2 - Problem

Unresolved emergence wording can produce these errors:

  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 name. 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. Description displaces the subject. A publication, dashboard, model, or source interpretation is examined in place of the holon or characteristic the claim concerns.

B.2.P:3 - Forces

ForceTension
Useful recognition vs false kindEmergence wording often marks a modeling concern, but it does not name a selected root kind.
Whole reidentification vs property changeSome cases need B.2; many cases need only characteristic, capability, function, architecture, evidence-use, or mathematical-lens patterns.
Collection language vs collective systemCollection words can name membership, a constructed whole, an acting system, or a characteristic bearer.
Source mnemonics vs current authorityShort labels help recognition but can preserve rejected ontology.
Mathematical expression vs ontology replacementFormal or statistical expressions can bear on a claim only after the thing or claim and its pattern are identified.

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. Object and scope. Which whole, constituent, group or relation is the claim about? Work back from the recipient’s decision to the distinctions that matter. A fleet may be a set of vessels for a count, an organized service for a delivery, or the subject of a model whose resolution has changed. For a claim linking these, establish how particular vessels contribute to the service and how the model represents that contribution. A class of vessels and an assembly of vessels require different grounds.
  3. Claim. Which fact is claimed about construction, identity, capability, a characteristic value, evidence, publication or representation? Is the change confined to the wording? Keep the subject fixed and vary the report, then keep the reported result fixed and vary its source or organization. Use any difference that changes the intended conclusion to choose what the replacement must distinguish. Mark a consequence derived under design assumptions as conditional.
  4. Subject pattern. Which pattern defines or constrains that object and claim without using emergence as a substitute?
  5. Disposition. Give the supported reading or readings. When several readings lead to the same action, give that result at its warranted scope. If the commission asks which reading the speaker intended, identify the words, facts or clarification that distinguish it. Open B.2 for a remaining identity question. Where the wording joins several supported claims, return their connection to the receiving decision.

Retain the source phrase beside the recovered claim and replacement only when that comparison is needed.

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

Recovered claim kindUse this subject patternDo not overread as
Whole reidentification of a holonB.2, with B.2.2, B.2.3, or the pattern for the new whole’s admitted kind; B.2.4 connects capability/functioning facts to the B.2 questiongeneric emergence, metric gain, or title mnemonic
Candidate new system wholeB.2.2all emergence cases or all system aggregation
Candidate new episteme wholeB.2.3 plus C.2.1 and episteme familyepisteme agency, publication authority, or EFEM by title
Capability or functioning facts that make whole reidentification live; evidence separately supports the claimB.2.4 under B.2generic capability, generic function, or all functioning
Ordinary capability claimA.2.2 and C.16MHT
Function or functioning claimA.6.F, A.3.4, C.30.TFS-REL, C.16, or subject pattern named by valueU.Emergence or MHT by wording
Whole-level characteristic or thresholdC.16 and A.19 for the characteristic, bearer and criterion; A.13 for a separate agency or agency-profile question; evidence-use patterns for a needed support or reliance accountnew whole by metric alone
Architecture-induced property or residualC.30 for the architecture contribution and A.22 for a selected organization; C.30.ASV for a needed structural-view qualification, C.30.TFS-REL for a selected transformation-flow structure or network, and C.30.ILC for a cross-scope or interlevel residual. Use C.29 for a remaining mathematical representation, correspondence, transfer or reliance question.MHT unless B.2 reidentification is recovered
Selected dependent U.Structure, including bounded model useA.22, A.1.1, and the patterns for its selected relation occurrencesa holon, acting agent, system part, or new whole named by an MHT claim merely by selection or name
Several changes in one work or flowA.3.4 for each independently identified changea composite transformation, transformation parthood, holonhood, or atomism without a composition governor
Mathematical emergence, scale, coarse-graining, graph, morphism, benchmark, or MSPD expressionApply the mathematical rule and subject pattern to the recovered claim; an adequate calculation can finish. Use C.29 for a remaining representation-choice, correspondence, transfer or reliance question.ontology by mathematical spelling
Metric or benchmark mirageIdentify the characteristic or benchmark and its measurement or evaluation rule, retaining the source and correspondence grounds the inference uses. Apply A.10 for a needed source-to-use account and C.29 for a remaining mathematical representation or transfer question.MHT or system admission
Collection or collective wording mixed with emergence, MHT, or synergyFirst recover membership, collection-as-whole, acting collective, whole-level characteristic, or MHTcollection admission by B.2.P
Model-use or model-comparison claimC.2.1:4.0.3 distinguishes a claim-bearing episteme from a physical specimen or observed performance used as a model. Recover the modeled entity, operation or observation, and grounds for the inference under the subject Method. Use B.5.MR for refinement or abstraction between models.reidentification of the modeled holon merely because the model changed
Publication, dashboard, theory-text, or report claimC.2.1 for episteme identity and content; E.17 for a needed publication face; E.24.PUB for publication, availability, expression or carrier distinctions; C.30.AD for an architecture-description question; a source-use pattern for the corresponding source claimin-life whole by description alone

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

When claim-kind recovery leaves a question about actual whole reidentification, first establish whether there is a prior holon. For a first constitution or recognition without one, use B.2:4 to return to A.1 and the applicable subject pattern. If the wording concerns a proposed arrangement, retain its design conditions and use the design branch of B.2:4 when needed. If the wording alone is in question, an adequately qualified restatement can finish the work. For a comparison with an established prior whole:

  1. name the receiving claim or use, the 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. perform B.2:4.2’s comparison: distinguish a possible continuation from the history that actually occurred and retain the whole for the conclusion the evidence supports; establish insufficiency from a violated necessary condition or an independently closed comparison; otherwise leave the deciding question unresolved;

  4. when the comparison establishes that the prior whole is insufficient, require B.2 and execute the A.1 criterion: designate the candidate as a U.Entity; recover its constituents, obtaining constructive relations, assembly, reidentification rule, and composition-grounded whole characteristic.

    Show that its 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 kind-specific criterion;

  5. return the supported result: the existing whole suffices, its insufficiency is established, or a deciding question remains unresolved. In the new-whole branch, report the candidate recognition result separately; a failed or unresolved candidate test does not establish that the old whole suffices;

  6. only when a 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.

    Follow B.2:4.3–4.4 for conditional assurance and for typed references to an established result; a preliminary, failed, or unresolved evaluation can be retained in the optional assertion without declaring a positive holon result.

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 candidate, a required constructive fact, or the larger-assembly compatibility condition lacks a defining rule or needed grounds, stop and name that gap.

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 when that profile is elected by publication choice or a named requirement;
  • 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 system-role-kind or assignment claim when either is current;
  • use C.16 for a whole-level characteristic.

Use each pattern for its corresponding claim. 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 thing or claim and its 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 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. State the B.2 comparison result and remaining question. When the new-whole branch is selected, identify its candidate and test its kind under the subject pattern; cite a separate 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”

Start with the decision in which the phrase was used. A harbour office asking how many vessels are on its eligible list can use the membership rule and a complete register. For a threshold, a sufficient bound may settle it. For an order to carry two cargoes on the same tide, trace each cargo to feasible vessels, loading work, shared berth time and who may assign it. The number of vessels can stay fixed while a change in control of the berth changes whether both deliveries can be promised. Confirmed access, terms and capacity can support that promise before either delivery occurs. A statement that the fleet became a new acting whole also needs its construction and continuity grounds. Recover the claims the particular wording makes:

  • 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.
  • For a new-system candidate selected by the B.2 comparison, are the A.1 criterion and the B.2.2 System criterion satisfied? Recover the delimitation, objective, coordination and capability claims used in this fleet case with their supporting grounds. Add assurance for a named assurance question or binding requirement.

If whole identity remains in question, use B.2 and, for its new-system candidate, B.2.2. For a managed collection with a whole-level metric, recover membership, any required collection construction, and the characteristic bearer and value under A.14, C.13 and C.16 respectively. Use B.3.5 only when its assurance profile is elected.

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

Recover:

  • What is used as the model, which entity does the inquiry concern, and which operation or observation on the model supports the inference?
  • If the model is a claim-bearing episteme, what are its claims and interpretation? If a mathematical expression or lens is used, what calculation and correspondence does the inference need?
  • Is robustness a characteristic-space claim?
  • Is the result a benchmark artifact?
  • Does the claim concern reidentifying the actual holon?

When a physical specimen or observed performance is used as a model, distinguish it from an episteme reporting its observations or results, as C.2.1:4.0.3 explains. Apply the model or evaluation rule to the recovered result and C.16 to its characteristic claim. Recover the assumptions, correspondence and evidence used by that inference; apply A.10 when a source-to-use account is needed, and C.29 for a remaining representation, transfer or reliance question. An adequate calculation can finish. Use B.2 when the actual whole’s identity 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 selected relation organization and its constituents from the account. If it is BoundedModelUseStructure, keep it as dependent U.Structure under A.1.1 and A.22. Naming, depicting or selecting that organization does not itself establish structural parthood, agency, holonhood or MHT; establish the needed facts under their predicates.

If the source concerns a system whole, begin with B.2’s comparison of the existing whole and changed facts; apply A.1 and System recognition when the new-whole branch is selected. First recognition without a prior whole remains with A.1 and the subject pattern.

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

Recover the 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 a construction or changes the 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 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 governor supplies constituent contribution, compatibility, boundary, interfaces, whole identity, and reidentification, return that blocker. Do not infer either composition or atomism.

B.2.P:5.7 - Bias-Annotation

BiasHow to address it
Emergence-as-root-kind biasThe recovery starts from EntityOfConcern, claim kind, and subject pattern; no generic U.Emergence is introduced.
Collection-agency biasCollective nouns are separated into membership set, constructed whole, acting collective system, whole-level characteristic bearer, or candidate new holon named by an MHT claim.
Metric-as-whole biasIdentify the characteristic or benchmark and apply its measurement or evaluation rule with the source and correspondence grounds it uses. Open B.2 only when whole identity remains in question.
Math-lens-as-ontology biasGraph, scale, morphism, benchmark, and MSPD expressions stay mathematical-lens or evaluation material until the in-life EntityOfConcern is recovered.
Source-mnemonic biasMET, MFT, promotion, and post* spellings remain recognition cues until the thing or claim and its pattern are named.

B.2.P:6 - Conformance Checklist

CheckRequirement
CC-B2P-1Precision restoration starts with claim-kind recovery, not lexical replacement.
CC-B2P-2No generic U.Emergence is created.
CC-B2P-3Whole reidentification requires B.2; B.2.P does not declare MHT.
CC-B2P-4Collection admission remains with subject patterns. Collection wording entangled with emergence or MHT selects B.2.P for clarification, not for admission.
CC-B2P-5Capability, functioning, characteristic, architecture, evidence, model-use, model-comparison, math-lens, publication, and source-use claims keep their subject patterns.
CC-B2P-6Source mnemonics and result-field spellings do not identify subject patterns or become U-kinds.
CC-B2P-7The replacement identifies the subjects, ranges and relations on which the intended conclusion depends and keeps conditional and actual claims distinguishable. The wording is reread in its complete natural span through F.19 with E.10 cues inside; only a remaining FPF question opens the applicable lexical or subject rule before live use.
CC-B2P-8Whole-reidentification recovery identifies the existing whole, changed facts and identity rule, then retains a supported sufficient explanation, establishes insufficiency, or states the deciding gap. In a selected new-whole branch, apply the A.1 criterion, including governed larger-assembly compatibility, and the kind-specific criterion; preserve a failed or unresolved recognition result. First constitution or recognition without a prior whole returns to A.1 and the subject pattern.
CC-B2P-9Evidence, evaluation, assertion or record identity, G.11 currentness, and receiving reliance remain separate from world-side construction and reidentification.
CC-B2P-10Selected dependent structures and collections do not become holons by name; several changes do not become a composite transformation, and a missing composition governor does not establish atomism.

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

Anti-patternSymptomRepair
Emergence as root kindThe sentence needs a new named thing called emergence.Recover claim kind; use B.2, C.16, C.29, C.30, A.2.2, A.6.F, A.10, or source-use pattern.
Collection receives agency by wordingA community, pool, fleet, or base acts because the noun is collective.Recover membership, collection-as-whole, acting collective system, whole-level characteristic, or MHT separately.
Metric jump as new wholeBenchmark improvement is declared as emergence.Establish what characteristic or benchmark changed under its measurement or evaluation rule, preserving the grounds needed for that inference. Use B.2 when whole identity remains the question.
Title mnemonic as authorityMET or MFT is used as if the acronym named the thing or claim under discussion.Recover an episteme-whole reidentification claim, capability or functioning facts, their episteme or function pattern, or source-only wording.
Representation as represented wholeA model, dashboard, report, or twin is identified with the holon it represents merely because it represents it.For a model, recover the modeled entity, the entity used as its model and the grounds for that use through C.2.1:4.0.3 and the subject Method. For a description, recover its claims, expression and publication under their patterns. Recognize each claimed holon under its own pattern.
Evidence decides ontologyMissing or stale evidence is taken to end a whole, while a current record is taken to create one.Keep construction and reidentification world-side; evaluate support, currentness, and reliance separately.
Selected structure as new wholeA bounded model-use structure or Context Map is called a meta-system.Keep dependent U.Structure under A.1.1 and A.22, and identify any candidate new system independently.

B.2.P:8 - Consequences

Positive consequences:

  • Readers can distinguish emergence-family claims without inferring a new kind from the wording.
  • 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 thing or claim and its pattern are identified.

B.2.P:9 - Rationale

Emergence-family wording can mark a useful explanatory question while leaving its object and claim unclear. Read the complete span through F.19 with the E.10 cues. Use E.10.ARCH or a subject pattern only for the remaining FPF meaning question, then reread the repaired sentence through F.19. The result states the object, claim, and conditions needed for its use.

B.2.P:10 - SoTA-Echoing

FPF uses claim-kind recovery (B.2.P:4.1–4.4) to keep whole reidentification with B.2 and ordinary characteristic, capability, evidence, and measurement claims with their subject patterns. Membership, a constructed whole, an acting collective system, a whole-level characteristic bearer, and a candidate new holon named by an MHT claim must be identified separately. Publication, source-use, model, dashboard, and architecture-description claims remain separate from the in-life whole-reidentification claim.

A historical comparison shows why the distinction matters for mathematical emergence. Hoel, Albantakis, and Tononi (2013), Abstract and Fig. 2 compare effective information at micro and macro scales in systems whose micro mechanisms are fixed; a macro model can have greater effective information.

FPF adapts this comparison by keeping that mathematical result separate from an MHT claim, which needs the B.2 identity account. Mathematical and statistical treatments of scale, coarse-graining, graphs, morphisms, and benchmarks can clarify a claim without replacing the ontology: keep the in-life EntityOfConcern and subject rule identified, using C.29 for a remaining representation, correspondence, transfer or reliance question (B.2.P:4.2 and B.2.P:5.2).

B.2.P:11 - Relations

B.2.P:End

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

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

B.2.2:0 - Use This When

Use this pattern when the decision about continuing or replacing an operating whole requires testing a candidate under the already admitted U.System kind. A candidate can be supplied, or its boundary can be part of the engineer’s design commission. Examples include a production cell, platform or organizational unit with the organization to act in Work or transformation while remaining itself.

First useful move. For a specified candidate, apply A.1’s six common components and then the U.System criterion. Establish its physical embodiment and the organization through which it can act in Work or transformation while preserving its identity. When the commission instead leaves the system boundary to the engineer, use B.2:4 and :4.1 below to form the candidate from the required use. A design can establish what would qualify on its stated conditions.

After those two tests, recover only the additional facts used by the 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 for the comparison with the prior whole, including a proposed change. Use B.2.2 for the system question and return its answer to that comparison. For the first construction or recognition of a system with no established prior holon, use B.1.2 and A.1.

What goes wrong if missed. An operating whole is 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 practitioner obtains a System-recognition result for B.2’s candidate and can determine which claims about the new operating whole need their own grounds.

Not this pattern when.

  • If the result whole is claim-bearing and non-agentive, use B.2.3 and the episteme family.
  • If capability or functioning facts are sufficiently explained without whole reidentification, use their subject patterns. A.2.2 governs capability, C.16 measured characteristics, A.3.4 transformations, and C.30.TFS-REL the selected flow structure’s bounded architecture use. Use A.6.F for unresolved function-like wording and A.10 for a needed replayable source-to-use account.
  • If the claim is ordinary system aggregation or delimitation, use B.1.2, A.1, A.14, and C.13.
  • If the claim concerns a mathematical, simulation, graph, benchmark, or scaling expression, use its mathematical or subject pattern, with C.29 for an unresolved representation-choice, transfer or reliance question. Use the relevant description or publication pattern when that claim is current; return to B.2 only for a whole-reidentification question.
  • 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.

B.2.2 tests whether B.2’s proposed new whole satisfies A.1, is physically embodied, and has an organization through which it is eligible to act causally in work or transformation while preserving its identity—the U.System criterion.

If it does, recover the separately governed system-level claims needed by the case, 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 A.1 recognition and the U.System criterion.

B.2.2:2 - Problem

When system recognition and the claims about the new whole are conflated:

  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 collective name is used in place of System-recognition grounds or of the additional facts that the claim needs, such as an objective, coordination relation, or capability envelope.
  3. Supervision is overread. A coordination mechanism is treated as a containing whole, safety warrant, or system recognition without the corresponding facts.
  4. Transformation is confused with containment. One system changing another holon is treated as part-whole construction instead of transformation and work.
  5. Representation is mistaken for the represented system. Dashboards, diagrams, simulations, bills, and digital twins are identified with the system they represent.

B.2.2:3 - Forces

ForceTension
Component assurance vs result-system assuranceOld component claims may matter, but they do not automatically cover the new operating whole.
Delimitation vs external participationThe result system needs an admitted delimitation while external acting systems, external resources, and its environment remain outside it.
Coordination vs whole identityAn obtaining coordination relation can make the system question live, but coordination alone does not satisfy A.1 or the U.System criterion.
Capability gain vs identity changeA new capability envelope can reveal a result system, but some gains remain ordinary capability or functioning claims.
System architecture vs system descriptionArchitecture claims concern the operating whole; diagrams and records have separate description, representation, or publication uses.

B.2.2:4 - Solution

After B.2 leaves a whole-reidentification question open, continue with the candidate new whole and its facts.

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

Start with B.2’s candidate designated as a U.Entity, proposed for the already admitted U.System kind.

When the task is to propose the system, trace the result required at its interface to what must be organized together to deliver it. Which component changes can the surrounding system accommodate? Which relations must the proposed assembly itself preserve? Compare an internal component with access to the same service from an independent provider. They may yield the same output today and different answers about who can control a later change. Include the provider as a constituent only on the grounds for that parthood. Relate any required Method and its operations, or Work and its performances, to the system through what it can enact or actually performed. Return a proposed boundary, the relations on which delivery depends and the limits of that conclusion. Apply the following tests to each candidate whose recognition matters.

After the recognition tests below establish the result, use B.2’s one resultHolonRef for that individual and its one resultHolonKindRef resolving to U.System. The references may appear in B.2’s optional HolonReidentificationRecord when a receiving use needs a durable account. Preliminary, failed, and unresolved evaluations follow B.2:4.4.

Before calling the candidate a system result:

  1. execute the A.1 criterion over the candidate’s constituents, obtaining constructive relations, governed assembly, reidentification rule, and composition-grounded whole characteristic;
  2. show that its 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 U.System criterion to that individual: establish that it is physically embodied and that its organization makes it eligible to act causally in work or transformation while preserving its identity;
  4. recover only the additional system facts used by the 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 each additional result-system fact or claim needed by the use under the pattern that defines or tests it:

  • 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 claims through their subject patterns; use A.6.F for unresolved function-like wording, E.18 for a selected transformation-flow structure, and C.30.TFS-REL for its bounded architecture use;
  • architecture through C.30 and its selected A.22 structure; use C.30.ASV when a structural description must also be assessed as a U.View;
  • evidence under its subject pattern; use A.10 when a replayable source-to-use account is needed, B.3 for a named assurance use or binding requirement, and B.3.5 only when its additional relation-assurance profile is elected;
  • temporal claims under their patterns, with C.27 for a dynamics question and A.19 for a characteristic-space claim.

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 continuing relation; establish each changed result-system fact under its subject pattern.

Where evidence is relied on, recover its relation to the result claim. Apply B.3 for a named assurance use or binding requirement as in B.2:4.3; reuse existing support when it is adequate for that claim and use.

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:

Cue recorded in MHTTriggerProfileSystem-case readingSubject pattern kept visible
Delimitation changeThe operating whole now has an external delimitation and crossing relations that differ from the old aggregate.A.1, B.1.2, A.14, C.13
Objective or evaluation changeRecover the system-level objective, mission, or SLO used as an evaluation criterion; distinguish any safety case or viability claim from that criterion.C.16, E.13, decision or assurance patterns; A.10 for a needed replayable source-to-use account
Supervision or coordination changeRecover how constituent behavior is regulated for the result whole, including controller or distributed-coordination facts; name any protocol or governance claim separately.B.2.5 only for supervisor-subholon feedback; A.12, A.3.4, A.15.1 for their separately current claims
Capability or closure claimRecover the capability envelope and closure relations of the proposed new whole after recognition under U.System; keep supporting evidence separate.A.2.2, C.16, B.2.4 when whole reidentification is current; A.10 for a needed replayable source-to-use account
Agency thresholdThe result whole crosses a concern-specific agency threshold in characteristic space.A.13, A.19, C.16
Temporal consolidationA commissioning, phase, release, or operating-time consolidation changes the system identity claim.C.27, A.15.1, temporal patterns
Context reframeA changed question or selected model-use structure changes which whole is under concern; it does not itself change that whole’s identity.A.1.1, A.22, B.2, and the whole’s identity pattern

Use the cues to locate the facts that decide the question. One such fact can refute recognition if it contradicts a necessary condition. A single adequate engineering account can also supply all the grounds for a positive recognition. In either case, return the consequence for the commission. Whether the prior whole is sufficient is decided by B.2’s comparison.

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 is admitted.

B.2.2:4.5 - Assurance Re-Basing

When a receiving use or binding requirement needs assurance about the recognized U.System, test whether existing support applies to that system and claim. Reuse an applicability assessment when its claim, use and conditions match.

Ask:

  • Which component evidence 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 where its evidence or source-use relation supports that claim and applicability is established for the receiving use. Reuse a matching judgment; reassess when the claim, basis or relevant conditions change. 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

In this constructed case, B.2 has compared an established drone-system whole with the proposed coordinated search arrangement. Its supported result is that the prior whole cannot meet the search use while retaining its identity, and it names the proposed search-and-rescue swarm as the candidate new whole. The project retains individual-drone navigation and maintenance records. Test the candidate below; its mission objective, coordination relation, external command relation, capability envelope and swarm-level risks retain their own grounds.

  • Candidate new whole: the search-and-rescue swarm named by B.2.
  • A.1 basis: 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 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. Their contribution to a swarm-level claim depends on that claim and the evidence’s applicability.

Choose the assurance claim about the swarm. If it requires every current member to hold a specified certificate, a complete membership list and a valid certificate for each member can settle it. If it requires the swarm to cover the search area, establish how the members’ paths together cover that area under the mission conditions. The same set of certified drones can fly overlapping paths that leave part of the area unsearched.

B.2.2:5.2 - Cloud Platform

Consider independent services proposed as one platform with a shared control plane, system-level SLO, deployment and rollback coordination, platform-level evidence, and external commitments. Establish those case facts under their patterns and test the proposed whole under :4.1.

If a better dashboard or an additional service is sufficiently explained as a change of the existing whole under its identity rule, use the relevant architecture-description, publication, measurement, or component pattern.

Use B.2.2 when B.2 identifies the operating platform as the candidate new whole to be tested under A.1 and the U.System criterion. Claim a system result only after those tests pass; retain a failed or unresolved evaluation under :4.1.

B.2.2:5.3 - Production Cell

A proposed production cell has a machine, robot, fixture, workpiece carrier, and inspection station as candidate constituents. Apply :4.1 to recognize the whole. For the operating-cell case, separately establish its delimitation, objective, coordination relations, transformation structure, Work occurrences, and capability envelope, with evidence for those claims.

Suppose the order asks for inspected workpieces by closing time. An available outside station with an assured handoff and enough time for inspection and delivery can supply a viable route. This can finish a request to choose a route. An order for inspected workpieces is fulfilled when the agreed inspection and delivery have taken place by closing time. If the order also requires a cell that retains inspection while the outside station is unavailable, work back from that use to the provision for inspection under those conditions. An installed station is one possibility. Determine its interfaces and the assembly relations that would make it part of this cell. A plan for the installation gives a conditional design result. A claim that this cell did the inspection requires grounds for what happened on the order.

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

Bias riskFailureMitigation
Named aggregate as systemA fleet, platform, or cell name is treated as system recognition.Apply B.2 to one candidate; require the A.1 criterion and the U.System criterion.
Component evidence transferComponent certificates are read as assurance for the proposed new whole after its recognition under U.System.Assess applicability to the result-system claim through the evidence or assurance relations; reuse a matching assessment, rather than transferring support by label.
Coordination as wholeA controller, protocol, or coordination relation is treated as automatic system MHT.Recover the obtaining relation, then require B.2 whole reidentification plus A.1 and U.System recognition; keep any support separate.
Representation as represented systemA dashboard, simulation, model, twin, or bill is identified with the system it represents.Recover the represented system, the representing entity and the grounds for that use. C.2.1:4.0.3 distinguishes model use from episteme identity; apply the description or publication patterns to those separate claims. Any claim that the representing entity is itself a System needs its own A.1 test.
Transformation as containmentAn external system changes a holon and is treated as its part or containing whole without a separately obtaining part-whole relation.Use A.12 for the acting side, A.3.4 for the transformation, and A.15.1 for any claimed Work. Use B.2.5 when supervisor-subholon feedback is the question and a part-whole pattern when parthood is claimed.

B.2.2:6 - Conformance Checklist

CheckRequirement
CC-B2.2-1B.2 supplies the whole-reidentification question. Where proposing a boundary was entrusted to the practitioner, justify it from the required work and the relations the assembly must maintain. A specified candidate may be assessed directly.
CC-B2.2-2For a proposal, state the conditions under which it would meet the requested use and qualify as a System. Recognition of an actual system result requires the candidate to pass A.1 and the U.System criterion on the facts that obtain. Failed or unresolved recognition follows :4.1.
CC-B2.2-3Use B.2’s references for the candidate and established result. Any durable account remains an optional C.2.1 episteme under B.2.
CC-B2.2-4Identify the result-system delimitation and any crossing relations needed by the claim under their predicates.
CC-B2.2-5An obtaining supervision or coordination relation is not treated as automatic system recognition, and evidence for it is not treated as safety warrant.
CC-B2.2-6Acting-system participation, transformation, and work are separated from parthood.
CC-B2.2-7Component assurance is not silently transferred to the result system.
CC-B2.2-8Recover the model-use, episteme, representation or publication claim separately from recognition of the System it concerns. If the representing entity is itself claimed to be a System, test that entity separately under A.1.

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

Anti-patternSymptomRepair
Named aggregate as system“The platform” or “the fleet” is treated as a system because it has a name.Identify one candidate and apply the A.1 and U.System criteria; if either fails or cannot be determined, withhold system-result recognition and return that failure or unknown to B.2 without inferring that the old whole is sufficient.
Component certificate transferIndividual part certificates are used as result-system assurance.Re-base assurance through B.2.2:4.5 and evidence-use patterns.
Controller as containing wholeA controller or external system is treated as the new whole because it changes the parts.Use A.12 and A.3.4 for the acting-side and transformation claims. Use B.2.5 for a supervisor-subholon feedback question and a part-whole pattern for the claimed parthood.
Dashboard as represented systemA monitoring model is identified with the system it monitors.Use episteme, publication, source-use, C.30.AD, or digital-twin description patterns for the monitoring account; recover the monitored system independently.
Capability jump as system MHTA metric improves and the result is called a new system.Perform B.2’s ordinary existing-whole comparison; return to capability, characteristic, Method, Work, or architecture patterns if the existing whole remains sufficient.

B.2.2:8 - Consequences

Positive consequences:

  • Meta-system transition remains usable for engineering and organizational systems without making B.2 system-only.
  • A.1 and the U.System criterion apply to the candidate; each additional system claim retains its grounds.
  • 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 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.

Recognizing the candidate requires construction and acting eligibility under A.1 and the U.System criterion. A description or coordination claim supplies only its contribution; every additional claim about the recognized system needs its subject-specific grounds.

B.2.2:10 - SoTA-Echoing

A new coordinated whole can become the relevant operating object. Within B.2’s whole-reidentification comparison, B.2.2 applies A.1 and U.System recognition to the proposed candidate (B.2.2:4.1). B.2.2 keeps the facts with their subject patterns when the claim concerns changed operational closure, coordination, external commitments, or assurance at the level of the new whole proposed for and then recognized under U.System. Component support contributes to assurance for that recognized system only where it applies to the result claim.

A historical comparison clarifies the coordination question. Maier (1998), Architecting Principles for Systems-of-Systems, §§1 and 2.6–2.7 distinguishes systems-of-systems whose components retain operational and managerial independence. In his collaborative category, central management lacks coercive power to run the system; treating it as a directed system can lead to unwarranted assumptions about component cooperation.

FPF adapts this distinction in B.2.2:4.3 by recovering the controller or distributed-coordination facts and naming any protocol or governance claim separately. Maier’s taxonomy does not supply the A.1 or U.System recognition tests.

Acting on an object and being part of it are different relations. A.12, A.3.4, A.15.1, A.14, and C.13 remain separate subject patterns.

Descriptions can track a system without being that system. Use episteme, description, representation, and publication patterns for the descriptive item; recover the operating system independently as EoC.

B.2.2:11 - Relations

  • Specializes: B.2 by testing its candidate new whole under the A.1 criterion and 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 marked informative

B.2.3:0 - Use This When

Use this pattern when whole reidentification concerns a theory, model family, standard, doctrine, specification body or other claim-bearing non-agentive holon. B.2.3 supplies the test for a proposed U.Episteme. If the commission includes constructing the account to be tested, work from the conclusion its recipient needs.

Use B.2 for the comparison with the prior whole and B.2.3 for the proposed episteme. Where the commission concerns first constitution or recognition with no established prior whole, use A.1 and C.2.1 as explained in B.2:4.

First useful move. For B.2’s candidate, identify its interpreted claim content, the independently identified EntityOfConcern, and the effective rules for designating that entity and interpreting those claims (C.2.1:4.1.1). Test whether their EpistemeConstitutionRelation obtains. When the recipient needs a claim or a new account and leaves its construction open, start with what the account must establish. Use :4.1 to select its premises and their interpretation.

Keep grounding, viewpoint, view, publication, source use, representation, evidence, and assurance in their neighboring 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 new episteme whole is treated as a pile of publications.

What this buys. The practitioner can recognize B.2’s candidate as an episteme under C.2.1 and distinguish that result from its publication, use, and assurance claims.

Not this pattern when.

  • If the result whole is a physically embodied holon eligible to act, use B.2.2.
  • When no whole-reidentification question remains, use the episteme, publication or source-use pattern for the remaining question; :4.2 and CC-B2.3-4 distinguish these uses.
  • 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.
  • Use A.15.1 to establish performed synthesis Work and A.12 or A.3.4 for acting-side and transformation claims. For an order to construct a claim-bearing account, identify the result needed in :4.1. Use B.2 when its relation to a prior whole matters.
  • If the wording is ambiguous emergence-family language, use B.2.P before selecting B.2.3.

B.2.3:1 - Problem Frame

A collection does not become a theory merely because its items are stored together. Distinguish the claim-bearing whole from its publication form and carrier.

A group of papers, models, datasets, design notes, forecasts, standards, or local doctrines may remain a collection. Use B.2.3 when B.2’s candidate new whole is to be tested under A.1 and the C.2.1 constitution criterion for one interpretable claim-bearing episteme.

B.2.3 tests B.2’s candidate under A.1 and C.2.1, then retains B.2’s one resultHolonRef and resultHolonKindRef for the established result. Each neighboring relation keeps its subject pattern.

B.2.3:2 - Problem

Confusing the episteme with its collection, representation, or publication can produce these errors:

  1. Collection as MHT. Storing publications together is treated as sufficient for an episteme-result MHT without testing the candidate’s constitution and the B.2 comparison.
  2. Publication form becomes episteme. A carrier or publication form is mistaken for the claim-bearing episteme it presents.
  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 establishing B.2 whole reidentification by itself.
  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 claim graph, reference scheme, and grounding relation.

B.2.3:3 - Forces

ForceTension
Synthesis vs aggregationA new episteme whole can integrate claims, but many collections remain indexes, reviews, or portfolios.
Episteme identity vs publication formThe episteme may be published in many forms; no publication form is the episteme by appearance.
Claim organization vs agencyAn episteme can organize claims and guide use, but systems perform work with or on it.
Constituent evidence vs result assuranceEvidence for parts may bear on the result. When assurance is required for a result claim, test whether that support applies to the claim and its receiving use.
Source mnemonic vs ontologyShort labels can aid recognition while hiding whether the question concerns B.2 whole reidentification, C.2.1 constitution, A.6 morphing, E.24.PUB publication, an E.17 reader face, or source use.

B.2.3:4 - Solution

Use B.2.3 as the U.Episteme specialization of B.2. Reuse its existing whole, candidate new whole, construction facts, and any optional C.2.1 records needed for this use.

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

Start with B.2’s candidate designated as a U.Entity, proposed for the already admitted U.Episteme kind. If the candidate is given, assess it directly. When the practitioner is to construct the account, start with the conclusion the recipient needs about its subject. Trace that conclusion back to the claims that could warrant it, including any relation needed to use them together. Ask whether the relevant terms designate the same objects, populations and occasions across those claims. Two local models may give the same totals while assigning them to different individuals. A total can settle a threshold for the whole. A conclusion about which individual qualified requires the distinguishing information or another ground that settles it. If an existing account already yields the required answer, give that inference. An order to construct a new unified account calls for its own result. To build it, choose its constituent claims, the inference joining them and a scheme that preserves their intended interpretation. A source consulted in this work may supply a premise without becoming a constituent of the resulting episteme.

For recognition, execute the A.1 criterion over that candidate, including the larger-assembly applicability and compatibility condition. Apply C.2.1 to that individual:

  1. identify its interpreted claim content, including the semantic relations among its claims, under C.2.1:4.1.1;
  2. identify the independently governed U.Entity that those claims concern;
  3. identify the effective reference scheme: the designation and interpretation rules under which those claims are read about that entity; and
  4. test whether the 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 participant triple. A reference or representation alone does not establish that the constitution relation obtains. 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.

For an established episteme result, B.2’s resultHolonRef designates that individual and resultHolonKindRef resolves to U.Episteme. Preserve a preliminary or unresolved judgment in an optional C.2.1 assertion only when a receiving use needs it; B.2:4.4 governs that distinction.

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

The ClaimGraph, EntityOfConcern, and effective ReferenceScheme are the three participants of C.2.1’s EpistemeConstitutionRelation. C.2.1:4.1 identifies the ClaimGraph and ReferenceScheme as epistemic constituents of the interpretable claim-bearing whole. Establish that constitution for the candidate, and recover any further claimed part or composition relation under its pattern.

The EntityOfConcern remains an independently governed entity related through aboutness and reference. Keep all other questions in their relations:

  • empirical grounding uses EpistemeEmpiricalGroundingRelation only when designated empirical claims have current claim-to-world mappings involving the grounding holon;
  • viewpoint selection for a describing use follows E.10.D2; U.View recognition requires E.17.0 conformance of the episteme to a viewpoint;
  • publication occurrence, publication form, carrier, source use, and C.29 representation remain distinct from the episteme and its constitution;
  • an 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 obtaining A.13 assignment, while any transformation remains a separate claim; and
  • evidence and assurance support or challenge the claims being made, including claims about constitution; they add no identity discriminator to C.2.1’s ClaimGraph/EntityOfConcern/ReferenceScheme triple.

Add only the neighboring object or relation required by the receiving use. Establish each such relation under its predicate and participants; keep it separate from the episteme’s 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:

Cue recorded in MHTTriggerProfileEpisteme-case readingSubject pattern kept visible
Delimitation changeRecover what changed in claim content, EntityOfConcern or effective ReferenceScheme. Identify a claim scope when the claim requires one.C.2.1, A.7, source-use patterns
Objective or evaluation changeThe result episteme contains an answer or evaluation claim for a question that the collection did not answer as one claim-bearing whole.C.2.1, C.16, E.21 or relevant evaluation pattern
Supervision or coordination changeRecover a supervision or coordination relation under its defining pattern. Principles, axioms, invariants, reference schemes, and claim-graph constraints instead organize claim interpretation; inspect that change as a constitution or claim-composition claim rather than filling a relation-occurrence field with it.C.2.1, A.6.0, A.6.1, C.29 when formal lens is current
Capability or closure claimThe candidate episteme supports a new explanatory, predictive, specification, or coordination use; evidence for that claim remains separate.C.2.1, C.16, the pattern for that use; A.10 for a needed replayable source-to-use account
Agency thresholdThe episteme remains non-agentive. For an agency-characteristic claim, recover the System and characteristic predicate, with any scope and window required by the receiving use, and test the characteristic independently; that characteristic claim does not require an assignment. A precise agency claim requires the separate A.13 core. If dated Work is also claimed, recover each performer through A.13 and let A.15.1 independently admit the Work. Add F.6 only when the receiving claim consumes precise assignment-bound attribution; missing or failed F.6 alone leaves independently admitted Work intact. If the same finding also invalidates a premise consumed by the A.13 or A.15.1 admission, recheck that premise and its dependent conclusions.A.12, A.2.1, A.13, A.19, C.16, A.15.1, F.6
Temporal consolidationA chronology or source-currentness change prompts inspection of the knowledge body. Test any changed ClaimGraph, EntityOfConcern or effective ReferenceScheme under C.2.1; currentness alone changes none of those identity values.C.2.1, C.27, G.11, E.17, and source-use patterns
Context reframeNew terms, reference schemes, or EntityOfConcern mapping reframe the knowledge body.C.2.1, A.6.3, A.6.4, F.18

These cues identify claims and relations to inspect. They neither constitute the candidate episteme nor select B.2; the facts, 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

Recognition of an episteme result establishes neither agency, publication authority, nor inherited assurance. Use the applicable subject patterns for those separate claims; the non-use cases in :0 identify the other operations.

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

B.2.3:5.1 - Reliability Doctrine

Reliability work may begin with local runbooks, incident reports, dashboards, and definitions that remain a collection. A first doctrine constitution requires A.1 and C.2.1; the collection supplies no prior holon merely by being named. The following constructed case instead starts with an already recognized episteme and asks whether it can support a stronger deployment claim.

Supplied setting and receiving need. The example stipulates a modeled deployment S = Relay-S/D17, independently identified by its deployment configuration, and a fixed nonempty set of requests. Use classical two-valued logic. Ack(r) means that D17 emits an acknowledgement for request r; PrimaryStored(r) means its primary store holds that request’s payload when the acknowledgement is emitted. The already recognized episteme E0 = <G0, S, R0> has a ClaimGraph containing the sole premise:

P: for every request r, Ack(r) implies PrimaryStored(r).

R0 is the complete scheme interpreting this graph, with those request, acknowledgement, and primary-storage designations. The receiving work now needs one episteme whose stated premises support a derivation of:

Q: for every request r, Ack(r) implies
   (PrimaryStored(r) and ReplicaStored(r)).

Here ReplicaStored(r) means the replica holds the same payload at acknowledgement time. Q concerns the deployment S. The required new object, if established, is an episteme carrying and supporting Q.

Compare with E0. In the comparison vocabulary, retain all R0 meanings and add ReplicaStored. Set Ack(r*) = true, PrimaryStored(r*) = true, and ReplicaStored(r*) = false for one request, with Ack = false for every other request. This valuation satisfies P and falsifies Q, so G0’s stated premise does not entail Q. To obtain the required derivation, supply the additional premise:

T: for every request r, Ack(r) implies ReplicaStored(r).

T is a stipulated premise of this example, not a reliability fact proved about an operating service. Let G1 contain P, T, Q, and the inference deriving Q from P and T by conjunction introduction under the common antecedent. Let R1 retain R0’s meanings and add the replica-storage designation. The candidate is E1 = <G1, S, R1>.

Nonentailment alone would not establish a new identity. Here C.2.1’s declared identity discriminators are the ClaimGraph, EntityOfConcern, and effective ReferenceScheme. Keeping E0 requires retaining G0 and R0. Adding the premise, inference, and effective designation needed for this use changes both G and R, so the result cannot be E0 under that identity rule. This establishes insufficient for E0 and this receiving use. E0 exists and supports P; a different layout or publication of its unchanged triple would leave it E0.

Recognize the candidate. The construction supplies each A.1 ground:

GroundSupplied fact or demonstrated result
Individuated candidateE1 is the candidate <G1, S, R1>.
ConstituentsG1 and R1 are its epistemic constituents under C.2.1; S remains the independently identified EntityOfConcern.
ConstructionR1 interprets every claim and inference in G1 about S, and G1 organizes P and T as premises for Q. This satisfies the C.2.1 constitution predicate for one interpretable claim-bearing whole.
IdentityC.2.1 reidentifies this episteme by that G1/S/R1 triple. A change in one of those values identifies another episteme.
Composition-grounded characteristicG1 supplies the inference organization and R1 its interpretation about S; together they yield an interpretable derivation of Q. P and T each leave one of Q’s conjuncts unestablished.
Compatibility with a larger assemblyThe argument construction below incorporates E1 unchanged and uses Q in a further derivation.

For the last ground, supply a local argument-assembly rule: retain an interpreted argument as an unchanged constituent, preserve its graph and interpretation, and join its conclusion to an additional compatible premise by a named inference. Construct E2 = <G2, S, R2>. G2 contains G1 as an unchanged subargument and adds the supplied lemma L: (PrimaryStored(r) and ReplicaStored(r)) implies Recoverable(r) for each request. R2 retains R1 as the fixed local scheme for that subargument and adds the meaning of Recoverable(r): the modeled recovery method can read back r’s payload at the stated time.

Under the assumption Ack(r), Q gives both storage conditions and L gives Recoverable(r) by modus ponens; discharging the assumption yields Ack(r) implies Recoverable(r). Under this construction rule, E1 is a constituent of E2 with its graph, local scheme, subject, and identity preserved.

E1 therefore satisfies the displayed A.1 grounds and C.2.1 constitution and meets the receiving need. If later work needs a reidentification record, resultHolonRef names E1 and resultHolonKindRef names U.Episteme. The record and any classification assertion concern E1; Q concerns S.

The logical construction establishes the conditional derivation, not the truth of P, T, or L for a real deployment. A use that must rely on those service claims needs their grounds and any assurance required under B.3. When the question is whether the stated derivation is available, the displayed construction settles it. In another doctrine whose interpreted premises already entail Q, a request to derive Q can be met from those premises. For assurance about one actual request, an applicable record establishing the acknowledged payload at both stores may already suffice. Neither conclusion establishes that a particular operator consulted the doctrine. That historical question turns on evidence of its use.

Change the interpretation condition. Suppose the supplied candidate uses G1 with the complete R0, whose declared vocabulary has no interpretation of ReplicaStored. The proposed <G1, S, R0> fails constitution: its scheme cannot interpret the whole graph. Supply a scheme that does interpret it and identify the resulting episteme.

By contrast, if R1 exists but is unavailable to the evaluator, evaluation is unknown; recover the scheme or withhold the classification. Neither result erases E0 or changes the identity of an already constituted E1. A failed or unresolved judgment is not a typed positive result in the optional record.

For a larger reliability doctrine, the comparison uses its claims about user-visible service harm and reliability, its independently identified subject, and its effective designations. Add empirical grounding to operating services, handbook publication, and source use for standards or training materials only when the receiving use needs them.

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 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 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 the publication, source-use or characteristic pattern for that claim. Use A.10 when its source-to-use account must be replayable and C.29 for an unresolved representation-choice, transfer or reliance question.

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 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 performer through A.13 and admit the Work independently under A.15.1. Add F.6 only if the account consumes precise assignment-bound attribution; missing or failed attribution alone leaves independently admitted Work intact. If the same finding invalidates an admission premise, apply CC-B2.3-5.

The PDF file carries an expression of the standard. A selected publication form supplies the reusable rules that this expression follows.

B.2.3:5.4 - Bias-Annotation

Bias riskFailureMitigation
Library as MHTA repository, dashboard, or reading list is taken as sufficient for an episteme-result MHT.Recover the candidate’s claims and constitution under A.1/C.2.1, then test the B.2 whole-reidentification claim. Ordinary episteme constitution alone does not establish that claim.
Publication as epistemeA publication form or carrier is treated as the claim-bearing episteme.Keep the episteme, publication form and carrier distinct under C.2.1 and E.24.PUB.
Episteme agencyA theory, standard, or doctrine is described as performing Work or enforcement.Recover every acting System through A.13 and let A.15.1 independently admit the Work. Add F.6 only when the receiving account consumes precise assignment-bound attribution; a missing or failed attribution alone leaves independently admitted Work intact. For an admission premise invalidated by the same finding, apply CC-B2.3-5.
Morphing as MHTView, translation, coarsening, or retargeting is taken as sufficient for B.2 whole reidentification.Use the A.6 operation; C.2.1 decides whether its source and target are different epistemes. Use B.2 when the whole-reidentification question remains.
Source trust transferTrust in constituent sources becomes assurance for the result episteme.Assess the support and source-use relations against that result claim; reuse a matching current applicability judgment and retain only support that applies.

B.2.3:6 - Conformance Checklist

CheckRequirement
CC-B2.3-1B.2 supplies the question about continuity. For a commission to build an account, the proposed claims, inferential organization and effective interpretation are justified by what the recipient must establish. A request about an existing account can be settled by its present grounds.
CC-B2.3-2A positive episteme-result claim requires B.2’s candidate new whole to pass the A.1 criterion and C.2.1 constitution under the already admitted U.Episteme kind. Failed or unresolved recognition follows :4.1.
CC-B2.3-3Retain B.2’s candidate and established-result references. C.2.1’s ClaimGraph, EntityOfConcern and effective ReferenceScheme remain the identity discriminators; neighboring relations and any optional durable account stay separate.
CC-B2.3-4Use C.2.1 for constitution and the patterns in :4.2 for neighboring claims. Use E.24.PUB for publication availability, form or carrier distinctions and E.17 for a needed reader face of an accepted account. Use C.2.P for unresolved source-expression or source-to-use wording, and C.2.P.DR for claims inferred from declarative form alone.
CC-B2.3-5The episteme is non-agentive. Acting Systems first satisfy A.13, and synthesis or enforcement Work is independently admitted through A.15.1. F.6 enters only when the receiving use consumes precise assignment-bound attribution; missing or failed F.6 alone leaves independently admitted Work intact. If the same finding also invalidates a premise consumed by the A.13 or A.15.1 admission, recheck that premise and its dependent conclusions. Agency-characteristic evaluation remains independent of assignment.
CC-B2.3-6Assurance for the result episteme is not silently inherited from constituent epistemes or publications.
CC-B2.3-7Effect-free morphing, viewing, retargeting, and controlled coarsening are not treated as B.2.3 unless whole reidentification is current.

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

Anti-patternSymptomRepair
Collection as MHTAggregation is taken as sufficient for an episteme-result MHT.Recover the candidate and test A.1 plus C.2.1 constitution and the B.2 comparison; if recognition fails, withhold episteme-result recognition. Keep any independently established collection or ordinary episteme claim without inferring that it is sufficient for the use; report unknown when a required test cannot be evaluated.
PDF as epistemeA PDF carrier or its publication form is used as the theory itself.Use publication patterns for the PDF and keep B.2’s resultHolonRef for the independently constituted episteme.
Doctrine receives agency“The standard enforces…” or “the theory decides…”For a literal claim of dated enforcement or decision Work, recover its performer through A.13 and admit the Work independently under A.15.1; add F.6 only when the use consumes precise assignment-bound attribution. Otherwise use F.19 to retain ordinary guidance wording when its capable user and action are recoverable.
Morphism as MHTA view, translation, coarsening, or retargeting is taken as sufficient for B.2 whole reidentification.Use A.6.2, A.6.3, A.6.4 or A.6.3.CSC for that operation and C.2.1 for episteme identity; use B.2 for a remaining whole-reidentification question.
Synthesis as high trustA new theory inherits trust because its sources were reliable.When this assurance claim is needed, assess it under B.3 and retain the source-use relations. Use A.10 for a needed replayable source-to-use account, B.3.5 only when its profile is elected, and C.2.1 for a live constitution question. Reuse adequate existing support rather than inheriting assurance from the sources.

B.2.3:8 - Consequences

Positive consequences:

  • The practitioner can distinguish a new claim-bearing whole from a collection or changed publication.
  • 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 C.2.1 constitution, not only cite a portfolio.
  • Result-episteme assurance needs warranted applicability to the result claim and receiving use. A matching current applicability judgment may be reused; reassess when the claim, basis or relevant conditions change.
  • Some “new theory” claims return to publication, source-use, morphism, benchmark, or evidence-use patterns.

B.2.3:9 - Rationale

A knowledge synthesis may yield a new claim-bearing whole. Establish that conclusion through the whole’s construction and identity, then assess its other uses separately.

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

The distinction between episteme constitution and neighboring relations is an FPF construction. B.2.3 requires C.2.1 constitution. State the synthesis claim within the scope needed for its interpretation and use. Recover evidence relations, currentness qualifications, and maintenance conditions only where the receiving use or a binding rule requires them. Assurance and source use remain neighboring relations.

A knowledge body can be represented as related claims, evidence, and sources. The ClaimGraph is a C.2.1 constitution participant. Keep its graph representation, evidence, and sources in the neighboring relations described in B.2.3:4.2; C.2.1 governs episteme identity and B.2 governs whole reidentification.

Fields and theories can consolidate into named bodies with new scope and organizing principles. B.2.3 treats a named consolidation as a cue to inspect; use C.2.1 for the candidate’s constitution and B.2 only for a whole-reidentification question.

A standard, report, model, or dashboard use may concern claim content, a representation, a publication form, or its carrier; its name alone does not decide which. Publication availability, form and carrier distinctions follow E.24.PUB; use E.17 when a reader needs a face of an accepted account.

Source-use claims retain their relations; use A.10 when bounded reliance needs a source-to-use account. Those relations remain separate from the episteme’s constitution. The constructed case in B.2.3:5.1 applies these distinctions to a stronger claim about a deployment.

B.2.3:11 - Relations

  • Specializes: B.2 by testing its candidate new whole under the A.1 criterion and C.2.1 constitution for the already admitted U.Episteme kind.
  • Builds on: B.2 for the 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 marked informative

B.2.4:0 - Use This When

Use this pattern when a claim about capability, functioning or transformation flow raises a consequential question about the identity of the whole. The question may concern an existing bearer or the organization a proposed bearer would need.

First establish what the recipient must decide about the ability, its exercise or the identity of its holder. A supported account of one performance may settle a question about that occasion. For a promise or a design, identify the conditions under which the holder must be able to deliver. When that decision depends on keeping or changing a whole, compare what the existing arrangement can support under its identity rule. Use B.2 for the remaining identity question, including one whose deciding grounds are unresolved.

Evidence and measurement support, challenge, or leave unresolved the claims about those facts. Use the supported facts in B.2’s comparison of the existing and candidate wholes.

What goes wrong if missed. A 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 practitioner can distinguish a change within an existing whole from a capability or functioning change that requires testing a new whole.

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 claim, use A.6.F to recover its subject pattern; an already precise functioning claim returns 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.
  • Use A.3.1 for Method identity, B.1.5 for Method composition, A.3.2 for a MethodDescription, A.15.2 for a WorkPlan, and A.15.1 for a Work occurrence; A.15 aligns roles, Methods, and Work.
  • If bearer allocation is the question, use the 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 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 their respective subject questions. Use A.10 when a replayable source-to-use account is needed.
  • 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 capability, functioning, or transformation-flow facts raise a consequential question about retaining or reidentifying the existing whole. Evidence bears on claims about those facts.

B.2.4:2 - Problem

Confusing capability and whole identity produces these errors:

  1. Capability becomes generic emergence. A threshold crossing or new envelope is treated as a new whole without B.2 checks.
  2. Function wording hides the claim. A function label substitutes for identifying the obtaining relation and its participants.
  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 result whole is left as “just a better capability”.

B.2.4:3 - Forces

ForceTension
Capability facts vs whole identityCapability facts can make a new-whole question live; capability claims stay with A.2.2 and measured-characteristic claims with C.16, whether or not that question arises. Their evidence remains separate.
Functioning relation vs part-whole relationFunctioning often crosses parts and bearers; it is not parthood by wording.
Transformation-flow structure vs mathematical descriptionFlow structure may enter architecture claims; selecting a graph or diagram as an object of concern does not identify it with the flow structure it represents. Its lens, description, or publication use remains separate.
Method composition vs performed workA method relation can describe possible doing, while a dated work occurrence is an in-life fact and evidence only supports claims about that occurrence.
New whole vs local improvementThe pattern must preserve novelty without turning every improvement into MHT.

B.2.4:4 - Solution

Use the capability and functioning facts to decide whether B.2 whole reidentification is needed.

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

  1. Start from the required result and scope. Whose ability or work matters, under which conditions, and what would a different answer change? For a whole-identity question, identify the relevant holder and the conditions for its continuity.
  2. Trace the needed functioning back to the systems that provide it, the operations that compose the Method, and any Work whose performances the claim concerns. Choose the extent of each from its contribution to the required result. Vary which participant supplies an operation while the output stays fixed, then ask what the same participant could supply under a different arrangement. Keep distinctions that change the recipient’s decision or its grounds. Establish each capability, functioning relation or in-life transformation-flow structure under its subject pattern. A design specifies what would have to hold.
  3. State the claim made about those facts. For any relied-on evidence or measurement result, identify whether and how it supports or challenges that claim, retaining any unresolved conclusion. Keep the measurement and its result distinct from the evidence-use relation.
  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. If the practitioner is asked to develop an arrangement, work from a missing contribution to a feasible change in the Method, allocation, external support or assembly. Test whether the contributions can be obtained together under the required conditions. A justified limit may decide feasibility. An order for one workable arrangement can finish with the first supported one.
  5. Use B.2 for a remaining whole-reidentification question, including an unresolved deciding ground. When the comparison establishes that the existing whole is insufficient, B.2 identifies a candidate new whole, applies the A.1 and kind-specific criteria, and tests whether it meets the receiving use before claiming whole reidentification.

If a receiving use needs a durable account, use B.2’s optional C.2.1 epistemes to state the facts, comparison, and supported conclusion.

B.2.4:4.2 - Subject-Pattern Test

Begin by testing whether the facts are already explained under an applicable subject pattern:

Fact or claim under concernSubject pattern if sufficientB.2.4 remains current only when
Capability envelopeA.2.2 for the capability of a System holder, C.16 for measured characteristics; A.10 when a replayable source-to-use account is neededthe envelope and holder facts leave a consequential question about whether the existing whole carries the receiving claim
Function or functioning relationThe pattern for the functioning claim; A.6.F for unresolved function-like wording, A.3.4 for a transformation and C.16 for a measured characteristicthe obtaining relation and whole-level facts leave a residual new-whole question
Transformation-flow structureE.18 for the selected structure, A.3.4 for transformations, C.30.TFS-REL for bounded architecture use; C.29 for an unresolved representation-choice, transfer or reliance questionthe selected in-life structure leaves a consequential question about which whole can carry the claim
Method relation or method familyA.3.1 for Method identity, B.1.5 for composition, A.15 for role–Method–Work alignment, and G.5 for registry or selector-facing use; use the pattern for any separately claimed family relation and C.29 for an unresolved representation-choice, transfer or reliance questionthe method facts leave a consequential question about whether the existing whole carries the receiving claim
Method description or procedure textA.3.2 and C.2.1 distinguish the MethodDescription and its episteme identity; use E.24.PUB for a publication availability, form or carrier question, E.17 for a needed reader face of the accepted account, and C.2.P for unresolved source-expression or source-to-use wording. Use A.10 when bounded reliance needs a source-to-use account and G.6 when a provenance chain must be citable or replayable, preserving each direct relation and its governoran in-life whole-reidentification question remains after the description is separated
Work plan or work occurrenceA.15.2, A.15.1planned or performed work facts leave a new-whole question; the plan or occurrence is not the whole by label
Module, component, or bearer allocationThe allocation or parthood pattern; A.6.M for unresolved module/interface wording; C.30, A.22 or C.30.ASV only for the corresponding claimallocation and architecture facts leave a consequential question about retaining or reidentifying the whole
Metric, score, threshold, robustness, or quality claimC.16 and A.19 for their respective subject questions; A.10 when a replayable source-to-use account is neededthe underlying characteristic facts leave a consequential question about whether the existing whole carries the receiving claim

B.2.4:4.3 - Existing-Whole Explanation

Perform B.2:4.2’s ordinary existing-whole comparison for the named receiving claim or use and the established whole’s identity rule. Distinguish a supported explanation, established insufficiency, and an unresolved comparison. Materialize its optional ExistingWholeExplanationResult only when another use must inspect or cite the outcome. If no prior holon has been established, use B.2:4’s first-constitution or recognition return to A.1 and the applicable subject pattern.

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 for the receiving use, retain the existing whole and finish B.2.4. Use the subject pattern for any remaining question. The same performance records may leave it open whether the holder could repeat that result when support is unavailable. Conversely, a binding provision for support and a suitable operating arrangement can establish a conditional ability before the next performance. Use the applicable identity criterion if the conclusion also names a continuing holder.

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

Use B.2 when subject-pattern explanations leave a consequential question about whether the existing whole can carry the subject claim. The comparison can retain that whole, establish the need to test a proposed new whole, or remain unresolved. Examples:

  • a production cell has a 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;
  • 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 constitution and explanatory-use facts that leave an episteme whole-reidentification question.

Use B.2 for the remaining comparison and, when required, the test of a candidate new whole. When needed, preserve the comparison in its optional result episteme or an established new whole in its reidentification record.

An unresolved comparison requires its missing grounds; it does not establish that a new whole is necessary. B.2:4.4 separates the candidate designation and optional evaluation from typed result references. The subject patterns define and test the contributing facts; evidence and measurement support 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 proposed production-cell whole becomes current for B.2’s comparison when the capability, functioning, coordination and transformation-flow facts leave a consequential question about retaining or reidentifying the existing whole. 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 unresolved 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 when those facts leave a consequential question about retaining or reidentifying the cell whole.

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 Method and Work patterns for the method relations and performed release work.

B.2.4 becomes current when capability, coordination, commitment, and work facts raise a consequential question about whether the existing team or platform carries the receiving claim. Evidence may support that claim; an automated delivery label or score does not decide the ontology.

Suppose each of two teams can obtain a whole shift on a shared test bench when the other team is idle. One release yesterday establishes a performance. To decide whether both can be promised a release on the same shift, recover the test each release requires and the bench time they can use together. If each requires the whole shift for its own test, one available bench excludes that joint arrangement. If one test is valid for both releases and the teams may use the same result, that part of the promise can be met in one shift. Determine separately whether the other conditions for both releases hold. The decision can turn on the Method and the rights to use the result while both teams retain their identities.

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 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 tests the candidate under U.Episteme; C.2.1 defines its constitution; use C.29 for an unresolved representation-choice, transfer or reliance question.

B.2.4:5.4 - Bias-Annotation

Bias riskFailureMitigation
Capability as emergenceA new capability label or supporting report declares a new whole.Recover the capability facts and pattern, separate their evidence, and perform B.2’s ordinary existing-whole comparison.
Function as partA function block or functioning relation becomes physical or organizational parthood.Separate functioning relation, bearer allocation, selected structure, and part-whole claims.
Method chain as wholeA sequence of methods or work stages is called a new holon.Keep method, method description, work plan, and work occurrence with subject patterns.
Diagram as flow structureA diagram or graph is treated as the in-life transformation-flow structure.Recover the described flow and distinguish it from its representation. Use description, publication or mathematical-lens guidance for a question about those subjects; use E.18 for the selected structure and B.2 for a remaining whole-reidentification question.
Metric jump as MHTA benchmark, KPI, robustness, or threshold gain declares whole reidentification.Recover the characteristic/value claim and its grounds, then perform B.2’s existing-whole comparison. Use A.10 when a replayable source-to-use account is needed.

B.2.4:6 - Conformance Checklist

CheckRequirement
CC-B2.4-1The comparison answers the receiving question about the holder and its continuity over the conditions that matter. Established performance, capability conditional on support and a proposed arrangement each supply the conclusion their grounds warrant. Close a sufficient subject-pattern answer at its own scope.
CC-B2.4-2Ordinary capability, function, functioning, transformation, method, work, module, characteristic, evidence, and architecture claims return to subject patterns.
CC-B2.4-3A capability or function label does not substitute for the subject-pattern facts or B.2 whole comparison.
CC-B2.4-4Distinguish the Method and its operations, its description, the plan and the Work performed. Where their organization or a choice among arrangements matters, show how the selected contributions can meet the intended use together.
CC-B2.4-5Mathematical or publication descriptions of transformation-flow structure do not replace the in-life structure.
CC-B2.4-6If B.2 remains current, it handles the remaining whole comparison, tests a candidate new whole under the A.1 and kind criteria when required, and supplies any optional record needed by the receiving use.

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

Anti-patternSymptomRepair
Capability by declarationA leader names a new capability, but the capability facts remain component-level or unknown.Test the capability claim under A.2.2; use C.16 for a measured-characteristic claim and A.10 when a replayable source-to-use account is needed. Use B.2 if a consequential whole-reidentification question remains.
Function as partA function block is treated as a physical or organizational part.Recover the functioning, allocation or parthood claim under its pattern. Use A.6.F or A.6.M for unresolved function-like or module/interface wording; use E.18, C.30.TFS-REL, C.30, A.22 or C.30.ASV only for the corresponding flow, architecture, selected-structure or view claim.
Method chain as wholeA sequence of methods is called a new holon.Recover the method relation and any current work occurrence; use B.2 when those facts leave a consequential whole-reidentification question.
Diagram as flow structureA diagram or graph is treated as the transformation-flow structure.Use the applicable description, publication, mathematical-lens, or selected-structure pattern; use B.2.4 only after the selected structure is recovered and a whole-reidentification question remains.
Metric jump as wholeA KPI improves and MHT is declared.Test the characteristic claim under its subject pattern and perform the existing-whole comparison. Use A.10 when a replayable source-to-use account is needed.

B.2.4:8 - Consequences

Positive consequences:

  • Capability and functioning facts can make 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 test the applicable subject-pattern explanations before declaring that whole reidentification is needed.
  • 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 facts, not the availability of supporting evidence, determine whether the existing-whole explanation still works.

B.2.4 asks whether the capability and functioning facts can be explained while retaining the existing whole. Use B.2 for the whole-identity question that remains, including a deciding ground that is missing. This keeps local capability improvement available without overlooking a change of whole.

B.2.4:10 - SoTA-Echoing

FPF’s construction in B.2.4 preserves capability and functioning claims while deciding whether whole reidentification is needed (B.2.4:4.1–4.3). The A.2.2 capability claim concerns the named System holder’s ability under the conditions in its capability envelope and at the stated attained bounds. Evidence and source-use relations support or challenge that claim and qualify reliance on it.

Obtaining functioning relations and selected in-life flow structures can make a new-whole question live; descriptions and diagrams remain distinct from those facts. Method, method description, work plan, and performed work occurrence must stay separate when capability evidence is interpreted.

When a receiving use consumes agency-characteristic values, select the needed characteristics from A.13’s profile and retain the grounds and uncertainty of those values. Use the applicable characteristic and measurement patterns; a measurement keeps C.16’s measurement conditions. State a concern-specific threshold when the use makes a threshold judgment. B.2.4 does not create a binary agency kind. A.13:8 identifies the profile’s FPF engineering choices and its research motivation.

B.2.4:11 - Relations

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 marked informative

B.2.5:0 - Use This When

Use this pattern to describe two-sided feedback between one supervising acting system and one or more supervised holons, or to specify that coupling in a proposed control arrangement. If the supervision is conditioned by a local system-role kind or assignment, recover that classification and assignment separately.

First identify the decision for which feedback matters. Is the question about a specified exchange, supervision of each member, control of an organized whole or a policy to be designed? Use the observations and actions that could change that decision to select the relevant participants, scope and interval. For a claim about an exchange that took place:

  1. Name the supervised holons and the admitted system supervising them.
  2. State the feedback use, policy, and time window. Add a local supervisor system-role kind and assignment when that classification matters.
  3. Identify the observation, report, signal, publication, or source relation that conveys state.
  4. Identify the influence, constraint, objective, mode, or Work change returned to each holon.
  5. State the rule and case facts coupling each return to its observation.
  6. Separate any additional transformation, Work, architecture, evidence, assurance, timing, or causal claim.

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 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 pattern.
  • If module or interface wording hides the claim, use A.6.M to recover it; use the 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 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 rules for those additional claims.

B.2.5:2 - Problem

Keep three structures distinct:

  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

ForceTension
Recognizable feedback language vs kind precisionEngineers use feedback, control, supervision, and regulation language naturally; FPF needs the relation and neighboring claim kinds named.
Relation vs viewA supervisor-subholon relation may appear inside a control-structure view, but the view and relation are different objects.
Acting system vs epistemeA theory, model, standard, dashboard, or report used as a claim-bearing episteme remains distinct from the System that revises or uses it.
Closure vs stronger claimsA two-sided feedback relation can supply input to stability or assurance work, but does not certify those claims.
Medium visibility vs perfect communicationThe relation needs observation or report and influence or constraint sides, including publication or medium limits when current.

B.2.5:4 - Solution

For a claim about actual supervision, identify who or what was observed and who or what received the coupled influence. A controller may use a joint condition to act on a whole. A local observation may instead govern an action on one part. For a claim that holds separately for several holons, state it for the required members and interval. One account applying throughout that scope can support all the pairs. State the result in a C.2.1 episteme using A.6.RCD’s compound-claim branch. A further use may call for a separately reidentifiable occurrence under :4.1.

For a nonempty set H and each h in H, recover three propositions under their 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 named use, participants, scope and temporal qualification. This is logical conjunction of those propositions, not a combination of probability scores or assurance results.

Recover each 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 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

Trace the observation into the choice made under the applicable rule and the resulting influence to its recipient. An observation can enter the choice even when another reading in the same range would yield the same action. A matching schedule and a copy of the observation show no such use by themselves. A record that identifies the actual input, executed rule and delivered result can settle the question directly. For one-way reporting, retain the established observation.

A confirmed failure of a condition required by the claim, such as a return to a named supervised holon, rules out that claim for the stated interval. When the remaining decision depends on an unspecified coupling rule, identify the missing rule. If the rule is applicable and a required fact is undecided, identify the information that would settle it. Check the rule’s requirement for a nonempty supervised set before an affirmative assertion.

Keep the base occurrences and their 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 pair is supported. A common rule and evidence covering every required member may supply those grounds together. To establish feedback on a particular part, show how the observation represents a relevant state of that part and how the coupled return reached it. For a question about receipt alone, confirmed delivery to every member can establish that one member received the message even when its state was never observed.

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. The supervising entity must be independently admitted as U.System; it may supervise under a 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 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 supervisor system-role kind and A.2.1 supplies the obtaining assignment. Distinguish that system from an episteme it uses, such as a policy or report.

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.

To design the feedback, start with the decisions the responsible system must be able to take. Which changes of state would require different action, and by when can that system observe the difference and act? Several arrangements of the parts can give the same whole-level indication. For each indication available before the decision, choose a permitted response that serves every admissible arrangement still consistent with it. If no such response exists, seek a timely observation that separates cases sufficiently for that choice, or revise the proposed policy. The aggregate can suffice when the same response serves the entire group. Specify the participants, observation, return and coupling for the required uses. This conditional result can complete a design commission. An assertion about an actual interval still uses :4.1.

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 a remaining mathematical representation, correspondence, transfer or reliance question.

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.

Case facts under R1Compound result
At tick 10, C receives d1’s 1.2 m report, generates reduce speed from it under R1, and d1 receives that command.All three conjuncts hold for {d1} at tick 10.
At tick 11, C receives telemetry, but the only delivered command is an unrelated scheduled broadcast.The known command has no R1 coupling to that report; it does not satisfy this feedback predicate.
At tick 12, the report arrives but the complete tick trace shows no returned command.The return conjunct fails. Reporting remains an independently supported fact.
At tick 13, the link breaks and the complete trace shows no same-tick report or return.The claim covering every tick 10–13 fails under R1. A supervisor assignment may still continue under its rule.
At tick 14, the link reconnects and a new report, R1-based command and delivery are established.The tick-14 claim is supported from those new facts; the earlier interval does not become uninterrupted.

If the tick-13 trace is unavailable and the remaining evidence permits both a complete exchange under R1 and a failure at that tick, feedback at tick 13 remains unresolved. The complete trace at tick 12 still refutes uninterrupted feedback throughout ticks 10–13. The wider and narrower questions can therefore have different answers from the same records.

If R1 changes to R2, use R2’s coupling test for the new interval. Adding d2 requires d2’s 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.

Name the admitted System performing the review or revision; its local system-role kind and assignment, when relevant, 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 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. For example, a release coordinator may change the shared release window in response to the total backlog. The total can support that common decision even when the same total arises from backlogs at different teams. To choose which team can release its own change, the coordinator may instead need its outstanding checks. A total that leaves that choice open can still settle the window question. What the coordinator actually used in yesterday’s decision requires grounds for that occasion.

Work alignment uses A.15; a separate work-authority claim needs its pattern; use the lookup in A.15.4:3.5 when the required permission or authority claim is unclear.

Gate passage uses A.21; A.6.M restores interface wording before the commitment claim returns to its pattern; architecture view uses C.30.LCA when the control structure is described.

B.2.5:5.4 - Bias-Annotation

BiasCorrection
Supervisor relation mistaken for parthood or containing-whole identityThe supervisor relation is not a parthood claim; A.1 governs holon recognition, A.14 the mereological claim, and B.1 or C.13 the applicable construction account.
Feedback-as-proof biasA closed feedback relation may supply input to separate stability, safety, assurance, or timing work, but does not certify those claims.
Description-as-relation biasA diagram, dashboard, report, or control-view description does not establish the in-life feedback relation by itself.
Episteme-agency biasOnly an independently recognized Holon fills a supervised reference. A theory, standard, model, dashboard, or publication may instead be used on the source side under its kind and relation; the supervising acting system must be named, and any system-role assignment is separate.

B.2.5:6 - Conformance Checklist

CheckRequirement
CC-B2.5-1Identify the supervised holon or holons and the supervising acting system at the scope the receiving use requires. A design states the conditions on which the proposed policy would provide feedback. Add a local supervisor system-role kind and assignment when applicable.
CC-B2.5-2For an actual feedback claim, identify the observation and returned influence, the rule used and the grounds for their coupling over the stated participants and interval. For a proposed policy, explain how the available observation permits the required choice and how the return could reach its recipient in time.
CC-B2.5-3The assertion is the conjunction of observation, return and coupling for every member of a nonempty supervised set. It introduces no fused U.Relation occurrence. Use the applicable mathematics for a loop; C.29 addresses a remaining representation, correspondence, transfer or reliance question.
CC-B2.5-4Observation and influence references retain their kinds; a report episteme, signal occurrence, and source-use relation are not interchangeable.
CC-B2.5-5Parthood, control-structure view, base publication and source-use relations, and the compound feedback assertion are kept separate. Each base occurrence keeps its identity and extent rules.
CC-B2.5-6Stability, safety, timing, causal, evidence, assurance, gate, and mathematical-lens claims use the patterns that define or test them.
CC-B2.5-7Episteme examples name the acting systems that perform review, revision, publication, or use.

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

Anti-patternSymptomRepair
Unspecified supervisor-subholon feedbackSubholons are said to be coordinated through supervisor-subholon feedback, but no supervising acting system, medium, or feedback relation is named.Recover the supervised holons, supervising System, observation side and returned influence side. Record that claim only when the receiving use needs it; add a system-role kind or assignment only when independently current.
Functional layer as componentA planning or control layer is modeled as a physical part of the controlled holon.Separate parthood from feedback relation; use C.30.LCA for the view.
Perfect communicationState access is assumed instant, complete, or lossless.Name medium or publication limits; use C.27, A.3.3, or evidence-use patterns for timing and information claims.
Episteme actsA claim-bearing episteme is assigned sensing, judging, planning, or adaptation that a system performs.Name the acting System and distinguish it from the episteme it uses. If the account asserts a dated Work, recover the acting System through A.13 and let A.15.1 independently admit that Work. Add F.6 only when the account consumes precise assignment-bound attribution through the obtaining A.13 assignment; F.6 identifies neither assignment nor performer; missing or failed attribution alone leaves independently admitted Work intact. If the same finding invalidates an A.13 or A.15.1 premise used for admission, recheck that premise and the conclusions that depend on it. A short sentence may omit an unused assignment identifier. Name the Method or review practice structuring the Work when relevant, and any publication or source-use relation. This Work rule does not make assignment or system-role classification a condition of the feedback claim itself.
Relation certifies safetyThe feedback relation is treated as evidence, assurance, gate, or safety result.Keep the relation and use the pattern for the stronger claim.

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 naming the 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 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 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 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 coupling rule. This supports a 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 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 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 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 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 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. A visible label or artifact contributes only through the claim and basis the argument uses.

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

First useful move. Identify the conclusion its recipient must assess, how it will be used and the work entrusted to the assessor. A sufficient existing argument can settle a question about one claim. To design an assessment, work back from the recipient’s decision to the distinctions the assessment must make (§4.1). To establish how someone actually used a result, identify the decision and the evidence about its use (§4.6). The domain rule governs the resulting action.

What goes wrong if missed. A visible label or a score starts raising trust without a 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 sufficient for 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 domain pattern for safety, permission, access, responsibility, release, compliance, or controlled action. Consequence alone does not create an assurance claim. A domain rule may require one, but the claim must be stated before B.3 is applied.

First output. For each assurance question, state the bounded AssuranceResult or the limits of the available support. If the commission concerns several claims together, carry these judgements through to the conclusion the recipient needs. For a commission to design the assessment, supply the way to reach that conclusion under the permitted conditions.

B.3:1 - Problem frame

Assurance concerns a claim, not the world-side subject in isolation. Begin with one 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 subject identified by its pattern.

For example:

  • a battery-pack safety fact and its 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 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 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

ForceTension
Small result vs inspectabilityA practitioner needs a quick result, while a consequential or reusable claim may need a replayable argument.
Shared discipline vs domain meaningAssurance needs common boundaries, while each characteristic and aggregation rule gets its meaning from its subject and domain.
Conservatism vs useful synthesisThe result must avoid overstatement without discarding justified combination or independent lines of support.
Formal clarity vs warranted beliefFormalization can improve inspectability and checking while leaving truth or empirical adequacy unchanged.
Current use vs change over timeAn assurance conclusion must be usable now and reopen when its basis, scope, or conditions change.

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 target claim;
  2. the named assurance use;
  3. the conclusion that must be supported, narrowed, or refused for that use.

When you must choose the argument, start from a difference that could matter to the recipient. Hold a test result fixed and vary the assembly in which the tested part is used. Hold the reported performance of the assembly fixed and vary which part supplied it. If the assurance judgement changes, trace the relevant part, its connection or its enclosing system until the evidence reaches the subject of the claim. Choose the extent of each other inquiry by the same test. The operations required by an assessment Method can differ from the work performed on one occasion. A report may identify the work that supplied a premise. Establish the relation on which the inference depends.

At each relevant scale, ask whether situations your model describes alike could require different assurance conclusions or explanations. Recover a missing distinction when it matters, or show that the available grounds suffice throughout the admitted range. For an assessment of future cases, use those differences to choose what to examine, how the assessor can obtain it in time and what follows from each relevant finding. An assessment designed under stated assumptions can be delivered before it is performed.

Keep the following objects separate:

  1. world-side facts and 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 C.2.1 episteme or one C.2.1 ClaimAddress when the use concerns one addressed claim inside a larger episteme. basisRefs cite the results, evidence-use relations, provenance paths, argument claims, or domain rules used. A compact result is complete when these fields decide the named use and its basis and limits are recoverable.

Keep the assurance argument readable beside its result or through references that let the recipient inspect it. Explain why the cited basis supports the target claim for this use, including assumptions, limitations and contrary results. This written account is an assurance case.

Develop it while reasoning: start with the claim and use, state the proposed support, and revise the argument when a premise or inference proves inadequate. A short coherent paragraph can suffice; add detail when review, transfer or later reconsideration needs it.

Use C.2.1 to identify the epistemes whose claims make up the case. A claim about a system retains that system as its subject. For an assurance-result episteme, the EntityOfConcern is the target claim content or episteme whose support is being judged; targetClaimRef locates that subject.

A case can bring several such epistemes together, preserving their identities and argument relations. The text or diagram expresses their claims; E.24.PUB governs the expression and its carrier. When the receiving decision depends on several judgements, establish how they fit together. Two results can each apply to a different configuration with no configuration in which both required conditions have been established. For a decision about one configuration, establish the required compatibility there. For a claim about every allowed configuration, cover that range and its shared conditions. A single argument can do so. Where the uses concern different configurations, explain how their separate results enter the decision. Evidence that a necessary condition for the decision fails can settle a refusal. When only one supporting argument fails, assess any other sufficient argument on its own grounds.

An unfinished argument remains useful working material: identify the missing support and return the appropriate unresolved disposition. A positive assurance result requires an argument sufficient for the named use under the applicable domain rules.

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. Safety authority, contest, and redress remain governed by their domain rules, as described in §4.7.

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 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 domain definition, bearer and scale, with any applicable unit and the population or trials, conditions and qualification window required by that definition or the receiving use. A system reliability measure and an evidence-quality judgment are not interchangeable.
  • Relation congruence. Characterize one 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 result claims being combined;
  2. the dependency or alternative-path structure;
  3. the domain aggregation rule or model;
  4. the assumptions required by the rule or model, including any independence, dependence, calibration or unit assumptions;
  5. the calculation or ordered comparison;
  6. any rival rule that is plausible at comparable effort and could change the result or its warranted use.

Use min when the subject model explains what it means for the target quantity. For a bottleneck model it may give the value itself. For a probability of joint success, the smaller marginal probability gives an upper bound. State the direction of the bound before using it to decide a threshold.

When unlike quantities have no common aggregation rule, keep their meanings and use the criterion for the decision. Separate limits on accuracy and response time can support one conclusion when both limits hold in the required operating conditions. A direct observation, bound or qualitative argument can settle a question without assigning an overall score. State which part of the conclusion remains open when the available grounds run out.

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 evidence model; it is not an assurance arithmetic shortcut.

B.3:4.5 - Add the proof detail the assurance use needs

Add calculated or model-bearing details, replay details, or both to the compact result when the named assurance use needs them.

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 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 performer and A.15.1 to admit the dated occurrence independently. Add F.6 only if the replay must also say 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 visible artifact, such as an attestation or dashboard tile, contributes to assurance only through a claim and basis relation used by the argument. Establish whether the artifact supplies a cue, source, evidence item, or representation for that use.

If the question concerns only a status, gate decision, permission, warning, or source location, use its pattern and produce no B.3 result.

For a question about past reliance, identify the result available to the decision maker at the time and the grounds used for that decision. A decision record can establish reliance directly. If asked whether that result changed the choice, establish what would have happened without it. A binding rule can establish what would have been permitted or required without that result. To infer what the decision maker would actually have chosen, establish that the rule controlled the choice under those conditions or use other causal grounds under C.28. A result can have been considered even if the same choice was already warranted.

If an assurance claim is current, cite the item only for the property it 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 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 rule as a premise or limitation.

When a domain rule says a consequential use requires an assurance claim, state that claim and then apply B.3. When the rule requires a decision, permission, review, contest route, or redress relation instead, use that result. 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 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.

An argument about a design can establish what follows if its assumptions hold. Evidence from an implementation can establish that specified assumptions held for a given run. Combine the two when the design, implementation and conditions match in the respects the receiving claim uses. A successful run can demonstrate an attainable result or bear on a wider claim to the extent its selection and the domain argument warrant. Preserve the conclusions supported for each scope.

B.3:4.9 - Use causal-use and method-structure results

When an assurance argument depends on a causal-use claim, consume the 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 predicate for the relied-on fact.

Use A.22 only when a separately selected organization 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 needs the empirical basis required by the assurance use; an inferential claim needs its reasoning basis; an axiomatic or constructive claim needs the 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 target claim and named assurance use;
  2. cites only basis results and relations that bear on that use;
  3. states assumptions and limitations, including any unsupported stronger use relevant to the receiving decision;
  4. keeps target fact, claim, evidence, assessment, result, record, publication, and later use distinct;
  5. names a reopen condition;
  6. uses the 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, applicable unit, dependency, calibrated mapping, aggregation rule and calculation it uses. Explain sensitivity to assumption failures when it matters for the named assurance use. If a rival rule is plausible at comparable effort and could change the result or its warranted use, 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 depends on that fact. No record field stands in for an obtaining relation.

B.3:6 - Worked cases

B.3:6.1 - 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

On the independence assumption, treating min(0.9, 0.9) = 0.9 as the joint probability would overstate it. Even with unknown dependence, joint success cannot be more likely than either necessary event. On these marginal estimates its probability is at most 0.9. For a more demanding decision, establish the dependence or obtain other sufficient bounds.

Return to the protection function. Success requires both events, so its probability is at most 0.81 under the stated model and estimates. This rules out a required minimum above 0.81. For a minimum of 0.80, the assessor needs to bound the remaining failures. If the probability that both events occur and the function still fails is at most 0.01, the model gives a lower bound of 0.80 for success. With no such bound, the upper bound alone leaves that acceptance open. To claim equality with 0.81, establish zero probability of failure with both conditions present. For a decision about the actual design, establish how well the estimates and the dependence assumption apply to its demand class, including uncertainty that could change the decision.

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

Starting sentence: “The dashboard approves launch.”

Suppose the dashboard 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 a 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 model claim, its empirical-validation result, A.2.4 first-use classification and the direct support relation 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 not carried. No dated assessment Work or reusable record is added because the use does not depend on who performed the already cited validation.

The engineer states the supporting inference: “The validation compared M’s predictions with observations over the region needed for this comparison, and its stated error bounds meet the comparison’s tolerance. Those predictions are therefore supported as one input to the reversible comparison within that region and the stated validity window.”

These are premises of this worked case. If the validation does not establish that coverage or tolerance, narrow the use or return an unresolved disposition. Keep the argument beside the compact result or accessible through basisRefs. A later correction to the validation reopens the conclusions that depended on the corrected result.

If the engineer is asked to design the assessment for later comparisons, start with the choice those comparisons must support. Suppose the task is to rank two proposed settings by response. A common offset can leave their ranking unchanged. Error in the predicted difference can reverse it. Choose conditions and evidence that bound the error in that difference over the uses promised. For a strict ranking, a predicted advantage greater than the bound on the absolute error in the difference establishes its sign. To decide whether one setting clears an absolute limit, the offset can matter again. The existing validation can supply either bound if its result covers that quantity and range.

B.3:6.4 - Order-sensitive Method case

An assurance argument relies on a manufacturing sequence whose result can change when two steps are reversed. To establish what a specified order would achieve, recover the order, any applicable joins and the rule that gives their consequence. For a claim about an actual batch, an applicable final inspection may answer directly. To establish how the batch was produced, use A.15.1 to identify the relevant work, its order and its contribution. To establish which steps are constituents of one reusable Method, use B.1.5.

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 relies on.

B.3:6.5 - Bias annotation

RiskCountermeasure
Formal prestigeAsk what uncertainty or verification need the formalization closes.
One-number preferenceKeep unlike characteristics separate unless an applicable model combines them.
Visible-authority biasResolve the claim and property established by the artifact.
Record completion biasAdd only fields the named use consumes.
Consequence inflationUse domain rules; consequence alone creates no assurance claim.

B.3:7 - Conformance checklist

IDRequirement
CC-B3-1Each assurance result identifies its target claim and use. For a joint decision, explain how the required conclusions apply together. An assessment design explains how the assessor selects the relevant distinctions and obtains sufficient grounds under its stated conditions.
CC-B3-2The compact result contains target, use, basis, disposition, limits, and reopen condition; optional fields appear only when they change the conclusion or its replay.
CC-B3-3Every characteristic has one bearer, property, scale and unit where applicable, interpretation, and basis.
CC-B3-4Formality is not treated as monotone truth, empirical adequacy, or warrant.
CC-B3-5Aggregation cites the domain model, dependencies, required assumptions, applicable units, calculation or ordered comparison, and any relevant rival; no default min, mean, penalty, or ordinal arithmetic is used.
CC-B3-6Design and run results remain separate when their conditions or evidence differ.
CC-B3-7Target fact, target claim, evidence use, assessment Work, input results, assurance result, witness, note, publication, and later reliance or decision remain recoverable separately.
CC-B3-8A label, dashboard, card, provenance mark, attestation, or publication contributes only the property established through a cited relation.
CC-B3-9Safety, rights, access, responsibility, contest, redress, status, permission, release, and controlled action remain with their patterns.
CC-B3-10A causal-use premise cites the C.28 result. A Method premise cites its composition, selection or other result; add an A.22 structure only when independently selected organization changes the assurance question, with all four identity discriminators recoverable.
CC-B3-11Work, performer, Method, bindings, witnesses, reusable notes, and an optional F.6 assignment check are added only for a replay, competence, independence, timing, contest, or redress need. Every Work follows the §4.5 A.13 then independent A.15.1 route.
CC-B3-12A positive result states its reopen condition and any unsupported stronger use relevant to the receiving decision.

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

Anti-patternWhy it failsRepair
Universal weakest-link formulamin can be an upper bound for a conjunction and can ignore alternatives or dependence.Use the dependency model and domain rule; otherwise report inputs separately.
Ordinal penalty subtractionAn ordinal label is subtracted from a probability or ratio quantity.Use a calibrated mapping to the quantity when one exists, or keep the values separate.
Formality raises assuranceA more formal wrong model receives a better result.State the inspectability gain and the uncertainty it closes; keep truth and empirical adequacy separate.
Same letter, different propertyR names system reliability in one row and evidence quality in another.Give each characteristic its bearer and definition.
Safety-case inflationA warning, access value, or consequential display triggers a generic B.3 package.Use the domain pattern; apply B.3 only to an assurance claim.
Evidence creates truthNew evidence is said to make the target fact obtain.Revise the warrant or disposition unless the world-side facts changed.
Assessment-record collapseA checklist, trace, witness, or note is treated as the assessment Work or result.Identify each object separately and add only what the use consumes.
Design and run conflatedAn assumption established for the design is silently treated as true of the installed system.Identify the configuration and operating evidence needed to apply the design result. Use their joint implication for the installed system when those premises hold.

B.3:9 - Consequences

Benefits

  • Assurance remains explicit without forcing one cross-domain score.
  • A small local claim can stop with the compact result and its recoverable argument.
  • Visible assumptions and dependency structure let the practitioner check whether a calculation applies.
  • Domain safety, access, responsibility, status, and decision rules retain their 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 domain requirement is supplied.
  • Reusable replay records can add cost; include them when the receiving use needs them.

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 models that define them.

B.3:10.1 - Decision-bearing SoTA account

Practical questionSourceContribution to B.3Applicability condition
What makes an assurance case inspectable?ISO/IEC/IEEE 15026-2:2022, edition 2 specifies assurance-case structure and maintenance. The GSN Community Standard v3 gives engineering-argument notation and guidance.Adopt explicit claim, argument, evidence, context, defeater, and maintenance structure. Adapt it to the compact and replay paths. Reject document or diagram appearance as assurance, approval, or permission. Sections 4.1–4.2 apply this structure to the smallest result sufficient for the use.Use the governing assurance-case edition and check that the compact result states the claim, argument, and evidence needed for the receiving use.
How may reliability-like inputs be combined?NASA’s Fault Tree Handbook with Aerospace Applications, v1.1, chapter 6, derives AND-event probability from conditional probability and uses a product only under independence.Adopt dependency- and assumption-specific calculation. Reject universal min and any claim that it is always conservative. Section 4.4 and case 6.1 apply the dependency model before selecting arithmetic.Use a dependence model warranted for the claim. A different validated domain model changes which calculation applies.
Can one trustworthiness tuple compare unlike AI or system properties?NIST AI Risk Management Framework 1.0 treats trustworthiness characteristics as context- and use-dependent and recognizes trade-offs and domain metrics.Adopt named characteristics and use-specific thresholds. Reject same-letter cross-domain comparability and monotone formality. Section 4.3 keeps the bearer and scale explicit.Keep numerical assessments of unlike properties separate unless a validated common measurement model supplies the bearers, scales, units, and interpretation needed for their comparison.
What can provenance and attestation establish?C2PA Technical Specification 2.4 distinguishes provenance validity from value judgments. in-toto Attestation Framework 1.2 defines authenticated metadata about software artifacts.Adopt subject, source, binding, and verification claims. Reject a valid credential, manifest, attestation, or display as automatic truth, safety, compliance, readiness, or release. Section 4.6 and case 6.2 distinguish the verified property from the later decision.Check the property warranted by the applicable specification and whether the domain rule makes it sufficient for the named use.

B.3:11 - Relations

  • Builds on: C.2.1 for target and assurance-result epistemes; A.2.4 for 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 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 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 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 assurance result. The consumer applies its 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 assurance claim about that 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 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

Status: Stable

B.3.3:1 - Problem Frame

Use this when. A team needs to assess a claim for a receiving use, interpret a published assurance level or design criteria for recurring decisions. Start with what the recipient needs to decide, the applicable conditions and the choices left to the assessor. A published profile may have settled some of those choices.

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 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 use. Ask what could make the proposed conclusion fail. Follow that possibility to the correspondence, inference or observation that can resolve it. A single applicable argument can settle the use. For a decision requiring several contributions, check that their subjects, conditions and conclusions fit together. A result can be given without an AssuranceLevel.

B.3.3:3.1 - Assurance subtypes answer different questions

SubtypeCodeQuestion answeredContribution and boundary
Concept-Bridge AssuranceCBADo the load-bearing terms and participants correspond across the descriptions being used?Compare the relevant meanings, referents and conditions through B.5.3 when movement across vocabularies can change the argument. A discovered or repaired mismatch can change the assurance conclusion. Performing a comparison does not itself improve a relation’s congruence.
Verification AssuranceVADoes the claimed consequence follow under the stated specification and assumptions?Inspect the proof, logical argument or applicable construction. The result supports that consequence under those premises; it does not establish that a running system satisfies its environmental assumptions.
Validation AssuranceLADoes the empirical basis support the claimed performance in the receiving conditions?Examine relevance, coverage, measurement quality, limitations and contrary results. A simulation supports a claim about its modelled conditions; transfer to a system needs the applicable model-to-world warrant.

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 protective argument and required evidence; neither FV ≥ threshold nor EV > 0 establishes that adequacy.

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 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, conditions, meaning of any levels used, evidence rules, the basis for any thresholds, and reconsideration conditions. State the measure and its scale where a threshold is used.

To design such a profile, take the actions its recipients must distinguish and work back to what would justify each. Hold the apparent level fixed and change the subject, the part tested or the conditions of operation. Would the same level now warrant a different action? Retain the difference in the criteria or limit their applicability. Select the grounds for meeting each criterion, including alternative sufficient arguments where the decision permits them. Ask which cases the proposed rule could accept despite a missing condition and which sufficiently supported cases it would exclude. A general argument can settle either question. Adjust the rule to the intended use or retain an exclusion required by that use.

Where levels are ordered, establish the ordering their meanings promise. If one level is said to support every use allowed by another, establish that implication across the applicable conditions. A narrower operating range with better accuracy need not contain a wider range with looser accuracy. State what each qualifies when the uses differ.

To assign or endorse an assurance level on its merits, apply the profile and show how the evidence meets its criteria. To report the level an authority actually assigned, identify the decision, the designation or profile it used and its scope. An error in applying the criteria can change what the assignment warrants while the historical fact of assignment remains established. The legacy names Unsubstantiated, Substantiated and Axiomatic do not supply default criteria. In particular, an axiomatic or constructive justification concerns a 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 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 grounding

A claim about a design-time MethodDescription and one about performed Work or its Trace have different subjects. For an inference across composition scales, identify the relation the receiving claim uses. A condition established for every operating mode applies to a specified mode within that range. A rate for the whole constrains its parts to the extent their sizes and overlap permit. If passing and failing exhaust the outcomes on this criterion and at most two of 100 distinct readings failed, at least eight of any ten of those readings passed. Conversely, two groups of ten can each report nine passes yet share the same nine passing readings and have different failures. Their combined set then has nine passes among eleven readings. Establish the coverage and common conditions needed for the conclusion in the chosen direction.

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 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 threshold and evidence rules. The earlier limited result remains an account of what it supported.

To design a profile for later converter assignments, recover what each recipient uses the measurement to decide. An offset that stays the same in two readings cancels in their difference. The same offset can decide whether an absolute limit has been crossed. Develop criteria for the quantity being accepted and the operating conditions that could change its error. Applying the existing 2% criterion remains sufficient for the original assignment when its grounds still hold.

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 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): An endorsed level MUST have an applicable profile and evidence meeting its criteria. Reporting a past assignment requires grounds for what the authority decided, including its scope. A commissioned profile explains how its criteria distinguish the intended decisions and what grounds justify the claims of ordering or coverage it makes. The target claim and receiving use determine which formal, empirical or constructive support is required.
  • 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 a sufficient ordinary judgement.
  • CC-B3.3.5 (Scope of support): Design and performance claims MUST retain their subjects, evidence and conditions. An assurance conclusion transferred from a whole to a constituent, from constituents to a whole or from a design to an execution states what warrants that inference under the receiving conditions.
  • 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

Anti-patternFailure in useRepair
Tested but referring to different thingsRequirements and architecture use “Sensor” for different participants; the test concerns only one.Resolve that correspondence and re-examine affected claims; more test links do not fix it.
Perfect blueprint, unsupported operationA proof assumes conditions that the actual system has not been shown to meet.Obtain or use the needed empirical and assumption evidence for the claim, or narrow the conclusion.
Maturity by receiptA fresh smoke test and a term mapping receive a positive performance label.Judge the support for the requested performance, not the receipt count or type combination.
Proof as an admission tollSufficient empirical support is rejected because an unrelated formal proof is absent.Apply the receiving claim’s evidence rules; retain formal proof obligations where their contribution is necessary.

B.3.3:6 - Consequences

Recipients can inspect which claim and use an assurance result supports, its grounds and its limits. Teams direct effort towards relevant gaps and can reuse evidence that covers the claim.

Comparability becomes profile-specific. Defining a useful shared profile takes judgement about consequences, criteria and evidence; routine uses avoid that overhead.

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

Status: Stable

B.3.4:1 - Problem Frame

Use this when. Decide whether earlier evidence can still support a named use, or design the way a recipient will notice and act on a consequential change. Start with the claim, the use and when the decision must be made. For a question about past reliance, distinguish the conditions that held then from what the decision maker could know at the time.

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 licence deadline, calibration qualification or promised-use window remains a condition of the 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 change the outcome.

B.3.4:3 - Forces

ForceTension
Stable inference and changing premisesA valid derivation remains valid under its premises, while those premises may cease to describe the receiving situation.
Needed review and finite capacityA timely inspection can prevent harm; an unnecessary repeat can displace it.
Visible warnings and alert noiseA recipient needs action-changing limits, not a warning for every old carrier.
Requirements and their meritsA current institutional condition can bind the action even when there is a justified proposal to amend it.

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

To design reconsideration, work back from the decision that could become unsound. Keep a component and its inspection result fixed and change the way the assembly uses it. If the earlier conclusion can now fail, identify an observable change in the assembly, its use or the support on which the argument relies. Choose who can detect it, how soon it must be detected and what the recipient can do by that time. When a condition can change between inspections, use a warranted bound on that change, a timely event signal or a suitably restricted use. A dated observation of the whole can settle a decision confined to its state on that date.

Keep three judgements distinct: whether the earlier evidence applies, whether it is sufficient for the present claim, and whether the proposed action satisfies its conditions. Currentness alone answers neither sufficiency nor permission.

B.3.4:4.2 - State what each date bounds

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 govern the use.

For a retrospective question, locate the change and the time it was discovered separately. A later inspection may show that the condition had already changed by a given date while leaving its first change time open. It can settle a question about the earlier state if that bound suffices. To establish what supported a decision at the time, identify the information then available and, where actual reliance is claimed, what the decision maker used.

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 applicable unit, policy purpose, and meaning of any action threshold. An epistemic_debt_budget is then a planning-policy limit, not a universal allowance of harm.

For example, a team may count 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 require different judgements for different uses. For a staffing decision, recover the work remaining, its due windows and the people able to do it. A single inspection may supply both uses. Distinct mandatory inspections sharing an assessor can compete for the same time even when each fits on its own. A count suffices when the question asks only how many obligations are overdue.

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 change

Determine which continuation the available support and applicable rules permit. Choose the response that addresses the change:

ResponseWhen usefulResult for the receiving use
Continue on applicable supportAvailable information is sufficient for the unchanged bounded use. A scoped reconsideration, if needed, has found no relevant loss.Retain the qualified result. No new experiment, waiver or separate no-refresh record is required merely to continue.
Narrow or restrict the useSupport remains sufficient for a smaller envelope or less demanding claim.State the usable boundary and the limitation that changes the recipient’s action.
Refresh or inspectAn obtainable check can resolve a material uncertainty or fulfil a binding review requirement.Choose that check with regard to what its result can change, its cost, delay and displaced work; assess its result if the check is performed.
Suspend reliance or deprecate the affected resultThe necessary support is absent or defeated and no permitted continuation carries the requested use.Remove or qualify that reliance and communicate the affected reach. A status downgrade does not accept the underlying harm.
Apply an authorized exceptionAn applicable rule permits a bounded exception and a competent authority can grant it for this case.Follow the mandate, scope, conditions and accountability. A senior title alone grants no authority over affected risk bearers.

C.11 and C.19.2 support the choice of worthwhile additional evidence. An existing result may already establish the required condition for this use. A design commission can finish with the justified trigger, observation and response. A separately required inspection calls for the agreed work or evidence that the required inspection has taken place. If it cannot be performed in time, identify the unfulfilled requirement and any warranted action still available.

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 deprecated, not as proof that refresh was skipped.

B.3.4:4.5 - Follow affected dependencies and preserve expiry

Trace a changed premise to the conclusions whose argument uses it. Identify the subject, operating conditions and time each such conclusion covers. A lost premise can defeat one argument while another sufficient argument remains available. A shared premise can undermine several apparently independent judgements. Where the recipient needs them together, reconsider their fit for the same use, including a possible loss of compatibility while each separate result still holds. Reuse the branches whose grounds remain adequate.

Keep 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; that report alone does not establish 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 assessed envelope. The earlier report alone leaves support for that traffic open. Check for another applicable assessment or a sufficient bound. If none decides the question, restrict the supported use or obtain the assessment the proposed load requires. Evidence that a proposed load is unsafe can settle a refusal.

Suppose the available inspection team can either inspect a suspected load-bearing defect or repeat an 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 binding repeat requirement prevents that choice, seek an authorized amendment; the resource conflict does not itself remove the requirement.

A commission to set the review policy starts a step earlier. Identify which changes in load, structural condition or inspection access could affect each promised use. A change reported after a crossing may help reconstruct that crossing. A policy intended to prevent an unsupported crossing must give the responsible person enough warning and a feasible response before entry. An existing load limit enforced at entry may already handle excess traffic. A change in structural condition can require a different signal.

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, applicable unit, purpose and the meaning of any action threshold. No project has a default obligation to adopt one.
  • CC-ED.3 (Affected reach): Reconsideration MUST follow the support dependencies relevant to the requested conclusion. Account for retained alternatives, shared premises or joint conditions where they can change the result. A commissioned policy links the relevant changes to observations and responses available in time for its promised uses. Use an interpreted model for any aggregate.
  • 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 qualification, rights and resource-use expiry.
  • CC-ED.5 (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 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

Anti-patternFailure in useRepair
Old therefore invalidAn unchanged qualified library result is discarded because its report crossed a generic date.Check the condition that matters; retain applicable support without automatic renewal.
Unchanged file therefore safeA newly relevant dependency vulnerability is ignored because the library bytes are unchanged.Reopen the affected security claim and communicate its unsupported reach.
Green therefore assuredFresh reports or zero overdue reviews hide an unresolved performance failure.Assess relevance and adverse results for the target claim; report dashboard meaning.
Status as risk acceptanceLowering a badge or obtaining a senior signature is treated as permission to expose others to harm.Establish the rule, authority and permitted response; restrict unsupported use where needed.
Maintenance by forced experimentA repeat test consumes the only opportunity for a protective inspection without changing any relevant conclusion.Compare marginal contribution and displaced cost; retain binding conditions while seeking any justified amendment.

B.3.4:7 - Consequences

Teams can retain applicable support and direct review towards changed premises, reducing needless repetition without losing 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 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.

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 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 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. B.3.5 helps an author connect a readable relation claim to the grounds a recipient must be able to inspect. Its elected profile covers structural parthood, collection belonging and other permitted claims such as the use of a lemma in a proof.

Use this when. Start from what the reader needs to decide or explain about the relation. If the relation has been supplied, establish its participants, meaning and grounds for that use. If you must design the account, choose the relations that can distinguish the required answers. A publication choice or named requirement can elect CT2R-LOG for specified claims. Those claims then carry the grounding and validationMode required by their branch.

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 relation kind.

Not this pattern when. Not this pattern when a relation claim is sufficient and no publication choice or requirement elects this assurance profile. Also not this pattern when the 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. The relation pattern supplies the conditions for each relation, including any separately claimed parthood.

B.3.5:1 - Intent

Keep Working-Model relations readable and, when this profile is elected, connect each covered assertion to inspectable grounding and a declared validation posture.

What you get (manager/engineer view). The same relations (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 decides when it obtains. CT2R-LOG records the branch-specific support link and declared assurance posture. An optional tv:AliasOf declaration resolves a local relation label to its accepted Tech designation under E.10 and Lang-CHR.

B.3.5:2 - Problem Frame

B.3.5 exists where a readable Working-Model relation must remain usable by practitioners while assurance readers need a grounding relation and declared validation stance. The pattern governs how a public relation claim connects to the support required by its selected assurance use.

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 relation layer does not depend on electing the profile.

B.3.5:3.1 - Forces

  • Readable claims and inspectable support. Practitioners need stable relation meanings; assurance readers need the facts and identity conditions supporting each claim.
  • Parsimony constraint. The Kernel stays minimal; construction is outside the Kernel.
  • Unification inside FPF. FPF unifies external vocabularies; the same discipline applies 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

The Working-Model and Assurance layers name E.14’s presentation order: the claim first, its needed support accessible underneath. When two models are being compared for abstraction or refinement, use B.5.MR’s comparison of their admitted answers.

To choose the relations, ask which changes could leave your statement true while altering the reader’s decision. Holding an item’s registration fixed, it can move from a warehouse into an assembly. Holding the assembly fixed, responsibility for maintaining it can pass to another operator. Follow the part relations of the system, the constituent operations of a Method or the parts of performed Work as far as their arrangement affects the requested answer. Establish links between these accounts by the facts they assert, such as who performed the installation and which installed equipment the record describes. A direct fact about one relation can already settle a request confined to that relation.

Choose the distinctions to publish from the same question. Can the reader reach the required decision, with its grounds, in all the arrangements the model describes alike? Keep a missing distinction in the statement or in a grounding account accessible when it is needed. If the commissioned conclusion uses several assertions together, establish their compatibility for the items, times and uses it covers.

CT2R-LOG distinguishes an optional link between relation designations from the grounding link and validation flag required for each covered assertion:

  1. Alias link (lexical). tv:AliasOf may link a local relation designation to the accepted Tech designation of the same relation in that use. The definition in :5 fixes both endpoints and the conditions for using this alternative label. Cite the relation pattern to recover the relation’s meaning.

  2. Grounding link (assurance). Each relation assertion covered by this elected profile carries tv:groundedBy according to its relation kind:

    • ComponentOf, PortionOf, or AspectOf requires one current C.2.1 construction-trace episteme in the applicable sum or slice form and validationMode=axiomatic. PortionOf uses the measured-portion profile in C.13:4.1.1; AspectOf uses the facet profile. This requirement follows the asserted relation, including measured text portions, and does not make those two profiles interchangeable.
    • 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 use the support appropriate to their claim: an admissible evidence object for postulate, a followable argument for inferential, or a qualifying C.13 construction account for axiomatic. Constructive grounding is optional in this branch; select the mode from the basis used for this assertion.
  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 applicable branch above selects the allowed modes and grounding targets. The mode declares the author’s justification posture; B.3.3 judges what that support establishes for the receiving use.

Relation, grounding, and assurance. Published relation claim: :PumpA ut:ComponentOf :Skid12. Assess its expression properties under C.2.3 when that assessment matters to the use. Grounding account: the assertion links to :trace_Γm_sum_456, a C.2.1 episteme about the construction facts. Assurance posture: tv:validationMode=axiomatic is the author’s declaration. B.3.3 assesses the 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 - Inspect correspondence to a target kind or logical representation

When a constructive trace, Working-Model relation and target kind or logical representation must be used together, state the question and the direction of the inference. Consider the permitted source arrangements that a target description can represent. If it describes two different arrangements alike, see whether that difference could change the required answer. A dated entry certifying the installation of a pump of an approved class can establish that class for the installation. If it omits the unit identifier, several individual pumps may still fit the entry. For a claim about that unit, find its binding to the installation or give the narrower conclusion. A difference lost in the mapping can be immaterial to another question. An argument covering the relevant arrangements settles whether the inference holds.

The optional block records the correspondence and its limits. Use A.22.CGUS for a remaining question about potential continuations and their conditions.

StructuralCT2RTypingGroundingUnfoldingStructureBlock:
  unfoldingStructureRef: independently selected A.22 structure, when needed
  workingModelOrConstructiveRepresentationRef:
  targetKindOrLogicalRepresentationRef:
  bridgeRef?:
  constructiveTraceRef?:
  preservedStructure:
  lostOrCollapsedStructure:
  CL_or_CLk?:
  admissibleReuse:
  blockedSubstitution?:
  evidenceOrProofLinkageRef?:

When the receiving use needs a selected A.22 structure, unfoldingStructureRef names it. Recover its constituents, obtaining relations, applied constraints and named selection/use frame under A.22.

StructuralCT2RTypingGroundingUnfoldingStructure is a local designator for that 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 used.

When an inadequate working account requires general diagnostic recovery of the subject construction, use A.7.1. That return may stop at a 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 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. 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 part relations under their 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 six A.1 matters pass.

  • Alias declaration (lexical). a tv:AliasOf t states that local designation a denotes the same relation as accepted Tech designation t in the stated use. Both endpoints are designations. Identify the source or practice, effective scheme and local meaning under E.10:6.2.1; preserve the relation’s applicability and the roles and order of its participants. The direction points from the local expression to the Tech designation used to recover its meaning. Cite the defining passage, such as A.14 for ComponentOf, as the semantic source.

    A glossary sentence can make this declaration once for its stated use. A clear Tech designation needs no additional alias. Apply F.17/F.18 when the naming task requires their records; an alias alone creates no need for a NameCard or SchemeSenseCell. E.10 separately governs the use of a Plain twin.

    To use an alias, recover the declared meaning and participant positions, then apply the relation’s rule to the assertion. Recheck the declaration when its meaning or use changes.

    A broader meaning, or an expression that reverses participant positions, needs its own account: for example, hasComponent(whole, part) expresses the inverse of ComponentOf(part, whole). A bare alias declaration does not specify that reversal.

    When distinct local meanings require a semantic correspondence, use F.9; matching words alone leave that correspondence unresolved.

  • 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 lets a reviewer inspect the assertion’s basis.

  • 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. Temporal and workflow claims retain their own patterns.

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

Optional local wording. The team’s glossary uses “assembly component of” for A.14 ComponentOf, with the component first and its containing whole second. It can state “In this assembly glossary, ‘assembly component of’ is an alias of ut:ComponentOf as defined in A.14.” This one declaration lets readers recover the relation intended by “PumpA is an assembly component of Skid12.” Whether PumpA satisfies that rule is examined in the account below.

Suppose a later inventory glossary widens that phrase to include uninstalled spares reserved for a skid. The earlier alias no longer covers the widened meaning. Keep the assembly meaning explicit or use the inventory’s separately defined reservation relation. PumpA’s existing component claim can remain valid while it stays installed; the label change alone supplies no new assertion about a reserved spare.

  • Publication — Working-Model relation layer. They publish one assertion using the Working-Model relation ComponentOf, with named participants and the relation interpreted under its declared semantics. Those are its relevant expression properties under C.2.3; a universal F rank is unnecessary. The public view presents the Working-Model relation; a reviewer can follow its grounding link.

  • Constructive grounding (Γₘ). In the background, the published assertion links to :trace_Γₘ_sum_456, a C.2.1 episteme that names the 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 relations and reidentification rule, not the trace or input list, decide. If both installed equipment and its next service are in question, identify the service obligation separately. Two configurations with the same installed pump can require different service under their operating conditions or agreements. Select the additional relation on which the service decision depends. The pump-to-skid assertion alone can finish a request confined to installation.

  • 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. B.3.3 considers the 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. Consider a reader asking whether Vehicle 12 belongs to Fleet North. Under this fleet’s rule, the occurrence begins when the fleet accepts the vehicle’s registration, ends on withdrawal or transfer, and a later accepted registration begins another occurrence. State the membership supported for the date in question. This can finish the membership inquiry when no profile or further evidence has been requested.

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.

An authoritative roster can establish membership on a given date when its meaning and coverage are known. To reconstruct membership from events, consider later accepted registrations as well as withdrawals and transfers. A question about the continuity of the original registration depends on its own ending conditions. A change involving another vehicle may affect a complete roster while leaving the grounds for Vehicle 12 sufficient. A replacement rule can preserve Vehicle 12’s eligibility or change it. If the use needs the full current roster, establish coverage of entries and exits under that rule. The elected trace must be current for the assertion it grounds. Preserve the earlier trace for the earlier state and establish any separately claimed component relation under its own rule.

Epistemic constituent case. In this proof, one of two consecutive integers is even, so their product contains a factor of two and is even. The premise about the even integer occurs in the inference to the conclusion. Inspection of this derivation establishes that the premise is a constituent of the argument. A reference to a separate proof of that premise establishes that the writer cited the proof. To identify the separate proof as a subargument, establish where its reasoning enters this derivation. With no elected B.3.5 profile, state the relation that holds. The recipient may still require access to the proof.

If that recipient elects B.3.5 and the basis is the followable argument, link the assertion through tv:groundedBy to that argument and choose inferential. If a qualifying C.13 account instead explains the proof’s independently established constituent relations and assembly, it can supply an axiomatic basis.

A later proof that omits the lemma requires a content-part judgement; the earlier support remains about Proof P. Select and assess the support for the claim being used.

B.3.5:7 - Author Standard (at a glance)

Begin with what the recipient must learn from the relation account.

  1. State or choose the relation. Work from the question to the relevant participants, their relation and its conditions. Say, for example, “Impeller ComponentOf Pump” for an assembly claim, or “Vehicle 12 belongs to Fleet North under its registration rule” for an enrolment claim. Establish the asserted relation under its defining rule. For a broader conclusion, explain how the required assertions combine. When the supported readable claim completes the commission and the profile has not been elected, publish it directly.

  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 evidence object, argument or qualifying C.13 account used, with its corresponding mode from :4.
  3. Declare the selected tv:validationMode for every covered claim.

The public graph retains its relation vocabulary. For each assertion covered by the profile, a reviewer can follow the grounding reference to its construction or evidence account.

B.3.5:8 - Compatibility & cross‑references

  • B.3 and the proof or mathematical pattern. CT2R-LOG makes the relied-on construction or support account inspectable; B.3 judges its contribution to the assurance claim. State the logic and proof basis when a formal conclusion is used.
  • B.3.3 (Assurance subtypes and levels). The declared validationMode and 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 reinspection.

B.3.5:9 - Rule‑set — CT2R‑LOG (conceptual, human‑first)

Intent (one line). Publish readable Working-Model relation claims, resolve a useful alternative designation through an optional alias, and supply the assurance account required for assertions covered by an elected B.3.5 profile or named requirement.

B.3.5:9.1 - Vocabulary and meanings in this pattern

  • Working-Model relation. A human-oriented 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 relation’s defining pattern keeps the relation meaning fixed.

  • Assurance Layer. Within the branch requirements, an author may combine these grounding contributions:

    • 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: support for interpreting a relation designation or for a claimed correspondence between meanings. E.10/F.18 govern a same-meaning alias; F.9 governs a required correspondence between distinct local meanings. These contributions can be combined. Mapping supports interpretation or cross-context use; the assertion needs the construction account, argument or evidence required by its branch in :4.
  • Empirical Validation. Observations and calibration results support claims about the relation under the applicable conditions. Assess their contribution under B.3.

  • Grounding vocabulary (tv:).

    • tv:AliasOf — links a local relation designation to the accepted Tech designation of that same relation under :5.
    • tv:groundedBy — links the covered assertion to the author’s grounding account required by its branch in :4. Interpretation or correspondence support may accompany that account; it cannot replace the branch’s required basis for the asserted relation. 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 justification posture 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. Assess that account under the relation’s conditions and its receiving use.

Use these terms consistently across notations; their meanings do not depend on one notation or execution environment.

B.3.5:9.2 - Normative rules (MUST/SHALL clauses for thinking‑and‑writing)

S‑1 (Working-Model first). Authors SHALL state each covered 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 using the relation.

S‑2 (Alias declaration). When an alternative relation designation helps readers and carries the same meaning, the author SHOULD declare its tv:AliasOf link to the accepted Tech designation under :5. State the local use and cite the defining passage so readers can recover the intended relation. A claim using a clear Tech designation needs no alias.

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, state the working scope, link tv:groundedBy to an admissible evidence object, and give the empirical cues that would challenge the claim. No construction trace is required by this mode.

  • S‑3.b inferential. For a branch that permits it, link tv:groundedBy to a 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 participants, direct relation occurrence, applicable rule, and identity or reidentification conditions. The account makes those facts inspectable.

  • 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 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. Present the readable Working-Model claim before its needed assurance account. Assurance notation and record structure SHALL NOT dictate the public relation vocabulary. If support defeats or narrows the claim, revise it under its defining pattern and make the change visible, as E.14-P.2 requires.

S‑7 (Register discipline). When naming relations in an alias declaration, authors SHOULD use the accepted Tech designation and, where available and permitted by E.10, its Plain twin. Obey the minimal-generality and rewrite rules (LEX-BUNDLE). Keep the declared local meaning and use recoverable when comparing labels across contexts.

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.

B.3.5:9.3 - Scope & Non‑Goals

  • In scope. Canonical publication of relations for humans; clarity of relation designations and their semantic sources; 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. Choose the contribution for the question: resolve a same-meaning alias under E.10/F.18; use Mapping under F.9 for a required correspondence between distinct local meanings; use Logical grounding for an inference from premises and Constructive grounding for an account of a whole from its parts. Combine contributions when needed, retaining the claim support required by the elected branch, including its structural-parthood or collection-belonging trace.

B.3.5:9.4 - Author’s working moves

M‑1. Identify the decision and state the relation it needs in Working-Model form. If the choice is yours, vary how the participant belongs to a collection, fits an assembly or contributes to an action as relevant. Select the relation whose difference changes the answer. Where the decision depends on several relations, follow them back to that decision. M‑2. Establish which covered assertions require this profile under the publication choice or requirement. For each of those assertions, select the grounding branch and its validationMode. Use an adequate readable claim directly where no profile is elected.

  • For a permitted exploratory claim, choose postulate, link its empirical support, and state scope plus challenge cues.
  • For a permitted conclusion from known statements, choose inferential and link the followable 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.
  • For another permitted epistemic or constitutive claim whose chosen basis is a qualifying C.13 account, choose axiomatic and link that account.

M‑3. When an alternative designation helps readers, link that designation through tv:AliasOf to the accepted Tech designation of the same relation. State its local use and cite the definition; apply :5 when the meaning or participant order differs. M‑4. When the arrangement of work affects the claim, distinguish the operations prescribed by the Method from the performances that made up the actual job. If assembly used two parallel lines, establish how their work contributed to the assembly and which relations obtain between the assembled parts when the decision needs them. M‑5. Return what the readable claim and any elected grounding establish for the recipient. A joint conclusion has grounds for the connections it needs. Keep an unsupported part open and state the narrower result the available grounds support.

B.3.5:10 - Bias-Annotation

Bias (name)Symptom in the modelCognitive counter‑move (conceptual only)Where to check
Formalism captureA trace, constructor expression, or validationMode is treated as the source of the relation or whole identity.Recover the participants, direct relation occurrences, construction rule, and identity or reidentification rule first. Treat the trace as a current C.2.1 account and the mode as the author’s assurance posture.CC‑CT2R‑1, CC‑CT2R‑2, CC‑CT2R‑3; C.13 trace separation.
Canonical inversionB.3.5 fields are demanded before using the relation, or one assurance branch is imposed on every relation.Use the claim first. After election, use the applicable branch: structural parthood or collection belonging takes its required axiomatic trace; other permitted claims may use inferential or postulate support.CC-CT2R-2, CC-CT2R-3, CC-CT2R-5.
Order/time leakageInferring parthood from sequence, parallelism or interval inclusion alone.Recover the independent part relation under A.15.1 or A.14 when it obtains, and keep Method/order/time claims separate.B.1.5, C.27 and B.1.4; A.15.1 or A.14 for the part/phase claim.
Notation lock-inTreating one diagram or syntax as sufficient grounds for the relation, or leaving its meaning unrecoverable outside that notation.Keep the relation’s meaning recoverable independently of one notation. Explain the interpretation and any reasoning or construction step carried by the expression under E.5.2.E.5.2:4 and CC-NI.1–3.
Unexamined mapping fitA composed claim relies on a mapping without inspecting preserved and lost distinctions.State the mapping, its applicability and loss. Use a numeric reliability consequence only when the receiving model establishes its meaning and calculation; ordinal CL alone is insufficient.B.3 and the mapping or representation pattern.
Collection/composition swapA belongs-to predicate is used as PartOf, or a part claim is used as collection belonging, and reliability is carried over as if both were one construction.State collection belonging and constructive parthood separately under A.14. When both obtain, keep both claims and their different set and sum accounts.A.14 and C.13.
Design/run conflationConflating design and run claims or carrying support between them without the needed grounds.Keep design and run claims, their evidence and conditions distinct; justify any contribution across those scopes. A design result alone does not establish successful performance.B.3:4.8 and B.3.3:CC-B3.3.5.

B.3.5:11 - Conformance Checklist (normative, author-facing)

IDRequirementPurpose
CC-CT2R-1 (Canonical-first).A relation published for readers SHALL be stated in Working-Model terms, such as ut:ComponentOf or an ordinary belongs-to sentence, as the canonical form; any constructive or logical justification is recorded as grounding (not as the definition).Preserve human-first canon and didactic primacy.
CC‑CT2R‑2 (Mode declaration).For every relation or rule covered by an elected B.3.5 profile, the author SHALL declare tv:validationMode ∈ {postulate, inferential, axiomatic} in prose. A relation outside the profile needs no B.3.5 mode.Declare elected assurance intent without taxing ordinary use.
CC‑CT2R‑3 (Structural axiomatic grounding).A covered structural parthood assertion uses validationMode=axiomatic and links to its applicable current C.2.1 sum or slice construction trace. The account reports independently grounded participants, occurrences, rule, and identity conditions.Make elected structural assurance inspectable without turning it into a truth-maker.
CC‑CT2R‑4 (No parthood from order/time alone).Authors SHALL NOT infer parthood from sequence, parallelism or temporal slicing alone. Any Work-part or proper-phase claim satisfies A.15.1 or A.14 independently; Method order and temporal relations use their patterns.Preserve distinct relation meanings while allowing independently established temporal parts.
CC‑CT2R‑5 (Collection vs part).Authors keep collection belonging under the collection’s own rule distinct from every PartOf branch. A claim needs no profile fields; after B.3.5 election it uses validationMode=axiomatic and one current C.13 set trace. If constructive parthood also obtains, state and support that claim separately.Prevent category errors without taxing ordinary belongs-to prose or prohibiting a stronger independently grounded claim.
CC‑CT2R‑5a (Set trace reports).The elected set trace names the collection, the entity said to belong, the already established occurrence, the collection’s own belongs-to rule, and the identity conditions. The set trace supplies no structural-composition reliability.Keeps optional assurance from becoming ontology.
CC‑CT2R‑6 (Mapping fit).Where a claim relies on a mapping or alignment, state its applicability and what follows in the direction used. Establish that distinctions lost in the mapping leave the receiving conclusion warranted, or recover the missing information. Any numerical adjustment requires a justified receiving model, compatible scale and calculation.Make the reach of the inference inspectable.
CC‑CT2R‑7 (Notational independence).Core meaning MUST NOT hinge on any specific diagram or syntax; illustrative renderings, if present, are labelled informative.Ensure longevity and cross‑discipline portability.
CC‑CT2R‑8 (Layer direction).Present the readable Working-Model claim before its needed Mapping, Logical, Constructive or Empirical support. Authors SHALL NOT let assurance notation or record structure dictate the public vocabulary. If support defeats or narrows the claim, revise the claim under its defining pattern and expose the change.Preserve unidirectional dependence of layers.
CC‑CT2R‑9 (Claim and scope).State the relation claim and the use it serves. For an elected assurance profile, authors SHALL state the assurance claim and its scope. When tasked with choosing the relations, explain which distinctions the recipient needs and how the selected claims support the requested conclusion together. Identify the distinct subjects, evidence and conditions of any design and run claims used.Connect the grounding of each assertion to the recipient’s use.

B.3.5:12 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhat goes wrongRepair
Trace as relation or truth-makerA Gamma_m trace is treated as the public relation or the source of whole identity, or its presence or notation is treated as proof that the relation obtains.Keep the Working-Model relation canonical; recover the relation facts and reidentification rule independently; attach the trace only as their inspectable C.2.1 account.
Unchecked relation label or modeA familiar label or an axiomatic flag is published as sufficient grounds for a relation or identity.Establish the relation under its defining rule. When the profile is elected, add the required support and mode. Identify any missing fact and give the conclusion that the available grounds warrant for the receiving use.
Order/time leakageSequence, phase labels or parallel timing are treated as sufficient evidence of parthood.Recover each relation separately: A.15.1 for Work parts, A.14 for a proper phase of an unchanged non-Work carrier, and B.1.4 for aggregation of recovered order or temporal relations.
Assurance by notationA diagram, graph display, or data format is treated as if it made the relation true.Use the display to present the relation claim and establish its grounds under the relation rule. When this profile is elected, state its grounding relation and validation mode.

B.3.5:13 - Consequences (benefits, trade-offs, mitigations)

Benefits

  • Cognitive clarity for authors and readers. Working-Model relations remain canonical while assurance accounts stay beneath them. Every claim covered by the elected profile carries only its branch-specific support account; ordinary claims remain lightweight. CT2R preserves an inspectable assurance account while keeping collection belonging, constructive parthood, and order or temporal relations distinct. Order and time may organize a structure without establishing parthood.
  • Use-specific assurance without tooling commitments. Teams choose the grounding that the relation’s elected branch and receiving claim require. The declared modes distinguish justification postures; they are not an ascending scale of empirical confidence.
  • Mapping fit. Inspect the mapping and its losses before relying on a composed claim. Its limitations can qualify, narrow or block that conclusion; a quantitative effect requires the declared receiving model.
  • Distinct relation kinds. Distinguish collection belonging, parthood, Method composition and temporal relations by their rules. Their separate meanings can coexist in one inspected account without inferring one relation from another.

Trade‑offs & mitigations

  • Extra prose discipline. Declaring validationMode and writing a short grounding narrative (when axiomatic) adds authoring effort. Mitigation: reuse local templates; keep narratives concise and Γ_m‑oriented by idea rather than notation.
  • Insufficient grounding for the receiving use. An empirical or logical account can omit a premise or fail to satisfy the elected branch. Use B.3.3 to identify that gap and the worthwhile repair; retain sufficient support without demanding a more formal mode merely for its label.
  • Inspecting mapping limits costs effort. Recover the correspondence, align units where lawful, and verify the links needed by the claim. Retain a qualitative limitation when no justified numerical reliability model is available.

B.3.5:14 - Rationale (informative)

14.1 Why canonical‑first? CT2R-LOG puts a readable, task-appropriate relation claim first in the published account because engineers and managers use it to reason, decide and communicate. The relation’s defining pattern supplies its meaning. The selected assurance account makes the grounds needed for that use inspectable.

14.2 Why distinguish the two tv: links? tv:AliasOf connects designations so a reader can recover which relation an expression names. tv:groundedBy connects a covered assertion to the account supporting that assertion. An agreed glossary meaning can remain stable while a component is removed and the earlier construction account ceases to support the current claim. Conversely, a changed glossary can require a new interpretation while the physical assembly stays unchanged. Keeping these subjects distinct tells the author what to re-examine. Both links can be expressed in prose or another suitable notation.

14.3 Why a triad of validationMode? The triad {postulate, inferential, axiomatic} distinguishes permitted justification postures, not stages of formality or increasing confidence. The relation kind and elected profile determine which posture and support are appropriate for the receiving claim and use. A sufficient calibration account in a branch permitting postulate needs no mode promotion; an elected structural-parthood or collection-belonging claim requires its respective current construction trace.

Where a load-bearing claim needs stronger proof or an empirical check, select that contribution for the assurance gap it can resolve, not to advance through the three labels.

The mode declaration changes neither the canonical relation nor the strength of its support.

14.4 Why recover parthood independently of order and time? Order and temporal coverage answer different questions from parthood. A chronology or diagram supplies no part relation by itself. A.15.1 can independently establish a Work temporal part, and A.14 a proper temporal phase of an unchanged non-Work carrier. Preserve those relations alongside the applicable Method and temporal claims; B.1.4 aggregates only the relations recovered.

14.5 Why point to Γ_m.sum | set | slice (Compose‑CAL) for constructive grounding? The three C.13 forms—sum, set, slice—are sufficient to report the recurring construction accounts for integrated assemblies, collections, aspects and measured portions without expanding the kernel. They are not identity functions.

A truthful account carries participants, direct relation occurrences, the applicable rule, and identity or reidentification conditions: the same inputs under another assembly can form another whole, while a permitted replacement can preserve one whole.

14.6 Why mental obligations rather than process mandates? These obligations govern how a relation claim is justified and published: declare a permitted mode for an elected profile, supply the branch’s required support, and keep order and temporal claims distinct from parthood. A tool can help inspect that account; its successful execution does not replace the relation’s grounds. The requirements concern the claim’s justification, not attainment of an axiomatic strength level.

B.3.5:14.7 - SoTA-Echoing

The assurance profile uses the following contributions. The W3C recommendations supply established semantic distinctions for the alias account; they do not define the FPF-specific predicate.

Source lineContribution and boundaryApplication in B.3.5
A.14’s constructional comparisonAdopt construction and identity before relation choice. Reject both a universal collection-membership predicate and any inference from belonging either to parthood or to the impossibility of parthood.S-3.d/e, CC-CT2R-3/5/5a, and the Fleet North case keep collection belonging and a separately grounded part claim distinct.
ISO/IEC/IEEE 15026-2:2022, Assurance caseAdapt its separate, maintained assurance-case structure: an elected support account stays inspectable and current beside the claim it supports. Reject a mandatory full assurance case for every Working-Model relation. The FPF-specific validationMode triad is only the author’s declared posture; the standard is not cited as its source.The Solution, S-3, B.3.4 currentness relation, and conformance rows require support only after profile election and keep claim, support, and posture separate.
NIST’s Digital Thread for Manufacturing programmeAdapt traceable model-based information, validation, and conformance across engineering, manufacturing, and quality. Reject a shared model, thread, exchange, or passing syntax check as proof of a world-side relation.tv:groundedBy, the trace-family rule, and the two worked cases keep the support account versioned and inspectable while the relation and its own rule decide what obtains; a trace or evidence item creates neither the relation nor its identity.
SKOS / SKOS-XL (W3C, 2009) and OWL 2 Direct Semantics (W3C, 2012)Adopt the distinction between labels, relations between labels, and the relations they designate. OWL distinguishes equal property extensions from inverse properties with reversed participants. Adapt a directed local alias under E.10; neither a generic SKOS-XL label relation nor property equivalence supplies that declaration’s complete meaning.:5 defines designation endpoints, local use and participant positions. The assembly-glossary case shows why changing the label’s meaning and changing the assembly require different reconsideration.

B.3.5 starts with a readable relation and adds the branch-specific account when the publication elects the profile. Keep the assertion and its support current under their applicable relation and assurance rules.

Reconsider the affected assertion when its member, rule, trace, or evidence changes. Use the applicable relation and assurance rules when their editions change.

B.3.5:15 - Relations

Builds on

  • A.14 Mereology — supplies structural relations and the discipline for collection belonging under each collection’s own rule and separately grounded parthood; B.3.5 adds only the assurance branch elected for the relation.
  • A.11 Ontological Parsimony (C‑5) — constructive grounding lives in a calculus; the kernel remains minimal.
  • B.1 Universal Γ — shared invariants and the placement of order/time in their respective Γ‑flavours.
  • Part E authoring rules — canonical pattern template and notational independence, which CT2R‑LOG follows.

Coordinates with

  • Compose-CAL (Γ_m) and C.13 — supply current construction accounts for structural parthood and the set account for elected assurance of collection belonging. Each trace reports facts whose meanings and conditions come from the pattern that defines the relation.
  • A.22 / A.22.CGUS — Use A.22 when the receiving question needs a selected structure. B.3.5:4.1 supplies an optional record of construction-to-typed/logical correspondence and preserved or lost structure. Use A.22.CGUS when potential continuations and their conditions are at issue; A.7.1 supplies general diagnostic return to a subject construction.
  • KD‑CAL — provides inferential justification when authors pick validationMode = inferential.
  • E.10 / Lang-CHR (F.18) — govern relation designations, local aliases and register use; F.17 supplies naming records when needed.
  • Kind-CAL / F.9 — govern kind correspondences and correspondences between distinct local meanings. A same-meaning alias follows the naming rules above.

Constrained by

  • Notational Independence (E.5.2) — CT2R‑LOG refuses to prescribe formats, keeping all obligations conceptual.

Specialises / feeds

  • B.3, B.3.3 and B.3.4 — supplies the publication discipline (Working-Model relations, declared relation kind and validationMode; F per C.2.3 where relevant) that B.3’s trust calculus expects; interacts with ageing and assurance-level assessments without changing the relations themselves.

Non‑relations No introduction of order/time — CT2R‑LOG does not define SerialStepOf / ParallelFactorOf / temporal phases; use B.1.5 for Method-order claims, A.14 and B.1.4 for same-carrier temporal phases and their aggregation, and A.15.1 for Work parts and occurrences.

B.3.5:End

B.4 - Coordinate Repeated Adaptation (Canonical Evolution Loop)

Status: Stable Type: Pattern

Use this when. A recipient needs to decide how a subject should respond to repeated use or changing conditions, or to establish how it actually responded. What may they keep, change or rely on, for whom and over what period? Use the loop to design feedback, assess an existing arrangement or explain its history. Follow the subject and the relations on which that answer depends. Use B.4:4.2 for claims about particular dated Work.

What goes wrong if missed. Teams treat drift, learning, release, and improvement as unrelated events. Specifications become stale, findings lose the evidence needed for their use, and changes appear without a clear basis or treatment of the subject’s continuity. When particular Work is asserted, its performer and admission grounds can also be missing. At the opposite extreme, one generic loop is imposed on every subject: a description edit is called a Method change, completed Work is said to be revised, or an internal adaptation is rejected because its acting System is not external.

What this buys. The recipient can tell whether to keep the current arrangement, what would warrant a different response, or what changed in use. A proposed way to make those decisions can be assessed before anyone operates it. Subject-specific identity, evidence, authority and publication have their own grounds.

Not this pattern when. Use the subject pattern directly when one subject-pattern claim answers the change question without a repeated adaptation cycle. Use the relation pattern for relation grounding, adding B.3.5 when its working-model assurance profile is required. Use B.4.1 to publish candidate routes from a stabilized cue, B.5.2 for abductive hypothesis work, C.27 for temporal status, or A.15 for method/work alignment without an adaptation-loop claim.

B.4:1 - Problem Frame

The FPF is built on the Principle of Open-Ended Evolution (P-10): continued use can reveal reasons to adapt a System, an episteme, a Method, or a description. Feedback matters when what is learned in one use can affect a later decision. The decision may retain the existing arrangement, change it or end a use. A rule can specify that response before the occasions it governs. The identity question is not common. The same subject may continue through a change, a successor may be identified, or later dated Work may be a distinct occurrence rather than a revision of earlier Work. Use the subject pattern to settle that distinction or retain the open continuity question while coordinating the next needed contribution.

B.4:2 - Problem

When use, observation, and change are disconnected, three failures can follow:

  1. Design-reality divergence: The subject in use diverges from its design-time account. Models and assurance cases can continue to describe conditions that no longer hold.
  2. Unused findings: A finding that calls for a response has no usable path to the needed decision, change or renewed use. “Lessons learned” remain static documents.
  3. Unexplained change: Reactive patches have no stated observed basis, identity decision, or return-to-use condition. Hidden dependencies and unintended consequences accumulate.

B.4:3 - Forces

ForceTension
Stability vs. ChangeHow to adapt while retaining the identity and assurance commitments that still hold.
Learning vs. OperatingHow to keep use stable enough to serve its purpose while gathering and acting on evidence.
Top-Down Intent vs. Bottom-Up RealityHow to connect intended improvement with what use reveals.

B.4:4 - Solution

Begin with the recipient’s work. Which decision has to be made now or on later occasions? Is the requested result a recommendation, a rule for future decisions, evidence of what happened, or a change put into use? Keep any separately promised observation, trial, publication or deployment in the assignment. A question about what is already known can finish with an existing result. When you are to design the feedback, start from the actual commission before consulting the examples. Identify the choices supplied by the recipient and make the remaining choices yourself.

Work back from what the recipient will do with the answer. When the scope or model is yours to choose, ask what difference in the subject could change the action or the ground the recipient needs. Whose use is affected? Hold one component’s behavior fixed and vary where, when or alongside what else it is used. Would the decision about the whole change? Hold an overall reading fixed and vary how it arises across parts or occasions. Would a different participant have to act, or would the stated reason cease to hold? Follow the relevant links in each direction until the decision and its grounds are preserved. A rule about each part, dependence of one use on another and an outcome of their combination can require different evidence. A direct ground about the whole can settle the question without reconstructing its parts.

Choose what the model must distinguish at each needed scale. A service limit may suffice for an overall commitment, while deciding which caller to notify can require retaining a caller’s identity and deadline. To carry a finding from a coarser model to the operating situation, check that its admitted combinations include the relevant operating cases and that its outcome preserves the quantity or decision being bounded. A bound valid on the larger set then holds for those operating cases. A failure found only in an impossible combination cannot defeat the operating promise. Where separate descriptions lose a shared constraint, recover that constraint or use an adequate bound on the whole. A person or controller acts on a system, Work enacts a Method, and a description represents a Method. Establish the relevant connection before treating the result of one as a result for another. When different admissible situations give the same answer on sufficient grounds, use that answer. When they would require different responses, identify what the decision maker could distinguish in time, or give the supported conditional answer.

B.4:4.1 - Name the subject and continuity question

Subject kindState before using the shared cycle
SystemName the current System and the continuity or transformation rule. State whether the changed System remains the same System or whether a successor System is identified. Use A.1 for System recognition, A.3.4 for an actual bounded change of the continuing System, and A.15.PROD when the claim concerns first existence through production Work.
EpistemeIdentify the episteme or epistemes involved under C.2.1. Assert an EpistemeEditionRelation only when its historical-continuation conditions obtain. State replacement or another direct relation only when its grounds obtain; retain any unresolved continuity question.
MethodIdentify the current Method under A.3.1. If intended results, participant meanings, admissible conditions, safety bounds, semantic basis, acceptance criteria, or composition change, state whether the result is a refinement, substitute, or distinct successor Method. Use B.1.5 when order-sensitive composition is current.
MethodDescriptionIdentify each claim-bearing episteme under A.3.2 and C.2.1, and any obtaining edition relation. A later description does not by itself change the Method it describes.
WorkIdentify each dated occurrence under A.15.1. Completed Work is not revised: later review, repair, deployment, or follow-up is other Work, even when the occurrences belong to one longer effort.

Use the branch for each subject whose identity bears on the decision. To design a change, say what must continue and under which rule a later state or successor could be recognized. To report continuity or succession that actually occurred, apply that rule to the relevant subjects and times. Not every holon is an adaptation-loop subject, and the five branches are not interchangeable. A remaining identity question may be reported explicitly.

B.4:4.2 - Separate the changed subject from the acting side

Name the acting participant separately from the subject being changed. A System performs each piece of Work. The changed subject, performing System, dated Work, Method enacted by that Work, and result remain distinct. Practitioner prose can say “the engineer refined the design” or “the controller adjusted the valve” when that recognizable actor and action are enough. If that ordinary sentence is all the receiver needs, do not open a technical Work account.

If B.4 identifies one dated U.Work occurrence, first recover every performer’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 only when the receiving claim also needs assignment-bound attribution. A short B.4 account may omit an unused assignment identifier or classification only when every relation it consumes remains recoverable.

The performing System need not be external to the larger holon. For internal adaptation, apply the A.12 reflexive split: identify the changed subsystem or part and the acting subsystem or part as distinct participants, and establish their parthood in the containing holon independently. Use an external System when the case has one. Apply the same Work-admission and conditional attribution rules above to either acting side.

State authority, responsibility, permission, acceptance, or admission through its predicate, participants, and applicability basis; neither a phase label nor Work supplies them.

B.4:4.3 - Keep the four phase claims distinct

For a proposed feedback rule, work from the last time an authorized response could still affect the recipient’s result. Choose what can be observed by then, who can use it and which responses remain feasible, including retaining the current way. At an irreversible choice under a guarantee, the same information must allow a choice that meets the promise in all the cases still possible, with any later decisions based on information then available. If no such choice exists, identify the missing timely distinction or the limit of the promise. For a joint result, check that their respective responses can be carried out together with the shared resources and information actually available. For a recommendation, give its grounds to the person who may decide. To explain an actual adaptation, trace which observation or instruction was available and used, which response was chosen, and what that response changed wherever the conclusion depends on it. For a claim that the subject changed, compare the relevant property or relation before and after on a common basis. A new indicator, description or recording practice can change the account while the subject stays the same. Attributing an actual difference to the response also requires grounds for what would have happened otherwise. A new run cannot by itself recover a lost fact about an earlier one.

The four phases distinguish questions and results. Operation and observation can overlap. Identify the activities and dependencies needed for the transitions in question. Qualify particular Work claims under B.4:4.2.

PhaseQuestionOutput and boundary
1. OperateHow is the subject used, and under what conditions?Identify the relevant use. A record of a reading, comparison or intervention can establish the recorded fact when its source, meaning and coverage support that conclusion.
2. ObserveWhat do records, measurements, testimony, or other evidence show for the use?Identify the observation, comparison or interpretation and who carried it out when that matters. State the observed basis, finding, hypothesis or unclear cue under the result or evidence rule, including what remains unresolved. A sufficient observation result can finish the question before a change is selected.
3. RefineWhat change, if any, does the receiving use need, and what identity relation would it have?Retain the current way when its grounds suffice. Develop or select an alternative when the receiving decision calls for one. Establish the grounds required for its intended use, reusing applicable results and performing any needed revision or tests. State a continuity, successor, substitution, refinement or edition relation only when its endpoints exist and its conditions obtain; otherwise retain the identity question or intended treatment. A selected candidate does not establish availability for renewed use.
4. DeployHow was the selected change made available for use?Identify the deployment activity and what it established—for example, a changed or produced entity, publication, configuration, release or availability—under the rule for that fact. Acceptance, admission and later use remain separate claims.

Use the following conditions for the transitions on which the answer relies. In a design, describe what would allow each transition. In a history, establish which occurred.

  1. Operate -> Observe: a named cue, question, monitoring result, or review need requires interpretation.
  2. Observe -> Refine: a finding or routed cue changes which responses merit consideration. A new commitment or an applicable model can also warrant considering a change before any new use has occurred. Identify the basis that applies.
  3. Refine -> Deploy: one candidate is selected, the conditions required for that deployment are met, and its subject-specific identity question or intended treatment is explicit. State an obtaining continuity, successor, substitution, refinement, or edition relation here only when both endpoints exist; otherwise keep the question open until the change or production has occurred.
  4. Deploy -> Operate: renewed operation or use begins; availability does not close this transition.

Evidence is not a fifth phase. Evidence relations warrant the observed basis, candidate choice, transition, or renewed-use claim when a receiver relies on them. Evidence can be produced or used during several phases without duplicating those phases.

When asked whether something is stable, establish what the recipient needs it to preserve or return to, over which times and permitted changes. For example, a service manager asks whether to keep an existing rule that limits deviation from a target at every review. Let e_k be the deviation at review k. Suppose the operating conditions, available observations and feasible responses of that rule give |e_{k+1}| \le q|e_k|+d for every permitted update, with 0 \le q < 1 and d \ge 0. If |e_0| \le L and qL+d \le L, the next review stays within L whenever the current one does. Induction gives the requested guarantee at every review and can justify keeping the rule. Convergence to the target is a stronger question. For d=0 the same bound gives convergence. With persistent disturbances it can permit continued deviation. To promise a limit between reviews, establish what can happen within each interval. To say how the service actually ran, use grounds tied to its operation.

B.4:4.4 - Connect neighbouring cycles without collapsing them

The Canonical Reasoning Cycle (B.5) can supply reasoning Work within Observe and Refine. The B.5.1 development states and B.4 phases coordinate, but they are not a one-to-one implementation: a finding may reopen Exploration or Shaping, evidence use can support Evidence, and renewed use can enter or return to Operation.

When a preserve-worthy cue needs publication while its interpretation remains open, A.16.1 supplies a PreArticulationCuePack. Use B.4.1 after stabilization when the recipient needs a publication of possible continuations or of a route choice. An operator can use an adequately grounded next action directly. If communicating a recommendation was promised, check what the intended recipient must receive. Its routed result can return to Refine or enter another subject pattern when that pattern’s entry conditions hold.

Keep the answer proportional to its use. A designer can complete a proposed rule once it gives justified responses in the situations the recipient specified. An assessment may establish suitability, establish a failure, or identify exactly what the available evidence leaves open. One reliable observation may settle a question about an occurrence. Supply a full cycle trace when it was commissioned or a relying decision, assurance case, audit or replay needs it. Retain missing phases as missing.

Didactic Note: four practical questions

  1. Operate: What subject is operating or being used now?
  2. Observe: What has use shown, and who made the observation or interpretation when that matters?
  3. Refine: What warrants keeping the current way or changing it, and what would continue through a proposed change?
  4. Deploy: When a change is proposed, what would make it available for use? When reporting actual deployment or subsequent use, what establishes it?

Apply the questions that support the requested result. A future feedback rule can be delivered before its first use. An account of past events follows the participants, decisions and uses that actually occurred.

B.4:5 - Archetypal Grounding

The phase names can be shared, but each subject branch keeps its identity and return-to-use rule.

  • Cue preservation and optional B.4.1 routing:

    • Context: A delivery service operates a fleet of autonomous drones. Operators begin to notice that winter deliveries feel “off” before a clean anomaly statement exists.
    • Loop Example:
      1. Operate: The drones perform deliveries.

      2. Observe: Operators and the monitoring service identify repeated signs of battery strain in the observed cold-weather deliveries. This gives them a cue to investigate. Its cause and its reach across the service remain open.

      3. Optional B.4.1 route inside Observe: A team performs stabilization Work. Under A.16.1, a PreArticulationCuePack preserves the cue nucleus, primary witness traces, and current language-state position without pretending that a final anomaly or action record exists; when the pack is made available for this use, name the separate publication occurrence under E.24.PUB.

        The same or another team performs routing Work. Under B.4.1, a RoutedCueSet keeps multiple continuations visible—for example, battery-chemistry investigation or route-planning adjustment; again, name its publication occurrence under E.24.PUB when availability matters.

      4. Continue when needed: When a route is selected and its entry conditions hold, it enters Refine or another subject pattern. While selection remains open, retain the live routes and any unresolved conditions relevant to their use or selection. A selected change proceeds to Deploy when its required deployment conditions have been established; renewed drone operation is a further event.

  • Knowledge-instantiation slice (theory refinement loop):

    • Context: A scientific theory of protein folding (U.Episteme) is used to predict structures.
    • Loop Example:
      1. Operate: Researchers perform theory-application Work using the current theory episteme.

      2. Observe: A lab obtains a finding, identified under C.2.1, about a prediction for a member of the claimed class under the stated conditions. A reliable counterexample can defeat a rule asserted for every member. How many members are affected is a further question. Identify the E.24.PUB occurrence if availability of this finding is at issue.

      3. Refine: A research team performs revision and testing Work. A later theory episteme, identified under C.2.1 from its changed claim content, includes a term for the new protein class. Assert an edition relation between the two theory epistemes only if that relation obtains.

      4. Deploy: The team performs publication Work for the later theory. The publication occurrence, journal acceptance, admission into a configured knowledge base, and later community use are separate relations.

        Note. If a CN-frame is used for a chart or CG-frame readings derived from this episteme, identify the chart’s reference state and coordinate patch. For measured values, cite the measurement method and protocol; for evaluated or otherwise ascribed values, cite the rule and basis that establish them, as required by A.19.CN CC-A19.D1-3.

    Adaptive-specialization note. For a bounded task-family specialization claim, identify the bearer, declared task family or work target, prior basis and the result the refinement supports. Use C.22 for the needed TaskFamily or TaskSignature anchor. Use C.22.1 when the receiving question concerns specialization acquisition or its claimed transfer, retention, downside or corridor entry; preserve its acquisition fields and any additional claim-specific grounds. Ordinary task-family and threshold anchoring can finish under C.22 without an acquisition signature.

  • Method-instantiation slice (adaptive method loop):

    • Context: A field-maintenance organization uses an inspection-and-repair Method (U.Method) described by one current U.MethodDescription.
    • Loop Example:
      1. Operate: Maintenance teams perform dated maintenance Work that enacts the current Method.
      2. Observe: A reviewer performs review Work and records that the time from fault detection to safe restoration repeatedly exceeds the allowed window.
      3. Refine: Method maintainers perform revision and testing Work. A wording clarification can yield a later MethodDescription while the same Method remains current. Adding an earlier isolation action or changing a classification checkpoint can instead change identity-bearing Method semantics; decide under A.3.1 whether the result is a refinement, substitute, or distinct successor Method, and use B.1.5 if its composition changes. Then identify the MethodDescription episteme that describes the chosen Method.
      4. Deploy: A publishing team performs publication or release Work for the later MethodDescription and, where needed, configuration or training Work for renewed Method use. Decision results, authority, acceptance, admission, and later Work that enacts the Method remain separate. Completed maintenance Work is never revised.

    Changing the maintenance question. The service manager now asks whether to keep a promise of restoration within 30 minutes of each call. A record of one timely restoration settles that incident if the recording and restoration conditions are met. For the promise, consider who may call, when, and which demands can coincide. Suppose two simultaneous calls are permitted, each requires 20 minutes of exclusive work by the same sole qualified person, and the 30-minute clocks start together. Both responses would need at least 40 minutes of that person’s work in the same 30 minutes. More precise readings on either repair cannot rescue the promise. This conclusion concerns the arrangement even if that pair of calls has never occurred.

    Under different terms, at most one call can be outstanding. If the person is available and able to start at once on every such call and can complete all required work within 20 minutes, the standing rule meets the 30-minute limit. It can be retained. If the manager commissions a new dispatch rule, determine what a dispatcher could know before committing a response, which resources they could assign and how the assignment would meet the existing promises in each permitted situation. Whether a new dispatcher actually used the resulting rule, and whether the service improved as a result, are questions for evidence of use and effect.

    Adaptive-specialization note. When the method-instantiation slice carries a bounded task-family specialization claim, identify the selected specialist Method or portfolio and the grounds for its claimed fit. When the Method update is used as evidence of specialization acquisition, name the holder, dyad, team or scoped portfolio that carries that claim and explain what the Method change contributes. Use the C.22.1 branch above for the acquisition or reuse question. Retain any budget, escalation or commit checkpoint, and fallback required by the selected plan or use.

B.4:6 - Bias-Annotation

BiasSymptomCorrection
Self-evolution biasThe subject is said to observe, refine, or deploy itself, so the acting participant and activity disappear.Name the changed subject and distinct acting side. Ordinary actor wording can remain short. When one dated U.Work is identified, recover each performer’s A.13 core and independently admit the occurrence under A.15.1; add F.6 only when the claim needs assignment-bound attribution. A short account may omit an unused assignment identifier only when every relation it consumes remains recoverable. The acting side may be external, or it may be a distinct subsystem or part established through the A.12 reflexive split.
Design-time/run-time smearA live operational change is treated as if it had updated the design-time episteme, or a design-time edit as if it had changed the System in operation.Keep the design-time episteme, run-time System or use, deployment activity, evidence relation, and renewed use distinct.
Method/description smearA MethodDescription edit is called a Method change, or a changed Method is hidden as a documentation update.Test Method identity under A.3.1 and composition under B.1.5; identify MethodDescription editions separately under A.3.2 and C.2.1.

B.4:7 - Conformance Checklist

  • CC-B4.1 (Proportional loop integrity): The result MUST answer the receiving question about the specified subjects and uses. For a commissioned design, justify how the chosen observations and timely feasible responses support the required result over the admitted conditions, including any shared constraint. A supplied indicator or rule can be applied as given. When the design itself is owed, give the choices and grounds that make it fit the use. For an assessment, give the supported conclusion and any consequential uncertainty. For a history, connect the observations, decisions, changes and renewed uses actually relied on. Supply any separately commissioned work or trace. An adequate common ground can support the required range without another run.
  • CC-B4.2 (Subject identity): Where the answer relies on identity or succession, name the subject kind and apply its continuity rule: System continuity or transformation; episteme predecessor, successor, or edition; Method identity, refinement, substitution, or successor; MethodDescription edition; or separate dated Work occurrences.
  • CC-B4.3 (Acting-side distinction): Work that observes or changes a subject MUST have an identified performing System distinct from the changed subject in that Work account. Internal adaptation is permitted when A.12 establishes distinct subsystems or parts and their independently obtaining parthood. Every dated U.Work reuses each performer’s A.13 core and is independently admitted under A.15.1; F.6 is added afterward only for assignment-bound attribution. Its short B.4 account may omit an assignment identifier unused by the receiver only when every consumed relation remains recoverable.
  • CC-B4.4 (Adaptive-specialization anchoring): A bounded task-family specialization claim MUST identify its bearer, declared TaskFamily or TaskSignature, work target, claimed result and grounds. When a C.22.1 adaptation signature is selected, retain its threshold target, timeToThreshold, budgetToThreshold and priorExposureDeclaration, including a not-reached or unresolved result when the history warrants it.
  • CC-B4.5 (Adaptive-specialization boundary): Claimed transfer, retention, post-threshold efficiency, corridor entry and downside MUST retain the targets, baselines, windows and evidence required by the claim or receiving comparison. C.22.1 defines the selected adaptation-signature meanings; G.5 and G.9 retain their selector and parity rules when consuming that result.
  • CC-B4.6 (Phase and transition separation): Each claimed phase and transition MUST retain its question, result and conditions from B.4:4.3. Evidence can be used across phases, and cue preservation or routing can contribute within Observe without requiring another phase.
  • CC-B4.7 (No success inference): Establish acceptance and successful renewed use under their respective conditions when claimed. The same event can support more than one conclusion when it meets each condition. Record failure, reopening, fallback or another iteration when that is what occurred.

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

Anti-patternObservable symptomRepair
Change without a basisA feature or design appears without grounds for changing the relevant use.CC-B4.1 and CC-B4.2 connect the proposal or actual change to the relevant observation, commitment or other sufficient ground and to any identity decision the use requires.
Unidentified internal adaptation“The system automatically improves itself” hides who or what performed the activity.Identify who or what changes which subject. Use CC-B4.3 for a Work claim. For an internal acting side, recover the distinct participants and their parthood under A.12, together with the Work, Method and phase facts the receiving claim consumes; physical externality is not required.
Incomplete hotfix accountA quick run-time repair is reported as a complete successful loop, although design repair, evidence, or renewed-use confirmation did not occur.State only the urgent observation, change activity, deployment and immediate result that occurred. Later description repair, testing, assurance and follow-up operation are subsequent activities and may reopen the loop; qualify any Work occurrences under B.4:4.2.

B.4:9 - Consequences

BenefitsTrade-offs / Mitigations
Connects learning to a decision: Feedback can warrant keeping or changing the current way and, when required, explaining its effects in use.Record overhead: Keep the account proportional to the work commissioned and to what the recipient must be able to rely on, audit or replay.
Exposes design-reality divergence: Separate phase outputs make stale descriptions, failed deployment, and missing renewed use visible.No automatic success: The loop cannot guarantee reconciliation. Deployment can fail, evidence can overturn a candidate, and renewed use can reveal another problem.
Makes adaptation inspectable: Named subjects, activities, identity conclusions and evidence let a reviewer reconstruct why a change was made.Needed subject contributions: B.4 coordinates the identity, Work, evidence, publication or acceptance results on which the use depends.

B.4:10 - Rationale

This pattern operationalizes the Open-Ended Evolution Principle (P-10) by connecting use, observation, change, and renewed use. Subject patterns decide identity and continuity. The account distinguishes actual activities and their results and retains the evidence needed for relied-on claims. B.4 makes their coordination inspectable while permitting a sufficient local answer to stop before another phase.

The same coordination can be designed before use. Its adequacy depends on whether the people or systems involved can obtain the relevant distinctions and act on them in time. A justified decision to retain the existing way can complete that assessment.

B.4:10.1 - SoTA-Echoing

The phase rhythm has historical lineage in iterative cycles such as Plan-Do-Check-Act and Observe-Orient-Decide-Act. B.4 adapts that lineage rather than treating those labels as an ontology: it distinguishes design-time accounts from run-time use, applies a kind-specific identity rule, identifies activities and results, admits internal acting-side splits, and keeps evidence, deployment, publication, acceptance, and renewed use separate.

The four questions recur in repeated adaptation. Which ones need answers, at which scales and with what evidence, depends on what the recipient is entitled to decide or receive.

B.4:11 - Relations

  • Operationalizes: P-10 Open-Ended Evolution.
  • Uses: A.4 when Observe needs a comparison of a System’s intended design with its actual operating conditions; A.12 for external or reflexively split acting sides; A.15.1 for dated Work; and the subject patterns named in B.4:4.1 for identity and continuity.
  • Coordinates with: B.5 Choose the Next Reasoning Contribution (Canonical Reasoning Cycle), B.5.1 development states, and B.3 Is This Claim Supported for This Use? — Trust and Assurance Calculus. B.4 does not implement the B.5.1 states one-for-one, and evidence is not a B.4 phase.
  • Is detailed by: B.4.1 Publish Candidate Routes for a Stabilized Cue (RoutedCueSet) for optional early cue routing. The subject patterns in B.4:4.1 supply each subject’s identity and continuity rules.

B.4:11.1 - Pre-abductive seam compatibility

During Observe, use A.16.1 when a cue needs publication while its interpretation remains open, and B.4.1 when possible continuations or a justified route choice need publication. Keep multiple routes live while selection is unresolved. A selected route can enter Refine or another pattern when the receiving work calls for that continuation and its entry conditions hold. The receiving operation can use the routed cue publication or an available later typed publication such as U.AbductivePrompt.

B.4:End

B.4.1 - Publish Candidate Routes for a Stabilized Cue (RoutedCueSet)

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain-name. Candidate routes from an observed cue.

B.4.1:1 - Problem frame

Use this when. A recipient needs a publication of possible continuations from a stabilized cue, or needs to receive a route choice with its grounds. Start with the action or question the cue bears on. An operator who only needs to choose a next action can use the reasoning in §4 and act within their authority. A promise to publish the recommendation also requires making it available as agreed.

The publication in B.4.1 starts from a stabilized cue preserved in PreArticulationCuePack or an equivalent early form under A.16. Its grounds may suffice for action while the cause of the cue remains open. Keep an established anomaly, action claim or hypothesis under its own subject pattern.

B.4.1:2 - Problem

A cue publication can lose its useful continuations when it is forced prematurely into a late form such as AnomalyStatement, Characteristic, or ActionOption. A route choice can also remain hidden in cue-pack prose, leaving the reader without its grounds or the subject pattern.

B.4.1:3 - Forces

ForceTension
Early capture vs endpoint disciplinePreserve low-articulation cues without collapsing route discipline.
Plural route set vs recorded selectionPermit multiple candidate routes while requiring a selection record when selection occurs.
Useful publication vs extra kindsMake routes inspectable without introducing a new publication kind for every case.
Route content vs reader presentationPreserve the route-form requirements when selecting an MVPK face for the reader.

B.4.1:4 - Solution

Begin with the decision the recipient can make and the time they have to make it. What was actually noticed, about which part, use or occasion? What further result would let this recipient act or answer the question? Work backwards from that result to a possible next action, its actor and its entry conditions. A standing instruction or a reliable result already available may settle which action to take. If you have been asked to devise the continuations, make that choice from the work before consulting the route names in §4.2. Applying a supplied route exercises a different decision.

Choose how far to follow the cue. Hold the local observation fixed and vary its use elsewhere. Then hold an overall reading fixed and vary the affected parts or occasions. Which variation changes someone’s next decision or invalidates its grounds? Retain that distinction and the link to the recipient’s use. A common instruction applicable to all remaining cases can settle the action while their identities or causes remain open. Where the answer differs, look for a timely way to distinguish the cases, state the condition to the recipient, or identify what remains undecidable on the available evidence.

Some continuations are alternatives. Others supply different results the recipient needs together. In that case establish how those results could be combined, by whom and by when. A feasible choice for each person in isolation may depend on the same unavailable hour or on information they cannot share in time. If asked for one justified continuation, give it with its grounds. If asked to identify every admissible continuation, establish why the set covers them. The publication sequence for a stabilized cue is:

Observe -> Notice -> Stabilize -> Route

For the requested or needed route publication, use the RoutedCueSet form, normally downstream of PreArticulationCuePack. RoutedCueSet names the reusable publication rules defined below. The filled account states candidate routes and selection claims; C.2.1 governs its episteme identity. Its expression follows the route-form rules and, when selected, the presentation rules of an MVPK face under E.17.

The route publication should identify:

  • the originating cue pack, if any, or the equivalent early form preserving the stabilized cue,
  • the candidate route set,
  • the route decision state,
  • the selected route, if any,
  • the grounds for each live route,
  • any conditions that would change the candidate set or its selection,
  • and any published typed downstream publication.

An existing publication can serve the receiving question when its content, form and availability meet the publication requirements. A reasoned choice by the operator, a recommendation to the person authorized to choose, a publication available to its recipients, and an intervention that actually took place each have their own grounds.

For specialization-sensitive routes, state the declared task family or utility target, any budget condition that qualifies the proposed continuation, any unresolved fact needed for its use or selection, and the downstream subject pattern with its entry conditions.

B.4.1:4.1 - RoutedCueSet shape

A conforming route account may include these fields:

  • sourceCuePackRef
  • candidateRouteSet
  • routeDecision?
  • selectedRoute?
  • routeRationale?
  • routeSelectionStatus?
  • multiRoutePolicy?
  • publicationFaceRefs?
  • articulationThresholdStatus?
  • closureStatus?
  • scope?
  • GammaTime?

RoutedCueSet is not the late endpoint. articulationThresholdStatus and closureStatus report guard state only; their governance remains with C.2.4 and C.2.5, and route discrimination may cite C.2.6 or C.2.7 when source or use conditions or representation-factor differences affect the route choice.

candidateRouteSet is the core here. When reporting a selection, use routeDecision, selectedRoute, routeRationale and routeSelectionStatus to distinguish the decision, its status and what is known about its grounds. A record can identify a past choice while leaving the chooser’s reasons unknown. They do not belong in PreArticulationCuePack.

The status reports which candidate routes remain live and any selection made; endpoint admission, publication availability, current use or retirement, and any authority relation remain separate claims under A.16 and their patterns.

Use sourceCuePackRef when the originating early form is a cue pack; otherwise identify the equivalent early form and the stabilized cue it preserves.

Use publicationFaceRefs when publication or review needs to identify the selected MVPK face forms. An expression of the route account or a later typed account follows its content form’s rules and the presentation rules of any selected MVPK face. Selecting a face alone does not establish that the content rules are satisfied.

One RoutedCueSet can describe several candidate routes. A lineage fork requires distinct successor epistemes or project records under their identity and lineage rules. Use C.2.1 for episteme identity; publication availability remains separate under E.24.PUB.

B.4.1:4.2 - Starter route family and conditional extension species

The candidate route set may contain, among others:

  • starter routes:
    • EvaluativeRoute
    • ActionInvitationRoute
    • ProblemAbductionRoute
    • MethodWorkRoute
    • RequirementCommitmentRoute
  • conditional extension routes for bounded specialization or corridor discovery:
    • TaskFamilySpecializationRoute
    • AdaptationProbeRoute
    • NonHumanUtilityRoute
    • SubstrateDiversificationRoute
B.4.1:4.2.1 - Specialization-sensitive extension route family

These four routes are not part of the starter core. Use them only when the cue carries explicit bounded-specialization pressure, corridor-entry pressure, or substrate-fit doubt that subject patterns must be able to recover by value.

Use TaskFamilySpecializationRoute when the cue points toward acquiring one narrower higher-fit specialist lane for one declared task family under budget, where that lane may later resolve into one specialist method, portfolio, or competence bundle.

Use AdaptationProbeRoute when the next question is whether threshold-reaching specialization is attainable under the current budget.

Use NonHumanUtilityRoute when the cue suggests a promising utility target outside the current human-default solution corridor but tied to one declared task family or utility target.

Use SubstrateDiversificationRoute when the cue raises a question about whether the current method substrate, or a broader or different one, can meet the declared task or utility target.

Contexts may refine the route family locally, but they shall keep the distinction between early route publication and endpoint governance.

B.4.1:4.3 - Projection discipline

Here projection names route-bounded partialization. For a downstream projection under this section, publish the result in a typed publication form. The expression may also follow an existing MVPK face’s presentation rules. A recipient may carry out a selected action directly when authorized and its conditions hold. The subject pattern governs the downstream claim.

A routed cue set may support these continuations:

  • publish U.AbductivePrompt under B.5.2.0,
  • apply A.6.P, A.6.A, or C.16.Q under its entry conditions and produce the sentence, record, or other result that the selected pattern calls for,
  • or publish another explicitly typed upstream projection.

For a proposed downstream projection, if no applicable typed publication form can be identified, keep the content in RoutedCueSet; an MVPK face supplies no such form.

B.4.1:5 - Archetypal Grounding

Tell. Route publication requires a stabilized cue and a stated candidate route set.

Show (System). An operator alarm may support routes toward intervention, rollback, or anomaly investigation.

Show (Episteme). An inquiry cue about a model-vs-observation discrepancy may route toward anomaly framing, opportunity framing, or probe design before a hypothesis exists.

B.4.1:6 - Bias-Annotation

The pattern favors preserving low-articulation cues and exposing real alternatives. In a route publication, state the grounds for each live route and for any asserted selection. A single decisive ground can warrant the requested continuation across the whole relevant range.

B.4.1:7 - Conformance Checklist

  • CC-B.4.1-1 Observe output SHALL NOT be forced into AnomalyStatement when articulation threshold is not met.
  • CC-B.4.1-2 A routed cue set SHALL name its candidateRouteSet and explain how the stated continuations serve the receiving question in the applicable conditions. Support any claim of completeness. One justified route may suffice for a request for one continuation.
  • CC-B.4.1-3 A published selection SHALL identify the selected route and whose decision it was. For a past selection, state the grounds for attributing it to that person or system. Report their rationale when the evidence establishes it, and identify any rationale still unknown. A recommendation supplied by the author gives the author’s grounds. When publication is part of the assignment, establish availability to its intended recipients.
  • CC-B.4.1-4 publicationFaceRefs MAY be named. The expression SHALL satisfy the route-form requirements as well as the presentation rules of any selected MVPK face.
  • CC-B.4.1-5 RoutedCueSet SHALL NOT be treated as establishing a late endpoint result.
  • CC-B.4.1-6 When a specialization-sensitive route is kept live, the route package SHALL name the declared task family or utility target, any budget condition that qualifies the proposed continuation, any unresolved fact needed for its use or selection, and the downstream subject pattern with its entry conditions.

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

  • Anomaly inflation. Treat every early cue as an anomaly statement.
  • Cue-pack route smuggling. Hide route decision or route rationale upstream in PreArticulationCuePack.
  • False single-route certainty. Pretend one route is obvious when multiple candidate routes are live.
  • Projection capture. Treat a typed downstream projection publication or its MVPK face as if it governed the endpoint family.

B.4.1:9 - Consequences

Recipients can inspect candidate continuations, their grounds, and any selection before a downstream result is established. The cost is an additional route publication and its maintenance.

B.4.1:10 - Rationale

Cue preservation and route choice answer different questions. A separate route publication makes the proposed continuations inspectable while retaining the cue pack as the account of the stabilized cue.

B.4.1:11 - SoTA-Echoing

For the operator question in §13.1, the response-time clause and the latency rise support different possible continuations. Calling the alert an established duty would settle clause applicability without grounds; retaining only the cue would leave the proposed continuations implicit.

Adapting A.16’s distinction between preservation and routing, §4 publishes those continuations and the grounds needed for any choice, while §13.1 retains intervention and inquiry alongside the duty question. This comparison supports that bounded gain at the cost of publishing and maintaining the route account.

Existing content can serve as that publication when it exposes the needed distinctions. Reconsider the route set when its grounds or the receiving question change.

B.4.1:12 - Relations

B.4.1:13 - Worked Route Sets

B.4.1:13.1 - Multi-route operator case

An operator is asked what a service-latency alert warrants. The note records a rise after a configuration change. The response-time clause may apply to a particular service and incident window. To compare possible continuations for the recipients, the operator may publish a route set containing:

  • ActionInvitationRoute,
  • ProblemAbductionRoute,
  • and RequirementCommitmentRoute.

The investigator would need grounds for explaining the delay. The duty manager would need to know whether the clause applies and whether its trigger was reached within the window. An increase alone can occur entirely below a trigger. Use A.2.8 for the resulting duty question. An authorized intervention can be appropriate before either the cause or the contractual duty is established.

Suppose the only question now is whom to notify. The record establishes that the trigger was reached at one of two service desks during the covered window, but leaves the desk unidentified. If the current rule sends alerts from both desks to the same manager, the operator can notify that manager now. If the rules require different recipients and restrict disclosure to the responsible one, the same record leaves the choice open until the desk can be identified or an authorized disposition valid in both cases is found. A commission to publish the continuations for later shifts still requires an available publication. Neither a route choice nor its publication establishes that the notification was sent.

B.4.1:13.2 - Inquiry case

A conceptual mismatch may route simultaneously toward:

  • explanatory inquiry,
  • probe design,
  • and later lexical repair.

A published account that retains these routes explains what each could contribute and which question, if any, requires their results together.

B.4.1:13.3 - Invalid jump

It is invalid to treat a routed cue set as if it were a hypothesis, a gate, or a work plan. The route account records candidate continuations; the subject pattern governs the downstream result.

B.4.1:13.4 - Specialization-route and nonhuman-utility split

A routed cue set for a new task family may keep ProblemAbductionRoute, TaskFamilySpecializationRoute, and NonHumanUtilityRoute live together. The point is to preserve the declared task family, utility target, any qualifying budget conditions, any unresolved facts needed for use or selection, and any relevant corridor-entry conditions without presenting those candidates as a justified prompt, selector, or policy choice.

B.4.1:14 - Keeping route plurality useful

State the grounds for the live route or routes, the selection status, and the basis for any current-use or retirement claim. Preserve the alternatives that still matter to the recipient.

B.4.1:14.1 - Minimal route package

Use the minimal route package in §4 (Solution).

B.4.1:14.2 - Selected route is not endpoint governance

When one route is selected, the routed cue set states the route choice. If the receiving work calls for a further claim or result, apply its subject pattern under that pattern’s entry conditions. Publishing the routes and selection can be the sufficient result.

B.4.1:14.3 - Review prompt and threshold reminder

Review what the cue supports and the grounds for any recommendation or reported choice. Explain an exclusion when claiming that another route ceased to be suitable. Selecting a suitable route can leave other routes suitable. If the articulation threshold required for a proposed late prompt, requirement, or work claim is not met, keep the publication early.

B.4.1:14.4 - Deferred selection and route splitting

In a route publication, describe deferred selection through the live candidates, their grounds and any unresolved condition that matters to the recipient. Attribute an actual selection when one has been made.

One cue cluster may also split into several routed cue sets if different sub-cues support different destinations. Explain a split to later readers when their decision depends on how the sub-cues and destinations relate.

B.4.1:15 - Migration and worked continuation boundaries

B.4.1 governs route publication. Use the subject pattern under its entry conditions when the receiving work needs further abductive reasoning, lexical repair, a requirement or commitment claim, or work execution.

B.4.1:15.1 - Migration from anomaly-first prose

If a publication labels a cue as an anomaly before the anomaly’s entry conditions hold, recover the stabilized cue. Publish its candidate routes when the receiving question needs them.

B.4.1:15.2 - Intervention vs inquiry split

An operator-facing disturbance may support both:

  • an immediate intervention-oriented route,
  • and a slower explanatory route.

A publication for both needs preserves the two continuations with their grounds and selection conditions. For an immediate response alone, act on the grounds for that response when authorized. The explanatory question can remain open.

B.4.1:15.3 - Requirement-route overreach

A route set that includes RequirementCommitmentRoute should not be read as if the requirement exists. The route is one admissible continuation; the requirement or commitment claim is decided under its subject pattern.

B.4.1:15.4 - Continue under the subject pattern

For a selected further question or task, continue under the subject pattern when its entry conditions are met. Typical questions and entry requirements are:

  • relation-bearing wording whose relation, participants, direction, or required detail remain unresolved: A.6.P;
  • evaluative wording whose sense, bearer, comparison, or consequence remains unclear: C.16.Q; use its ordinary repair sequence first, and meet C.16.Q:4.1’s articulation and interpretation requirements when a transitional qualityTermAscription(...) is needed;
  • affordance-like or action-first wording with enough context to compare its consequential meanings: A.6.A; recover the supported claim or question, or the fact that would distinguish the alternatives, then apply its subject rule;
  • a declared prompt species, stable open question, scope, and provenance, with the articulation and closure conditions for rival answers to remain live: B.5.2.0;
  • a stated requirement or commitment claim over its subject: its requirement-facing pattern; use A.2.8 for a question about an individual duty;
  • or an alignment question involving Method, WorkPlan, or Work: A.15; use A.3.1, A.15.2, or A.15.1 when only the Method, WorkPlan, or dated Work is in question.

ActionInvitationRoute names the route to this wording-recovery use; it does not require an invitation occurrence. A.6.A can return an open question without settling its answer. If the selected next-use entry conditions cannot be established, keep that proposed use unresolved and retain the supported route account.

B.4.1:20 - Route Evidence and Discrimination Package

B.4.1:20.1 - Evidence-per-route rule

Each live route in a routed cue set should cite the cue grounds that support it and any further grounds used to keep it live. Where those grounds are not published, complete the route account so readers can assess the support.

B.4.1:20.2 - Discriminator publication

When further information is needed to decide a route’s use or selection, name the missing fact or condition and which question it would resolve. Several routes may remain live because they support different needed contributions.

B.4.1:20.3 - Multi-route state is not yet a lineage fork

One routed cue set may keep several candidate routes live without forking lineage. A fork claim requires distinct successor epistemes or project records and the lineage relation under their identity and lineage rules. State the preserved and lost content needed for that claim. Publication availability and any responsibility or authority handoff remain separate claims.

B.4.1:20.4 - Projection restraint

A typed downstream projection publication or prompt may be shown as one admissible continuation; the other live routes, their grounds and any unresolved conditions relevant to their use or selection shall remain readable.

B.4.1:20.5 - Review test for false single-route certainty

Consider the alternatives permitted by the original question. Would the same cue, in a different covered use, require a different recipient, continuation or reason? If so, preserve the distinction or state which needed fact is missing. If one ground establishes the requested continuation in all those cases, a single route suffices. For an account of an actual choice or publication, what establishes who chose or what was made available to whom?

B.4.1:End

B.5 - Choose the Next Reasoning Contribution (Canonical Reasoning Cycle)

Type: Method-description pattern Status: Stable Normativity: Normative unless marked informative

B.5:1 - Problem frame

Use this pattern when you have a question, surprising result or promising construction and need to choose the next reasoning contribution. You may owe someone an answer, be helping them work out what to ask, or be free to set the direction of inquiry. The work can call for a construction, proof, explanation, observation or new question. Choose and connect those contributions by what the inquiry is to obtain.

When work continues without a question because its outcomes are treated as ordinary, B.5.PI provides an earlier entry. An ordinary handover or demonstration can yield a question or an early cue without a recognized anomaly. Use that contribution here when reasoning can take it further.

First useful move. Recover what the recipient needs to understand or make possible and what they have left you to choose. In your own inquiry you may be choosing the question itself. Use an existing answer if it settles the question. Otherwise ask what a proposed next operation would establish even if it succeeded completely. Where it supplies a premise, identify what will connect that premise to the answer. Section 4.1.2 helps when the possible operations or distinctions are themselves unknown.

For example: “We need the highest component temperature, but our model reports a mean. Two states with the same mean can have different maxima. Next, determine which temperature differences this arrangement admits.” This redirects the inquiry before another model fit.

The practical gain is a useful answer or a better-founded next question. A correct answer to an inadequate formulation can otherwise consume the inquiry’s effort.

Use a known calculation, proof, observation or qualified Method when it answers the question. A separate cycle description adds nothing in that case. Detailed mathematical techniques, physical modeling and domain validation remain with their disciplines.

B.5:2 - Problem

A hypothesis-led inquiry has a productive structure: propose an explanation, derive consequences and compare them with observations. Trouble begins when this structure is made the only permissible form of reasoning. Constructing a mathematical object, finding a counterexample, exploring a phenomenon or discovering that the intended quantity is not recoverable can change the question before an explanatory hypothesis is appropriate.

A second difficulty survives even when result production becomes cheap. More proofs, simulations or candidate designs do not by themselves say which questions matter, what an argument explains, or which construction should be developed. The inquiry needs ways to inspect and change its formulation and repertoire while retaining adequate results.

B.5:3 - Forces

ForceTension
Purpose and discoveryA question directs effort, while a useful result may reveal a better question.
Construction and justificationA new object or conjecture opens possibilities; its properties and applicability need the appropriate argument.
Abstraction and useA simpler representation saves effort, while its lost distinctions can decide the intended use.
Rigor and affordabilityFormalization, computation and observation can expose errors, but their whole burden must serve the question.
Current result and future possibilitiesA sufficient answer deserves a stop; a retained construction may enable a different worthwhile inquiry.

B.5:4 - Solution

Choose reasoning by the result the question needs. The abductive–deductive–inductive loop remains the canonical route for hypothesis-led empirical inquiry. Its mantra is Propose → Analyze → Test: propose a conjecture, derive consequences that make a test interpretable, and compare them with relevant observations. Construction, exploratory observation and question formation can precede, interrupt or follow that route. A mathematical inquiry may finish with a construction, counterexample or proof.

B.5:4.1 - Form or recover the question

Say what an answer would help its user understand, construct, explain, decide or investigate. An epistemic aim, such as exposing an obstruction or finding a more informative theory, can justify inquiry without an immediate product application. Recover an adequate existing answer before commissioning new work.

Separate the subject from its description, the intended result from a convenient proxy, and established premises from assumptions. Use ordinary language, a sketch or a small mathematical example at the precision needed to expose the difficulty.

If there is no question, B.5.PI can connect one ordinary work occasion with the use of its result, including adjustments that made the work succeed. It may produce a question, preserve an early cue, or justify continuing without change. This entry does not require a monitoring duty or turn every action into an audit.

If a participant senses that an account misses something but cannot yet express what, B.5.EA helps develop a correctable distinction from their experience. Use the resulting question or contrast here; a better expression does not by itself establish a claim about the world.

An expressible account can omit a consequential relation. B.5.FM:4.2.1 uses a small conceptual scheme to find a question through that relation, while distinguishing an unknown contribution from an inapplicable scheme. Use an adequate answer.

When choosing the extent of the account is part of your task, C.39.SA:4 helps find the wholes, constituents and model distinctions the answer needs. If several existing models supply premises, establish that their results apply together to the subject and conditions of this question (C.37.MM:4.1.1).

When the formulation is inadequate, vary a consequential element. Useful operations include:

  • change the quantity or distinction that the answer must preserve;
  • restrict or widen a domain, scale, boundary or assumption;
  • construct a small case that defeats the claim;
  • introduce a new object, relation, operation or representation and ask what it makes expressible;
  • ask what observation or argument would distinguish the remaining possibilities.

Before adopting the new wording, work out what an answer to it would let the recipient conclude. An equivalent formulation can serve directly if its answer carries back to the original subject, conditions and required grounds. A narrower question can also settle the whole one, for example when an admissible counterexample refutes a universal claim. If the narrower answer supplies one premise, pursue the remaining inference. C.39.QR explains this return.

A useful new question can also have a genuinely different answer. When choosing the research direction is part of your work, weigh what the change makes possible and pursue it on those grounds. When someone has specified the result, use the new question to help obtain it, offer it for their decision, or explain the limit on what you can obtain. An interesting answer in a nearby field or at another composition scale can leave the specified result entirely open.

C.22.2 helps make a problem-side claim and its next use inspectable. C.29 helps when choosing a mathematical lens or its mapping is the live question. Use their supplied actions at those boundaries; an ordinary mathematical problem need not acquire a separate card.

When you can follow a concept’s explanation but cannot yet interpret the situation through it, use B.5.4 to construct and test the correspondence. Return with the interpreted participants and relations, then choose the reasoning contribution the question needs.

B.5:4.1.1 - Propose a first model

When the situation has no usable model yet, begin with the difference the answer must resolve. The question can concern one occurrence, a relation across composition scales, or a class of possible arrangements. Start from the part, whole, interaction or general condition that can disclose that difference. For each relevant kind of holon, follow its own part–whole relation. The steps prescribed by a Method and the performances that made up a particular job can concern the same undertaking while having different constituents. Choose what the model must distinguish at the needed scales. Explain how any inference from one scale or kind to another supports the question. C.39.SA develops these choices.

  1. Choose what must remain distinguishable. Identify participants, states or quantities whose differences could change the answer. Use observed differences and possible interventions to propose a boundary: what can vary separately, what connects those parts, and what surrounding conditions affect them? Keep a distinction when you can explain its consequence for the question.
  2. Propose how they are connected. State a relation the answer depends on and use the relevant subject knowledge to explain what follows from it. For an observed change, the relation might describe an interaction that could produce it. For a proposed arrangement, it might govern which combinations are possible. If that account is unfamiliar, use §4.3 to recover its concept of use. Mark the assumptions that let you omit other interactions or treat a quantity as fixed. When modeling a physical phenomenon mathematically, use physical knowledge to choose the law that the mathematical account will express.
  3. Obtain a cheap consequence. Follow the proposed relation far enough to answer a useful part of the question. A direction of change, limiting case or rough bound may suffice before parameter fitting or detailed computation. Show which premise makes that consequence follow.
  4. Challenge a consequential choice. Ask what observation, omitted interaction or changed condition could defeat the answer. Compare a plausible alternative when the observations leave materially different explanations. Revise the model or obtain the missing observation when that difference matters.

Return the provisional model and what follows under its assumptions. If a missing domain account or formal construction prevents the next contribution, use A.15.9 to request that help from the working description. Section 5.6 shows this entry before a heat-transfer calculation has been formulated. B.5.FM shows how to choose the model’s participants and relations and use them to derive a consequence, in physical and formal problems.

B.5:4.1.2 - Find useful questions and possible actions from incomplete information

Sometimes neither the decisive distinction nor a useful set of alternatives is known. Asking which answer would change the work then leaves the practitioner to invent the basis they need.

Choose a starting point for what it can reveal about the purpose of the inquiry. A rule for a class, a relation between parts and a whole, or a record of one episode can each disclose something different. In open research, a source, a proposed use or an available capability can suggest a question worth pursuing. A better question or a conditional account can be a useful first result.

The connection is constructive. Material lets the practitioner propose participants and relations; following a relation yields a consequence; a contrast or trial challenges that consequence; the changed account makes further inquiries or actions expressible. Their conditions and significance can then be examined. A new finding can return the work to any earlier contribution. Use an adequate supplied result at its point of entry instead of reproducing the whole connection.

Examine the material for the distinction you need. Say what you can learn from it about the subject, its explanation or its use. For example:

  • Follow one episode. Observe what arrives, what participants do or change, what result leaves, and how it is used in the work that follows. Ask about the adjustments that made the episode work. B.5.PI develops this examination of ongoing work before a problem is felt.
  • Recover the operation behind an existing answer, design or source example. Find what it takes as given, what it does with that input and what its result establishes. Work a small application through §4.3 or B.5.TU. A hidden assumption may become visible before its practical significance is known.
  • Try a proposed use, or reason forward from an available capability. Identify the interaction by which it could produce an effect. Reason back from that effect to the contributions it would require. The two directions can revise both the intended use and the proposed means; neither needs a complete future plan.
  • Where the subject is unfamiliar, inspect a representative case with a practitioner or seek an explanatory source through F.1. Ask for help identifying what happens and which distinctions the practice uses. A request to help formulate the question is legitimate before a request for a specific answer is possible.

In open exploration, accessible material earns attention through a plausible connection to the subject. A finding can be valuable before its eventual use is known. If the question is already set, identify what the examination could establish for that question. When every possible outcome leaves a needed distinction untouched, seek material that bears on it, or develop the missing connection. Compare the effort with a smaller sufficient inquiry or an adequate existing answer.

Separate what was observed or supplied from the interpretation being proposed. A source description says what its author asserts; observing one episode says what happened there. A theory, calculation or domain Method can supply the relation and its conditions. Establish which cases those grounds cover. A valid derivation for every admissible case can settle the wider question, including when the author presents the derivation inside one example.

Make a relation do work. Use B.5.FM to distinguish the participants and propose how they are related. Explain the transition the inference needs. An operation can depend on an input, several contributions can jointly produce a result, and a rule can imply a consequence for a whole class. Use subject knowledge to justify the transition. Where it is missing, retain a question for observation, a source or a qualified contributor. Naming two boxes or drawing an arrow does not supply their relation.

Follow the relation to what it establishes for the question. Could the same condition hold while the required answer differs? If so, identify the remaining premise or connection. When the relation warrants the answer under the conditions at issue, use it. Seek a contrast when it could resolve a remaining difference. For example, a calculation may assume a constant load, a handover may require a readable representation, or an experiment may rely on a measurement remaining comparable. The relation tells the practitioner what to vary or inspect. Trace what would follow with and without that premise, or compare two actual episodes in which it differs. Show the intermediate reason for any different result. A thought experiment creates a conditional implication; establish which conditions obtain through the appropriate subject inquiry.

A useful contrast can also come from a failed attempt, an unfamiliar use, another participant’s interpretation or two cases that the representation merges. A relevant conceptual scheme or mantra can direct attention to such relations before anyone feels a problem. Apply its substantive questions to the available case; an empty slot in a scheme is not evidence of a defect. When neither a consequence nor a useful contrast can yet be constructed, return to a smaller case, another representation or subject assistance. Guessing possible answers does not replace that missing work.

Work out which inquiries and actions the revised account makes possible. Keep four things distinguishable when they matter: an alternative action, an uncertain condition, a consequence under that condition, and an action chosen after an observation. They can be connected, but they are different answers. A participant being available is a condition; requesting their help is an action; a qualified answer is a possible result; changing the later choice in response is a further conditional action.

To identify a possible next inquiry or action, find an operation or inference for which the present account supplies the needed input. Establish what its result would answer or enable for the original purpose. Alternatively, work back from a desired result and use C.39 to develop a missing operation or a way to connect operations.

Compare retaining the present way, revising an assumption in the account, changing the corresponding condition in the situation, using another available means or obtaining the missing contribution. A changed operation can create an option that did not previously exist; it need not merely reveal which predetermined future will occur. B.5.QD and C.40.CD develop the question and the way together when either changes.

Qualify a proposed continuation at the condition that remains unresolved. Its logical consequence may be established while feasibility, a person’s agreement or applicability to the situation remains unknown. Distinguish an unknown condition of a described continuation from not yet having a way to construct a useful continuation. The second calls for further construction, description or help; labeling it “unknown” does not perform that work.

Several compatible contributions can be needed together. Do not turn them into mutually exclusive branches to draw a tree.

Establish what the new distinction changes and choose the next attainable result. Return the new distinction or possibility to the original purpose. Does it change an answer, attainable result, supported claim, admissible use or worthwhile research direction? Show the consequence through the relation just developed. If a provisional distinction makes no difference to this purpose, it need not be elaborated. This is a reason to stop the present line, not evidence that no other consequential distinction exists.

Now use C.11.DUA to compare an attainable further inquiry with continuing on the present basis or a narrower sufficient use. Include finding and learning the Method, obtaining help, access, waiting and checking. Where later action depends on an observation, C.43 relates the observation to the action that will still be available. An inquiry may instead change only what can responsibly be claimed. Keeping the same physical action can therefore accompany a useful change in its grounds.

For open research, the attainable contribution may be a new description, candidate explanation, observation technique or question. Explain why the chosen material and operation could yield that kind of contribution and why this bounded effort is worthwhile. Do not promise an identified discovery or require its practical consequences in advance. After the attempt, use the result to choose continuation, reformulation or stop. Discovery and justification remain separate: a newly generated explanation needs its applicable criticism and evidence.

Use available help. Reuse a sufficient result within its scope. Apply A.15.9 to decide whether a missing contribution is attainable and worth requesting. In the request, state the available material and the intended use. When another contributor’s work or response is unavailable, identify what can be examined independently and what conclusion must remain conditional.

A smaller supported answer, a different available source, an agreed joint attempt or a deferred dependent choice can be useful. Do not attribute a completed judgement or commitment to an unavailable contributor. If independent mastery is the purpose, obtaining an external answer alone does not fulfil it.

Return the supported result, the reasoning that connects it to the purpose and the remaining consequential uncertainty. If a premise fails, re-examine the model or source used to support the affected inference. If an inquiry depends on unavailable help, try another way to obtain the needed contribution or explain which part remains open. An unexpected possibility can justify a new direction when choosing the research question is part of your task. A sufficient answer ends the present inquiry.

B.5:4.2 - Perform the contribution that is missing

The following are common alternatives, not an exhaustive classification or a sequence to complete.

Missing resultUseful operationWhat the result can establish
An object, procedure or structure with desired propertiesConstruct it from stated elements and permitted operations; test examples and counterexamples; prove the relevant properties or expose the obstruction.A construction, existence or impossibility result under its mathematical premises.
A consequence or a mathematical justificationState premises and derive the consequence. Identify the step that carries the argument and the conditions on which it depends.The implication or theorem within the stated domain and inference rules.
An explanation of an anomaly, opportunity or probe resultUse B.5.2 to generate serious rival conjectures and compare their explanatory fit, constraints and prospects for criticism.A qualified explanatory conjecture, with its grounds and unresolved rivals.
A better description of an insufficiently understood phenomenonMake a purposeful observation or exploratory measurement; vary a condition and inspect what becomes distinguishable.Observations and possible regularities that can generate or change questions.
An empirical consequence of a conjectureDerive the expected contrast, obtain relevant observations and compare the actual result with it.Bounded corroboration, a discrepancy or a qualified basis for rejecting or revising the claim.

Recover a construction before trying to execute it. Use this continuation when the source names a desired object or property but you cannot yet obtain the result needed by the question. B.5.RC expands the method below with worked cases and explanations of shared prerequisites, alternative constructions and missing operations.

  1. Identify the starting objects or data that are available. State what must be produced and which property the receiving use needs.
  2. Find the source’s operations for producing or combining those objects. For each needed operation, recover its inputs, application conditions and output. Keep a statement that an object exists with certain properties as an existence claim; seek a way to obtain an instance when the next use requires one.
  3. Work backward from the desired result to the required intermediate results and starting inputs. Preserve joint dependencies and alternative ways where the source supplies them. A missing operation is a question for the source or the relevant specialist; a rule you propose is an addition to be tried and justified.
  4. Apply the operations to the inputs the question requires. A particular instance can show how a rule works. To recover a construction for a class, establish how to obtain its output for an arbitrary admitted input, including any conditions where a different operation is required. If the notation obstructs the work, use A.6.3.RT to prepare and compare a more usable expression. In a mathematical account, track the formation and equality rules on which the construction depends.
  5. Establish the needed property by the appropriate argument or test. Return the construction and what follows under its premises, or the input, rule or unsupported transition that prevents the result. Stop when this supplies the receiving use.

For example, a stand specification calls for a portable display. Its assembly rules allow a compatible upright to be joined to a base and a compatible panel to be attached to that upright. Those rules yield the assembly order and the connections to check. Portability remains a requirement to check on the resulting design.

If the supplied panel does not fit, the next contribution is a compatible panel, an adapter with its connection rules, or another assembly design. The construction result here is the assembly design; whether the erected stand is stable needs its physical-design argument.

Construction and deduction can work together: an auxiliary object can make a proof possible, and a theorem can suggest a new construction. Novelty does not belong exclusively to one inference type.

For a hypothesis-led test, derive the consequences needed to interpret the test. Check whether those consequences conflict with retained premises, and follow their implications through the part of the model relevant to the question. Return inconsistent premises for revision before relying on their joint prediction.

Keep the prediction, observations, measurement conditions and inference recoverable before treating the outcome as corroboration. A simulation establishes a result of the simulated model; applying it to the physical target needs a supported model–world correspondence.

An exploratory finding can supply a hypothesis. Its subsequent empirical assessment must account for how that hypothesis was obtained and for the dependence or selection involved. Use the domain’s appropriate design and inference; relabeling the same data as a later test does not create independent evidence.

A bounded result may be sufficient at any of these contributions. Assurance belongs to the claim and receiving use under B.3 and B.3.3, including the applicable domain proof or validation obligations.

B.5:4.3 - Make the result understandable for its use

Explain what was obtained, why the decisive step works, and where the result can be used. The needed depth depends on whether the receiver will apply, criticize, extend or teach the argument.

Recover the argument needed for that use. Begin with the conclusion or proposed change the receiver needs to understand. B.5.RA develops both the main reason for the result and the local transitions needed to use it.

  1. Read the claim with its domain and conditions. For a mathematical statement, recover the meanings of its objects and quantifiers.
  2. Work backward from that conclusion through the intermediate claims or constructions it uses. At each needed transition, identify the premises, the operation or inference, and what it establishes. Follow a shared premise wherever the conclusion depends on it; keep jointly needed premises together.
  3. Reconstruct a transition the receiver cannot follow from the source’s definitions, rules or worked cases. Obtain the missing explanation or specialist contribution when those do not suffice. A conditional argument can be useful while one premise remains to be established; state that premise and the consequence its failure would have for this use.
  4. If a premise or requested result changes, use B.5.RR to follow the affected reasoning and derive what still follows. Preserve joint prerequisites and sufficient alternatives. Stop at a sufficient argument for the receiving use or a named unsupported transition. An unchanged, adequately supported part can be reused; a full reproof is needed only when the question calls for it.

For instance, a team expects to recover a drawing because a backup exists. Recovering that conclusion requires the needed data in a readable format and an available way to decode it. If the backup is encrypted and its key is unavailable, the next question concerns access to that key or another copy of the drawing. Repeating the fact that a backup exists leaves that prerequisite unresolved.

When beginning with an unfamiliar theory, reconstruct its concept of use for one working question. State what the practitioner wants to explain, predict, construct or decide; which objects and relations the theory lets them describe; what information and operations the application needs; and how its result answers that question.

Use a source application when its operations and grounds answer the question. Otherwise derive an application from the theory’s objects, relations and operations, and examine their correspondence to the receiving subject. Use a small trial when it can expose a lost distinction. A derivation under the shared conditions can justify a whole range of applications. Identify what the source supplies and what you have proposed.

Use the intended application to choose what to learn next. Study the construction deeply enough to perform or change the contribution the work requires. B.5.TU develops this application-construction method, including recovery of the needed operations and use of a correct result that answers only part of the receiving question.

To compare theories or ways of using them, ask the same question of each account. Preserve each source’s meanings while comparing what is given, what operations are allowed and what answer follows. If the results differ, identify whether the difference comes from the question, assumptions, mathematical structure, inference or proposed physical mechanism. If one account answers a different question, state that complementary use. Choose or change an account for the distinction the receiving work needs.

Use C.29 for a proposed mathematical-lens transfer or local candidate choice; domain prediction and intervention claims need their applicable Methods and evidence. B.5.TC develops the comparison. Relate both applications to the same claim or establish how their different contributions answer the question together. Distinguish theoretical differences from approximation or execution, and return the use or inquiry that follows.

When the correspondence between a formal account and its intended use is the difficulty, recover it through a suitable instance or directly for the required domain. Name the variables and their domains, the given inputs, the assumptions and permitted operations, and the statement the calculation or proof establishes. Relate the decisive quantities and conditions to the intended use. A source’s worked case can supply this reconstruction; recover the omitted step if the receiver cannot yet carry it out.

If it remains unclear whether the correspondence preserves the answer you need, try to expose a difference that matters to that use. Look for a formally admissible answer the use excludes, or two situations the representation treats alike that require different answers. If this exposes a mismatch, repair the domain, constraint, quantity or correspondence, or use the existing result for a weaker question that it does answer. A relaxation can remain useful as a bound even when its optimizer cannot be enacted. The worked case below shows both uses.

For a physical application, connect the mathematical objects and quantities to the phenomenon, measurement and operating conditions. Ask which approximation, omitted interaction, scale or uncertainty could change the conclusion. A rigorous derivation from a model and evidence that the model applies answer different questions.

Use the explanation to test the formulation: does the result answer the intended question, or only the conveniently formalized one? If a distinction was lost, determine whether the use can tolerate that loss, whether a bound suffices, or whether another representation is needed.

B.5:4.4 - Settle the question or change the next inquiry

Return the result at its supported scope. Stop when it answers the use. Continue only for a remaining question whose possible answers could change understanding or action and whose investigation is worthwhile under the available conditions. Account for the effort of learning, obtaining, explaining, checking and maintaining the result as well as calculation cost.

When the result exposes a limitation, identify what must change:

  • The answer or construction for the same question: repair it or investigate a serious alternative.
  • The formulation: identify what changed in the target, assumptions or boundary. Return any usable result to the question already asked. If the result now sought is different, establish whether selecting that new direction belongs to you or whether the recipient still needs the earlier answer.
  • The available Methods or ways of constructing candidates: compare retaining, modifying or extending that repertoire. E.23 supplies improvement under an appropriate evaluation; C.18 applies when generation rules, retained alternatives or the effective space of possibilities are the question.
  • A participant’s ability to contribute: distinguish the capability question from missing access or support; use E.23.CAE and E.23.CDI where their conditions hold.

Use B.5.QD when the next question is unclear. Recover a failed dependency or a newly available construction. Specify the answer it makes worth seeking and use a case, construction or argument to show what that inquiry could establish. This can develop the inquiry after a success as well as a counterexample.

Use E.10.DEV if “development” hides the intended subject and C.36 for a cultural-generation, transmission or selection question.

Retain a construction or unresolved alternative when a named future inquiry makes keeping it worthwhile. C.17 can characterize novelty, value and diversity on a declared basis; C.18 distinguishes the archive from a comparison front and a new point from a change in admissible possibilities.

B.5:4.5 - Allocate and assess contributions to reasoning

For calculation, conjecture, proof, explanation, criticism and question formation, choose which agents will do the work and which tools they will use. Base that choice on the participants’ capabilities, available support, constraints and the evidence needed for the receiving use. Revisit it when those conditions change.

When the question depends on a result from another practice, use A.15.9 to use the available answer or select a worthwhile missing contribution. State the working question, available inputs, result needed and intended use in terms the receiver can check. When requesting a formal formulation, ask the provider to show how it corresponds to the working question.

Derive a participant’s required capability from their later work. What must this person understand, ask, construct, criticize or arrange with the assistance then available? For example, an engineer may need to interpret the main idea of a proof or recognize that a measured proxy omits the intended quantity, even when a tool performs most calculations. Constructing or modifying the theory calls for a different depth of mathematical study.

When assessing that capability, use representative work under the declared support and inspect the engineer’s contribution. A completed AI-assisted report alone leaves that contribution underdetermined.

B.5:5 - Archetypal Grounding

B.5:5.1 - A counterexample becomes a constructive mathematical question

An engineer models pairwise incompatibilities with a finite simple undirected graph and asks, “Does connectedness let us divide the vertices into two groups with every edge crossing between groups?”

A triangle answers the engineer’s question. Putting two adjacent vertices in different groups forces the third vertex to conflict with one of them. Connectedness therefore gives no such guarantee. An engineer who also needs a way to make the division can now ask a further question. What obstruction prevents the partition, and how can we return either the partition or a witness of failure?

Build the tree by keeping an ordered waiting list. The neighbours of a vertex are the vertices joined to it by an edge.

  1. Choose any unseen vertex as a root, mark it seen, give it depth 0 and put it on the waiting list.
  2. Remove the first waiting vertex. For each of its unseen neighbours, mark that neighbour seen, record the removed vertex as its parent, give it the parent’s depth plus 1, and append it to the waiting list. A seen vertex keeps its first parent and depth.
  3. Repeat step 2 until the list is empty. If an unseen vertex remains, start a new root and repeat; this covers disconnected components and isolated vertices.

This is breadth-first search: a discovered vertex waits behind the vertices already waiting. The recorded parent edges form a tree in each component. Assign even-depth vertices to one group and odd-depth vertices to the other. If every graph edge joins opposite parities, these groups give the partition.

If an edge joins equal parities, write each endpoint’s chain of parents back to the root. Keep the two paths up to their common vertex of greatest depth, discarding the shared part beyond it. The retained paths have an even total length; the extra edge closes a simple odd cycle. An odd cycle cannot alternate between two groups all the way around. Thus the procedure returns either a two-colouring or an odd-cycle witness.

For a worked traversal, take vertices A–F and edges AB, AC, BD, CE, DF and EF. Start at A and inspect neighbours alphabetically. The waiting list changes as follows; the processed vertex is the parent of each newly found vertex in that row.

Processed vertexNewly found vertices and depthWaiting list after processing
AB, C at depth 1B, C
BD at depth 2C, D
CE at depth 2D, E
DF at depth 3E, F
ENone; F was already seenF
FNoneEmpty

A has depth 0, so the groups are {A,D,E} and {B,C,F}; each of the six edges crosses between them. Now add DE. Its endpoints both have depth 2. Their parent paths D–B–A and E–C–A, joined by DE, give the five-edge cycle D–B–A–C–E–D. The added edge therefore prevents the requested two-group partition.

Parity and the parent paths establish what the procedure returns for an arbitrary graph in this class. To use it for allocation, establish which items the vertices represent and which assignments the edges exclude. Suppose three items may share a group in pairs but all three together are forbidden. No edge between those three items expresses that restriction faithfully. The allocation question can stay fixed while the model gains a condition on the triple. A particular colouring that also satisfies every such condition can supply one allocation. An odd cycle of mandatory pairwise incompatibilities still rules out a two-group allocation under the additional restrictions.

The practice targets are to explain the obstruction, construct a partition or failure witness for another finite graph, and handle disconnected components. Assess those capabilities on a changed graph with the references and assistance permitted in the intended work.

B.5:5.2 - A physical question changes the representation

In a constructed engineering case, a cabinet contains two components. The intended question concerns the hottest component, but a proposed lumped model reports only their arithmetic mean temperature.

Let the modeled component temperatures be T1 and T2, with mean m = (T1 + T2)/2. The states (20,80) and (50,50), in degrees Celsius, both give m = 50. Their maxima are 80 and 50. A stipulated threshold of 60 therefore gives different classifications. On a state set containing both pairs, no function of m can recover the maximum or that classification.

A constructive repair retains the signed contrast d = (T1 − T2)/2. Then T1 = m + d, T2 = m − d, and max(T1,T2) = m + |d|. If an independently supported bound |d| ≤ Δ holds for the physical conditions, m + Δ is an upper bound within that model. Otherwise the contrast has to be estimated or measured, or the inference restricted.

For the next physical inquiry, ask: which temperature differences are possible under the loading, coupling and time window; how well does one temperature represent each component; and what measurements and error bounds cover the hottest relevant region? Compare a direct measurement, a two-state model and a qualified conservative bound by the evidence each requires and the decision each can support. Use existing adequate physical knowledge before selecting another experiment.

The mathematical argument exposes the lost information. For physical use, justify the two-temperature approximation. A more accurate fit to the same mean cannot settle that lost distinction. The first useful return is the changed quantity and representation question plus the physical premise that would distinguish the continuations.

B.5:5.3 - The hypothesis-led route remains short

A service has unexplained latency spikes. B.5.2 supplies a qualified backup-interaction conjecture and serious rivals. Derive an observable contrast between backup and comparison intervals, accounting for traffic and other relevant conditions. If the requisite observations exist, compare them under the domain’s inference Method. If they do not, the result can finish as a qualified conjecture and a specified missing test.

A separately qualified operational workaround may answer the immediate service question. Using it does not require pretending that the causal explanation is established or rerunning a sufficient result through every reasoning contribution.

B.5:5.4 - A relaxed problem supports a different use

A planner must choose whole jobs for one worker’s four-hour window. At most one A-job is available; it takes three hours and has stipulated value 5. At most two B-jobs are available; each takes two hours and has stipulated value 3. For this constructed problem the values and durations add, and the question is which choice satisfying the stated availability and time limits has greatest value. The reader needs elementary algebra and can enumerate the few integer choices.

Let x and y count A- and B-jobs. The intended constraints are x in {0,1}, y in {0,1,2}, and 3x + 2y <= 4; maximize V = 5x + 3y. An AI-assisted calculation instead allows real x and y with 0 <= x <= 1 and 0 <= y <= 2. It returns x = 1, y = 0.5, V = 6.5.

Recover what that calculation establishes. From the relaxed time constraint, y <= (4 - 3x)/2, so V <= 6 + 0.5x <= 6.5. The returned real-valued pair attains this bound. This is an optimum of the relaxation. The proposed half B-job is excluded by the intended whole-job condition.

For the whole-job question, x = 0 permits at most y = 2 and value 6. With x = 1, the remaining hour permits y = 0 and value 5. Two B-jobs therefore attain the integer optimum 6. Check that the selected jobs fit the constraints and compare the best value for x = 0 with the best value for x = 1.

The relaxation also answers a threshold question. Every allowed whole-job choice is feasible for the relaxation, so none can reach 7. For this problem the whole-job values are integers. The upper bound of 6.5 therefore bounds their values by 6. Two B-jobs fit and attain 6. Taken together, that feasible assignment and the bound prove optimality for the original question, even without the preceding enumeration. The relaxed allocation itself contains a half job and cannot be scheduled as a whole-job assignment.

With five hours instead, the same argument gives V <= 7.5 + 0.5x <= 8. The choice x = 1, y = 1 attains value 8 in both formulations. The planner can use that relaxed optimum as the whole-job answer because this returned choice satisfies the integer conditions.

Allocate the work according to the contribution sought. A planner can use assisted optimization while being able to state what counts as a whole job, recover the constraints solved, and distinguish an attainable choice from an upper bound. If the required work is to develop the optimization Method, its construction and proof become additional capability targets. To assess a learner’s own capability, change the time window or the divisibility condition. With the assistance allowed in the exercise, the learner chooses the formulation and explains which result answers the question.

B.5:5.5 - Understand which composition a theory permits

A practitioner wants one input to feed two operations. Let X, Y and Z be distinct atomic types, with available operations f: X → Y and g: X → Z. A cartesian account supplies copying, Δ_X(x) = (x,x). The composite (f × g) ∘ Δ_X returns (f(x),g(x)) from one input.

Compare an account generated by f, g, identities, serial composition, tensoring and exchange of factors. Here f ⊗ g runs the two operations on separately supplied inputs, X ⊗ X. Every permitted generator preserves the number of atomic factors; composition and tensoring preserve that property. Therefore those operations cannot construct X → Y ⊗ Z. The missing contribution is a second input or an additional copying operation.

The receiving work determines whether copying its input is admissible. The comparison exposes that requirement before selecting an implementation. Baez and Stay, §2.3, supplies the cartesian/monoidal distinction; the generated-operation case above shows its use.

B.5:5.6 - Model the heat path before commissioning a calculation

An engineer is asked whether a stronger external fan can bring an overheating component below 65 °C. In this constructed case, inspection finds the component attached to a metal case through a pad; the fan blows over the outside of the case.

Begin by tracing where heat is generated and how it could leave. The pad suggests a path from component to case, followed by transfer to the surrounding air. Keep the component, the case at the attachment and the air distinguishable: they can have different temperatures, and the proposed fan change acts at the case–air part of that path. Treating the whole device as one temperature would hide the difference relevant to this decision.

Try a steady heat-transfer account first. Assume constant component heating and approximate all generated heat as passing through the pad to the case, with an unchanged linear conductance along that path. The physical premise is that, for a fixed conductance, carrying the same heat per second requires the same temperature difference. OpenStax, University Physics volume 2, §1.6, equation 1.9 explains that relation for a uniform conducting layer. Approximating this assembly by such a path is the engineer’s model choice; inspect bypass paths and contact behavior when assessing it.

Model the case as losing heat only to that air through temperature-driven transfer. At equal case and air temperatures this outward transfer is zero, so a steady case receiving positive heat must remain warmer than the air. The fan increases exchange with the air; air temperature is the ideal lower limit for the case in this model. The same OpenStax section, introduction and “Convection” explains the temperature-difference dependence and fan-driven exchange.

Suppose the steady readings are 80 °C at the component, 25 °C at the case attachment and 20 °C in the surrounding air. Take these values as exact for the first conditional calculation. The component–case difference is 55 °C. Under the proposed model it remains 55 °C when only external cooling changes. Even ideal cooling of the case to the 20 °C air therefore leaves the component at 75 °C. Improving only this part of the heat path cannot meet the 65 °C target under those assumptions.

This result redirects the design question toward the component–case path, a new direct heat path or reduced heating. It also identifies what could invalidate the estimate: airflow onto the component changes the assumed path, while temperature-dependent heating or conductance changes the fixed-difference argument. For the real device, check measurement uncertainty and those assumptions before relying on the bound.

A useful specialist request is now: ‘Given this assembly and load, can the component stay below 65 °C after improving its contact to the case; which additional observations would settle that?’ The engineer can request that model and calculation without first specifying its equations.

B.5:5.7 - Recover an argument, then change its starting point

A reader can use elementary algebra and wants to understand and adapt the claim that the sum of the first n positive odd integers is n squared, for a nonnegative integer n. Let S(n) denote that sum, with S(0) = 0.

Work backward from the formula. It is enough to establish its initial value and how it changes when one term is added. The next odd integer after the first n terms is 2n + 1, so S(n + 1) = S(n) + 2n + 1. The proposed value has the same change: (n + 1) squared - n squared = 2n + 1. Both start at zero. Repeating that step establishes S(n) = n squared for every finite n.

A square of n by n unit cells makes the same step visible. Add one row of n cells and an adjoining column of n + 1 cells; the resulting square has side n + 1. The added cells give 2n + 1. Counting the cells and the algebraic recurrence explain the same increase in different expressions.

Now the requested sum has n terms beginning at 3: 3 + 5 + … + (2n + 1). Recover which premise changed. These are the first n + 1 positive odd integers with the initial 1 removed. The retained argument therefore gives S(n + 1) - 1 = (n + 1) squared - 1 = n squared + 2n. For four terms, 3 + 5 + 7 + 9 = 24; the old n-squared formula would give 16.

The reusable contribution is the initial-value and increment argument. It lets the reader obtain the changed sum by identifying the changed range and reusing the established result. A different progression would require recovering its increment before selecting another formula.

B.5:5.8 - An available report exposes a previously unknown condition of use

In a constructed case, a coordinator asks whether an automatically produced attendance report can be sent to course leaders. The available material consists of one report, a copy of its source data and the documented transformation. No list of possible defects has been supplied.

Read one row and recover how it was produced. The transformation counts attendance records grouped by the participant’s displayed name. Ask a course leader to demonstrate the intended use: deciding whom to contact about missing sessions. This makes the relevant unit a participant, while the calculation groups by a name. The first question is now whether those identify the same thing in this use.

Construct a contrast from that relation. Two different participants called Alex, each present once, yield the same name and count as one Alex present twice. The report alone cannot tell the leader whom to contact. This conclusion follows from the grouping rule; it does not establish that a collision occurred in the course. A source check can establish whether that condition holds for the present cohort.

The data documentation also describes a stable participant identifier, making a previously unconsidered continuation expressible: group by that identifier and retain a suitable display label.

For this correction, the identifier must track the participant for the relevant period, and the receiving leader must be permitted to see the resulting information. Those are questions for the data owner and the arrangement. If the owner is unavailable today, the analyst can inspect the transformation and prepare a proposed change; that work supplies neither the missing qualification nor permission.

A qualified manual source may support today’s contact decision, or the dependent decision may have to wait. The total attendance count can remain usable if it is all the recipient needs and its conditions hold.

Suppose the owner establishes that no displayed name is shared by different participants. This settles the question of collisions between people. To group one participant’s work across the period, also establish a stable name or a reliable correspondence between that person’s names. For the contact decision, compare who was expected at each session with evidence of attendance at that session, accounting for possible recording gaps. Adding an enrolled participant who never attended can change the contact list while leaving every attendance record unchanged. When only a count of attendances is required, a complete record with one entry per attendance can suffice. Comparing those claims prevents both an unwarranted release and unnecessary work.

The reusable move was to recover an operation from accessible material, connect its output with a demonstrated use, derive a contrast from the mismatched identities and construct a changed continuation. Neither the receiving criterion nor the alternatives had to be fully specified beforehand.

B.5:5.9 - Inquiry obtains a distinction before there is an intervention to choose

In a second constructed case, a researcher has measurement traces with an occasional unexplained step. There is no proposed intervention, known cause or useful list of future actions. An accessible inquiry is to inspect one raw trace and reconstruct how the instrument’s software obtains the displayed quantity. This can reveal a measurement operation or a distinction that the present account omits; it does not promise an explanation of the phenomenon.

In this case the reconstruction finds that the display subtracts a reference value which can be updated during recording. Holding the raw reading fixed while changing the reference produces a step in the displayed quantity. This derives a candidate explanation from an exposed operation. It is not evidence that such an update caused the observed event.

The next useful contribution is to compare the reference-update record and raw readings with the display at that event, accounting for timing and measurement conditions. If those records do not exist, arranging to retain them in a later observation may make the distinction testable. B.5.2 and the domain research Method govern rival explanations and their assessment.

Had the software exposed no such operation, the inspection could finish with a more precise measurement account and an unresolved question. Further work would need an attainable contribution and grounds. The value of the initial inspection was its plausible access to the measurement process at modest cost, not advance knowledge of the reference update. The inquiry’s result concerns understanding; an operational change need not follow.

B.5:6 - Bias-Annotation

The examples favor discrete construction and a simple physical representation. Other fields may need probabilistic, interpretive, historical or other arguments with different criticism demands. Select the contribution by the question and discipline.

Easy-to-produce outputs can dominate attention. Recover the intended epistemic or practical purpose when speed, proof count, a convenient measurement or the favorite tool starts determining which question is asked.

B.5:7 - Conformance Checklist

  • CC-B5.1 — Question and contribution. The practitioner SHALL identify the question, who may choose or change it, and what the selected contribution supplies. When the working question differs from the one assigned, the result SHALL identify what carries back, what warrants that inference and what remains to answer. A conjecture retains its grounds, rivals and limits. A construction and its asserted properties remain distinguishable.
  • CC-B5.2 — Interpretable hypothesis-led testing. Before claiming empirical corroboration, the practitioner SHALL derive the consequences needed to interpret the test and account for how the tested hypothesis was obtained.
  • CC-B5.3 — Claim-specific support. A support claim SHALL identify the argument or result, its relevance, scope and limitations. An assurance level, when needed, SHALL follow B.3.3 and the applicable domain criteria.
  • CC-B5.4 — Result and continuation. For a performed empirical test, the practitioner SHALL keep its outcome, including a failed or inconclusive result, recoverable through A.10. A further inquiry SHALL use the result with its limitations and name the remaining question; a sufficient answer may finish the use.
  • CC-B5.5 — Development-state use. When B.5.1 is used, a transition SHALL meet its project and domain conditions. A reasoning result alone does not establish a development-state transition.
  • CC-B5.6 — Application and change. The practitioner SHALL distinguish a mathematical result from its physical application and a change of answer, question, Method or capability when that distinction changes the intended use.
  • CC-B5.7 - Recoverability for the receiving use. When recovering a construction or argument, the practitioner SHALL identify the required inputs and the operations or inferences needed by that use. A missing rule or unsupported transition SHALL be stated. A conclusion reused after a premise changes SHALL state which argument or construction supports it.

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

Recognizable failureRepair
Repeatedly improve the fit of a model that omits the intended quantity.Test the representation against a small action-changing counterexample; recover the missing distinction or qualify a sufficient bound.
Treat exploratory regularities as if they were independently predicted and tested.Preserve their origin and use a design and inference that account for the selection and dependence.
Produce an argument whose receiver cannot identify what the crucial step establishes.Work backward from the needed conclusion and recover the decisive transition and its premises. If a premise changes, follow its effect through the argument.
Demand a useful future branch before supplying any way to discover one.Examine available material, recover a subject relation and derive a consequence or revealing contrast through §4.1.2; appraise further inquiry on the basis obtained.
Generate more answers after the important question has changed.State the changed formulation and which prior results answer it before selecting further production.

B.5:9 - Consequences

The Method preserves cheap use of adequate results while making constructive and question-changing work available. It connects mathematical reasoning, physical interpretation and epistemic criticism without imposing one proof or empirical regime on them.

The cost is attention to purpose, premises and continuation. Keep that effort proportional: one counterexample or a short explanation can settle the question. A difficult theorem or consequential physical inference can demand specialist work and substantially stronger evidence.

B.5:10 - Architectural Rationale

Inquiry connects different kinds of useful results. A construction supplies an object or procedure; a deduction establishes an implication; a conjecture offers an explanation; observations supply evidence about a phenomenon. Their value depends on what question they answer and what further use their support permits. Treating every result as an explanatory hypothesis would obscure these differences.

Question formation belongs here because the result of one reasoning contribution can alter the premises or aim of the next. Detailed object identity, mathematical-lens use, evidence, search and capability development retain their Methods. Their results can enter an inquiry without turning each PatternID into a required stage.

B.5:11 - SoTA-Echoing

Which reasoning remains useful as result production becomes cheaper? Adapt Tao’s Mathematics in the age of AI (2026), §§2–8: select the contribution by mathematical and practical purposes, rather than problem-output count alone. Compared with continuing the same production task faster, §§4.1 and 4.4 make a changed question or repertoire available. This accepts the cost of purpose and interpretation work when it can change the next inquiry. Tao’s strong-capability premise is conditional.

What makes a produced proof useful to its receiver? Adapt Klowden and Tao (2026), §§4.2, 4.4, 6.3–6.4: recover the intended statement and the explanatory structure that enables reuse. Section 4.3 explains how to recover the needed transitions and follow a changed premise through their dependencies. Formal correctness suffices for some formal questions; application or extension can require this further account. Compared with rechecking the whole proof, the selected recovery spends effort on the receiver’s unresolved use. The paper provides a conceptual rationale for this recovery; the odd-sum example applies it to a small argument.

Must reasoning always begin with an explanatory hypothesis? Retain hypothesis-led inquiry where it fits and adapt Rodin (2023), §§3–6 for constructive work: recover object-forming operations as well as propositions about their results. Section 4.2 recovers inputs and rules before performing a construction; the graph case shows construction and justification together. An existence statement may answer the question of existence. When the next use needs an instance or procedure, recovering its construction supplies a further result. This accepts the cost of reconstructing only the needed operations, while leaving the choice of mathematical foundation to the question and subject practice.

How can an inquiry begin before equations are available? Adapt the qualitative entry described by Etkina and Brookes in the ISLE method explanation: observations can lead to proposed mechanisms, consequences and discriminating tests before quantitative formalization. Section 4.1.1 makes a first provisional account available; section 5.6 works an engineering model choice. ISLE supplies an instructional method in a supported learning setting.

How do grounds and alternatives arise before a testable hypothesis? Adapt Ott and Hannah (2024), Emergent Findings and tables 3–4: open encounters, mental trials and interpretation can reveal participants and dependencies before a test is formulated. Their longitudinal study of nine ventures describes contingent combinations of practices, not a universally validated algorithm.

Section 4.1.2 connects such constructive work to the existing first-model, reasoning and inquiry-appraisal Methods; that general connection is a methodological synthesis, with domain qualification required.

What does exploring an intended use contribute? In NASA’s engineering process, working through a concept of operations can expose interactions that the initial expectations missed. Agreement on the resulting expectations is a distinct step. The design study by Parsons and Shukla documents how visualization designers developed new questions while exploring possible solutions. In §4.1, use this freedom where framing the question belongs to the inquiry. For a specified result, carry a proposed change back to the person or practice that determines the aim. The distinction is a methodological synthesis. Its application depends on the work entrusted to the practitioner. NASA Systems Engineering Handbook, §§4.1.1.2.4 and 4.1.1.2.8–9. Parsons and Shukla, §§4–6.

Reopen these choices when a better method at comparable effort changes the attainable result, a receiving use needs a different explanation or criticism regime, or changed tools alter the useful division of contributions.

B.5:12 - Relations

  • B.5.2 supplies the explanation-led abductive Method; B.5.1 coordinates development states when that separate question arises.
  • C.22.2 supplies an inspectable problem formulation and next use. C.29 supplies mathematical-lens selection and correspondence, including preserved and lost structure.
  • B.5.PI, B.5.EA and B.5.FM supply inquiry entry, an expressible distinction and a first model. B.5.QD, C.39 and C.40.CD develop questions, missing operations and their connections. C.11.DUA appraises attainable further inquiry; C.43 constructs observation-dependent action where control is the receiving use.
  • A.15.9 supplies bounded use or acquisition of another practice’s result, including help with a missing formulation.
  • A.6.3.RT prepares and compares an expression when its representation hinders the needed operation. The construction or argument obtained through that expression remains the result of the applicable subject Method.
  • B.3, B.3.3 and A.10 govern claim-and-use-specific assurance and evidence reliance.
  • C.17, C.18 and C.19 supply novelty/value/diversity characterization, archive/front and possibility-space distinctions, and live-pool treatment when those questions arise.
  • E.23, E.23.CAE and E.23.CDI distinguish object improvement, capability-expression questions and development of a named capability holder. E.10.DEV recovers ambiguous development claims; C.36 governs the cultural-evolution question.
  • B.4 can use these reasoning results in an evolution inquiry. A sufficient reasoning result does not itself require another evolution cycle.

B.5:End

B.5.EA - Articulate a Distinction from Experience

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

B.5.EA:1 - Problem frame

Use this pattern when a participant recognizes something consequential in their experience but cannot yet express what it is. A familiar phrase keeps replacing the point they are trying to make. The participant can return to an episode, an impression of the work or a partly expressed concern; a colleague needs a contribution they can understand and use.

The result is a provisional distinction, relation or question with enough explanation to continue the work. The method can be used alone or with a listener. A listener, including an AI assistant, needs access to the participant’s corrections; generating a fluent account cannot supply those corrections.

Use an adequate answer. If the relevant contrast is expressible and a model is needed, B.5.FM can develop it. If you understand an available concept but cannot yet connect it to the situation, B.5.4 helps construct that correspondence. Articulation is useful while it can reveal a consequential part of the question.

B.5.EA:2 - Problem

A practitioner says that a meeting was “unproductive”, a movement felt “blocked” or a construction was “wrong”. The usual meaning of the word invites a familiar remedy, but the practitioner cannot yet explain why that remedy misses the difficulty.

Asking immediately for a definition can repeat the same label. Asking only for justification can suppress the still-forming contribution. Yet leaving the concern as an unexplained feeling gives other participants little they can work with. They need a way to develop its meaning and then decide what follows.

B.5.EA:3 - Forces

NeedDifficulty
Return to what prompted the concernA retrospective account can replace details the participant has not yet expressed.
Let a contribution developThe resulting distinction may become possible during formulation, rather than exist beforehand as a complete hidden sentence.
Make joint work possibleThe listener needs a usable expression while the participant retains the ability to correct it.
Use the result responsiblyAn expression can capture the intended meaning without establishing its cause or wider applicability.
Keep the attempt worthwhileFurther clarification consumes time that might be better spent on the work.

B.5.EA:4 - Solution

Alternate between returning to the experience and trying a formulation. Let the person with access to the experience correct the formulation. Continue into modeling or inquiry once the distinction is sufficiently expressed for that use.

B.5.EA:4.1 - Recover a place from which the participant can speak

Ask for an occasion connected with the concern: where the person was, what they were doing and which moment now matters. Begin with a fragment when a whole account is unavailable. A gesture, sketch, sound or rough phrase may help them return to it.

For human first-person work, allow time to attend to the experience before asking for an interpretation. Ask what comes back at the moment and how it changes. Preserve an uncertainty such as “I remember the pause, but not which sentence preceded it.” An imagined reconstruction remains a reconstruction.

A listener may repeat the participant’s phrase and ask what needs to be retained. Ask a question whose answer can develop the concern, rather than supply a diagnosis for agreement. “What happened just before that pause?” leaves a different opening from “Were you afraid to disagree?”

B.5.EA:4.2 - Develop what the familiar wording leaves unsaid

Try expressing the point without the word that keeps ending the explanation. A sentence, comparison or demonstration may work where a single term does not. Ask which part of the expression helps the participant continue and which part misleads them.

Keep a productive tension long enough to unfold it. “I was invited to choose, but I could not choose” might concern incompatible options, lack of information, an unaccepted responsibility or something else. Ask the participant to describe the occasion; do not decide among these meanings from the phrase alone.

First give the participant room to develop their own expression. A listener can then offer a tentative reformulation when it helps, making it easy to reject, amend or leave unfinished. If agreement merely repeats the listener’s words, ask what the participant can add or correct. Return to their words and the occasion when the suggestion prevents that contribution.

Record a phrase when it prevents losing the developing point or supports another participant’s use; no separate form is required for an ordinary conversation.

Test a proposed interpretation or remedy on the originating episode. If following it would leave the participant’s concern untouched, reopen the interpretation. Use the dialogue, document or work available before asking the participant to supply more material. Ask for a missing fact when it could change the next move; do not make the participant prove a diagnosis that neither party has developed.

Their correction can identify the limit of the listener’s account without establishing a rival explanation. B.5.PI keeps that opening connected with inquiry into the work.

B.5.EA:4.3 - Let episodes change the candidate distinction

Return to the details that matter. If another relevant episode is available, examine what each one contributes. One can reveal a relation the other made difficult to notice. Try the relation on the other episode and inspect both its contribution and its failure to fit.

A shared generic label is one possible result. The useful finding may instead be a contrast, an exception, a previously unnoticed participant or a distinction between two conditions. Keep recalled events, available observations and hypothetical changes distinguishable.

Ask what the formulation allows someone to notice, ask or do. When a relation can be stated, B.5.FM can develop its consequences. When the result is an explanatory question, B.5.2 can develop candidate explanations. Use the contribution that is missing; a full inquiry is unnecessary when the new distinction settles the use.

B.5.EA:4.4 - Separate intended meaning from the claim made with it

Distinguish three questions:

  1. Can the participant use this expression to continue what they were trying to say?
  2. Can the intended recipient recover the relevant distinction?
  3. What grounds support a conclusion about the situation beyond that expression?

The first can be answered through the participant’s continued account. For the second, invite an interpretation or next move when shared use needs checking. For the third, use the grounds appropriate to the claim and its consequences. C.11.DUA helps decide whether obtaining more information could change the action enough to warrant its cost.

If a new observation defeats the account, B.5.RR revises the affected reasoning. Preserve what remains useful. A formulation can be faithful to a person’s experience while their diagnosis of its cause is mistaken.

B.5.EA:4.5 - Carry the contribution into the work

Return the distinction, the conditions that make it meaningful and the next use it supports. A short statement may suffice. Preserve the original episode or phrase when later interpretation would otherwise lose the point.

Ask which question the formulation settles. A participant who wanted help saying what they meant can finish with a phrase they can use and correct. If their experience raised a question about how a whole practice works, use the distinction to locate the operation or rule that matters for that question. Establish what the episode or the participant’s further account actually shows about it. When the conversation is open to discovering new questions, the participants can choose one that has just become expressible.

Stop when the contribution is usable, when further articulation cannot improve the decision, or when the participant cannot recover enough to continue. An unresolved but better located question is a result.

For joint work, the participant supplies experiential correction, the listener supports expression, and a subject specialist may supply the account needed for a subsequent inference. One person may perform several contributions. An AI can help formulate, compare and reason from available material; the participant’s private experience is not made accessible to the AI merely by assigning it that role.

B.5.EA:5 - Archetypal Grounding

B.5.EA:5.1 - A meeting that was “open” but left no room to contribute

In this constructed dialogue, a designer says, “Everyone could speak, but the review was closed.” The listener’s first interpretation is that someone interrupted. The designer rejects it.

Returning to the occasion, the designer recalls a pause after their suggestion. The chair thanked them and continued comparing the two options already on the screen. “There was no room,” the designer says, but rejects “not enough time”: the discussion continued for half an hour.

Asked whether another occasion helps explain that phrase, the designer recalls submitting a design note. Its form allowed long comments, but the decision fields offered only the same two alternatives. “No room for comments” fails in that episode too: there was a comment box.

The listener asks, “What does the form help you notice about the meeting?” The designer answers, “Both accepted what I said as a comment. I wanted my proposal to become another option, not another comment about those two.” The second episode changes the meaning of “room” in the first; it does not just add another instance of an unproductive meeting.

The initial contradiction separates into two conditions: permission to speak and the possibility of changing the set being considered. The designer can request consideration of a third option. The listener has not established that the chair intended to exclude it.

If the chair explains that the third option was already considered and was excluded by a constraint, the next question concerns that constraint and whether it applies. Repeating the claim that speaking was ineffective would lose the new condition.

The designer’s request to explain what “no room” meant can end with that distinction. Suppose the review owner asks whether the standing procedure allows a third option. Follow how a proposal becomes an option for decision. If the applicable procedure gives the chair discretion to add an eligible proposal, that provision can settle the permission question. Whether this proposal qualified and why the chair continued with two options concern the particular review.

B.5.EA:5.2 - A teacher’s “they do not understand”

A teacher can repeat this judgement but cannot identify the missing contribution. The listener asks for the moment when it became noticeable. The teacher recalls that learners waited for the name of a method, then carried out its steps correctly.

The next formulation distinguishes selecting a method from executing it when named. It makes a different teaching question possible: what in a situation should help the learner choose?

If the teacher later notices that the waiting learners lacked a diagram supplied to the others, the interpretation changes again. Unequal access to a representation may explain this episode. The original distinction remains useful, but the episode no longer supports the same capability judgement.

B.5.EA:5.3 - A familiar gesture points beyond the available term

A craft practitioner describes an operation by tracing a brief path with one hand and saying “it catches here”. A colleague interprets this as a property of the finished shape. Repeating the gesture while describing the encountered resistance reveals that the practitioner means a transition during the operation.

The colleague asks which change in the work occurs at that point and can inspect that transition. The gesture helped develop the description; it did not by itself establish a physical cause. The applicable craft or physical account supplies that later explanation.

B.5.EA:5.4 - A clearer help form misses the concern

A reader objects to guidance that begins “when you notice a difficulty, ask for help”. The listener offers a more visible help form. The reader rejects this but cannot name a better method. The available exchange permits one test: would the proposed form change the situation of a worker who regards the result as ordinary and never seeks help? It would not.

The listener preserves that difference and examines how the work could first become a question, using B.5.PI. If the reader can only point to the passage and cannot continue, the passage and unresolved concern can remain as an early cue in the existing conversation. A polished paraphrase does not close the concern, and a new explanation is not yet established merely because the first one failed.

The cases are constructed; their supplied subject details are the basis for the illustrated conclusions.

B.5.EA:6 - Bias-Annotation

The listener’s expertise can make a premature explanation attractive. Preserve the participant’s opportunity to reject it. Conversely, a personally satisfying phrase can resist correction; another use or observation may expose a limitation even when the phrase feels fitting.

B.5.EA:7 - Conformance Checklist

  • A participant can return to the experience or identify the limit of that return.
  • The participant can use or correct the expression. Corrections that change the intended use remain recoverable.
  • For a completed articulation, the intended recipient can recover the distinction and how it bears on a question, interpretation or possible action. If the result is still a cue or a better located question, identify what is understood and what remains open.
  • Experiential fit, shared understanding and warrant for a world-directed claim retain their different grounds.
  • Continuation uses the result or identifies the remaining difficulty without requiring an entire research programme.

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

The listener completes the story too soon. Return to the participant’s account and ask which part of the offered explanation fits or fails.

Novel wording is treated as discovery by itself. Show the new distinction and its consequence. An existing concept may explain it.

An apparent contradiction is tidied away. Recover the situation before deciding whether the words refer to different conditions or the account is inconsistent.

Every concern is turned into an introspection exercise. Use an adequate description. This method addresses an expression difficulty, not every unanswered question.

B.5.EA:9 - Consequences

Previously unusable experience can contribute to joint reasoning. The participant may discover what they mean while the listener obtains something more useful than agreement with a vague label.

The method requires attention and, in its human experiential branch, the participant’s willingness and ability to return to the experience. Use accessible observations or another contribution when that return is unavailable.

B.5.EA:10 - Rationale

The operation between noticing and reasoning is often left implicit. Preserving a cue prevents loss; forming a model requires distinctions with which one can work. Articulation connects these contributions without treating a preliminary expression as either worthless or established.

Meaning can change during formulation. Retaining the ability to revisit the originating experience allows that change to be examined. The practical aim is a contribution to inquiry or action, including a better question.

B.5.EA:11 - SoTA-Echoing

The question is how to develop a useful contribution when the participant cannot yet express what their experience makes consequential. B.5.FM is an alternative: it can recover a contrast, compare cases and construct a relation. Use it when those questions let the participant supply usable distinctions. The extra operation here is returning to experience when familiar wording blocks that contribution, trying a different expression and letting the participant correct it before reasoning from it.

Adopt those operations from Gendlin’s account and appendix, steps 3–8, 2009: fresh phrasing and the reading of one episode through another can develop meaning that a stock label loses. Sections 4.2–4.3 and the two-episode comparison in §5.1 apply these operations. Reject the inference that a shared felt origin guarantees a logical connection among terms; §4.4 keeps intended meaning, public interpretation and grounds for a further claim separate.

Schoeller’s account, §3.1–3.2, 2022/2023, develops the human experiential and listening branch. Its listener initially refrains from adding suggestions. Preserve that first opportunity in §4.2.

Adapt the later interaction for joint work by allowing a tentative reformulation that the participant can amend or reject. The possible gain is a usable expression sooner; the cost is a greater risk that the listener’s interpretation displaces the participant’s contribution. Continued agreement alone cannot resolve that risk. Return to reflection of the participant’s words when they cannot develop or correct the suggestion.

The complete Thinking at the Edge practice is another choice when the person wants sustained experiential inquiry and theory development. This shorter method stops at the contribution needed for the work and leaves the practice’s training and later development outside its promise. It preserves return to experience and correction while accepting that narrower result. The sources motivate this choice; they do not establish comparative speed or effectiveness of the combined method. Reopen it if the participant repeatedly loses their meaning through suggestions, the needed result exceeds ordinary articulation, or another elicitation method supplies the same contribution with less interference or effort.

B.5.EA:12 - Relations

A.16.1 can preserve an early cue; C.2.4 characterizes articulation. Neither assessment nor a preservation record is a prerequisite for an ordinary attempt.

B.5.FM develops a model from an available contrast. B.5.4 interprets a situation through an available concept. B.5.2 develops explanatory conjectures; B.5.RR revises affected reasoning; B.5.QD develops further questions.

C.2.8 concerns the structure a reader can recover. C.11.DUA governs whether an additional inquiry is useful enough to undertake. These later questions use the articulated contribution under their own conditions.

B.5.EA:End

B.5.WN - Develop Lines of Thought with Notes

Type: Method pattern Status: Stable Normativity: Normative

B.5.WN:1 - Problem frame

Use this pattern when useful observations, reading or tentative thoughts recur across occasions, but keeping them has not yet made them available for developing a question or argument. You remember an interesting distinction without its grounds, find a relevant note without knowing why it matters, or repeatedly start an explanation whose missing connection remains hidden.

This is a branch of reasoning practice: developing thought through addressable notes and meaningful relations between them. Its material is an evolving formulation, the grounds it uses and the connections through which another occasion of reasoning can continue it. A note can be handwritten, an addressable block or a separate file. The method concerns what the practitioner does with that material; storage and retrieval engineering remain further work when the available means are inadequate.

First move. Take one available observation, source passage or rough note. Say what it lets you claim or ask, then compare that formulation with one relevant earlier thought. Write the consequential relation, including an unresolved difference when that is what the comparison produces.

The first result can be a better question, a counterexample, a missing premise or a usable continuation. A final publication topic need not be known. An assigned topic also provides an entry: follow the part of its argument that the available material cannot yet support.

Use a sufficient project record when it supports the next action. A longer-lived note network is worthwhile when later comparison, recombination or development warrants the work of keeping it usable. Routine recording, factual retrieval and recovery of a specified interrupted action can end without building such a network. Learning to reason independently and obtaining a useful argument with assistance are different purposes.

B.5.WN:2 - Problem

Chronological capture preserves occasions but can hide relations between them. A topical folder can collect similar material without explaining what one contribution changes in another. Extensive linking can make navigation possible while leaving the inference unwritten.

The opposite repair also fails: demanding a polished, correctly classified permanent note before its thought has developed removes the provisional material from which a question could emerge. The task is to give thought enough stable form to be compared and carried forward while allowing its meaning, connections and intended use to change.

B.5.WN:3 - Forces

ForceTension
Capture and present workA short cue can prevent loss, while recording and processing everything can displace the work that supplied it.
Stable arrangement and changing thoughtFamiliar placement and addressable units reduce repeated setup; an inherited classification can suppress a newly useful distinction.
Recombination and connected reasoningA separable thought can enter several arguments; excessive fragmentation removes the premises needed to understand it.
Retained observation and revised interpretationLater understanding can improve a claim without changing what was originally observed.
Deferred inquiry and timely relianceAn unanswered question can wait until useful; a premise consumed by today’s decision cannot.
Personal use and another readerAn abbreviated cue can serve its author now but fail after delay or transfer.

B.5.WN:4 - Solution

Develop the note through its use in reasoning. Recover its meaning, formulate the thought, test a meaningful connection, follow what that connection changes, and leave a usable way to return. These operations can recur in a different order as the work reveals another gap.

Recover a thought → make one useful connection → follow what it changes → leave a usable return.

A collection becomes useful through these continuations.

B.5.WN:4.1 - Enter through available material

Begin where something is available: an observed episode, a passage, an objection to a draft, an existing question or a rough phrase. Recover enough of its context to tell what the thought concerns and why it attracted attention. If a cue no longer permits that recovery, return to the episode or source when available. Otherwise retain the uncertainty or discard the cue when no needed use depends on it.

A short capture serves the interruption. Develop it while its meaning is recoverable when later work warrants retaining it. Ask what the next occasion would need to know. “Bench slow” may remind its author of a conversation today; later comparison needs the job, the observed intervals and which result was called slow. The useful repair supplies those distinctions, without expanding every cue into the same form.

Keep a simple stable place and means of addressing notes. A known capture place, a source return and compatible small units can make comparison and rearrangement routine. Start with material that matters. Processing an entire old archive is unnecessary when the present question can be developed without it.

B.5.WN:4.2 - Formulate a thought with its grounds

Write the claim, question or conjecture in terms you can use in reasoning. For a source-derived note, recover the source’s question, conditions and contribution before stating what follows for your own work. Distinguish the source account from your inference. A useful paraphrase preserves the source’s limits; a quotation needs its context when that changes its meaning.

Keep the reason with the thought. “These jobs have different total delays but equal bench occupation” needs the event choices and calculation that support it. “Delay comes from waiting” is a stronger explanation and needs another basis. Let the note retain the weaker result when that is what the material establishes.

Choose a unit that can participate in a later argument. Split two thoughts when each needs independent use or revision. Keep a short derivation together when separating its steps would make the inference hard to recover. One sentence, one screen and one file are possible conveniences, not definitions of a thought.

An unresolved question can have a stable address. Its address makes it referable; its formulation states what remains unknown. Where a later use depends on an earlier formulation, retain that formulation or a return to it before changing the note. An observed event, a claim about it and a project-specific restatement may require different change treatment.

B.5.WN:4.3 - Make the connection do reasoning work

Find an earlier thought that could change the new one or be changed by it. Search by the problem and possible contribution as well as by subject vocabulary. A note about obtaining a usable result may matter in testing, review and delivery although their local words differ.

Read the two thoughts with their grounds. Try the relevant operation:

  • compare their meanings and conditions before treating them as agreement or contradiction;
  • use one as a premise and attempt the inference the other needs;
  • use a contrary case to test a general claim;
  • carry a relation into another case and identify what makes that transfer applicable; or
  • expose an unresolved dependency that neither thought supplies.

State the relation that survives this attempt. “Related to note N” can be enough for a familiar return; otherwise add the reason for the connection. For example, “This second attempt defeats the earlier assumption that one job has one occupation interval; the earlier two-job calculation is unchanged.” The relation tells the later reader what to reconsider.

A resemblance can propose a question before it supports an explanation. Keep that difference in the note. If two cases lack the same result, their causes may differ. A consequential counterexample narrows or rejects the proposed relation; it need not erase the observations that prompted it.

Use B.5.QD when the result changes the question and B.5.RR when a changed premise must be carried through dependent reasoning. Use the relevant subject method for the inference, experiment or construction. A new arrangement can make a missing premise visible without supplying it.

B.5.WN:4.4 - Provide entries for future occasions

Give a retained thought a route from a question in which it may help. A subject label can be useful, but an entry such as “apparent speed differences with different completion events” names a future reasoning use more directly than “bench notes”.

A small overview can state how several notes connect. It can distinguish an established inference from a promising analogy and expose an open question. Revise that account when the relationships change. Its purpose is to make a line of reasoning findable and inspectable, not to establish a final taxonomy.

A journal preserves sequence and contemporaneous context. A note network can expose relations across episodes. A project file holds what one undertaking uses. They may refer to the same observation. Keep one observation’s identity and grounds recoverable across these uses; displaying it in several views creates no additional observation.

Use the access arrangement available. A link that only the author can open does not supply another reader with the note. When a collection becomes too difficult to find or maintain, the relevant knowledge-access, notation or integration method can improve that arrangement. A working pair of notes does not require that engineering work in advance.

B.5.WN:4.5 - Develop or defer the emerging question

Follow a connection while it can yield a useful next result under the available means. The result may be a refined question rather than an answer. Ask what evidence or construction could distinguish the live possibilities. Continue with that contribution, or leave the question in a form that a later occasion can use.

Two kinds of return are useful. A known deferred intention can be recalled at its next occasion. A semantic entry can expose a relevant thought while following a different question, including when its author has forgotten that it exists.

For a deliberate deferral, retain the open question, the basis obtained and what would make continuation worthwhile or necessary. Use a reminder when there is a known occasion. Use a meaningful entry when the future occasion is not known.

Compare deferral with the present reliance. If today’s choice consumes the missing premise, obtain it, choose a supported alternative or withhold the dependent conclusion. If no current use consumes it, the question may remain open. This is the resemblance to lazy evaluation: work can wait until its result matters, provided the later use can recover the dependency and initiate the needed work.

B.5.WN:4.6 - Compose an argument for a recipient

When a project or assigned question needs an answer, read that question before selecting the notes. Whose work does it concern, and which differences could change the conclusion? If it concerns a whole job, which performances contributed to its result? Two histories may fit every selected note and yield different answers. Look for the observation or argument that distinguishes them. Arrange the reasons in the order the recipient needs. A visible outline can keep the whole argument available while one passage is being written.

Turn the selected material into that argument. Supply missing transitions, examine contrary material, remove repetitions and distinguish a useful example from evidence for a general claim. Composition often exposes a premise that seemed present only because the author knew the collection.

A project may develop copies or selected passages differently from the retained notes. Keep a source return where it matters; the new use need not rewrite every original formulation. Conversely, if new evidence defeats a retained claim used elsewhere, return that change to the affected reasoning. Follow the dependency rather than synchronizing every sentence merely because it was copied.

A useful collection can remain incomplete. An argument offered for reliance must supply the premises and inferential steps its conclusion needs, or state its bounded unresolved result. Use the subject method to obtain what is missing. Stop polishing the surrounding wording when an unsupported premise is the obstacle.

B.5.WN:4.7 - Leave a usable continuation

At a useful stopping point, leave the result that was obtained and the next question or operation when one remains. The later user should be able to recover why that continuation follows. A completed argument, a narrowed question and a deliberately abandoned conjecture have different further uses.

Retain long-lived notes when their future use warrants it. Processed fleeting cues and completed project material can have other dispositions. Apply the relevant retention, confidentiality and access rules before sharing or discarding material.

For a handoff, select what the recipient needs to continue the reasoning: its question, obtained result, consequential uncertainty, usable source returns and next contribution. Make abbreviated personal relations explicit where that reader cannot recover them. The whole private collection need not travel.

Assess a stronger claim with the evidence it requires. A coherent note connection supports its stated inference. A reader’s successful recovery supports that use under that reader’s preparation and help. Independent capability, learning and improved production performance require their own assessment.

B.5.WN:5 - Archetypal Grounding

B.5.WN:5.1 - From a duration note to a new cross-case question

A practitioner is investigating reports that a bench is slow. Job Q41 is received at 09:05 and has a usable result at 10:00; the bench is occupied from 09:30 to 10:00. Q42 is received at 11:00, occupies the bench immediately and has a usable result at 11:30. The comparison developed in A.6.3.RT.OE distinguishes 55 versus 30 minutes until a result from equal 30-minute occupation.

A rough cue says “same bench time, different speed”. Before its context disappears, the practitioner writes a usable thought:

Compare the same beginning and result events. Q41 and Q42 both occupy the bench for 30 minutes. Their receipt-to-result durations differ because Q41 begins occupation 25 minutes after receipt. These observations distinguish waiting from occupation; they do not explain why the wait occurred.

The note returns to the two jobs’ observed times. An entry for “apparent speed differences” makes it available beyond a folder devoted to this bench.

Q43 later occupies the bench from 13:00 to 13:30 unsuccessfully, then from 13:50 to 14:20 successfully; its receipt is at 13:00. Time to the usable result is 80 minutes, occupation is 60 and the interval between attempts is 20. The practitioner adds:

One job can require several attempts. Relating one job to one occupation interval would lose Q43’s history. Keep the attempt and its outcome available when comparing time to a usable result.

The connection to the earlier note states the changed assumption. Q41/Q42’s observations and calculation remain valid. The new distinction changes the construction needed for Q43. The practitioner places this note under an entry for time to a usable result, with a return from the earlier speed-comparison entry.

In another project, all reviews are reported as completed, but the receiving comparison lacks a common basis: the reviews evaluated different configurations. While asking whether completed activities supplied the usable result needed, the practitioner follows the usable-result entry and retrieves the duration notes. Juxtaposition produces a new question:

Which event makes a result available for its next use? Ending the producing activity and obtaining a usable receiving result can differ. Investigate the required relation in each case; equal words such as “completed” do not establish it.

This note states the practitioner’s cross-case conjecture and question. Its links name the bench and review contributions and preserve their different grounds. It proposes an inquiry; it does not establish a common cause.

Now change the review facts: all reviewers used a common valid basis, but the recipient has not opened their results. The missing-basis explanation fails in that case. The practitioner narrows the connection to the distinction between a result’s availability and its use, retaining the original bench observations.

The records already account for the 25-minute difference between receipt and result for Q41 and Q42. Whether the bench is generally slow requires a comparison standard and grounds that cover the jobs to which it applies. In an open inquiry the practitioner can choose the new question about reviews and leave a route back to the bench question. When a decision about the bench is due, return the supported local finding and identify what the decision still requires.

B.5.WN:5.2 - Develop an assigned explanation from mathematical notes

A writer is asked whether knowing that both of two real addends are irrational determines whether their sum is rational. The writer knows the usual proof that sqrt(2) is irrational. One note contains a theorem about a different pair of addends. Adding a rational number to an irrational one yields an irrational sum. If the sum were rational, subtracting the rational addend would make the other addend rational.

A rough second note asks whether adding two positive irrational numbers must also yield an irrational number. Keeping the quantifiers in the formulation makes a counterexample searchable. The writer tries sqrt(2) and 2 - sqrt(2). Both are positive. The second is irrational, since making it rational would make sqrt(2) rational by subtraction. Their sum is 2.

The new note retains the two values and that short justification. Its link to the first says: “The first proof requires a rational addend; replacing that condition by an irrational addend permits a rational sum.” Separating the counterexample from its positivity and irrationality grounds would make later use require reconstruction. A small connected note is sufficient.

The writer also needs grounds that an irrational total is possible. A second pair satisfying the note’s stronger positivity condition suffices. Using sqrt(2) + sqrt(2) = 2sqrt(2) gives such a pair: if that sum were rational, division by the nonzero rational 2 would make sqrt(2) rational. The two cases support the bounded answer that the sum can be rational or irrational.

The writer can now answer the assignment. Both examples satisfy its premises, and their sums have different rationality. The first note explains why its theorem cannot decide between them. If a reader asks for every attainable total with unrestricted signs, the same two examples supply only two totals. For any rational target r, take sqrt(2) and r − sqrt(2), which are both irrational. For an irrational target t, take t/2 twice. If t/2 were rational, doubling it would make t rational. Thus with unrestricted signs every real total is attainable. The second question needs this argument across targets. The first can end with the two examples.

A later question about squares can enter through the same concern with what an operation preserves. The present note does not answer it. The writer either develops that question through the relevant mathematics or retains the possible connection for another occasion.

B.5.WN:5.3 - Carry a developing question into operational case work

An engineer has the notes in :5.1, including their corrected question about availability and use. The engineer keeps an entry for “completed activity, receiving result still unavailable”.

At an authorized support handover, a customer asks whether faster export workers would make a checked report available by 08:45. The current export delivers the file by 08:00. The senior analyst starts at 08:30 and the required duplicate check takes at least 30 minutes. The proposed workers would only advance delivery of the file. Private row contents remain in the customer’s system. The engineer may examine the support question and recommend further work.

The engineer follows the entry and brings the earlier question to this episode: which result must “finished” supply to the analyst, and what work remains after that event? The comparison produces a note:

Time the result the customer needs. With this staffing and check, the report cannot be released before 09:00. Earlier export still leaves the analyst starting at 08:30. The proposed purchase cannot meet 08:45 on those terms. The bench and review notes suggested looking beyond the recorded completion event. The grounds for the answer come from this customer’s schedule and required check.

This answers the purchase question. Suppose the customer also asks whether the manual reconciliation work can be reduced. Follow what happens to the data, which duplicate the analyst removes, and which transfer or check creates the work. A repeated delivery of a valid export and duplicate rows already present inside one export can both lead to a morning correction. Changing the resend procedure could affect the first cause while leaving the second untouched.

For the transfer question, the current manual distinguishes protocol v1, which requires manual receipt reconciliation, from v2, which permits idempotent resend after absence of a receipt has been confirmed. The installed protocol is unknown. The engineer can ask the authorized local service for that fact. The answer will determine which transfer rule applies. To recommend a change to the morning check, the engineer still needs grounds connecting the duplicates the analyst handles to that rule.

A signed configuration report identifies v2. At the next permitted handover, the engineer applies the manual to that configuration. It requires confirmation that the relevant receipt is absent before the proposed resend. The configuration report settles which rule applies. Evidence of what produced the duplicate and which checks the receiving arrangement requires would bear on the separate proposal to reduce manual work. The recipient can rule out the faster-worker purchase for 08:45 while those questions remain open.

The ordinary case record retains the duplicate episode, the protocol question and the eventual report. It is sufficient to resume this same support case; copying those facts into a second case ledger adds no needed capability.

The longer-lived note contributes a separately developed question, its grounds and its limits across the bench, review and export occasions. Making that thought available costs the formulation and maintenance of the note and entry. Use the record when it supplies the needed question. Keep the network contribution only for continuations that use it.

Finally change the governing source. A new manual describes v2 but additionally requires destination certification. The available report identifies v2 and says nothing about certification. Preserve that observation, the original duplicate episode and the question that connected them. Revise the conditional advice: the former basis is insufficient for this proposed resend. Obtain the certification contribution through an authorized route or withhold the action; the protocol fact need not be collected again merely because another premise is missing.

The note has helped construct and carry a question into work. The allowed encounter, configuration read, interpretation of the manual and controlled operational action remain contributions with their own conditions.

B.5.WN:5.4 - Keep the simpler project record when it suffices

An operator records a replacement part, installation time and required follow-up in an existing maintenance case. The next technician can find the current state and perform the scheduled check through that case. Copying those facts into a separate personal note network supplies no identified continuation.

Use the case. If several cases later expose a recurring unexplained relation, formulate that question with returns to the relevant observations. The later inquiry can justify a connected note without replacing the operational record.

B.5.WN:6 - Bias-Annotation

The method favors work in which thoughts can be expressed, compared and revisited. Tacit performance can supply observations, but written description does not by itself teach the performance. Source familiarity affects how much context a useful note needs.

The examples are constructed reasoning cases. They establish their calculations and inferences. Assistance may produce a useful formulation while leaving the user’s own ability to formulate and connect unchanged.

B.5.WN:7 - Conformance Checklist

  • CC-WN-1 — Recoverable thought. A retained formulation states a usable claim or question and the grounds its next use needs.
  • CC-WN-2 — Source and continuation. Source meaning, observation and own inference remain distinguishable where reliance depends on them.
  • CC-WN-3 — Consequential connection. A connection supplies a reason, contrast, counterexample, transfer question or other stated contribution to reasoning.
  • CC-WN-4 — Appropriate unit. Separation supports independent use without losing a required inference.
  • CC-WN-5 — Available return. A relevant future occasion can find and interpret the retained contribution under its access conditions.
  • CC-WN-6 — Changed condition. Contrary evidence or a changed question revises affected reasoning while preserving valid observations and results.
  • CC-WN-7 — Use-relative closure. Deferral, a completed argument and a blocked reliance retain their distinct requirements.
  • CC-WN-8 — Proportionate support. Capture, connection and maintenance contribute enough to the intended use to warrant their burden.

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

Failure in these situationsConsequenceRepair
Save a phrase after its context becomes unrecoverableA later reader cannot identify the thought or its grounds.Recover the source or episode, retain the uncertainty, or discard a cue whose loss defeats no required use.
Add links without examining the relationNavigation grows while the argument remains missing.Perform the comparison or inference and state its result.
Force every thought into one sentenceA claim loses the condition or derivation required for another use.Keep the needed reasoning together; split only independently usable contributions.
Turn a new interpretation into an old observationThe record seems to show something never observed.Preserve the observation and change the dependent account.
Keep a missing premise deferred while relying on its conclusionThe apparent continuation has no adequate basis.Obtain the premise, choose a supported alternative or stop that reliance.
Publish the note sequence as the argumentThe recipient must invent transitions and supply missing grounds.Select and rewrite for that recipient’s question; repair the uncovered dependencies.

B.5.WN:9 - Consequences

A useful thought can remain available across occasions without a finished project or final classification. Forming and examining connections develops reasoning, and composing an argument can reveal what the collection does not supply.

The practitioner spends time on recoverable formulation, meaningful entries and occasional revision. The return depends on later use. A sufficient immediate record can remain the better choice when that further work has no identified contribution.

B.5.WN:10 - Architectural Rationale

A retained expression and a line of reasoning have different continuity conditions. An observation can remain unchanged while an interpretation is corrected; a question can retain its address while its proposed answer changes; a project argument can select and rewrite only part of the collection.

Stable addresses and compatible units make those changes manageable. The reasoning comes from the operations on their content and relations.

B.5.QD develops a question from a result, B.5.RR revises dependent reasoning, and A.6.3.RT.OE prepares an expression for an operation. The present method connects such work across retained formulations and later occasions, including the passage from a developing network to a recipient’s argument.

B.5.WN:11 - SoTA-Echoing

Practice question. How can retained material develop thought across occasions without making capture and organization the whole activity?

Selected line. Adapt the connected practice in Sönke Ahrens, How to Take Smart Notes, revised and expanded edition (2022): source understanding and own formulation, meaningful connections, questions that develop through work, and composition that exposes missing argument. Chapter 2’s overview, chapters 10–12’s reading and connection work and chapter 13’s development of a written contribution supply that account. The appendix qualifies historical practice: an addressable note can remain abbreviated or unresolved. Stable routine arrangements enable comparison without making substantive classification final.

Comparable alternatives. Compare a sufficient chronological project record, a persistent note network and direct drafting for a fixed question. In :5.1 the project record preserves the bench events and supports its immediate calculation. The additional note and problem-based entry cost formulation and maintenance; they make the later cross-case comparison available without requiring the writer to remember the bench episode. If no such continuation is needed, retain the project record alone.

In :5.2 an assigned question starts the work; the existing theorem and two constructed cases suffice. Building a larger collection before writing would add no needed premise.

In :5.3 the case record supplies same-case resumption, while the connected note carries a question developed across unlike episodes. The comparison retains both the useful transfer and the no-network alternative; changed operational conditions require their own qualification.

Luhmann’s 1981 account, Kommunikation mit Zettelkästen, is a historical example of sustained practice. Andy Matuschak’s daily working log and writing strategy provide inspectable digital-practice alternatives. Their descriptions are method accounts, not controlled efficacy comparisons.

Decision and cost. Adopt stable addressability and recoverable source returns when later reasoning uses them. Adapt note unity to independent use and connected inference, and retain temporary project views when their argument develops differently. Reject a universal promotion ladder or note-count target: neither selects the useful result in these cases. The accepted burden is selective formulation and connection in exchange for an available later continuation.

Reopen the arrangement when useful thoughts repeatedly remain unfindable, mandatory structure suppresses a needed distinction, maintenance exceeds the contribution to work, or a simpler available practice supports the same continuation with less effort.

B.5.WN:12 - Relations

  • B.5.PI and B.5.EA help initiate inquiry and articulate a distinction from experience.
  • B.5.QD develops a new question from a result or construction; B.5.QD.CF examines conflicting assumptions when that is the obstacle.
  • B.5.RA and B.5.RC recover an argument or construction needed to understand and continue a source.
  • B.5.RR revises reasoning after a premise or question changes.
  • A.6.3.RT.OE constructs an expression for the next operation; A.6.3.RT preserves content through a representation change.
  • A.15.10 and A.15.11 supply resumption of interrupted work and an occasion where a relevant contribution can be used.
  • C.39.RO develops a reusable operation when the successful local construction needs that further result.
  • C.2.8 qualifies what a recipient can recover under stated preparation, access and assistance.

B.5.WN:End

B.5.MPC - Connect Physical, Mathematical and Computational Reasoning

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

B.5.MPC:1 - Problem frame

Use this when a physical question needs contributions from mathematics and computation, and their results do not form an interpretable answer together. You may be choosing a robot command, determining whether a gear arrangement can turn, or organizing entry to a room with a finite stock of cards. The difficulty is to connect what the physical arrangement does, what the mathematical result establishes, and what the procedure and its execution produce.

Begin with the difference the answer should help you understand or make possible. Take one available contribution and explain what it would have to mean, and what else would have to hold, for that contribution to answer the question. Work the first missing connection far enough to obtain a consequence or locate the next missing contribution. For a motion command, this might reveal that the supplied count concerns motor revolutions while the distance model concerns wheel revolutions.

The result is a connected solution, a useful conditional consequence or bound, or a missing connection that directs the next inquiry. This pattern specializes B.5’s choice and connection of inquiry contributions for this joint physical, mathematical and computational difficulty. It governs the reasoning that connects those contributions. Physical laws, mathematical constructions, algorithm design and the engineering of an executing arrangement supply their respective subject content.

This is an epistemological and methodological synthesis. The epistemological question is what the connected contributions allow us to know: what follows from the constructions and premises, and how those consequences bear on the physical situation. The methodological question is how agents obtain and apply that knowledge, divide the work and change their methods. A result can support a physical change, expose a limitation or make a further question worth pursuing.

A practitioner needs enough preparation to recover the question, follow the meanings of the important quantities and operations, and recognize where specialist help is needed. The worked cases explain their elementary algebra, graph and counting constructions. A more demanding application can require additional physical theory, mathematics, computation or measurement expertise; obtain that contribution with its explanation when it is missing.

Use an adequate calculation, implementation or operating procedure when its connection to the intended physical use is settled. A proof or bound can answer a physical design question before implementation is worthwhile. For an actual performance claim, add the observations, measurement relation and evidence needed for that claim; a conditional construction alone answers only what follows under its assumptions.

B.5.MPC:2 - Problem

Individually correct contributions can fail to support a joint result. A physical model may concern accumulated wheel rotation, a mathematical variable may represent orientation modulo one turn, and a program may accept an absolute target. Each account can be consistent while their composition loses the displacement that the user requested.

The same difficulty occurs without numerical approximation. A graph can correctly encode a chosen contact list, and a program can correctly colour that graph, while the contact list omits a mesh. A count invariant can be proved while the proposed admission procedure creates two independent stocks of cards. Improving the proof or the program leaves the missing physical correspondence untouched.

A division into “physics first, mathematics second, implementation last” also fails when a later contribution exposes an earlier omission. The interface may require initial state that the first model discarded. A measurement may distinguish fewer cases than the calculation assumes. A mathematical obstruction may make further computation unnecessary. The practitioner needs a way to construct the dependencies, use an available contribution at its point of need, and return a failure to the contribution that can change it.

B.5.MPC:3 - Forces

ForceTension
Shared answer and distinct expertiseSpecialists can work independently on contributions, while their results must concern compatible participants, assumptions and operations.
Useful simplification and physical interpretationOmitting detail can make a problem tractable; an omitted distinction can determine the requested action.
Constructive freedom and justified consequenceNew models, expressions and procedures can open a useful route; their decisive properties require the relevant physical or mathematical grounds.
Abstract result and executing meansA computation can be correct for its stated inputs while the proposed apparatus cannot prepare, represent or execute those inputs.
Reuse and changeExisting results save work, but their use depends on the premises and interpretations that the new question consumes.
Explanation and available effortThe receiver needs enough understanding to use and question contributions without reconstructing every discipline.

B.5.MPC:4 - Solution

Construct the answer by connecting the contributions it needs. For each connection, identify the supplied result, the receiving operation and the condition that makes the result usable there. Follow those meanings through the argument or construction that answers the physical question. Trace an instance when it can expose an uncertain correspondence. If the connection is missing, construct it, obtain it from a suitable contributor, or return the missing result that prevents the next move.

The long mantra keeps the whole question available while attention moves between contributions:

Orient by the physical question → propose the relevant physical account → construct a mathematical question and its interpretation → obtain a result and, where needed, a computation → connect its execution and observations to the intended quantities → return the consequence to the physical question → choose the useful action or the next missing contribution.

The arrows recall result dependencies. They do not prescribe the order in which contributors must discover, receive or develop every contribution. A theorem, algorithm, measurement or physical mechanism can be the first available input.

B.5.MPC:4.1 - Recover the physical difference the answer should resolve

Identify the thing or situation being understood or changed. Say which difference would make an answer useful: a displacement within a stated tolerance, the possibility of coupled rotation, a capacity bound during entry, or another consequence the work needs. Include the relevant boundary and operating conditions when changing them could change the answer.

Then recover what is available. An engineer may have a trusted motion model but an unfamiliar command interface. A mathematician may have an odd-cycle theorem and ask which physical arrangements its obstruction describes. A room attendant may have a reliable card procedure and want to extend it to a second entrance. Enter through that available contribution and recover only the other results needed to answer the question.

Use B.5:4.1 when the question needs formation or revision. B.5.4 helps recognize the participants and relations of an explained concept in a concrete situation. If the receiving use is unclear, work one small consequence of the available result and ask what it would let someone decide or do. Retain a theoretical question when its answer could enable a worthwhile construction, explanation or later inquiry.

B.5.MPC:4.2 - Propose the physical account and the observations it needs

Identify the participants, interactions and configurations that could determine the requested difference. Give separately used quantities their participants and reference conditions: the robot’s distance to a wall before motion, its distance afterwards and its displacement are three quantities, even though each is called a distance. Start from the arrangement and relevant subject knowledge. For a rolling robot, distinguish wheel, motor, transmission and ground contact. For gears, distinguish a contact from proximity in a drawing. For admission cards, distinguish a material card, its holder, the room boundary and the permitted transfers.

State the applicable physical or operating rules. Explain why a rule supplies the needed relation and where it is an assumption. Wheel rotation yields a distance relation only under the chosen rolling and geometry conditions. Exclusive possession of a card supports an admission limit only when the entrance procedure connects possession to entry and return. A.3.3 helps construct configurations, retained state and allowed continuations; the subject practice supplies the laws and mechanisms those continuations use.

Choose a sufficient account for the question. If the physical boundary or the procedure is yours to choose, ask which change in the arrangement could change the requested result while the description of one part stays the same. For an occupancy guarantee across entrances, follow the room boundary, the transfers each entrance permits and any relation between their card stocks. For yesterday’s occupancy, establish which transfers actually occurred or what the available evidence bounds. A direction or impossibility result may need less physical detail than a trajectory, speed or load calculation. Make an omitted interaction explicit when it could defeat the inference: slip changes wheel travel, a moving gear carrier changes relative rotation, and uncontrolled entry breaks the visitor-to-card association.

When observations supply an input or test a consequence, construct the relation between the sought quantity and the indication. Use C.16:5.3 and C.16:5.4 for the measurement method and model. Motor counts can indicate motor rotation under an encoder account; using them to establish travel additionally consumes the transmission and ground-contact account. If the available indication leaves different required answers possible, seek a discriminating observation or a sufficient bound. If a weaker question is useful, explain what answering it contributes and what remains open for the original use.

Return a proposed physical account and its consequences under stated conditions. An unknown interaction or calibration is a useful missing contribution when it determines which mathematical question can be constructed.

B.5.MPC:4.3 - Construct an interpretable mathematical question and expression

Choose mathematical objects and operations that retain the distinctions needed by the physical question. State what their important elements mean. For instance, let a vertex denote one gear, an edge denote a mesh, and a colour denote the sign of rotation when viewed from one common side. A colour number has meaning through that interpretation.

Construct the relation that connects the physical rules to the mathematical constraints. Derive a distance per motor increment from wheel circumference and transmission ratio; derive an opposite-colour constraint from the external-contact rule; derive a count invariant from a fixed stock and its permitted transfers. C.29:4.1 supplies the general correspondence-and-return method. When an operation or a compressed representation must preserve a result, use C.29.1 to compare performing the source operation and then transferring its result with transferring the inputs and then performing the receiving operation.

Work the distinction that could defeat the representation. A wheel orientation repeats after one turn; accumulated travel can continue to increase. A graph of opposite-direction contacts answers a different question from a graph in which an edge merely means “these parts are connected.” If two physical cases receive one mathematical representation but require different answers, retain their distinguishing information, restrict the cases or seek a weaker consequence.

Keep the relation available when the question changes. Identify which quantities are given and which must be obtained, then derive the computational direction that serves that question.

Under a model d = v*T and v = k*u, where u is a motor command setting, positive k, u and T permit T = d/(k*u) for a duration question or u = d/(k*T) for a command question. Obtain k and the range in which the speed model applies from the physical account. The device’s word “power” needs its interface meaning; u is not assumed to be physical power in watts. A resulting command outside the supported range returns a realizability question.

For a conditional example, let u be dimensionless and let k = 0.2 m/s. A distance d = 1 m at u = 0.5 takes T = 10 s. Changing the requested duration to T = 5 s requires u = 1. If the available range is 0 < u <= 0.8, the shortest duration under this model is 1 / (0.2 * 0.8) = 6.25 s. Returning that bound lets the requester change the deadline or seek a different realization.

An equality constrains the quantities in this model. A program assignment changes a stored value according to its execution rules. Construct the needed assignments or solver from the relation after selecting the givens and unknowns; C.29.2 supplies that formulation Method.

Make an expression that supports the next operation. Use A.6.3.RT:4.1 to express the givens and constraints under an available scheme and compare the result with its source. Put units and participant names where their absence permits the wrong operation. Keep a shared quantity recognizable across expressions, such as the wheel revolution in the transmission ratio and circumference relation.

Notation can contribute to obtaining the result. A table can expose mutually exclusive card states; a graph can make a closed contact path traceable; a labelled equation can reveal the missing subtraction of an initial position. The subject Method supplies the construction or inference performed with those expressions. If the available scheme cannot express the needed distinction, change the scheme or obtain notation-design work before treating its expressions as adequate.

B.5.MPC:4.4 - Obtain a sufficient consequence or construct its computation

Choose the result the use needs: a value, distribution, statistic, bound or property of ongoing behavior. A witness can establish one feasible arrangement; a counterexample can refute a general claim; a proof can establish an obstruction; a bound can settle a threshold decision. Compute an exact numerical answer only when that answer contributes to the use.

When a procedure is needed, construct its inputs, retained state, elementary operations and output interpretation. Explain how it obtains the mathematical result and why it terminates, or which property it preserves during continued interaction. C.29.2 supplies this formulation work; the relevant algorithmic or mathematical Method supplies the construction and its argument. B.5:4.2 and B.5:4.3 help recover a construction or a decisive proof step that the available explanation leaves inaccessible.

When an instance helps establish the correspondence, follow what each step of it means. In a two-colouring procedure, a waiting list records vertices to be processed, while parent links can reconstruct a failed closed path. In a motion calculation, the integer is a count of a kind of increment. In an admission procedure, taking a free card changes a finite state and determines whether an entry may proceed.

For a numerical approximation, carry the error that can affect the physical use. Separate rounding of a computed command from uncertainty in radius, calibration or physical response. For a resource claim, include the cost of obtaining the input, representing it and interpreting the output when those costs matter. Counting one graph-edge inspection as one operation is useful under an adjacency-list cost model; it does not estimate the effort of discovering the contacts.

Use a supplied proof or computation when its premises, meaning and relevant resource conditions fit. If a necessary construction remains unknown, state the missing operation and what it must connect. C.39 supplies the search for or development of a missing way. A conditional answer or a less demanding bound can finish the question while that larger construction remains open.

B.5.MPC:4.5 - Connect the computation to preparation, execution and observation

Begin with the abstract input and explain how the proposed arrangement represents it. Then identify the system actions that perform the operations and the observation or final state from which the result is read. Use C.29.3 for this realization comparison.

Compare two routes for the input:

abstract input → stated computation → abstract result
abstract input → prepared system → system operation → interpreted result

The comparison asks whether the second route returns the equality, bound, statistical agreement or behavioral property that the receiving use needs. Input preparation and output interpretation can use different relations. Preparing a motor command and reading robot displacement are different operations; counting free cards and authorizing one transfer use different aspects of the same arrangement.

Recover range, units, initial state, ordering and completion conditions at the point where they affect that comparison. A signed command field cannot carry every positive integer. A command meaning “add this displacement” differs from one meaning “reach this position.” A material card available for transfer cannot simultaneously be assigned to another visitor.

Include the timing and retained physical state that the comparison consumes. When a controller is paused for debugging, determine which physical processes continue and which command remains active. Observe or replay the operation with the timing it needs, or interpret the changed run under its changed conditions.

Establish the event that completes the requested physical action; program termination, a command acknowledgement and motor stopping can occur at different times. For an observation, include a settling interval or other preparation when the measurement relation requires it.

For a design question, use the stated model of the executing arrangement and return a conditional realization. For a claim about what happened, obtain the corresponding observations and their interpretation. A command receipt can establish that a command was accepted while leaving its successful physical completion open.

Use an existing adequate implementation when this comparison is settled for the receiving use. A manual procedure, analog apparatus or controlled material transfer can supply an execution. Its adequacy follows from its permitted operations and interpretation, not from whether it contains digital software.

B.5.MPC:4.6 - Keep joint requirements and alternative routes distinguishable

Recover dependencies by asking, for each needed result, “What results and conditions make this operation possible, and what other operation could supply the same receiving need?” Keep the answer with the derivation, diagram or explanation. A short case may need only a sentence; a shared design may need a dependency diagram.

An AND dependency means that contributions are needed together for the stated inference. The robot’s distance per motor increment uses the effective wheel radius, transmission ratio and increments per motor revolution together. Replacing any one can change the command. Establish that the required premises can hold in the same configuration. A controller might accept the required count in absolute mode and offer relative commands only over a smaller range. Separate evidence for the count and for the relative mode leaves their combination open.

An OR alternative is a different sufficient way to obtain the result needed by the receiving use. A proved upper bound at or below the limit can establish that the limit cannot be exceeded. If the bound extends above the limit, a tighter bound or an attainable violation can settle what that bound leaves open. Computing the maximum when it exists is another route. Each route retains its own assumptions. Two different approximations do not become sufficient alternatives merely because both return a number.

For a conditional physical consequence, one useful small rendering is:

applicable physical account
AND mathematical interpretation
AND (sufficient direct consequence OR sufficient interpreted computation)
→ consequence for the physical question

The computational branch additionally depends on a procedure and an adequate realization for any claimed execution. A claim about observed physical behavior adds the observations and measurement relation it consumes. These are different claims and can end the work at different places.

Keep a shared premise attached to every contribution that consumes it. Both an analytical calculation and a numerical simulation can depend on the same no-slip assumption. Switching between them does not remove that dependency. Conversely, when an upper bound answers the decision, the exact optimizer need not be obtained.

Enter a result at the place where it is used. Recover its inputs and conditions backward, then continue forward with its consequence. When a missing input blocks one route, compare another sufficient route using the available inputs. Do not combine an output from one route with the assumptions of another without establishing their compatibility.

A failed connection can send the inquiry back to its physical account, mathematical construction, notation, procedure, realization or question. Use B.5.MPC.R to locate the incompatibility, construct a sufficient repair and carry it through the affected contributions. If several causes remain compatible with the observations, obtain a discriminating contribution or use a sufficient conditional result.

B.5.RA supplies argument recovery and B.5.RR supplies general reasoning revision; C.29.1, C.29.2 and C.29.3 supply the transfer, formulation and realization methods respectively. Retain unaffected contributions whose conditions and meanings hold.

B.5.MPC:4.7 - Return the consequence and choose what to do with it

Explain the result in the original physical terms. A count becomes a modeled displacement; an odd cycle becomes a set of contacts that prevents the stipulated nonzero rotation; a card invariant becomes a bound on occupancy under the entry rules. State what the result enables and the condition that changes that use.

When the consequence is insufficient, make the next contribution specific. “Determine whether these two wheels slip differently under this load” can direct physical work. “Find a representation that retains accumulated turns” can direct mathematical formulation. “Establish whether this interface interprets the number as an increment or an absolute target” can direct realization work. The uncertainty can be the result if locating it prevents further work on the wrong question.

Distinguish the consequence of an obstruction. A mathematical contradiction blocks a construction under its stated premises. A physical restriction blocks an intervention under the applicable laws. An expensive computation can remain mathematically possible while unavailable within the resources of this use. Their repairs can require different questions, arrangements or Methods.

Stop when the supported result answers the intended use. When development is the purpose, work one consequential variation far enough to reveal a new construction, obstruction or missing operation. Explain which additional action or longer inquiry it could enable. B.5:4.4, C.39 and C.40 supply the corresponding question and repertoire development; continued work is justified by that use.

B.5.MPC:4.8 - Divide work by the result each contributor must supply

Allocate work around the dependencies above. A contributor can supply a physical account, a mathematical construction, a proof, a computation, a proposed realization or an explanation of the connection. State the question, available inputs, missing result and intended use when obtaining help through A.15.9. Ask for the formulation when the equation has not yet been constructed.

Retain enough understanding at each receiving point to use and question its input. The receiver of a motion count should be able to identify its unit, the rotation it counts, its sign and its dependence on the motion model. The receiver of a two-colouring result should be able to connect the returned labels or odd-cycle witness to the contact list. The receiver of an occupancy bound should be able to identify the material and procedural conditions that preserve the stock.

That understanding can be held by one agent or distributed across contributors with an effective way to obtain a missing explanation. Arrange a capable contributor for each consequential connection. A completed report alone does not establish that this capability is available when a premise changes.

Choose depth from the later work. Using a stable formula may require interpretation and checks at the connection. Changing the formula requires understanding its derivation. Designing a new algorithm or physical theory requires the additional specialist capability.

When assessing a person’s preparation, examine their contribution on representative work with the assistance that will be available. Include a change of the requested result or a relevant premise when later work requires that adaptation. Ask the practitioner to recover the retained relation, the new unknown and the dependent physical operation.

B.5.MPC:5 - Archetypal Grounding

The following are constructed cases under stated assumptions. They show how the coordinating Method obtains a jointly interpretable consequence. Physical motion, an assembled gear mechanism and an operating admission system require their corresponding physical arrangements and evidence.

B.5.MPC:5.1 - Construct a robot command from a motion question

An engineer wants a robot to advance by 1 m along a straight guide. The guide keeps its direction fixed. For this calculation, the effective rolling radius of the driven wheel is 0.05 m; rolling occurs without slip; the transmission makes ten motor revolutions for one wheel revolution; and successful execution advances the motor by one thousand commanded increments per motor revolution. Positive motor motion is defined to produce forward travel. The initial question is a conditional command design under those assumptions.

First construct the relation from the participants. One wheel revolution rolls through its circumference, 2π × 0.05 m. The motor makes ten revolutions during that wheel revolution, so that travel corresponds to 10 × 1,000 = 10,000 motor increments. Let N be the signed number of motor increments completed after the command begins. The modeled displacement s is:

wheel revolutions = N / (1,000 × 10)
s = [N / (1,000 × 10)] × 2π × 0.05 m
distance per motor increment = 0.0000314159265359 m

The factors expose wheel and motor revolutions and the command unit. A statement that the wheel turns through 2π radians would give orientation change for one turn; the present N retains accumulated turns because the receiving quantity is accumulated travel.

Invert this relation for the target displacement:

N_ideal = 1 m / (2π × 0.05 m) × 10 × 1,000
        = 31,830.9886183791 motor increments
N_command = nearest integer to N_ideal = 31,831

The computational procedure reads the target distance and the three parameters, computes the ideal count and rounds it to the nearest integer. Use enough numerical precision to determine that integer; if arithmetic uncertainty straddles a rounding boundary, refine the calculation or retain the resulting command uncertainty.

Now supply the realization input. The interface accepts signed relative motor-increment commands in the range −32,768 to 32,767. It performs a command to completion before reporting successful completion. Thus 31,831 is representable and its unit and relative-command meaning agree with the calculation. A different interface would require its own preparation relation.

Read the completed command back through the physical model:

s_command = 31,831 / 10,000 × 2π × 0.05 m
          = 1.00000035756417 m

maximum error from rounding to the nearest increment
          = 0.5 / 10,000 × 2π × 0.05 m
          = 0.0000157079632679 m

The rounding bound concerns discretization of the command. It leaves slip, effective-radius error and unsuccessful motor execution outside that numerical bound. If the engineering question is actual travel within a tolerance, those contributions determine whether this command is adequate. For example, motor counts alone cannot discriminate successful rolling from wheel rotation with slip; a displacement measurement needs its own relation to position.

The joint result is the command 31,831 and its modeled consequence under the physical and interface conditions. Physics supplies the rolling and transmission account. Mathematics supplies the relation, its inversion and the error bound. Computation supplies the integer and range check. The coordination connects their meanings and returns the supported displacement.

The same interface’s largest positive relative command represents about 1.0294056648 m under this model. If the requested distance and tolerated error require a larger positive count, use another realization or a procedure using several commands whose combination is justified.

If the wheel radius, the count’s meaning or the use of initial position changes, reconstruct the affected relation before reusing the command. Those changes can affect the physical parameter, mathematical expression and command preparation together; recover the disagreement and its dependent contributions as in :4.6.

B.5.MPC:5.2 - Use two-colouring to answer a gear question

A designer asks whether every gear in a connected arrangement can rotate while all specified meshes remain engaged. The supplied idealized account has parallel, fixed axes, external gear contacts and positive pitch radii. View every rotation from the same side. At each external mesh, the two gears have opposite signs of angular velocity. Contact geometry and tooth compatibility are additional physical conditions; this first question concerns the consistency of rotation directions.

Construct a finite undirected graph. A vertex represents one gear and an edge represents one of the stipulated external meshes. Assign colour 0 to one rotation direction and colour 1 to the other. An edge requires different colours at its endpoints. This expression makes the physical question a mathematical one: can the vertices be assigned two colours while satisfying every edge?

The graph records contact, not geometric closeness on the page. A drawing with crossing lines does not add a mesh between the gears at that crossing. If some contacts are unknown, an odd cycle of established external meshes already rules out nonzero rotation of the gears in that cycle under the stated conditions. Additional meshes cannot remove that obstruction. A colouring of the known edges establishes compatible directions for those edges. To extend it to the entire arrangement, establish that all remaining meshes permit compatible directions, for example from a rule about how the two groups may mesh.

Obtain either a colouring or a witness of failure by the following procedure.

  1. Choose an uncoloured vertex as a root. Give it colour 0, depth 0 and no parent; place it on a waiting list.
  2. Remove the first vertex from the list and inspect its neighbours. Give each uncoloured neighbour the opposite colour, record the removed vertex as its parent, give the neighbour depth one greater and append it to the list.
  3. For a coloured neighbour, compare colours. If they agree, use that edge and the two parent paths to construct the odd-cycle witness explained below, and return it.
  4. Continue until the list is empty. Start another root if an uncoloured vertex remains. If every edge joins different colours, return the colouring.

A vertex is added to the waiting list only once. Each recorded parent has smaller depth, so parent paths reach their root. A finite graph therefore yields a result after all relevant vertices and edges have been examined, or after a contradiction has been found. With adjacency lists, constant-cost access to a vertex’s recorded data, and constant-cost insertion and removal in the FIFO waiting queue, the work is proportional to the number of vertices plus edges.

Work a square contact cycle with gears A, B, C and D and contacts AB, BC, CD and DA. Starting at A gives A colour 0; B and D colour 1; and C colour 0. Every contact joins opposite colours. The groups {A,C} and {B,D} therefore give compatible direction choices. Reversing both groups gives the other choice.

Four equal pitch circles can be placed with centres at the corners of a square of side twice the pitch radius to obtain those contact incidences; tooth engagement and motion under load require the corresponding mechanical design.

Now work three gears with contacts AB, BC and CA. Starting at A gives B and C colour 1. Edge BC then joins equal colours. Its endpoints’ parent paths B–A and C–A, together with BC, give the three-edge closed path B–A–C–B. Alternating directions around three external contacts asks B to have both directions at once.

The same reasoning constructs a failure witness in a larger graph. For a same-colour edge, follow its endpoints’ parent paths until their nearest common vertex. Discard the shared path beyond that vertex. The retained paths have even total length because the endpoints have the same depth parity. The extra edge closes a simple odd cycle. Alternating two colours cannot satisfy every edge of an odd cycle. Conversely, if the procedure finishes without such an edge, its returned colours satisfy every listed constraint.

The physical interpretation can be made quantitative without hiding the direction question. Let rᵢ be a gear’s pitch radius and ωᵢ its signed angular velocity. Ideal external meshing with fixed axes gives:

rᵢωᵢ + rⱼωⱼ = 0 at each mesh
qᵢ = rᵢωᵢ, so qⱼ = −qᵢ

For a two-colouring, choose any nonzero value q for one colour and −q for the other, then set ωᵢ = qᵢ/rᵢ. This satisfies those kinematic equations.

For an odd cycle, following the equations around the cycle gives q = −q and hence q = 0. In a connected graph all gears then have zero angular velocity. Thus the odd cycle excludes the requested nonzero coupled rotation under the stipulated contact model; a stationary arrangement remains compatible with the equations.

Return the cycle as the set of physical contacts responsible for the obstruction. Removing one contact from the triangle leaves a chain and permits alternating directions. Deleting only its graph edge leaves the physical obstruction in place. An internal gear contact or a moving carrier changes the contact rule and requires a revised physical account before the colouring test is reused.

A compatible direction assignment answers this bounded question. It does not establish adequate torque, tooth phasing, freedom from interference or motion under the intended load. For those questions, retain the graph result and obtain the missing mechanical contribution. The common Method supplies the contact interpretation, the connection to the computational witness and the return to the design. The gear account and graph argument supply the substantive rules that make that return possible.

B.5.MPC:5.3 - Maintain an admission bound through material tokens

A demonstration room should contain at most three visitors. Initially the room is empty and three material cards are available. An attendant gives a free card to one visitor before entry. That visitor keeps it while inside and returns it after leaving. A new visitor waits for a card when none is free.

For this case, every entrance and exit follows the procedure, each card is assigned to one visitor at a time, and cards are neither lost nor duplicated. The material arrangement makes exclusive acquisition possible: taking the available card removes that card from the free stock. A photograph or printed copy of the card is not accepted for entry.

First consider a moment when every assigned card is held by a visitor inside and every other card is free. The one-card-per-visitor rule gives:

occupancy = 3 − number of free cards

During admission and return, cards can also be held by visitors outside. A visitor may hold a card while waiting to enter; a departed visitor may be walking to its return point. To preserve the physical meaning during those intervals, distinguish four states for each card:

StatePhysical interpretation
FreeThe card is available for a new admission.
ReservedThe card is held by a visitor who has not yet entered.
InsideThe card is held by its visitor inside the room.
Awaiting returnIts visitor has left, but the card is not yet free.

Let F, R, I and E count cards in those four states. Every card occupies one state, so F + R + I + E = 3. Under the visitor-to-card rule, occupancy = I. Therefore:

occupancy = I = 3 − F − R − E
occupancy ≤ 3 − F ≤ 3

The transition procedure has four ordinary operations: issue one free card to a waiting visitor; admit that card’s visitor; let the visitor leave with the card; and return the departed visitor’s card to the free stock. Their state changes are Free → Reserved → Inside → Awaiting return → Free. A cancelled admission can return a Reserved card to Free while its visitor remains outside.

Each operation moves one existing card between states. Issuing a card requires a free card; entering requires its exclusive reservation; returning it requires that its visitor is outside. Those conditions preserve the total stock and the association between visitors inside and Inside cards. The argument establishes the capacity bound for every sequence of those permitted operations, including overlapping visits.

Work two entries followed by one exit:

Operation just completedFRIEOccupancy
Initial arrangement30000
Issue card A21000
Visitor A enters20101
Issue card B11101
Visitor B enters10202
Visitor A leaves10111
Return card A20101

Counting free cards gives an upper bound on occupancy during handover and return. It gives the occupancy when R = E = 0. That distinction changes what an observer may infer from the same stock. The admission rule can preserve the bound without an exact instantaneous occupancy readout.

Connect the abstract transition rule to the physical means. Exclusive possession realizes consumption of a free token. Carrying it through entry preserves the visitor association. Returning it only after exit prevents its use for a fourth visitor while the first three remain inside. If a visitor passes their card to someone outside while staying inside, the allowed-transition premise fails: the reused card no longer represents one occupied or reserved place.

A second entrance needs access to the same total stock. A copied stock of three additional accepted cards permits six simultaneous admissions, even if both attendants follow their local rule correctly. A shared pool of the original three cards preserves the common bound.

Partitioning those cards, for example two at one entrance and one at the other, also preserves it. The partition can make a visitor wait at one entrance while a card is free at the other; redistribution then needs a transfer of an existing free card.

The result is a conditional admission design and an interpretation of its observable stock. Its computational contribution is a finite-state procedure that answers whether an admission can proceed and maintains the relevant count. People and material transfers can execute it without a digital program.

The coordinating Method makes the physical card and room-boundary rules, mathematical invariant and executing procedure agree. This is also why changing the stock or the return rule changes the joint result even when the counting arithmetic remains correct.

B.5.MPC:6 - Bias-Annotation

Likely biasConsequence for this workCorrective action
Familiar equations dominate the physical accountThe practitioner begins with a calculable proxy and loses the requested quantity.Name two physical cases that require different answers and determine whether the proposed variables distinguish them.
Successful computation dominates interpretationA number or certificate is accepted without its meaning in the physical arrangement.Interpret the decisive count, edge or token transfer and recover the premise connecting it to the receiving action.
Diagram familiarity hides physical assumptionsA graph edge is treated as a real contact, or its meaning changes across an example.Construct the contact or interaction list from the subject account and label the relation that each edge represents.
Digital implementation is treated as the defaultMaterial or manual realizations are overlooked even when they answer the question.Compare their input preparation, permitted operations and result interpretation with the computational need.
A precise answer hides an uncertain premiseSmall numerical error is reported while model or measurement uncertainty can dominate the result.Carry the uncertain physical premise into the returned consequence or obtain the measurement that can settle it.
Contributor identity substitutes for usable groundsAn expert or AI report is trusted beyond what its stated assumptions and explanation support.Recover the connection consumed by this use and obtain the missing explanation or evidence from a capable contributor.

These biases can affect one person as well as a team. Apply the correction at the missing subject operation, correspondence or observation.

B.5.MPC:7 - Conformance Checklist

Use these checks on the claimed joint result and its explanation. They establish conformance to this Method’s stated use; physical validity and any stronger assurance claim require their applicable subject evidence.

CheckContent to inspect
CC-MPC.1 — Receiving questionThe explanation identifies the physical difference to be resolved and what the supported answer enables.
CC-MPC.2 — Physical premisesParticipants, interactions and operating conditions are sufficient to recover the mathematical question; consequential assumptions remain distinguishable from observations.
CC-MPC.3 — Interpretable constructionImportant quantities, structures and operations have meanings that survive the construction, and a lost distinction either leaves the use intact or changes the returned result.
CC-MPC.4 — Obtained consequenceThe proof, construction, bound or computation reaches the requested instance or range under its stated conditions. A result about part of the arrangement identifies what it establishes for the whole question and any operation still needed.
CC-MPC.5 — Executing arrangementAny realization claim connects preparation, system operations and result reading. Range, units, initial state and ordering are recovered wherever they change the inference.
CC-MPC.6 — Joint and alternative dependenciesJointly needed contributions remain together; alternative routes each satisfy the receiving need under their own conditions. A shared premise remains shared across alternatives.
CC-MPC.7 — Notation in useThe expression supports the needed operation under explained or familiar rules; new subject conclusions are justified by that operation rather than presented as mere re-expression of givens.
CC-MPC.8 — Supported returnThe consequence is interpreted in the physical question with the bounds and uncertainties its use consumes. Conditional design and observed performance remain distinguishable.
CC-MPC.9 — Useful continuationThe explanation ends with an adequate use, a specific missing contribution or a justified next question. A change returns to its affected contribution and dependents.

A short sufficient calculation can satisfy these questions without separate records for each row. A shared or consequential result retains enough of the derivation, interpretation and evidence for its receiver to inspect the connections.

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

MisuseFailure visible in the worked casesRepair
Substitute the right number into the wrong commandA count of relative motor increments is treated as an absolute wheel-position target.Recover the interface’s counted participant, unit and initial-state use; construct the input it accepts.
Check only the middle calculationThe robot arithmetic is correct while rolling or successful completion remains unsupported for an actual-travel claim.Add the physical and observation contributions consumed by that stronger claim, or return the conditional design.
Treat a sufficient abstraction as complete physical designA gear colouring is taken to establish torque or mechanical compatibility.State the bounded direction consequence and obtain the missing mechanical account when the decision requires it.
Repair the drawing while leaving the arrangement unchangedAn odd-cycle edge is deleted from the contact graph but the gears remain meshed.Change the contact or revise the contact rule with its physical basis, then reconstruct the graph consequence.
Count reservations as occupantsThree cards outside the free pool are reported as three visitors inside during handover.Retain Reserved and Awaiting-return states, or report the resulting occupancy bound.
Preserve local rules while duplicating a shared resourceEach entrance has its own three-card stock and both are used for one room.Use one total stock or a partition of it; transfer existing free cards when balancing entrances.
Traverse every contribution before using a sufficient resultA proof excludes a design, yet simulation and implementation continue as compulsory stages.Return the proved physical obstruction under its assumptions and choose a revised design question.
Ask a contributor for an unexplained answerThe receiver gets a count, proof or program whose needed meaning cannot be recovered.Request the interpretation, decisive argument or operating condition required by the next use.

B.5.MPC:9 - Consequences

The practitioner can assemble a useful answer from contributions obtained at different times and from different people, AI systems or established sources. The resulting explanation identifies how the answer concerns the physical situation and which premise or operation would change it. That makes a partial result useful: a bound can settle a decision, an odd cycle can locate a design obstruction, and an unresolved command meaning can direct one precise request.

The method also changes what work is commissioned. Instead of asking for another undifferentiated simulation or report, a team can ask for the missing physical relation, retained state, constructive algorithm, measurement or realization. An adequate contribution remains available when an unrelated part changes.

This connection work has a cost. Recovering an unfamiliar source, learning notation or obtaining a physical premise can take more effort than calculating the displayed answer. Spend that effort where it changes the receiving use.

B.5.MPC:10 - Architectural Rationale

B.5.MPC:10.1 - Why the connection is a Method

The receiving physical question joins several operations whose local success has different meanings. Derivation establishes what follows within a mathematical account. A physical explanation supports the choice of that account for a phenomenon. A procedure obtains a represented result; its realization connects that procedure to available system behavior. Coordinating these operations requires preserving their result dependencies while selecting a useful next contribution.

The epistemological and methodological contributions meet in the use of a result. Axiomatization can make the objects, premises and permitted constructions explicit. A physical postulate contributes to empirical knowledge through an interpreted model whose consequences can be compared with observations. Computational formulation and realization let agents work through consequences using specified operations on represented inputs.

The practitioner connects these contributions to obtain and apply knowledge, then uses an encountered limitation or a newly available operation to change the method or pose another question. Their detailed constructions give substance to the pragmatic question: which further work becomes possible?

The robot makes the need concrete. Circumference, transmission ratio, integer rounding and signed-command semantics are separately intelligible. The useful command exists only when they refer to compatible motion and counts. A.3.3 can help recover state, C.29 can construct and transfer the mathematical consequence, and C.16 can interpret an observation. Their contributions enter the joint question through the dependencies explained in :4.

B.5 provides the general inquiry method: recover the question, perform the missing contribution, make its result understandable, and settle or revise the inquiry. This specialization adds the recurring connections among physical account, mathematical interpretation, computational formulation and executing arrangement. The relation is specialization of inquiry coordination and composition with the constituent Methods.

An alternative is to use a fixed forward sequence. That is convenient when every input is new and later stages expose no earlier gap. It becomes wasteful when a theorem supplies the answer, and inadequate when command semantics require an earlier state distinction. The dependency method retains a forward traversal but also supports backward recovery, direct entry and returns after changed conditions.

Another alternative is to let each specialist check only their own output. That can be sufficient when all receiving correspondences are established. Where they are unresolved, a correct local output can remain unusable by the next contributor. Give the connection a receiving question and a capable contributor.

B.5.MPC:10.2 - What the sources contribute to the synthesis

Rodin’s Axiomatic Architecture of Scientific Theories develops a constructive account of axiomatization in which object-forming activity matters alongside propositions. That supports asking how the needed object is obtained and which operations its theory permits. In :4.3–4.4, this becomes recovery of a construction. Physical interpretation requires its subject account; the mathematical construction does not establish that a proposed physical interaction occurs. See Rodin, 2020, §§4.2.2–4.2.3.

Fong and Spivak make preservation under composition explicit: a functor preserves identities and composition between categories. The use here is the comparison of corresponding operations, supplied by C.29.1. It explains why relabelling objects alone cannot establish a transfer. A physical approximation may instead need a bound or another qualified relation; the coordinating Method does not require every connection to be a functor. See Seven Sketches in Compositionality, §3.3.2.

Horsman, Stepney, Wagner and Kendon distinguish the representation of a physical system from the preparation and interpretation needed to use a physical process for computation. Their account supports :4.5’s two routes and the distinction between refining an abstract description and realizing it. It also permits input preparation and result reading to differ. The present Method adapts that comparison to a receiving physical question and to useful bounds, rather than adopting their account as a universal definition of all computation. See When Does a Physical System Compute?, 2014, §§VI–VIII.

Turing’s 1936 construction of a universal computing machine provides a historical demonstration that an executor can interpret an encoded description of another machine’s procedure. That helps distinguish the rule description, its interpreter and the realized operation. The finite interpreter in C.29.2:5.1 provides a small entry to that distinction. Use C.29.2 for the computation-specific cost account when a resource limit matters; :4.4 carries that cost and the computation’s meaning into the joint use. See Turing, On Computable Numbers, §6.

These contributions answer different construction questions. The synthesis is to hold their input and result meanings together for a physical use, inspect their joint and alternative dependencies, and let a failed connection determine the next contribution. It preserves mathematical, empirical and realization grounds at the points where they are needed.

B.5.MPC:10.3 - Why notation and understanding remain part of the work

An expression can help a practitioner perform a construction. Macbeth’s account of paper-and-pencil reasoning explains how a diagram or inscription can participate in the reasoning, including by allowing the same content to be analysed in more than one way. Dutilh Novaes examines formal languages as cognitive tools whose use depends on learned abilities to read and manipulate signs.

These accounts support the operative expression step in :4.3. They do not establish that a notation improves every task or that a human learning effect transfers unchanged to AI. See Macbeth, 2011 and Dutilh Novaes, 2012, §§3.2, 5.2 and 6.1.

Naming the count N in several expressions is useful only while its participant and operation remain recoverable. A gear graph helps reason about closed contact paths because its edge meaning and traversal rules are available. The four card states distinguish occupancy from reservation throughout entry and exit, where an undifferentiated “not free” count gives only a bound. These are changes to what the expression helps someone do, not merely choices of appearance.

A second alternative is to make one formal language carry the whole inquiry. This can help when a language expresses the required physical, mathematical and execution distinctions and its users can work with it. If it cannot express a necessary distinction, use another representation or develop the language. Retaining interpretable correspondences allows several forms to contribute without assuming that one form covers the whole problem.

Levenchuk’s 2012 robotics account describes difficulty combining familiar speed calculations, several distance quantities, program expressions and physical timing. It motivates changing the question while retaining the interpreted relations in :4.3, and examining the timing of observation and execution in :4.5. The account is a historical report of a learning situation. The resulting Method here is a methodological synthesis.

AI can reduce the cost of obtaining a calculation, candidate proof or explanation while leaving the choice and interpretation of the receiving question open. Klowden and Tao discuss the difference between a formally checked statement, its intended meaning and the understanding that enables further use. Section :4.8 turns that distinction into a contribution question: who can recover the decisive connection and adapt it when the premise changes? This is a capability to arrange, not an assertion that every participant must reproduce every proof. See Mathematical Methods and Human Thought in the Age of AI, 2026, §4.

B.5.MPC:10.4 - Why a sufficient answer can also open a better question

Deutsch’s discussion of foundational theories treats their connections as sources of criticism across areas, rather than relying on a theory’s foundational status to settle another question. This motivates examining how a claim about computation constrains a physical proposal and how physical knowledge constrains an executing arrangement. The correspondences require their arguments. See Deutsch’s interview on The Beginning of Infinity.

The same connection work can generate a worthwhile next problem. The robot account raises which observations distinguish rolling from slip. The gear witness raises which physically available contact change removes the obstruction. The card bound raises whether redistribution can reduce waiting while preserving the shared stock. Each continuation identifies an additional possible action and a construction or uncertainty that matters to it.

A sufficient answer remains a stopping point when the use is complete. When inquiry development is selected, retain the useful connection and work a consequential change to the question or apparatus. A general invitation to keep exploring supplies less direction than the obstruction or newly available operation.

B.5.MPC:11 - SoTA-Echoing

For the declared coordination question, the selected answer is the combination of physical interpretation, operation-preserving mathematical use, computational formulation and realization comparison. The sources below supply advances and alternatives. The combined Method is a methodological synthesis. The three cases are constructed under their stated conditions.

How should a discrepancy between a physical prediction and an indication be investigated?

Dounas-Frazer and Lewandowski’s 2018 account of experimental modeling distinguishes the model of the physical system from the model of the measuring system and distinguishes changing either model from changing either apparatus. Adopt these separate contributions in :4.2 and the return in :4.6. Compared with fitting one model to raw readings, this exposes whether the observation relation needs repair. Source, §2.

The source develops a framework for experimental-physics modeling; it supplies neither every physical law nor the whole joint Method. Reconsider the selected return when another diagnosis better distinguishes the live causes or when the current physical question needs no measurement.

What makes a mathematical result usable after changing its representation or receiving operation?

Fong and Spivak’s preservation-under-composition account supplies a comparison where category-theoretic structure is applicable. Adapt it through C.29.1 and :4.3 to the equality, bound or behavioral relation needed. Compared with transferring a result because formulas look alike, this exposes a failed operation or a lost distinction. Source, §3.3.2.

Mathematical preservation does not establish the physical account. Use a less elaborate argument when it supplies the same comparison; reconsider the chosen relation when the receiving operation or tolerated loss changes.

What connects a valid computation to an available physical execution?

Horsman and colleagues compare abstract evolution with preparation, physical evolution and interpretation. Adopt and adapt this construction in :4.5. Abstract refinement and a successful software trace remain useful alternatives for their own questions, but leave input range, material exclusivity or physical result reading open when those are the unresolved connection. Source, §§VI–VIII.

This is an account of physical computation, not a universal criterion established for every use. Reconsider the selected realization when its operations or observation rules change; reuse it when the receiving conditions remain supported.

When should notation be changed during the reasoning?

The operative-notation accounts discussed in :10.3, together with Zhang and colleagues’ How Notations Evolve (2026), support relating meaningful distinctions to the expressive and perceptible differences of a notation. Adapt that question in :4.3: construct an expression and try the operation it should support. Compared with assessing the appeal of isolated symbols, this can expose an omitted count meaning or an unusable compound expression. Contemporary study.

The historical analysis supports notation-design questions; it does not demonstrate that these expressions improve human or AI performance. Reconsider the scheme when the intended operation cannot be performed or a meaningful difference cannot be recovered at acceptable effort.

What understanding is needed when proof and calculation can be obtained from AI?

Klowden and Tao’s 2026 discussion separates proof production and formal verification from interpretation and the understanding used to extend an argument. Adapt that distinction in :4.8: obtain the needed contribution and retain capability to recover its receiving connection. Compared with accepting a polished answer or requiring every receiver to reproduce its full derivation, this targets the understanding the next work consumes. Source, §4.

The source combines observations, arguments and forecasts; it establishes no universal allocation of human and AI work. Reconsider the allocation when support, capabilities, required adaptation or consequences change.

The source-supported distinctions remain useful even when their historical origin is older than a current tool. Their selection here depends on the defects and constructive differences in these comparisons. Further disciplinary development can supply better constructions, representations or realization Methods without replacing the need to interpret their joint result.

B.5.MPC:12 - Relations

RelationContribution
Specializes B.5 — Canonical Reasoning CycleRetains question formation, selection of a missing contribution, result understanding and sufficient-result closure; adds the joint physical, mathematical and computational connections and their dependencies.
Uses B.5.4 — Recognize a Concept in a SituationSupplies recognition of an explained concept’s participants and relations when the physical situation has not yet been interpreted through it.
Uses C.29 — Mathematical Lens UseConstructs the mathematical account and returns its consequence to the question.
Uses C.29.1 — Mathematical Result TransferConstructs the correspondence and tests the operations and distinctions needed to carry a result between mathematical accounts.
Uses C.29.2 — Computational FormulationConstructs the computational state, operations and obtaining procedure, with the result argument and resource account that its use needs.
Uses C.29.3 — Computational RealizationCompares input preparation, system operation and readout with the required result, and returns a failed connection to its repair.
Uses A.3.3 — U.DynamicsSupports the construction of configurations, retained state and allowed continuations when the receiving prediction or operation requires them. It uses the supplied subject laws and interaction rules.
Uses C.16 — Measurement and Metrics CharacterizationConstructs and interprets the measurement relation connecting the sought quantity, apparatus influences and indication. This contribution is needed when the joint consequence consumes an observation.
Uses A.6.3.RT — Representation TransitionConstructs an operative expression under the conventions of the chosen representation and compares its content and use with the source. The applicable subject Method supplies any new conclusion obtained with that expression.
Uses A.6.1 for realization semanticsKeeps a declared operation, its realization relation and the performance of a Method distinguishable when those claims matter to the executing arrangement.
Uses A.15.9 for a needed contribution from another practiceHelps obtain the result, explanation or formulation that the next operation needs, with its receiving use made explicit.
Coordinates with C.39 and C.40Searches for a missing way and develops the problem or Method repertoire when the existing connections expose a worthwhile construction question.
Uses C.11.DUA for a decision about further effortCompares whether additional calculation, observation, explanation or checking can change the receiving action enough to justify its cost.
Uses B.3 and B.3.3 for stronger assurance questionsQualifies evidence and assurance for the claim and use when a conditional consequence or ordinary construction no longer suffices.

B.5.MPC:End

B.5.MPC.R - Repair a Physical-Mathematical-Computational Connection

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

B.5.MPC.R:1 - Problem frame

Use this pattern when a physical question has an attempted answer, but the physical account, mathematical reasoning, computation or observed execution no longer fit together. A requested result may have changed, a command may produce an unexpected motion, or an observation may fail to distinguish the physical possibilities that the answer assumes.

First useful move: state the difference that matters and compare the two contributions at the point where their meanings or results disagree. For a delayed robot stop, compare the duration used in the distance calculation with the duration for which the motor remained active.

The result is a repaired connection and its consequence for the physical question, or a located incompatibility that directs the next contribution. The method specializes B.5’s reasoning revision for the joint work described by B.5.MPC. B.5.RR supplies the general treatment of affected reasoning, shared prerequisites and sufficient alternatives.

The practitioner needs the subject knowledge required to interpret the contributions, or access to that help. Use a known adequate correction when its conditions fit. Use B.5.MPC when the joint account has yet to be constructed. A fault located within one discipline can proceed through that discipline’s diagnostic or repair method.

B.5.MPC.R:2 - Problem

Local success can survive a failed joint answer. Algebra can produce a command beyond the device’s range. A frequency calculation can correctly analyze samples while those samples are compatible with several physical frequencies. A voltage measurement can be accurate for the connected circuit while the question concerns the circuit before the meter was connected.

Trying harder within the successful contribution can leave the failure unchanged. More arithmetic precision does not make an unavailable command executable. More samples taken under the ambiguous sampling relation may preserve the ambiguity.

The difficulty is to locate which connection fails and change the contribution that can repair it. Several accounts may explain the same discrepancy, so an observed disagreement must not be assigned to a component before the available reasoning distinguishes those possibilities.

B.5.MPC.R:3 - Forces

ForceTension
Local correctness and joint usefulnessA valid result can answer a question different from the receiving physical question.
Stable relations and changed unknownsThe physical relation can serve several questions, but each may require a different computation.
Observation and interventionObtaining an indication can change the state or conditions whose behavior is being inferred.
Economical repair and unresolved alternativesA short correction can suffice; an ambiguous discrepancy may need a discriminating observation or a conditional result.
Abstraction and realizable operationMathematical possibilities can exceed the preparation, timing or range of the available apparatus.

B.5.MPC.R:4 - Solution

Keep the receiving physical question in view while tracing the failed connection:

State the changed result or disagreement → recover the contributing relations → locate the incompatible use → construct a sufficient repair → carry it through the affected contributions → use the revised physical consequence.

These are dependencies of the repair. A known physical change, a failed calculation or an observation can each be the starting point.

B.5.MPC.R:4.1 - Compare results for the same physical question

Name the physical difference that the answer must resolve and the conditions under which it is wanted. Put the attempted result beside the changed request or observation. Recover the participants, units, times and operating regime needed to compare them.

For instance, a predicted displacement during eight seconds of motor operation and a measured displacement during eleven seconds concern different durations. Aligning the comparison may explain the discrepancy.

If the question changed, say which quantities are supplied and which must be determined. Keep the physical relation available while choosing its new use. A velocity-to-duration calculation can become a duration-to-command calculation.

If the comparison concerns a performance claim, recover the observation and its measurement relation. An acknowledgement can supply information about command reception while leaving physical completion unobserved.

B.5.MPC.R:4.2 - Recover what each contribution supplies to the next

Start at the mismatch and follow the needed relations in both directions. Ask what the receiving operation takes as input, what the supplied result represents and which condition permits that use.

The following questions distinguish common repair locations. Use the ones that can explain the disagreement.

Connection to inspectQuestion that can locate a repair
Physical account to mathematical formulationWhich interaction, boundary or operating assumption licenses this equation or constraint?
Mathematical formulation to computationDoes the procedure obtain the quantity or property requested, with the required constraints and approximation?
Representation to another representationWhich distinction or operation must survive, and does the correspondence preserve it?
Computation to executing arrangementCan the arrangement prepare the input, perform the operation and finish with the state or result being used?
Observation to physical inferenceWhich physical possibilities can produce this indication under this measurement procedure?

Explain an unresolved connection in the notation. Use B.5.RA to recover a needed argument and B.5.RC to recover a construction. C.29.1 compares mathematical transfers; C.29.2 constructs a computation; C.29.3 compares a computation with its realization. Their results answer the corresponding rows, while the physical question determines which row matters.

Keep a common premise visible across different contributions. An analytical calculation and a simulation that both assume no slip leave the same question open when slipping is suspected. A different algorithm is a sufficient alternative only if its premises and output interpretation fit the receiving use.

B.5.MPC.R:4.3 - Locate the incompatibility without guessing its cause

Work a small instance or derive a consequence that distinguishes the competing accounts. If a command is outside the admitted range, its value and range establish that incompatibility. If two physical inputs produce the same represented data but require different answers, exhibit those two inputs and their common representation.

When several explanations remain, compare what each would require you to change. A motion discrepancy might come from calibration, a retained command or an incorrectly interpreted position. Recover an available observation that distinguishes those accounts, or choose a worthwhile further observation through C.11.DUA. An investigation is unnecessary when a sufficient bound or conditional answer settles the decision.

Account for what the observation does. Identify which processes continue during measurement or debugging, which input remains applied and which state is changed by the probe. Use A.3.3 for the state and C.16 for the measurement relation when that construction is unresolved.

A mathematical account may support several physical interpretations. Compare their additional physical assumptions and the observations or interventions that distinguish them. Retain an unresolved difference when the available observations do not decide it; use the consequences shared by those interpretations when they suffice.

B.5.MPC.R:4.4 - Construct the repair that the receiving use needs

Choose the contribution by the result the recipient needs. To explain a particular failure, seek what distinguishes its possible causes on that occasion. To restore a required behavior, a change shown to work across the remaining causes can suffice while their identity stays open. When a repair is to serve future operations, derive its required range from their permitted inputs, timings and uses. A successful rerun of the original case covers that range only with grounds for the other permitted conditions.

  • If the requested unknown changed, retain the interpreted relations, release the former fixed value where appropriate and derive the new computational direction.
  • If a representation merged cases that the question must distinguish, retain the missing information, obtain a different observation or use a result that the merged representation supports.
  • If the procedure uses the wrong operation, constraint or approximation, replace that part and establish the property the receiving use needs.
  • If the physical or measurement account omits a consequential interaction, model that interaction or change the arrangement so that the retained account applies.
  • If execution differs in preparation, range, state or completion, revise that part of the realization or choose an available realization that supplies the required behavior.

An expression of an equation states a relation; an assignment or solver performs a chosen operation. Keep the equation’s meanings when generating or editing that operation. A modelling environment can help transform the equation system, but the physical interpretation and the requested result guide the choice.

Compare the repair with a sufficient alternative. Changing a deadline may be cheaper than replacing an actuator. An ambiguity result may suffice before changing measurement equipment. Present a changed requirement as a choice for the receiving work.

B.5.MPC.R:4.5 - Carry the repair through its dependents

Use B.5.RR to derive the affected consequences. Reuse contributions whose conditions and meanings fit; revise each needed use of a changed shared premise.

Compare the repaired contributions on the input or physical case. For a mathematical change, derive the needed property. For numerical work, carry the error relevant to the physical question. For an execution claim, compare the prepared state, operation and interpreted observation with the intended result.

Keep the comparison at the claim’s scope. A conditional calculation can establish what a proposed arrangement would do under its assumptions. Actual performance requires the observations and inference appropriate to that use.

If the comparison fails, follow the remaining disagreement. Seek information that can distinguish the alternatives that change the answer. If the means available cannot settle the commissioned question, return the supported result and the remaining gap. A proposed change of question then carries that information to whoever can choose the continuation.

B.5.MPC.R:4.6 - Return the physical consequence and the next useful action

State what can be understood, constructed or changed. Return a usable command, corrected interpretation, realizability bound or a remaining ambiguity with its effect on the receiving decision.

When work is divided, give the next contributor the quantities and conditions at the unresolved connection, the result needed and how it will be used. The receiver must be able to reconnect the supplied contribution to the physical question. A.15.9 helps obtain that contribution.

The repaired reasoning may reveal another worthwhile problem: extending an operating regime, constructing a more informative measurement or developing an operation for a changed class of questions. Carry that possibility into B.5’s next inquiry when pursuing it would enable further work.

B.5.MPC.R:5 - Archetypal Grounding

These are constructed cases under stated models. They demonstrate different repair locations and the contributions that follow from them.

B.5.MPC.R:5.1 - A robot receives a new deadline, then keeps moving during a pause

A robot must travel d=1 m along a straight guide. In the stipulated regime, constant speed obeys v=k*u, where u is a dimensionless command and k=0.2 m/s. The model initially idealizes starting and stopping as immediate. The available command range is 0<u<=0.8.

With u=0.5, the relation d=v*T gives T=d/(k*u)=10 s. The question then changes: find the command for T=5 s. Keep the relations but choose u as the unknown:

u=d/(k*T)=1/(0.2*5)=1.

The algebra supplies a value outside the available range. The corresponding lower bound on duration is T>=1/(0.2*0.8)=6.25 s. This answers the feasibility question before another controller is written. Changing the deadline or the available motion capability is a choice.

Suppose the requester chooses T=8 s. The required command is u=0.625, giving v=0.125 m/s. A controller applies that command, counts eight seconds of active program execution and then issues stop.

During a diagnostic run, a debugger freezes the program and its timer for three seconds. In this example the output retains u=0.625 and the motor continues to run. The stop is therefore issued after eleven seconds of physical operation, giving d=0.125*11=1.375 m under the model.

The disagreement concerns execution timing. The equation and chosen command remain appropriate to eight seconds of motion. For a prediction about uninterrupted operation, use the eight seconds of motion under the stipulated model. For a claim about an actual uninterrupted run, establish its timing and displacement from evidence about that run. If such pauses can occur in the required operation, provide a stopping mechanism whose elapsed-time behavior survives the pause, or revise the control arrangement accordingly. Test its physical completion at the condition the use needs.

For example, suppose an independent timer can remove the motor command and continues to run while the controller is paused. Start it with the command and set it to remove the command after eight physical seconds. Under the example’s immediate-start/stop model, motion then lasts eight seconds and covers 0.125*8=1 m, including a run with the three-second program pause.

Compare the timer’s actual behavior with those conditions before relying on that performance. If no such mechanism is available, the next contribution is a way to stop motion with that timing or a revised operating requirement.

A stopping delay or speed transient would be another changed premise. Incorporate it when predicting final displacement; acknowledging stop does not measure that displacement. The example’s next useful result is a duration bound or a repaired timing design with an identified performance question.

B.5.MPC.R:5.2 - A correct spectrum calculation answers an ambiguous physical question

A measurement uses uniformly spaced samples at f_s=100 samples/s. The earlier physical account admits a single sinusoidal signal with frequency below 50 Hz. A spectrum calculation returns a 10 Hz component, interpreted under that restriction.

The apparatus is changed and the admitted frequency range becomes 0 to 120 Hz. The same interpretation is in question. For ideal samples of a unit-amplitude cosine at times n/100 seconds:

cos(2π*90*n/100)=cos(2π*10*n/100)

for every integer n. This follows because 90/100=1−10/100 and cosine is periodic and even. A 110 Hz cosine gives the same samples as well.

Consequently, the sampled sequence fits physical frequencies 10, 90 and 110 Hz in the new range. The spectrum calculation can remain correct for its input. Increasing its arithmetic precision or collecting more samples at the same times leaves this ambiguity.

To determine which frequency is present, change a contribution that distinguishes those cases. For the stipulated single-tone model, sampling at 300 samples/s places the whole admitted range below half the sampling rate. A three-second record of a 90 Hz signal then contains 270 cycles; the spectrum can return 90 Hz under the stated ideal timing and signal assumptions.

For a physical measurement, obtain the needed sampling and input-conditioning behavior from the instrument account. Frequencies outside the admitted band, timing error and an unsuitable analog input path can reopen the interpretation. A filter that removes the signal of interest changes the measurement question rather than recovering its frequency.

The new record identifies the frequency during its own acquisition. To use it for the earlier signal, establish that the source kept the same frequency or recover independent information about the earlier interval. For the ideal unit cosine above, the original sample at n=1 requires cos(2πf/100) = cos(2π·10/100). Thus f = 100k ± 10 Hz for an integer k. In the admitted range only 10, 90 and 110 Hz remain. All exceed 5 Hz, so the old record already settles that threshold for its own interval. They straddle 50 Hz, leaving that threshold and the exact original frequency open.

B.5.MPC.R:5.3 - The voltmeter changes the circuit being inferred

An ideal 10 V source drives two 1 MΩ resistors in series. The wanted quantity is the midpoint voltage before a meter is connected. The divider relation gives 5 V.

A voltmeter with 1 MΩ input resistance is connected between the midpoint and the lower terminal. In the connected circuit it lies in parallel with the lower resistor, whose combined resistance becomes 0.5 MΩ. The divider construction gives:

V_mid=10*0.5/(1+0.5)=10/3 V.

The indicated value can agree with the connected-circuit model. Comparing it directly with the unloaded prediction had omitted the meter’s interaction.

One repair is inferential: with these resistor, source and meter models, recover the unloaded value from the model, keeping its conditional status. Another is experimental: choose a measurement arrangement whose loading is small enough for the wanted use and account for its remaining effect. Repeating the same connection alone preserves the load.

The result tells the practitioner which voltage was observed and how the wanted voltage can be obtained. A different observed value may require revisiting the assumed source, resistor or instrument behavior through their subject methods.

B.5.MPC.R:5.4 - A motion command changes its unit and starting point

In C.29.3’s robot case, the effective wheel radius is 0.05 m, ten motor revolutions turn the wheel once, and the interface counts 1,000 increments per motor revolution. A two-metre displacement requires a total of 63,662 motor increments after rounding. C.29.3 handles sending that total through the available command field.

Now change the radius to 0.06 m and the interface to an absolute wheel-position target. It counts 1,000 units per wheel revolution, reads 3,000 and admits targets from 0 to 65,535. The requested forward displacement remains 2 m. Assume rolling without slip and completion at the commanded count.

Recover the count’s new meaning before reusing the calculation. If q is the target, the wheel travels (q−3,000)/1,000 revolutions, so the model gives:

d=(q−3,000)/1,000 * 2π * 0.06 m.

The new scale counts wheel revolutions; use that scale to obtain the needed increment:

Δq=2/(2π*0.06) * 1,000 ≈ 5,305.16477.

Round to 5,305 and add the initial count, giving target q=8,305. This target is admitted. Its modeled displacement is approximately 1.99993788 m. Nearest-integer rounding contributes at most half a count, corresponding to π*0.06/1,000 m ≈ 0.00018850 m; compare that contribution with the receiving accuracy requirement.

Reusing the former total 63,662 as the absolute target would pass the new range check but give approximately 22.8690 m under this model. The value has changed from a relative motor increment to an absolute wheel position. The repair therefore changes the physical parameter, the count-to-motion correspondence and the computational use of initial state together.

The return is the new command with its displacement and rounding consequence. A changed starting count requires recomputing the target; a changed radius or count scale reopens their correspondence. A slip or incomplete motion requires the relevant physical or execution repair. C.29.3’s preparation and completion comparison can then use this revised command.

B.5.MPC.R:6 - Bias-Annotation

The cases use elementary models so the connection can be worked. Nonlinear dynamics, statistical observations or coupled physical computations can require more demanding subject contributions. Preserve their interaction and uncertainty conditions when applying the same repair method.

A visible software failure can attract attention even when the computation is correct and its physical interpretation is wrong. Compare the meaning of the input and output before choosing a programming repair.

B.5.MPC.R:7 - Conformance Checklist

  • The attempted and wanted results concern a stated physical question and comparable conditions.
  • The contribution supplied at the disagreement has an interpretable meaning and receiving operation.
  • The repair distinguishes a located incompatibility from an unresolved diagnosis.
  • Shared premises remain visible across calculations, simulations and observations.
  • The repair changes the responsible relation, procedure, realization or requested result.
  • Its dependent consequences are reworked and returned at the supported scope.
  • The receiver can perform the next action or identify the contribution needed.

B.5.MPC.R:8 - Common Anti-Patterns and How to Avoid Them

FailureConsequenceRepair
Solve for the former unknownA correct formula answers the old question.Retain the relation and select the givens and unknowns again.
Refine the computation of ambiguous dataThe physical alternatives remain indistinguishable.Change acquisition or return the supported ambiguity.
Treat debugger time as physical timeA retained actuator command can continue to act during the pause.Recover the timer and actuator behavior.
Treat a probe as passive despite its couplingThe observed system differs from the modelled unobserved arrangement.Include the probe interaction or change the measurement.
Switch algorithms while retaining the disputed physical premiseThe alternative preserves the same failure.Compare its complete application conditions.

B.5.MPC.R:9 - Consequences

The method makes a failed joint answer useful: the disagreement can reveal a range limit, a lost distinction, an omitted interaction or a missing construction. It also supports division of work by the contribution needed at the failed connection.

The cost is reconstruction across disciplinary boundaries. A sufficient conditional result or a known correction can keep that effort small. Where several causes remain compatible with the evidence, the result can remain a bounded diagnostic question.

B.5.MPC.R:10 - Architectural Rationale

The common revision method B.5.RR follows affected reasoning. This specialization adds the recurring correspondences that a physical application consumes: a physical account expressed mathematically, an interpreted computation and a realized or measured operation. It lets the practitioner choose the repair that can change the physical answer.

Working from the disagreement can settle the question with a bound or identify the observation that must change.

The physical and mathematical accounts need each other without becoming the same account. A mathematical equality can expose why two frequencies have identical samples. The physical sampling arrangement determines whether those are the relevant possible inputs. Computational analysis then operates on the resulting data. The knowledge comes from keeping those relations together; applying it can change the measurement method.

B.5.MPC.R:11 - SoTA-Echoing

How can an expression help locate a failed connection? Adapt Sussman and Wisdom’s Structure and Interpretation of Classical Mechanics, second-edition preface (2015): expressing mathematics as executable procedures exposes operations that informal notation can leave implicit. Sections 4.2 and 4.4 use that feedback where available.

Compared with polishing a symbolic answer alone, it can locate an unusable operation; its extra formalization is worthwhile only for the receiving question.

What survives a changed computational direction? Adapt the separation of equation models and generated computations in ModelingToolkit’s version-10 documentation, alongside Ma et al.’s 2021 account. Section 4.4 retains relations while changing givens, unknowns or the obtaining procedure. This supports acausal modelling rather than making one assignment direction part of a physical law.

An adequate explicit formula remains cheaper for the robot’s small calculation; no modelling platform is required.

When must observation be treated as an operation? Adapt Khrennikov’s Contextual Measurement Model (2024), §§2.1–2.2: the measurement procedure can change the context used by subsequent inferences. Section 4.3 therefore recovers that operation when it matters. The passive-observation account remains useful where its approximation is adequate. The voltmeter case supplies an elementary circuit construction of an interacting probe; broader physical interpretations need their own assumptions and observable consequences.

Which sampling repair changes the physical inference? Use NI’s sampling and aliasing account, “Sample Rate” and “Aliasing” for the acquisition constraint and input conditioning. Section 5.2 derives its alias equality and states f_s and the admitted signal band. Compared with increasing numerical precision, changing acquisition can distinguish the physical cases. The instrument’s bandwidth, filtering and timing remain part of that repair.

Reconsider the chosen repair when a physical theory, representation, computational method or executing technology supplies a better way to resolve the same disagreement. Compare the operation, consequence and conditions that let the receiving work use it.

B.5.MPC.R:12 - Relations

  • B.5.MPC constructs the joint physical, mathematical and computational answer; this method repairs an attempted connection.
  • B.5.RR revises affected reasoning. B.5.RA and B.5.RC recover an argument or construction needed for that revision.
  • C.29.1, C.29.2 and C.29.3 supply mathematical transfer, computational formulation and realization.
  • A.3.3 constructs the relevant state and continuation account. C.16 constructs and qualifies the measurement relation.
  • A.6.3.RT helps express the changed relation or operation. A.15.9 helps obtain another practice’s contribution.
  • C.11.DUA compares further effort with its effect on the receiving decision. B.3 and B.3.3 supply claim-specific assurance when required.

B.5.MPC.R:End

B.5.RC - Recover a Construction from Its Description

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

B.5.RC:1 - Problem frame

Use this pattern when a description points to a result you need, but you cannot recover how to obtain it from what is available. You may be reading a mathematical construction, an assembly method or a way to transform data. The difficulty is in the connection between starting material, allowed operations and the required result.

Here, a construction is a way of obtaining an object by applying operations to given objects. In a mathematical construction, those operations form mathematical objects. In an assembly method, they may produce a design or a physical assembly; identify which result the description promises. The relevant practice supplies the operations and their application conditions.

First useful move. Name the result needed for the next use. Find an operation that could produce it and follow its prerequisites back to available starting material. Work forward on the actual inputs or on a smaller case that preserves the missing connection.

This method needs access to the description and enough subject knowledge to interpret its objects and rules. Use an adequate known construction. If the task is to invent a method where no usable account is available, use C.39 for that development; a missing operation discovered here can become its input.

B.5.RC:2 - Problem

A reader can recognize the name of a result and repeat its desired properties while remaining unable to construct it. The source may compress several operations into one verb, leave a prerequisite implicit or describe a property without giving a procedure that produces an instance.

Execution then fails at the first unprovided intermediate result. Guessing a plausible step can make the example work while changing the method being recovered. Repeating the requirement leaves the difficulty in place.

The result is a recovered construction that can be performed for the intended case, or a localized missing contribution that makes the next source return, specialist request or method-development move possible.

B.5.RC:3 - Forces

ForceTension
Required result and available meansWorking backward keeps the desired result in view; working forward reveals what the available operations can produce.
Source fidelity and useful inventionFilling a gap may solve the task, but the added operation then needs its own justification and must remain distinguishable from what the source supplied.
Properties and ways of obtaining an objectA property can guide construction or follow from it. The next use determines whether an existence result suffices or an instance must be obtained.
Shared prerequisites and execution orderSeveral steps may use the same object, and one step may need several results together. A list can hide either relation.
Small case and reusable methodA small case exposes missing operations cheaply; broader use depends on which conditions and operations survive the change of case.

B.5.RC:4 - Solution

Recover the construction in two connected directions: from the required result toward its prerequisites, then from the available inputs toward a result. Keep the needed property in view throughout. The following actions form an order; return to an earlier action when a missing condition changes the construction.

B.5.RC:4.1 - Fix the result and starting situation

Say what the next user needs to obtain and what they will do with it. Recover the conditions that distinguish a usable result: for example, a triangle on a supplied side, a display design that uses the supplied fittings, or data in the format required by a calculation.

Identify what the task supplies and what it leaves you to construct. For an exact reproduction, recover which objects, operations or resulting features must be the same. When an equivalent result is allowed, work back from the property its recipient needs. For a display stand, two panels that fit the same upright may put different loads on its base. Follow that difference as far as it affects the requested design. If proving existence settles the question, the proof can finish the work. If a particular object is due, locate the operation that can produce it.

Use the actual input when it exposes the missing operation. A smaller case is useful when it retains the troublesome dependency and makes the operation easier to recover.

B.5.RC:4.2 - Recover the operations

Read the description for ways of forming, transforming or combining the objects. For each operation needed by the case, recover:

  • what it takes as input;
  • the conditions under which it can be used;
  • what it produces.

This information can appear in a definition, diagram, earlier construction or convention used by the source. A verb such as “combine” is enough only when its operation is recoverable. Otherwise ask which parts are combined and how.

In a mathematical account, include the formation and equality rules that the construction uses. A rule for forming an object and a claim about its properties do different work: the first supplies an object for a later operation, while the second may justify applying that operation. Both can be needed.

Use the rules of the account being recovered. For a physical assembly, a joining operation may require compatible fittings and available components. For a mathematical expression, using one value at two places depends on the rules of that expression. Recover the relevant condition where the construction relies on it.

B.5.RC:4.3 - Follow prerequisites backward

Start with an operation that produces the required result. Ask what must be available just before it can be applied. Repeat for any prerequisite not supplied.

Keep joint prerequisites together: drawing a segment between two points requires both points. Keep alternative constructions separate: either one complete construction or another may produce an acceptable result. Where several later steps use an intermediate object, retain that shared dependency instead of creating several unrelated objects.

Stop tracing a branch when it reaches an available input or an understood subconstruction whose starting inputs are available. The resulting dependency structure may have shared parts and alternatives. Draw it when that helps retain them; the structure does not have to be expressed as a graph.

If tracing returns to a result that it requires, examine the source. It may describe an iterative construction with a starting value and stopping rule, a simultaneous problem with a separate solving method, or an omitted prerequisite. Recover that method or prerequisite before treating the circular description as executable steps.

A missing operation gives a focused question: “How is this intermediate object obtained under these conditions?” Return to the relevant source passage or specialist with that question. When you propose an operation yourself, treat it as a contribution to the construction and establish the conditions for using it.

B.5.RC:4.4 - Carry the construction forward from its inputs

Begin with the available inputs. Apply an operation when its prerequisites and conditions hold, retaining the output needed by later operations. At an unfamiliar transition, write, draw or perform enough of it to see what changes.

If the construction uses a notation you can read but cannot operate with, use A.6.3.RT to prepare a usable expression under its rules. If interpreting the notation remains the difficulty, obtain that missing preparation. A more legible expression helps only when it preserves the relation required by the operation.

Where an operation admits several outputs, select one that permits the intended continuation. If the source only guarantees that some suitable object exists, determine whether its account also provides a way to obtain the instance your next use needs.

Retain the difference between the construction being described and the trial. One successful trial can reveal the method and expose a gap. A claim about a whole class of inputs additionally needs the argument or other subject support appropriate to that claim.

B.5.RC:4.5 - Establish the property and continue

Recover why the constructed object has the property the next use requires. An auxiliary construction can make the argument possible; an established property can permit the next construction step. Use B.5.RA when the argument is present but its reasoning remains unclear.

The stopping point can be:

  • the required object and a sufficient account of the property being used;
  • an answer about existence or impossibility, with the grounds that establish it, when that was the question;
  • a conditional construction whose unresolved condition matters to the next decision;
  • an identified missing input or operation, with enough context to obtain it.

Select the support needed for that next use under C.11.DUA and the relevant subject method. A design calculation, mathematical proof and trial assembly answer different questions. If an existing result supplies the needed support, use it.

An explanation to a collaborator should let them continue from the recovered result or address the localized gap. Use the drawing, expression or conversation when it carries that information.

B.5.RC:5 - Archetypal Grounding

B.5.RC:5.1 - Recovering an equilateral-triangle construction

A reader has two distinct points A and B in the Euclidean plane and needs an equilateral triangle on side AB. The description says to draw two circles, each centred at an endpoint and passing through the other endpoint, and use an intersection as the third vertex.

The reader recovers three operations: draw a circle with the given centre and radius; select a common point of the two circles; join two given points by a segment. The third vertex requires both circles. The final triangle requires that vertex together with A and B. The two circles share the segment length AB as radius.

For a small case, place A at (0,0) and B at (2,0). The circles have equations x²+y²=4 and (x−2)²+y²=4. Subtracting gives x=1, and substitution gives y²=3. Thus the two common points are (1,√3) and (1,−√3). Selecting C=(1,√3) supplies the vertex above AB. Joining A to C and B to C completes the construction.

The property follows from how C was obtained: AC and BC are radii of circles of radius AB, so AC=BC=AB. The coordinate calculation also supplies the intersection in the Euclidean-plane account used for this case. A description formulated under a different set of construction rules must obtain that intersection under those rules.

To see why the same two-circle construction works for any two distinct endpoints in the Euclidean plane, use their midpoint as origin and AB as the horizontal axis. For a side of length d, the circle equations give a horizontal coordinate of zero and a vertical coordinate of either √3 d/2 or −√3 d/2. Both points are at distance d from each endpoint. Either point answers an order for one triangle. An order for every possible third vertex needs both, and the circle equations give only those two. Coincident endpoints cannot be the side of a nondegenerate triangle.

The Euclidean account supplies the circle and segment operations and their justification.

B.5.RC:5.2 - Recovering a display-stand assembly design

A team receives a drawing of a display stand and a base, upright and panel. The organizer wants a stand made to the drawing and asks whether its complete packed kit meets a 10 kg carrying limit. The drawing shows how to join the upright to the base and attach the panel to the mounted upright. Each operation requires matching fittings.

Work back from the mounted panel. It requires a compatible panel and an upright already connected to the base. Work forward on the supplied parts. The base and upright fit, but the supplied panel has a different fitting. That prevents assembly with this set. If the drawing specifies a particular panel, obtain the matching specified part. If the organizer permits alternatives, a compatible panel or an adapter may also be considered. An adapter adds a part and a joint. Check each changed connection and any load requirement it affects under the proposed arrangement.

Suppose the specified panel arrives and its fittings match. The team can now give the assembly sequence. For the carrying decision, identify everything that must travel together. Suppose the verified upper bounds for the base, upright, replacement panel, fittings and case sum to 9.5 kg and cover the complete kit. This establishes the mass requirement before packing, even if the exact packed mass is unknown. A request confined to how the parts connect can end with the sequence. Delivery of an assembled stand still requires someone to assemble and deliver it.

B.5.RC:6 - Bias-Annotation

A fluent description can hide an unfamiliar operation behind a familiar verb. Keep attention on what the operation takes, permits and produces. Conversely, a formal description can make an existence claim look like an executable recipe; use the next task to decide whether a witness or construction procedure is needed.

Examples can also narrow the apparent method. The circles in :5.1 and fittings in :5.2 supply different subject operations. The common move is recovering and using their prerequisites, including the property needed for continuation.

B.5.RC:7 - Conformance Checklist

For the construction being recovered:

  1. The requested object, property or reproduction determines what may vary and whether to work directly on the original or through a smaller case.
  2. Starting objects are distinguished from the intermediate objects to be produced.
  3. Each operation needed by the case has recoverable inputs, application conditions and output.
  4. Joint prerequisites, shared objects and alternative constructions retain their different effects.
  5. The forward construction reaches a useful result or locates the input or operation that prevents it.
  6. The property claimed of that result has the support its use requires; a broader claim retains its broader support question.
  7. An invented addition is identifiable as an addition, and the next collaborator can use the result or act on the gap.

Apply these questions to the work done. Write a separate account only when its recipient needs one.

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

Failure in the situationRepair
Repeating “construct an object with property P” when the obtaining operation is missingRecover the last producing operation and trace its prerequisites to available inputs.
Flattening a construction into a list that loses a shared object or a joint conditionPreserve those dependencies and perform each operation only when its inputs are available together.
Filling an omitted operation with a plausible guess and attributing it to the sourceName the addition and establish how it works, or return to the source for the missing operation.
Treating a successful small case as a result for all inputsRecover which conditions carry the general argument and which belong only to the trial.
Continuing source reconstruction after the intended use is possibleUse the recovered construction; reopen only for a further question that requires more.

B.5.RC:9 - Consequences

The practitioner can turn a compressed account into an obtainable result and a division of further work. A specialist request can name the missing operation and its inputs rather than ask for a second explanation of the entire source.

Recovery may expose a gap in the source or in the reader’s preparation. It also costs more than directly using an understood construction. The stopping rule preserves that cheaper route and allows a useful conditional result.

B.5.RC:10 - Architectural Rationale

Backward recovery and forward construction answer complementary questions. The backward direction reveals what the desired result requires. The forward direction tests whether the available inputs and operations can supply it. Either direction alone can leave a gap: a plausible plan may lack an executable step, while available operations may produce objects irrelevant to the question.

The method follows the construction’s dependency structure. One intermediate object can support several later steps, and several objects can be required jointly. Preserving these relations makes the construction intelligible and helps divide its execution among performers. The receiving operation determines what a collaborator needs to supply.

Construction and reasoning about properties remain connected. In the triangle case, the construction creates a common point and the circle properties establish equal sides. In the stand case, fitting conditions permit assembly, while load and carrying requirements can lead to design revision. This relation warrants cooperating methods for construction recovery and argument recovery.

B.5 coordinates these contributions within inquiry. C.39 develops a missing method, C.29.2 develops a computational formulation, and A.6.3.RT prepares an operative expression. Their results can supply a missing step here.

B.5.RC:11 - SoTA-Echoing

Constructive and propositional accounts. Rodin’s One Mathematic(s) or Many? Foundations of Mathematics in Today’s Mathematical Practice, especially its discussion of Euclid’s operations and problems, treats object-forming procedures and reasoning about their properties as connected contributions to mathematical practice. This pattern adopts that connection in :4.2–:4.5. It leaves the choice of mathematical foundations to the account being used. A propositional existence result remains sufficient when that is the required result; obtaining an instance calls for the corresponding construction.

Problem reduction. Rodin’s Kolmogorov’s Calculus of Problems and Its Legacy, in the 2023 author manuscript’s discussion of reductions among problems, supplies an earlier account of solving one problem through solutions to others. The present method uses that idea for prerequisite recovery, including joint and alternative contributions. It does not require the reader to adopt intuitionistic logic for every subject.

Bounded method choice. For a compressed construction whose result is needed, compare a linear paraphrase of the source with backward prerequisite recovery followed by a small forward construction. The triangle case requires two circles together; the stand case exposes the unmatched fitting before a complete display exists. The second method is selected because it makes those dependencies actionable. If the source provides an executable construction understood by the reader, direct use is cheaper.

The recovered procedure and the stand example are the present synthesis. Reconsider the backward-then-forward approach when, for the same unfamiliar construction and reader preparation, another recovery method supplies the missing operation more reliably at comparable effort.

B.5.RC:12 - Relations

  • B.5: selects construction recovery as one contribution to inquiry and connects its result with further reasoning.
  • B.5.RA: recovers the argument for a property that construction or later use needs.
  • B.5.MPC: uses recovered constructions while connecting physical, mathematical and computational reasoning.
  • A.6.3.RT: helps change the representation when the inspector needs another operation on the recovered construction. A.6.3.RT.OE supports making an expression under an available notation.
  • C.29.1 and C.29.2: supply mathematical result transfer and computational formulation when those are the missing constructions.
  • C.39: develops a missing way of working from the localized problem.
  • C.11.DUA: selects the additional checking or information worth obtaining for the intended use.

B.5.RC:End

B.5.RA - Recover an Argument for Use

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

B.5.RA:1 - Problem frame

Use this pattern when you have an argument or a reported result but cannot understand why it supports the conclusion you want to use. Ordinary prose or dialogue may leave the argument uncertain: which claims are being made, which reasons work together and what the speaker is trying to establish. You may need to apply the result, criticize it, explain its decisive step or decide which part survives a proposed change.

The argument is the reasoning that connects premises to a conclusion. It may use a mathematical construction, a calculation or a subject inference from observations. The relevant practice supplies the permitted inference and the grounds for its premises.

First useful move: state what you want to do with the conclusion, then recover the main reason offered for it. Follow the needed intermediate claims until you can explain the decisive transition and its conditions.

The reader needs the subject preparation assumed by the source, or access to the missing explanation. Use an adequately understood result when its conditions fit the task. A request to understand the argument can stop before re-proving every established result it uses. A separate obligation to validate the entire proof or underlying observations selects the corresponding checking work.

B.5.RA:2 - Problem

An argument can be present without being usable by its reader. A reader may recognize each term yet miss why a lemma was introduced, where two premises must be used together, or how a local calculation establishes the general conclusion.

Reading each sentence fluently or checking isolated inferences leaves the overall method uncertain. Reading only the overview can hide a decisive unsupported transition. Either failure prevents useful transfer: the practitioner cannot tell what to use, which condition matters or where to ask for help.

The result is enough recovered reasoning to perform the intended use, or a localized gap whose resolution would make that use possible. This may be a conditional conclusion when a needed premise remains open.

B.5.RA:3 - Forces

ForceTension
Local inference and overall methodIndividual transitions can be understood while the purpose of a construction or the route to the conclusion remains obscure.
Understanding and checkingUnderstanding may reuse established results; validating a whole argument can require additional work under a different question.
Useful compression and hidden dependenceA lemma can make a long argument manageable, but the reader must know what it supplies and which conditions it uses.
Conditional result and unresolved premiseUseful consequences may follow before every premise is established, provided the next use preserves the condition.
Source recovery and new reasoningRepairing a gap can open a valid use, while attribution must distinguish the supplied argument from the reader’s addition.

B.5.RA:4 - Solution

Recover the reasoning at both the level of its main contributions and the transitions needed for the next use. Move between these levels when a local step changes your understanding of the whole argument.

B.5.RA:4.1 - State the use and read the claim

Name what the result would let you do: calculate a quantity, choose between alternatives, criticize a conclusion, adapt an argument or explain it to someone else. This determines how far recovery needs to go.

Read the conclusion with its objects, domain and conditions. If an ordinary-language argument relies on “everyone”, “always” or another universal expression, use C.39.QR:4.1.1 to recover the domain and the force of the remark before testing the inference. In a mathematical statement, recover the quantifiers: which objects are arbitrary, which may be chosen, and on what a chosen object may depend. In an empirical argument, recover what observations and inference support which population, conditions or phenomenon.

Locate the source’s definitions when a word or symbol admits different readings that would change this use. If a formal statement accompanies an informal one, compare the part of their meanings on which the intended application depends. For example, whether zero is allowed among “natural numbers” can change the statement.

B.5.RA:4.2 - Recover the main reason

Read for the difficulty the argument overcomes and the contribution that overcomes it. Ask why a construction, lemma, decomposition or comparison appears where it does.

Express the main reason in a short explanation: what is established first, what that makes possible, and how the remaining step reaches the conclusion. This may involve a reduction to an easier problem, an invariant, an exhaustive case distinction or another subject method. Use the method present in the source.

The first explanation is an interpretation. Check it against the decisive steps. If it cannot explain why those steps are needed, revise it rather than retaining an attractive summary unrelated to the argument.

B.5.RA:4.3 - Recover the dependencies of the conclusion

Work backward from the conclusion through the claims or constructions it uses. At each needed transition, identify its premises, the inference or operation, and the result.

Keep jointly needed premises together. Preserve a sufficient alternative as a separate way to reach the conclusion. Track a shared premise wherever a later step uses it; repeated uses of one assumption do not provide independent support for that assumption.

Read a claim about a whole back onto its subject. Which parts have to work together for the conclusion to follow? Could each fact cited about a part remain true while a different arrangement changes the answer? Recover the ground for the connection that matters. In :5.2 three intact copies can share an unavailable key. The inventory can answer a question about the number of copies while leaving recovery of the drawing open.

Distinguish a premise supplied for the argument, a result established earlier and a temporary assumption used inside a subargument. Recover the point at which a temporary assumption is discharged and what then follows. If this logical form is unfamiliar, obtain the relevant explanation before treating the subargument’s assumption as an established fact.

Use established results at the level needed for the task. If the question concerns what a lemma permits, its statement and conditions may suffice. If the question concerns how to alter the lemma’s proof, recover its internal reasoning.

B.5.RA:4.4 - Explain the transition that is missing

For a transition you cannot follow, recover the relevant definition, rule, earlier result or construction. Apply it to the participants at that transition. Say why these premises license this result and which condition is doing the work.

A useful self-explanation supplies this relation. “I understand this line” reports confidence; a paraphrase repeats the claim. Neither supplies the omitted inference when that is the difficulty.

Work a small instance when it helps reveal an operation or dependence. Identify what carries the inference through the stated domain. In :5.1 the step for an arbitrary integer holds throughout the range, including when shown in a drawing. Substituting 3 checks one value. One admissible failure would suffice to refute an assertion made for every value.

If the source’s resources do not close the gap, ask for the missing step with its premises and desired result. A proposed repair is new reasoning until it is justified. Keep the consequence conditional when a premise remains unresolved and conditional use is sufficient.

Where the missing step constructs an auxiliary object, use B.5.RC. Where it makes a statistical, causal or other subject inference, use that subject’s method and conditions.

B.5.RA:4.4a - Construct and examine an argument from prose or dialogue

Use this branch to examine testimony, analogy or a practical recommendation whose support remains open to challenge. When its claims and structure are clear, begin at :4.4a.5 with the known premises, inference and conclusion; return to reconstruction if a question exposes an uncertainty. Also use this branch when ordinary wording leaves uncertain what is being asserted, what is offered as a reason, or how the reasons reach the intended conclusion. It applies to arguments in your own draft too.

Reconstruction produces an interpretation that can be examined; it does not establish that the premises or inference are acceptable. Some recovered arguments are deductive, while testimony, analogy and proposals based on expected consequences commonly remain open to challenge.

B.5.RA:4.4a.1 - Recover the question and the claims before drawing links

Read enough of the surrounding text or exchange to identify the question being answered and what the speaker asks the recipient to accept. A recommendation, an assertion about what happened, and an explanation of an accepted event can occur in the same paragraph. Ask of each passage: is this a reason to accept a disputed claim, an account of why an accepted event happened, a question, a request, or background? The word “because” fits both argument and explanation. Their difference here is the work done in the exchange; an explanation can contain claims that need argument when challenged.

Write the potentially relevant claims as complete sentences, with enough of their source wording or location to check the interpretation. Resolve “it”, “they”, the occasion and the comparison class where the context permits. Preserve negation, quantities, time, modality and attribution: “Lee says the room may be available” neither asserts certain availability nor independently establishes it.

Split a sentence when it contains claims that can be accepted or challenged separately. Do not cut a logical relation into newly asserted facts. “If P, then Q” states a conditional; it asserts neither P nor Q. To use it to reach Q, recover a separate ground for P and preserve whatever qualifications the conditional has.

Clarify only as far as the next use requires. Replacing “works well” with a measured criterion can make a claim testable, but an invented threshold is your proposal until the speaker or source supports that reading. Rhetorical questions can convey commitments, and imperatives can express recommendations. Recover the proposed commitment from context instead of treating every question mark as disposable filler. A literal command alone does not state its justification.

If the conclusion is unstated, propose the claim the offered reasons appear intended to establish. For example, a successful rehearsal with unchanged equipment may support another successful display; it does not by itself establish that another test is unnecessary or that this is the best venue. Keep a reconstructed conclusion distinct from a conclusion you decide to argue for yourself.

B.5.RA:4.4a.2 - Compare consequential readings and try a scheme

Where the wording admits readings that change the support, make the alternatives explicit. Compare them with the assertions, the question under discussion, surrounding replies and any shared premise that can be established. Prefer the reading that accounts for those contributions with the fewest unsupported additions. Interpret the speaker reasonably, but do not improve a weak argument into a different strong one and attribute the improvement to them. Agreement with the conclusion is no reason to prefer a reading.

Ask a discriminating question when a reply is available: “By free, do you mean unbooked at that time or without a hire charge?” If the source cannot be consulted, preserve both live readings or limit the use to what they share. Choosing a provisional reading can be sufficient for examining its consequences; it does not resolve the remaining ambiguity.

An argumentation scheme describes a recurring arrangement of premises and conclusion. Try one as a hypothesis about the inference. Fill its places from the recovered claims and identify every place missing. For expert opinion, find the relevant expertise, the assertion and the proposition it is offered to support. Someone who handles a booking calendar can instead know its entries through ordinary access. A professional title by itself does not establish either expertise about this question or knowledge of this occasion.

A missing scheme premise gives a question, not permission to invent its answer. Look for evidence that the source relies on it; if none is available, retain the gap, try a better-fitting scheme, or describe the inference. For instance, calling a new expense “a waste” need not invoke sunk costs. The latter reading needs past investment and a claim that stopping would waste that investment. An argument against an unnecessary future expense can have neither. Scheme selection follows the offered support, not the word that first caught the reader’s attention.

B.5.RA:4.4a.3 - Recover the intermediate conclusions and missing grounds

Work backward from the proposed conclusion and forward from its offered reasons. Ask at each join what these reasons, if accepted, support immediately. A booking report may establish availability; availability together with a claim about the rehearsal’s requirements may establish feasibility; feasibility needs a choice rationale before it supports selecting the venue. Write an intermediate conclusion when this distinction changes what can be challenged or reused. It has both roles: the result of one inference and a premise of another.

To find a hidden premise, explain why the stated reason bears on its target. Look for the condition, comparison, generalization or value judgement that would license that move. Ask whether the supplied reason could hold while the conclusion fails; the resulting counterexample can reveal an omitted qualification. For “the hall is available, so use it”, a hall too small for the cast exposes a requirement that availability alone cannot answer. An unfamiliar subject inference needs its subject method, not a sentence invented merely to make the arrow look complete.

Retain the different grounds for an addition. A context-supported implicit premise belongs to the recovered interpretation, with the supporting context made clear. An unresolved candidate premise remains a question about what the speaker meant. A premise you independently investigate or introduce belongs to your repaired argument. One bracket style is optional; these distinctions are not. Do not add a premise equivalent to “these premises establish this conclusion” as an explanation of why they do.

Try the resulting account against the original passage. Can it explain the role of each relevant contribution and the conclusion’s stated strength? Does it attribute something the source could consistently deny? Does an apparently unused sentence support an intermediate claim, supply an objection, or merely explain the occasion? Revise the arrangement when these questions expose a better reading. Leaving a passage as background can be faithful; making every sentence support the final conclusion cannot be a goal.

B.5.RA:4.4a.4 - Make the selected structure inspectable

Use a short outline or argument map when the dependencies would otherwise be hard to inspect. Write a claim at each point where someone may need to accept, contest or reuse it. Connect an offered reason to its target and explain the inference. The link means support; it does not mean temporal succession, physical causation or part–whole membership. A causal claim can be a premise or conclusion.

Put jointly used premises in one reason group. To check the grouping, remove one premise in thought and ask whether the offered inference still supplies a reason for that target. If its bridge is gone, keep the co-premises linked. If another complete reason remains, show that reason separately. Separate reasons need not each be sufficient for the contemplated use; several weak reasons may be cumulative, and their adequacy remains a subject judgement. Retain common sources or assumptions across groups so that repeating one report does not create independent evidence.

Use A.6.3.RT.OE when the expression obscures the recovered relations. Show an intermediate conclusion at both of its uses and keep an objection attached to the claim or inference it challenges. Preserve source attribution and consequential uncertainties in the outline. Read it back as ordinary reasoning and compare it with the text. If the map seems more certain, more comprehensive or easier to defend, find what was lost or added.

The selected structure can be used for criticism. An answer may require changing the structure: a supposed eyewitness report can turn out to be an inference from an observed clue, as in :5.5. Return to the interpretation and grouping when that happens, rather than merely adding a negative mark to the first scheme.

B.5.RA:4.4a.5 - Ask a consequential question and revise its target

Turn the scheme’s critical questions into questions about this case. For expert opinion, ask about relevant competence, the domain of the claim, the statement made, reliability, disagreement and the underlying evidence. Select questions whose answers could change this use, and add a question exposed by the circumstances even if it is absent from the standard list. Name what answer or evidence would resolve the concern.

The question ‘Did the specialist assess this adapter?’ can lead to confirmation, a request for evidence, or a finding that the cited assessment concerns another setup. Those outcomes require different revisions.

To construct a question rather than repeat a catalogue, isolate a consideration carrying the inference and ask both what supports its application here and what could make that application fail. For Dana’s expertise, ask which experience supports this assessment and which part of the setup might fall outside that experience. Seek the relevant facts on both sides; do not invent adverse evidence to fill the second answer. Add a contextual consideration when its absence could change the conclusion, such as whether the tested configuration is available. Explain how the answers affect support in this case; they are not votes.

Place an objection at its target:

What the objection challengesWhat to examine next
A premiseThe ground for accepting that premise, and every reason group that needs it.
The transition from premises to conclusionWhether the stated circumstances permit that inference, even if its premises are accepted.
The conclusionThe opposing argument and its grounds alongside the argument offered.

An objection also needs grounds. A question can expose an unsupported premise without establishing its negation. A reply that answers the question may restore that support; a reply that merely repeats the conclusion does not. When disagreement persists, locate whether it concerns evidence, an inference condition or the criterion for accepting the result. Use the relevant practice to settle that issue.

Return the strongest conclusion the surviving grounds justify for the intended use, with an unresolved condition when necessary. Apply B.5.RR to a changed premise or inference condition and follow its affected dependents. Keep a sufficient alternative that survives. If no adequate route remains, obtain the missing ground, narrow the conclusion or leave it unresolved. A map and a familiar scheme organize this work; the subject reasoning determines what follows.

When this is your own draft, use the exposed gaps to obtain grounds, alter the argument or narrow the conclusion before rewriting the prose. In a joint reading, compare the claims and links on which the participants differ; agreement on the drawing is neither agreement with the conclusion nor evidence that it is true. Ask each reader what in the text supports their interpretation, and revise the account or keep the difference explicit.

Learning to do this reliably can require practice with feedback; a completed map or a worked example does not establish that capability.

B.5.RA:4.5 - Use the recovered reasoning and stop at a useful result

Perform the use named in :4.1. Apply the result under its conditions, explain the decisive step, identify a consequential criticism, or name what must be recovered before the use is possible.

Make the conclusion no stronger than the recovered reasoning supports. If recovering the argument reveals an open premise, state its effect on the intended use. When several sufficient arguments are available, an unresolved branch may be bypassed through a branch whose premises and reasoning are adequate.

If a premise or requested conclusion changes, use B.5.RR to follow the affected reasoning and derive what still follows. The recovered dependencies supply the starting point for that work. An unchanged, adequately supported part can be reused.

C.11.DUA governs whether more checking or information is worth obtaining for this decision. Understanding an argument, verifying its correctness and establishing its real-world premises can require different work. Select further work from the unresolved question.

When the work is divided among agents, give the next contributor the premises at the missing transition, the result needed there and the intended use. On return, connect the supplied reasoning to the argument’s main reason. Use the explanation or working notation that makes the continuation possible.

B.5.RA:5 - Archetypal Grounding

B.5.RA:5.1 - Understanding why the sum of odd numbers is a square

Consider this compressed argument: “The sum of the first n positive odd numbers is n²: the sum and the square start at zero, and both increase by 2n+1 when n increases by one.” The statement concerns every nonnegative integer n. A reader recognizes the formula but needs to explain the steps compressed in that reason.

Write S(0)=0 and S(n+1)=S(n)+(2n+1). The main reason is that both the sum and the square start at zero and grow by the same amount when n increases by one. The algebraic identity (n+1)²−n²=2n+1 supplies that connection.

Recover the general transition. Assuming S(n)=n² for an arbitrary nonnegative integer n gives:

S(n+1)=S(n)+2n+1=n²+2n+1=(n+1)².

The temporary assumption is the induction hypothesis. It supports the successor step. Together with S(0)=0, that step establishes the statement for every nonnegative integer by induction.

For n=3, the sum is 1+3+5=9. Adding the next odd number, 7, gives 16. This instance makes the equal-increment operation visible. The argument’s reach comes from the arbitrary n, the base value and the induction rule.

A square drawing gives another way to follow the increment: grow an n-by-n square with a row of n cells and a column of n+1 cells. That adds 2n+1 cells. The drawing and algebra expose the same increment under the counting interpretation.

The reader can explain the role of the initial value and successor step. If the next task instead asks for the sum of n odd terms beginning at 3, the changed range opens a revision: use the established sum through the (n+1)th odd number and remove the first term, giving S(n+1)−1=n²+2n. For four terms, 3+5+7+9=24. The reusable contribution is the recovered relation between range, initial value and increment.

If the original question asked only for 1+3+5, direct addition would supply the result. Recovering the general argument earns its effort when explanation, general use or revision needs it.

B.5.RA:5.2 - Understanding a drawing-recovery argument

A team needs to open an archived engineering drawing for reuse. Someone argues that the drawing is recoverable because three backup copies exist.

Recover the method behind that conclusion. For the encrypted-backup route, the needed contributions are readable stored data, an available way to decrypt it and a decoder for the drawing format. Their joint use produces a readable drawing. Having more copies addresses loss of stored data, while all three may share one decryption key.

Suppose the key is unavailable. The backup count leaves the decoding route incomplete. The next useful question is whether the key can be recovered or another usable copy obtained. The recovered argument identifies that missing prerequisite.

Now suppose a separate plaintext copy in a readable format is available. That gives a different route to the drawing and permits the team to continue without recovering the encryption key for this use. The original encrypted route remains conditional.

The result is a usable recovery choice or a focused request for a missing contribution. A later claim that the opened drawing describes the present equipment requires its own comparison; the file-opening argument answers the immediate recovery question.

B.5.RA:5.3 - A projection argument with two grounds and one shared condition

A seminar organizer receives the message: ‘The slides should display correctly. Dana says the projector is compatible, and yesterday’s rehearsal worked.’ The organizer needs to decide whether another display test is needed before using projector P with laptop L and adapter D. The relevant technical claim C is: the current PDF can be displayed at 1080p by this setup.

Construct the offered argument. Ask what ‘compatible’ and ‘worked’ mean here. Suppose Dana maintains these projectors and reports that the setup used for yesterday’s rehearsal, with P, L and D at those settings, can display the current PDF at 1080p. Separately, the organizer inspected all pages of that PDF during the rehearsal and found them displayed correctly at 1080p. To use either ground for the planned showing, establish condition S: the relevant equipment, PDF and settings from the rehearsal will apply there.

The expertise and the assertion work together in the first reason. Neither ‘Dana is an expert’ alone nor an unattributed compatibility sentence supplies that reason. The rehearsal is a different ground: it is an observed instance under the required setup. Its use for another showing depends on S and on the ordinary technical judgement that the successful test remains applicable. It is not a deductive guarantee of future operation.

The following outline is an argument map. Braces group premises used together; arrows mean support for C, not physical causation or event order.

R1: {Dana has relevant expertise; Dana says the rehearsal configuration can display this PDF at 1080p; S}
    --expert-opinion inference--> C
R2: {the organizer observed the current PDF displayed correctly on P/L/D; S}
    --applicable rehearsal result--> C

R1 and R2 are separate grounds, but they share S. R2 is not merely another report of Dana’s judgement.

Question the ground. A colleague asks, ‘Did Dana assess this adapter, or just the projector’s ordinary input?’ Dana replies that her message was shorthand: she knows P and L but had assumed that D was compatible. This answer removes the claimed coverage of her assessment. Mark the objection at R1’s asserted scope and its use for C. The resulting conclusion is not ‘the slides cannot display’. R2 supplies the observed result for P/L/D. If that rehearsal is an adequate technical basis for this modest use and S holds, the organizer can use C on R2 alone. The map records why losing one reason need not lose the conclusion.

Revise after a common condition changes. Before the seminar, D is replaced by D2. B.5.RR follows the changed configuration through both uses of S. The rehearsal remains evidence about D, and Dana’s statement supplies no assessment of D2. C for the new setup is unresolved. Testing the new setup, restoring D, or obtaining an applicable technical account can close that gap. Repeating the old positive reports cannot.

Suppose a test with D2 then shows that the current PDF is not displayed under the intended settings, after the operator checks the connections and follows the equipment’s setup instructions. This is a new opposing observation for that tested setup. The organizer can report that the attempted display failed and return to technical diagnosis; the observation alone does not identify which component caused the failure.

Decide whether another test is needed. If the organizer may rely on a successful rehearsal of the current PDF and unchanged setup, the observed rehearsal meets that condition. If the seminar requires a fresh test after an adapter change, replacing D made such a test due. The failed trial with D2 supplies its outcome. To display the slides, the organizer can now restore the earlier configuration if still available and permitted, or arrange a working alternative.

Choosing between venues is a further decision. Even a working projector could be needed for another booked session. If the organizer must also choose the venue, compare the available arrangements, their consequences and costs through PSDA.5/.6/.8. The decision about needing another test can stand on its own.

B.5.RA:5.4 - From an ambiguous message to a conditional venue argument

An amateur theatre group is choosing a room for a complete three-hour rehearsal on Friday evening. It receives this message:

Use the school hall on Friday. If it is free, we can rehearse there together. Noor says it is; she manages the bookings. We missed last week because the band had the hall. Paying for the studio would be a waste.

Begin with possible readings. “Free” could mean unbooked or without a hire charge. “It is” could refer to either meaning, and “we can rehearse” might concern some rehearsal rather than the complete three-hour session. The opening recommends a venue; it does not itself justify that choice. The conditional in the second sentence supplies a proposed relation between availability and rehearsal feasibility. It does not establish availability.

A first sketch that puts “the hall is free” and “we can rehearse” into two boxes as asserted facts has strengthened the text. A sketch that puts every remaining sentence directly under “use the hall” hides how the recommendation is supposed to follow. Two more faithful readings remain: the message could argue from available space or from avoiding a hire charge. The booking role makes the first reading plausible, but does not prove which meaning the speaker intended.

Ask the organizer what was meant. Suppose the reply is: “I meant unbooked for our Friday rehearsal. Noor told me there was a free slot. I was explaining last week’s cancellation, which we all already know about.” This supports the availability reading and identifies the “because” sentence as an explanation of the accepted cancellation. Keep that explanation as context; it supplies no evidence that the hall is available this Friday. The reply does not establish the slot’s duration or the relative cost.

Extract the claims without filling the gaps. The organizer’s proposed conditional is: if the school hall is available for the required Friday session, the group can complete that rehearsal there. Noor is reported to have said there is a free slot. Managing the bookings gives a reason to treat her as able to know the booking entries, not as an expert on every condition of a rehearsal. Recovering her statement’s scope is necessary before using it for the three-hour claim.

The sentence about waste suggests a practical choice: avoid paying for an alternative when an adequate option exists and the payment buys no relevant advantage. It does not mention past investment or abandoning an earlier undertaking. A sunk-costs scheme therefore adds the wrong premise. The question is which present and future differences make the studio expense unnecessary.

A provisional structure makes the missing intermediate result and grounds visible. Braces below group co-premises. “Reported” retains attribution; “proposed implicit” identifies a reading supported by the waste remark but not confirmed. Arrows mean the indicated support.

{Noor manages the bookings; Noor is reported to say a slot is free}
    --ordinary knowledgeable-source inference-->
    A: a Friday slot is available (its hours remain unconfirmed)

{A with the hours required by the group;
 the organizer's conditional about completing the rehearsal}
    --conditional application-->
    F: the group can complete the required rehearsal in the hall

{F;
 D: using the hall has lower relevant burden and the studio adds
    no compensating benefit [needed comparison, not supplied];
 V: choose the adequate option without that unnecessary burden
    [proposed implicit choice rationale]}
    --practical inference--> C: use the hall for this rehearsal

A is not the premise about the required hours, and F is not another independent reason alongside Noor’s report. F depends on the availability claim and the organizer’s conditional. D is an exposed need for evidence, not a fact extracted from “waste”. The practical argument remains conditional on it and on the other requirements in F. The map therefore recovers both the plausible offered reasoning and what it has not supplied.

Use the structure to ask the next question. The availability claim affects every later step, so ask Noor for the interval before making a booking. She replies: “The hall is unbooked from 18:00 to 20:00; another group has it after that.” The actors need 18:00 to 21:00 for the complete run. Preserve Noor’s narrower claim; do not revise it into a false claim that the hall is occupied all evening. Replace A’s uncertain scope with the two-hour interval. That interval does not supply the required three-hour premise, so the route to F and C fails for the intended session. It is unnecessary to settle the cost comparison to reach this result.

B.5.RR follows that affected route while retaining the usable booking information and last week’s explanation. A shorter rehearsal, a different time or the studio can become alternatives, but each changes a condition or opens another argument. The source has not justified any of them merely by losing its first recommendation. If the group changes the task to a two-hour scene rehearsal, reassess the conditional’s remaining requirements and the practical comparison for that new use.

Separate reconstruction from a repair. Suppose the reader checks room capacity, access for every actor and both venues’ charges. Those findings may help construct a better choice argument. They are new grounds obtained by the reader. They do not make the original message complete or turn its ambiguous “free” into a statement about price.

B.5.RA:5.5 - An expert’s title cannot turn a clue into an observation

A workshop colleague writes: “The parcel has arrived. Noah, our electronics expert, says so: the goods trolley is back by the door.” The recipient wants to tell an assembler that the replacement parts are ready to collect.

Trying expert opinion first exposes a mismatch: electronics expertise does not establish knowledge of this delivery. Ordinary access could matter instead. A person who checked the parcel could report its arrival without being an expert. Before replacing the first scheme with knowledgeable testimony, recover what Noah knows.

Ask, “Did Noah receive or see this parcel, or infer its arrival from the trolley?” Suppose Noah replies, “I saw the trolley. I haven’t looked for the parcel; deliveries usually bring it back.” Now the distinction changes the structure:

{Noah saw the trolley by the door; his report is usable for that observation}
    --ordinary observation report--> T: the trolley is by the door

{T; a proposed connection between this trolley's return and this parcel}
    --inference from a clue--> P: this parcel has arrived

Noah’s claim about the trolley can remain credible while his conclusion about the parcel is unsupported. The observation and inferred arrival were compressed into one attributed statement. The repair separates them and locates the missing connection.

Ask what other work moves the trolley and whether this delivery was due to use it. Suppose the workshop uses the same trolley for outgoing parcels, and today’s dispatch account explains its position. That removes the offered clue’s claimed discrimination for this arrival. A receiving record or inspection can provide fresh evidence of arrival. Its bearing on collection depends on what happens to the parts after receipt.

This differs from a disagreement over the trustworthiness of a witness who saw the parcel. In that case the disputed ground would be the report. Here the observation is accepted and the disputed transition is from trolley position to this parcel’s arrival. The dispatch record explains the trolley’s return and leaves the parcel’s arrival open. The assembler still needs to know whether these parts are ready to collect. A current collection record can settle that question. Receipt can suffice if the receiving arrangement makes these parts immediately available and they remain so at collection time. If parts may have been issued, held or moved, check their present availability. For a request confined to what Noah saw, his report already supplies the answer.

B.5.RA:6 - Bias-Annotation

A familiar scheme label can make a reader force the text into its expected premises. A fluent paraphrase can turn a condition into a fact or a tentative report into certainty. Return the proposed structure to the source and the question being answered, especially when the map looks stronger than the passage.

Familiar vocabulary and a correct-looking calculation can create confidence before the reasoning has been recovered. Conversely, checking every line can consume attention while leaving the role of a lemma unexplained. Use the local transition and the main reason together.

AI-generated formal proofs make the distinction consequential: a checked formal derivation supplies a result under its definitions, while the intended statement and the explanatory structure needed for reuse may need recovery. The relevant comparison is the one that can change the contemplated use.

B.5.RA:7 - Conformance Checklist

For the argument and use being recovered:

  1. The intended use and the conclusion’s domain and conditions are recoverable.
  2. The explanation states the main reason for the result and connects it to the decisive steps.
  3. The needed transitions identify their premises, inference or operation and result.
  4. Joint premises, sufficient alternatives, shared assumptions and temporary assumptions retain their different roles.
  5. The reader can perform the intended use or identify the missing transition or premise that prevents it.
  6. A general conclusion has grounds covering its stated domain. Any instance used supports the claim made on its basis.
  7. Further checking is selected for an unresolved question, and adequately supported parts remain reusable.

For an argument using :4.4a, also inspect whether the claims preserve the source’s scope, conditions and attribution; a consequential competing reading has been resolved or retained; and the selected scheme fits the offered reasoning. Intermediate conclusions and joint reasons must expose the dependency.

Reconstructed premises and conclusions remain distinguishable from supplied ones and from the reader’s new grounds. Each consequential objection has a target and grounds. A changed condition should revise the affected support without automatically asserting the opposite conclusion.

These are questions about the recovered reasoning. Their answers may be evident in the explanation or application.

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

Failure in the situationRepair
Choosing a scheme from a keyword or title and supplying its absent premisesMatch the claims; recover contextual evidence for an implicit premise or revise the scheme.
Splitting a conditional into two asserted factsKeep the conditional relation intact and obtain a separate ground for its antecedent before using it.
Making a charitable repair indistinguishable from the source’s argumentState which additions have contextual support and which are your new grounds or proposed revision.
Paraphrasing successive claims while the inference remains missingApply the relevant definition, rule or earlier result to the transition’s premises.
Checking local steps while failing to explain why a lemma or construction appearsRecover the difficulty that contribution resolves and connect it to the conclusion.
Treating several uses of one premise as several independent groundsKeep the common prerequisite visible and examine its role in the needed branches.
Promoting a temporary assumption to an established premiseRecover the subargument and the conclusion obtained when that assumption is discharged.
Extending a successful calculation on particular inputs to every allowed inputRecover the step that holds for an arbitrary input or establish that the cases considered exhaust the domain. An admissible failure can settle a claim of universal success.
Demanding a complete reproof when the task only needs an established result under its stated conditionsUse that result at the needed level; open its internals when the new question requires them.

B.5.RA:9 - Consequences

A recovered argument can support application, explanation, criticism and later revision. Work can be divided around intermediate results, and a request for help can name the transition that remains obscure.

The method can reveal that the source’s conclusion exceeds its support or that the reader lacks a prerequisite. Its stopping points are a sufficient argument for the use, a useful conditional conclusion or a localized gap.

B.5.RA:10 - Architectural Rationale

A source orders its text for exposition; the argument relates premises, intermediate contributions and conclusions. Understanding therefore needs more than following the paragraph order. Backward dependency recovery identifies what the desired conclusion uses, while recovery of the main reason explains why those contributions were chosen.

Local and overall understanding constrain each other. In :5.1, the equal-increment idea explains the role of the recurrence, and the induction step establishes the general result. In :5.2, the recovery route explains why the key and format matter, and their availability determines which route can be used. A fluent summary that cannot support these transitions is insufficient for the intended use.

For ordinary prose, interpretation and evaluation constrain each other without becoming the same judgement. Context can justify reading a statement as a recommendation while its grounds remain inadequate. A later answer can expose a mistaken structure rather than a false premise within the original structure. Claim extraction, comparison of readings and scheme testing make that return possible. Going straight to a familiar scheme saves effort only when the offered inference is clear; strengthening the source to fit it loses the argument being recovered.

This common method concerns recovery of reasoning offered for a result. B.5 coordinates the broader inquiry; B.5.RC recovers an auxiliary construction; a subject method supplies an unfamiliar inference. To explain the result to someone else, select the reasoning and representation that make their intended use possible. C.2.8 helps characterize what that recipient can extract under stated preparation and access.

Recovery also makes revision possible. The changed premise can be followed through the contributions that use it, while independent arguments remain available. Revision has its own task and result; recovering the original argument supplies the dependency information it needs.

B.5.RA:11 - SoTA-Echoing

Local and overall proof comprehension. Mejía-Ramos and colleagues distinguish understanding terms, logical status and justifications from understanding a proof’s main idea, components, transfer and examples. Their 2017 account of developing and validating proof-comprehension tests, §2.2, develops the earlier 2012 model and makes the dimensions operational for particular undergraduate proofs.

This pattern adopts the combination of local transitions and overall method in :4.2–:4.4. The published assessment results concern those proof-reading settings, while the generic recovery procedure here is a synthesis.

Self-explanation. Hodds, Alcock and Inglis’s work is accompanied by the Loughborough guide for mathematics lecturers. It explains why relating claims to prior knowledge and to other claims differs from confidence reports or paraphrase. This contribution informs :4.4. The evidence reported there concerns undergraduate mathematical proof comprehension.

Later assessment work. The PRIUM framework, Cooley and colleagues (2024), develops proof-comprehension assessment through questions about definitions, statements and their relationships, with revision informed by discrepancies between intended questions and student answers. That is an assessment contribution to consider when demonstrated comprehension is required. The present method supplies the recovery work; it does not require a departmental assessment programme for an ordinary use.

AI-assisted reasoning. Klowden and Tao’s Mathematical Methods and Human Thought in the Age of AI, especially §4.4, distinguishes a verified formal statement from the intended statement and from the explanatory reasoning around a proof. This pattern adopts the intended-use comparison and the recovery of the method behind the result. The essay provides a contemporary conceptual argument, rather than an experiment validating this procedure.

Recoverable methods beyond answer production. The Math and AI declaration raises the risk that rapid answer production can outpace understanding and development of methods. It is a position statement. This pattern takes the resulting recovery question: which reasoning can the next practitioner use? Human or AI production does not settle that question; the returned argument and its use do.

Schemes and argument construction. Walton’s Argumentation Schemes & Their Application in Argument Mining, §§1–4 is a historical methodological source, republished from 2011. It separates scheme recognition from matching keywords, distinguishes ordinary access to knowledge from expertise, and rejects a sunk-costs reading where the required prior investment is absent. These distinctions guide :4.4a.2 and the different failures in :5.4–:5.5.

From prose to a revisable map. Davies, Barnett and van Gelder’s Using Computer-aided Argument Mapping to Teach Reasoning (2021), §§2–15 develops claim clarification, context-sensitive reconstruction, intermediate conclusions, hidden grounds and linked premises in §§3–15. Section 2, especially p. 119, also describes maps as support for writing and joint discussion; these are applications of mapping. Adapt that construction in :4.4a and :5.4–:5.5 while retaining source attribution and unresolved alternatives.

Treat their term-matching and layout rules as search aids, not universal inference laws. Their conclusion leaves inference objections and fuller evidence integration undeveloped; those questions return here to the inference and its grounds. The teaching sequence remains a separate contribution to capability development.

Limits of a question catalogue. Hernández’s Disentangling Critical Questions from Argument Schemes (2023), §§2–5, contests the idea that scheme questions supply a complete evaluation. Adapt its attention to the question–answer exchange and the counterargument it can produce. The article proposes, but does not solve, a comparison of argument strength. The present synthesis keeps schemes useful for recovery while requiring contextual grounds for an evaluative conclusion; it adopts no score based on counting failed questions.

Bounded method choice. Compare line-by-line paraphrase, full proof validation and use-directed recovery on the same short argument. Paraphrase can retain the odd-sum formula while missing the equal-increment reason. Full validation answers correctness, but may spend effort inside usable lemmas. Recovering the main reason together with the needed transitions gives the explanation or changed-use basis sought here.

Select it when that is the unresolved task; retain full validation when correctness of the complete argument is the required conclusion. The drawing-recovery case extends the dependency method to a practical inference without treating mathematical proof as the sole form of reasoning. Reconsider this recovery approach if prepared readers repeatedly cannot recover why the decisive inference works, while another explanation or reading method enables the same use with comparable effort.

Baumtrog’s Designing Critical Questions for Argumentation Schemes (2021) contributes paired inquiry into support and possible failure. This pattern adopts that practical move without requiring his complete scheme design.

B.5.RA:12 - Relations

  • B.5: coordinates inquiry and the revision that can follow recovery of an argument.
  • B.5.RC: obtains an auxiliary construction that a decisive transition requires.
  • B.5.MPC: connects arguments and constructions across physical, mathematical and computational contributions.
  • B.3 and B.3.3: govern confidence and assurance questions when the intended reliance requires them.
  • C.11.DUA: selects additional checking and information for the decision at hand.
  • C.2.8 and C.37: characterize recipient-accessible structure and support selection of representations.

B.5.RA:End

B.5.RR - Revise Reasoning After a Premise or Question Changes

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

B.5.RR:1 - Problem frame

Use this pattern when reasoning that you could previously use needs to answer a changed question, or when a premise, observation or application condition changes. You need to know what still follows, what must be worked again and what can be done.

The object of revision is the reasoning used for that question: its premises, intermediate contributions, conclusion and conditions of application. The relevant practice supplies its inference rules and the grounds for using its premises.

First useful move: state the change beside the result you need. Find where the earlier reasoning used the changed condition, or where the new result requires a contribution the earlier argument did not supply.

This work requires enough subject knowledge to follow the argument. Use B.5.RA when that reasoning must first be recovered. If the established result answers the new question under conditions that hold, apply it and stop. Rebuilding the entire argument is useful when recovery would cost more, or when an obligation requires a full new derivation.

B.5.RR:2 - Problem

A familiar answer often survives in a formula, report or program after the reason for using it has changed. Repeating the earlier steps can produce a convincing answer to the former question. Discarding everything can waste constructions and arguments that remain useful.

Revision requires following the reason for a result. One conclusion may need several premises together; another may have two sufficient arguments. A premise may be shared by apparently different arguments. A change can also make a formerly fixed quantity the unknown, so replacing a number leaves the task undone.

The result is reasoning that answers the changed question at its supported scope, or a partial result and the contribution needed. It should let the receiver act, obtain that contribution or pursue the newly exposed question.

B.5.RR:3 - Forces

ForceTension
Reuse and hidden dependenceRetaining an established result saves work, but its application may use the changed premise indirectly.
Local repair and a changed questionA small correction can preserve the conclusion; a new objective may require another argument.
Several arguments and a shared weaknessAn alternative can preserve a conclusion, while a premise common to both can defeat that apparent independence.
Useful qualification and continued inquiryA conditional result or bound may suffice; another use may need the unresolved premise or a new construction.

B.5.RR:4 - Solution

Start with the receiving question, follow the affected reasoning and derive the result that can be used. A reminder is:

Changed question or condition → affected reasoning → retained or replacement contribution → revised conclusion → receiving use.

B.5.RR:4.1 - Say what changed and what is needed

Compare the earlier question with the present one. State the result needed and the changed condition in terms that can be used in the reasoning. For a calculation, that may be a new range or an input that is now an unknown. For an empirical conclusion, it may be an observation, a changed population or an operating condition.

Establish who has changed the question. A recipient may commission a new result. You may also try a different question as a way into the one still assigned. Could two situations give the same answer to your question and different answers to the recipient’s? If so, recover what distinguishes them for the assigned use. In an inquiry whose direction is yours to choose, you can pursue a newly interesting question on its own terms.

Distinguish a change in the situation from a correction to your account of it. A measurement taken yesterday can remain a sound report of yesterday while being insufficient for today’s operation. A proposed condition can be explored without replacing the account of what has happened.

Keep the meanings of the quantities and claims visible. If the same term denotes a different quantity, translate the question before substituting its value. If only the spelling or presentation changed and the established application fits, no reasoning revision is needed.

B.5.RR:4.2 - Recover the dependence that matters

Begin at the changed premise and at the desired conclusion. Find which intermediate claims or constructions connect them. At each relevant transition, ask what is needed together, what is produced and why that transition is allowed.

Keep a sufficient alternative separately. For example, recovering a file may require either a readable local copy or an available remote copy. If both are encrypted with one unavailable key, the two storage locations leave the same prerequisite unresolved.

Use an established lemma at the level its receiving use needs. Inspect its statement and application conditions first; open its proof when the revision requires changing or checking the reasoning that establishes it. Do the same for an established measurement or computation: inspect the part whose application the change calls into question.

A sketch or a few statements can hold these dependencies. Use B.1.1 when a dependency representation needs its relation clarified. A reasoning dependency says which premise or operation supports a conclusion; physical causation and temporal order require their own relations.

If the needed dependence is missing from the account, recover it through B.5.RA or ask for that contribution. Treat a supposedly unaffected part as reusable only when its independence from the change is adequately understood for this use.

B.5.RR:4.3 - Derive what follows after the change

Work from available premises through the affected transitions. Reuse a contribution whose conditions and required result fit. Where they do not, derive the replacement, select an adequate alternative or identify the unresolved step.

Withdrawing a premise removes that premise as a basis for asserting the conclusion. Another sufficient argument may support it. To assert the opposite conclusion, obtain a reason for that assertion. The conditional argument can remain available for situations in which its premises hold.

Follow the change through each needed use of a shared prerequisite. Keep the premises of an alternative argument together: pieces from two incompatible situations do not form a supported argument for either situation. If conclusions refer back to one another, recover the grounding of that reasoning, such as an initial case and induction step. Mutual repetition alone cannot replace the starting support.

A changed requested result can require working backward as well. Identify what the new conclusion would need, reuse the earlier contributions that supply it, and produce the remaining contribution. Release a former fixed value when the question asks you to determine it.

Compare the work of recovering and repairing the affected reasoning with the work of obtaining a fresh sufficient answer. A short new calculation can be cheaper and clearer. A maintained dependency account is useful when repeated revisions repay its cost; it is optional for an ordinary one-off question.

B.5.RR:4.4 - Choose the result the present reasoning supports

Relate the revised conclusion to the result requested in §4.1. It may supply the requested answer, a conditional answer, a bound or an obstruction. Say what the receiver can do with that result.

For a mathematical argument, carry the domain and assumptions into its conclusion. For an empirical application, examine the changed observation or applicability premise using the relevant subject method. Recomputing a model can establish its new consequence while leaving its correspondence with the physical situation unresolved.

If the question asks whether a result is attainable under fixed conditions, a proof of impossibility answers it. If the recipient still needs a usable object or arrangement, explain what the obstruction rules out. You can propose a change to a condition the recipient has authority to revise. Carry the answer under the original conditions with the proposal so the recipient can decide whether to commission the changed work.

Obtain further evidence or checking when its possible outcomes can change this use. C.11.DUA helps compare that contribution with its cost. The method can finish with a conditional result when conditional use is sufficient.

B.5.RR:4.5 - Apply the result and carry the change to its users

Perform the receiving use, or give its next contributor the revised conclusion and the condition that governs it. When others rely on the earlier result, tell the affected users what changed and which application must change with it. Their unchanged uses need no new argument merely because a nearby result was revised.

Check the changed transition by the method appropriate to its claim. A small instance can reveal a substitution error; a proof establishes its stated general conclusion; an observation can test a physical consequence. Choose the check for the result being relied on.

Stop when the receiving question is answered at the required level, or when the remaining contribution has been located well enough to obtain it. A useful new question can begin another inquiry under B.5.

B.5.RR:5 - Archetypal Grounding

B.5.RR:5.1 - Changing the range of a sum

A reader has established S(n)=n² for the sum of the first n positive odd integers, with S(0)=0 and n a nonnegative integer. The argument uses the shared initial value and increment: S(n+1)−S(n)=2n+1, also the increment from n² to (n+1)².

The new question asks for n terms beginning at 3: 3+5+…+(2n+1). The change is the range of summation. Reuse the established result on the first n+1 terms and remove the initial 1:

T(n)=S(n+1)−1=(n+1)²−1=n²+2n.

For n=4, the new sum is 3+5+7+9=24. The old formula applied unchanged would return 16. The proof of S survives; the application of that proof changes.

This repair also exposes a reusable construction. For n terms starting at a and increasing by 2, term j, counted from j=0, is (2j+1)+(a−1). Summing the established odd-number terms and the n equal additions gives n²+n(a−1). Changing the increment would require another derivation. The worked extension makes the next question precise.

Suppose a recipient keeps four terms and the increment 2, allows any integer starting value, and requires a sum of 28. The starting value is now the unknown. Solving 16+4(a−1)=28 gives a=4, and 4+6+8+10=28 checks the result. If the terms must still be odd, this same calculation proves impossibility since the only possible starting value is even. For zero terms, the empty sum is zero for every a, so a positive required sum is impossible. Either impossibility answers a feasibility question. Changing the term count, permitted values or total would be a new design choice.

B.5.RR:5.2 - Losing one way to recover a report

A team needs to read revision 17 of a report. Its established account has two ways to obtain that revision’s bytes: decrypt the local backup using its available key and decryptor, or obtain an unencrypted remote copy. An available viewer then displays the report.

The key becomes unavailable. Following that change removes the local decryption route. The remote copy and viewer supply the requested reading, so the team can proceed through them. The missing key need not be recovered for this use.

Now consider a different finding: the supposed remote alternative is encrypted with the key. Both routes need that key, so neither supplied route obtains the bytes. The next contribution is the key, another usable copy or a different way to obtain the report. A second storage location had concealed a shared prerequisite.

If instead the viewer becomes unavailable, either route may provide the bytes. Reading needs a suitable viewer or format conversion. This repair preserves the obtained result and locates the different operation that the receiving use requires.

B.5.RR:5.3 - A repeated conclusion loses its starting support

An analysis establishes claim A from an observation O, derives B from A and uses B in a further argument for A. A corrected interpretation of O removes its support for A.

The second occurrence of A does not preserve that support: its offered reason B was obtained from A. Reopen both uses and look for an argument grounded in retained premises. The conclusion may be true, but this circular route no longer establishes it.

Contrast this with an induction argument whose base case remains established and whose step derives the next case from the preceding one. Its recurrence has a grounded way to obtain each finite case. The relevant inference, rather than the visual presence of a cycle or repeated letter, decides what can be retained.

B.5.RR:6 - Bias-Annotation

The examples favor explicit premises and recoverable derivations. In statistical or interpretive work, revising one observation can require reconsidering dependence, selection or meaning before the changed conclusion can be obtained. Use the practice’s inference method.

The method can also overvalue salvage. When the earlier reasoning is poorly recoverable and an adequate new answer is cheap, obtain the new answer.

B.5.RR:7 - Conformance Checklist

  • The present question and the consequential change are stated.
  • The reasoning used by the receiving conclusion is recoverable at the needed depth.
  • Joint prerequisites, shared premises and sufficient alternatives are preserved.
  • Affected transitions are reworked under their applicable inference or construction rules.
  • The revised conclusion retains its domain, conditions and any unresolved premise.
  • The receiver can identify the next action, useful stop or contribution required.

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

Observed failure in revisionWhy it mattersRepair
Replace a number while retaining the old questionThe calculation solves for the former unknown.Restate the givens and requested result before choosing the computation.
Treat the loss of one argument as a refutationA different sufficient argument may remain.Examine its premises and derive the conclusion or its negation separately.
Count two dependent arguments as independentBoth can fail with their shared prerequisite.Follow the common premise through both uses.
Preserve a conclusion through circular repetitionThe retained statements supply no starting support.Recover a grounded argument or leave the conclusion unresolved.
Repair the whole report to answer a small changeUnaffected results are needlessly reproduced.Compare affected repair with a fresh sufficient answer and choose the useful scope.

B.5.RR:9 - Consequences

The practitioner can change an application while retaining useful reasoning, or explain why a larger change is required. A failure can expose a missing condition, a different construction or a worthwhile next question.

Recovery costs attention and sometimes specialist help. Its value increases when the same reasoning must be adapted repeatedly or divided among contributors. A short independent solution may remain the better choice for one small question.

B.5.RR:10 - Architectural Rationale

An argument and an application can change separately. A theorem can remain established while its former substitution ceases to answer the question. An empirical premise can become doubtful while its conditional consequences remain worth investigating. Keeping those distinctions lets revision preserve knowledge without preserving an unsupported use.

The method therefore joins backward recovery of what the desired result needs with forward derivation from the premises available. Alternative arguments preserve useful results; shared prerequisites explain where that preservation fails. Detailed deduction, statistical inference and physical-model revision remain contributions of their respective practices.

This is a method of obtaining and applying knowledge. Its result can also change the method repertoire: the revised sum reveals a parameterized construction, and an unresolved dependency can become the next research question. Those continuations are useful when they enable further work.

B.5.RR:11 - SoTA-Echoing

Which part of an argument needs revision? Adapt the assumption-sensitive reasoning of de Kleer’s A General Labeling Algorithm for Assumption-Based Truth Maintenance (1988), §2. Compared with discarding every conclusion that used a removed premise, §4.3 retains sufficient alternatives and their shared conditions. This historical computational method supplies a model of conditional support. The present method uses that insight without requiring an ATMS or exhaustive assumption labels for an ordinary inquiry.

When is incremental repair cheaper than starting again? Adapt the comparison in Hu, Motik and Horrocks, Optimised Maintenance of Datalog Materialisations (2018), §§1–4: eagerly finding alternative derivations can avoid unnecessary deletion, but that search can be costly; recursive support needs more than simple counting. Section 4.3 therefore compares recovery and repair with a fresh answer. These are results for Datalog maintenance; selecting subject premises and interpreting empirical change require further reasoning.

What should repair preserve for its receiver? Adapt Klowden and Tao’s Mathematical methods and human thought in the age of AI (2026), §§4.4–4.6. An inspectable proof result can serve one use, while changing its assumptions or applying its idea needs recoverable reasoning. Sections 4.1–4.5 retain that receiving question. The trade-off is explanation and recovery effort when another use needs them; full exposition is unnecessary for an adequate application.

What does automated proof repair contribute? Wang et al., Learning to Repair Lean Proofs from Compiler Feedback (2026), §§3–5, studies repair from generated failures and compiler feedback. Adapt its use of a localized failing transition when such feedback is available. Its single-shot formal-repair result answers a narrower question than choosing changed premises or interpreting an application. Section 4.4 preserves those questions instead of using compiler success as their answer.

Reconsider the repair when better dependency recovery, subject inference or repair support changes the attainable result or the cost of obtaining it.

B.5.RR:12 - Relations

  • B.5 coordinates inquiry and the next useful question. B.5.RA recovers the argument; B.5.RC recovers a needed construction.
  • B.1.1 clarifies the represented dependency relation. A.6.3.RT helps when the expression prevents the revision operation.
  • B.5.MPC connects physical, mathematical and computational contributions. B.5.MPC.R uses this reasoning revision to repair a failed connection.
  • B.3, B.3.3 and A.10 supply the claim-specific assurance and evidence conditions. C.11.DUA helps choose worthwhile additional checking or information.
  • C.39 develops a missing way of obtaining a result. Revision may supply the construction from which that work begins.

B.5.RR:End

B.5.FM - Construct a Model for the Question

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

B.5.FM:1 - Problem frame

Use this pattern when you need to reason about a situation or formal problem but do not have an account on which to perform the needed inference. You may know relevant laws, facts or techniques while being unable to choose the participants, distinctions and relations that make them useful here.

Begin with what the answer should help you understand or do, the observations or formal rules available, and enough subject knowledge to propose a relation. Construct a provisional model, obtain a consequence and use it to answer the question or locate the next missing contribution. A sketch and a limiting argument may provide that first result.

“First” means the first usable model for this question. An earlier model, an analogy or a specialist’s explanation can supply its starting material. Use an adequate existing model when construction is unnecessary. If an available concept is understood but its correspondence to the situation is missing, B.5.4 supplies that interpretation work. If the required inference needs subject knowledge you cannot recover, obtain that contribution.

B.5.FM:2 - Problem

A request to “model the system” leaves important work unstated. Which things may change separately? Which interactions matter? What may be treated as fixed? What operation on the proposed description could answer the question?

An early description can hide the decisive relation. A device described by one temperature conceals a heat-transfer restriction inside it. A draining vessel described only by liquid height conceals the effect of trapped air. Counting all possible binary strings ignores a rule that forbids some continuations.

A model becomes useful when its selected distinctions and relations permit an inference whose meaning can be returned to the question. Constructing that possibility is part of the reasoning.

B.5.FM:3 - Forces

ForceConsequence for construction
A question selects what matters; a model can reveal that the question needs changing.Keep the receiving use visible while allowing the construction to expose a better question.
Familiar concepts provide useful relations; the situation may need a new combination.Reuse what works and explain the connections introduced between contributions.
A detailed description can be expensive to build and difficult to reason with.Add a distinction because its omission changes a needed consequence.
A cheap consequence can guide action before the model is fully developed.State what supports that consequence and which unresolved choices matter to its use.
Different representations expose different operations.Choose or change the expression while constructing the inference.

B.5.FM:4 - Solution

Construct a model by selecting distinctions, proposing their relations and making those relations usable in an inference. Work can move back and forth between these contributions. Keep the question and the consequence connected as the model changes.

B.5.FM:4.1 - Recover the contrast the answer must resolve

State what alternatives the answer should distinguish: whether an intervention can reach a target, which arrangement could explain an observation, how many constructions meet a rule, or what condition prevents a result.

Start from the rule, observations or arrangement that bear on the question. Inspect a small instance when it can expose a consequential difference. Describe the supplied facts and the account you propose. If the construction reveals a better question, ask what its answer would contribute to the investigation already in hand.

If the participant cannot express what differs or matters, B.5.EA helps articulate that contribution before model construction. Return here when the resulting distinction permits a question or contrast; do not require this preliminary work when the contrast is usable.

When the account is clear but leaves you unsure which question matters, the scheme comparison in :4.2.1 can expose a useful distinction. A discovered question may have an adequate answer; use it without requiring a larger model.

Determine what the recipient needs from you. An existing answer may settle a decision. A request for a model they can use under changed conditions also needs the participants, relations and limits that let them derive the new consequence. Where the question is fixed, retain any newly discovered question for the work it can inform and return to the one commissioned. C.11.DUA helps when obtaining more information or refining a model competes with acting on a sufficient answer.

B.5.FM:4.2 - Choose the participants and distinctions

Follow what can be transformed, exchanged, combined, constrained or observed. Propose the objects and relations needed to describe those changes. For a physical situation, an interaction may cross the first proposed boundary: air surrounding a vessel or a path through its casing can matter to the answer.

When the choice of scale is yours, start with what the recipient has to judge. Hold a part fixed and vary how the whole uses it, or hold a reported total fixed and vary the arrangement that produces it. Follow the constituents whose variation could change the answer or its explanation. Determine what counts as a constituent for each kind involved. A proposed Method has operations, a particular job has performances, and the evidence for what happened may come from a record of that job. Connect them where the question requires it. C.39.SA:4 develops this choice.

Try treating some of the remaining situations alike. If they require different answers, different grounds the recipient must explain, or actions that cannot be chosen on the available information, recover the lost distinction. If the order asks for one workable choice, a choice shown to work in every situation left open can suffice even when other choices differ. An object can need several quantities, and several objects can sometimes be represented together.

For a question about permitted continuations, A.3.3 helps construct a sufficient state description. For an observation, C.16 helps connect the quantity of interest to what the observation reports.

B.5.FM:4.2.1 - Let a conceptual scheme expose a useful question

Start from what the account is meant to enable, even when the question is provisional: prepare a workshop, interpret an effect or improve a construction. Choose a small, understood conceptual scheme whose relations could reveal a consequential distinction. Here a scheme means related concepts and the inferences their relations permit. For example, connecting a learner’s attempt, what an instructor can observe and the feedback required can expose a question that a seating plan leaves unanswered.

State the possible contribution before expanding the account. Recover the selected relation’s participants, conditions and a consequence; B.5.TU helps if that theoretical contribution is unfamiliar. Use B.5.4 to construct its tentative correspondence to the case. Keep what the source account says distinguishable from what the scheme suggests adding. A sketch or ordinary question can carry the correspondence.

When a relation appears absent, distinguish the following outcomes:

What is availableUseful continuation
The account supplies the relation and answer.Use them.
The relation applies, but a participant or condition is unknown.Ask whether resolving it could change the work.
The relation does not apply under the scheme’s conditions.Drop that question or try an applicable scheme.
The expression cannot represent the needed distinction.Change the expression or scheme; A.6.3.RT helps when that change needs work.
The scheme conflicts with a consequential part of the case.Reconsider the correspondence or assumption before using its consequence.

An empty position in a diagram establishes none of these outcomes by itself. If adapting a scheme changes a relation’s meaning, state that change and reconsider the conclusions that depend on it.

Compare plausible answers when that cheaply reveals what is at stake. A difference that changes the continuation gives a reason to inquire. Use the decision criterion the work requires. For a guarantee, a rule or a bound may establish that one action works in every admissible situation. When the recipient can observe a condition before acting, assess the resulting choices together. For a decision based on risk or expected outcome, apply the agreed measure. If the choice is still open, formulate what would help in the participant’s working language: a condition, construction, distinction or bound. The benefit can concern a later inquiry or a new method. C.11.DUA governs whether obtaining the answer is worth its burden.

Use the resulting answer or continue constructing the model it needs. A subject specialist or AI can supply a relation, correspondence or calculation; the required knowledge and access depend on that contribution.

B.5.FM:4.3 - Build relations that can produce a consequence

Use subject knowledge to propose how the selected participants interact or which operations are permitted. Explain how each proposed relation answers part of the question. A physical interaction law, a mathematical formation rule and an execution rule supply different kinds of premise.

When the question is causal and the proposed mechanisms need to be expressed as comparable models, use C.28.CM to construct and challenge those models. Keep the outcome and time horizon comparable across the accounts, together with any intervention being considered. Make the variables, mechanisms, assumptions and material alternative influences explicit. Return each model with its useful consequence or the premise needed to derive one; continue with inference and criticism in :4.4–4.5.

An annotated sketch or ordinary explanation may suffice. Use a supplied or readily constructed model when it supports the needed inference.

Starting material can come from more than one source. A known model may need to be altered before it becomes a useful analogy. Recover the corresponding participants and relations, then examine the changes needed in the situation. The construction can improve both the proposed model and the understanding of what it represents.

Keep coupled choices compatible. If liquid leaving a closed vessel increases the space occupied by trapped gas, a pressure calculation must use that changed space. If two classes of formal objects permit different extensions, their counts must remain distinguishable until the extension is performed.

Use an expression that lets you carry out the next inference: an annotated sketch, a table of permitted operations, equations or a computational construction. When a physical surrogate is used as the model, establish which results of observing or testing its material behavior can inform the original situation. C.29 helps construct and use a mathematical representation, including when no mathematical object has been selected. A.6.3.RT helps when the expression prevents the operation.

B.5.FM:4.4 - Obtain the smallest useful consequence

Derive a consequence at the reach the question needs. Working one case can settle a question about that case, exhibit a feasible construction or refute a universal claim. For a consequence claimed across a range, identify a rule or bound that covers the admissible variations. In :5.3 the rule for extending any valid prefix supplies the counts at subsequent lengths. Computing the count at length four illustrates one use of that rule.

Show which premise makes the consequence follow. If calculation or simulation is needed, C.29.2 supplies computational formulation and C.29.3 supplies realization. If the reasoning is available but difficult to follow, B.5.RA helps recover the decisive inference.

Return the consequence to the question. A limiting value can rule out an intervention under the model’s assumptions. A constructed recurrence can supply a count. An unresolved interaction can turn “calculate the system” into a request for another contribution.

B.5.FM:4.5 - Examine a choice that can change the answer

Challenge the model at a consequential choice: an omitted interaction, a grouping of cases, a fixed quantity, an operation rule or a correspondence. Use an available observation, a contrasting case or an inexpensive trial when it can distinguish the remaining alternatives.

An operation performed on a model establishes a model consequence. Reliance on a physical prediction also depends on the physical correspondence and conditions. Obtain the assurance needed for that receiving use; a sufficient conditional answer can remain useful while a premise is unresolved.

When a discrepancy has several possible explanations, retain those possibilities until the question needs them distinguished. B.5.MPC.R helps repair a failed physical, mathematical and computational connection. B.5.RR carries a changed premise through affected reasoning.

B.5.FM:4.6 - Apply the result and choose the continuation

Use what the model supports: make a design choice, reject an option, construct an object, specify a calculation, select an observation or revise the question.

Try the proposed use of that consequence. For example, sufficient average delivery can settle a capacity question; continuous supply also depends on delivery times, consumption and available stock. If the intended action needs such a further relation or condition, keep the supported answer and identify the missing contribution. Supply the assumptions another contributor needs to use the result.

Name a missing contribution by the result it must provide. For example, ask which heat-transfer path a proposed change affects, which state distinguishes two continuations, or which operation produces the needed formal object. A.15.9 helps obtain that contribution from another practice.

Keep an explanatory trace when later use or collaboration requires it. A new model-building move can also become material for C.39’s method development and C.36.RP’s shared-method renewal when that further work is needed.

B.5.FM:5 - Archetypal Grounding

These constructed cases expose different model choices. Their calculations establish conditional consequences.

B.5.FM:5.1 - Choose the heat path before commissioning a calculation

An engineer asks whether a stronger external fan can bring an overheating component below 65 °C. Inspection finds the component attached to a metal case through a pad; the fan blows over the outside of the case.

Trace the proposed path from component to case and then to the surrounding air. Keep the component, the case at its attachment and the air distinguishable: their temperatures can differ, and the fan acts on one part of that path.

Try a steady account with constant component heating, all generated heat passing through the pad, and an unchanged linear conductance between component and case. Carrying the same heat per second then requires the same temperature difference across that path. Treat outward case-to-air transfer as driven by temperature difference. A steady case receiving positive heat must remain warmer than the air.

Use supplied steady readings of 80 °C at the component, 25 °C at the case attachment and 20 °C in the air. The component-to-case difference is 55 °C. Even ideal external cooling of the case to the air temperature leaves the component at 75 °C under these assumptions. The fan-only proposal cannot reach 65 °C in this model.

The result directs work toward the component-to-case contact, another heat path or reduced heating. Airflow onto the component would change the assumed path; temperature-dependent heating or conductance would change the fixed-difference argument. Measurement uncertainty matters to the real-device conclusion.

A useful next request is: “Can this component stay below 65 °C after changing its contact to the case, and which observations distinguish the relevant heat paths?” The model supplies that request before a detailed equation set is commissioned.

B.5.FM:5.2 - Include the air when modeling liquid discharge

Consider a rigid vessel with a liquid outlet near its bottom and trapped air above the liquid. The question is whether enlarging the outlet will allow most of the liquid to drain. A model based only on liquid height can miss what changes when liquid leaves.

For a first conditional account, assume that no air enters and the liquid is incompressible. Treat the trapped air as an ideal gas at constant temperature and fixed amount. Consider slow flow whose inertia is negligible and whose motion is dissipated by resistance at the outlet. Include the gas volume and absolute pressure, the liquid height above the outlet and the outside pressure. Liquid leaving increases gas volume and lowers gas pressure.

At the no-flow equilibrium, the internal pressure at the outlet equals the outside pressure. For the following rough calculation take liquid density as 1,000 kg/m³ and gravitational acceleration as 10 m/s². Initial liquid height is 20 cm, trapped gas volume is 100 cm³, vessel cross-section is 100 cm² and initial gas and outside pressures are both 100 kPa.

Let q be the discharged volume in cm³. The gas occupies 100+q cm³; liquid height is 20−q/100 cm. The isothermal gas relation and hydrostatic head give the equilibrium equation:

10000/(100+q) + 0.1*(20−q/100) = 100   [kPa]

The positive solution is about 2.039 cm³, with gas pressure about 98.002 kPa and liquid height about 19.980 cm. In this slow-flow account, the discharge approaches a stop after a small volume. Changing outlet size changes resistance and the approach to equilibrium; this equilibrium balance applies while air entry and inertial effects remain negligible.

Allowing ambient air to reach the gas space changes the model: gas pressure can remain near outside pressure as liquid leaves. Air entering through the outlet, gas-temperature change, vessel deformation or appreciable capillary pressure requires another account. The result is the distinction between an outlet-flow restriction and a gas-replacement restriction. Investigate the air path before treating outlet enlargement as the answer.

B.5.FM:5.3 - Construct classes that permit a counting inference

We need counts of binary strings at several lengths under a rule that forbids consecutive 1s. Use length four as a small case. The question supplies symbols and a restriction, but no recurrence.

Start with short valid prefixes and examine their allowed next symbols. A prefix ending in 1 may receive only 0. A prefix ending in 0 may receive either symbol; the empty prefix has the same two permissions. Group prefixes by those extension permissions.

Let r_n count valid length-n prefixes that are empty or end in 0; let b_n count those ending in 1. Every valid prefix can receive 0, while only the r_n prefixes can receive 1:

r_0 = 1, b_0 = 0
r_(n+1) = r_n + b_n
b_(n+1) = r_n

The pairs for lengths 1 through 4 are (1,1), (2,1), (3,2), (5,3). There are eight valid strings of length four.

The inference works because each extension produces a distinct string, deleting its final symbol recovers its unique predecessor, and the two resulting classes exhaust the permitted cases. The total alone does not tell how many prefixes permit appending 1; keeping the two classes makes that operation possible.

If the restriction changes to “no three consecutive 1s”, the same grouping loses a needed distinction. Separate prefixes with zero, one or two trailing 1s and reconstruct the permitted transitions. This change identifies what the state must retain; the subsequent recurrence or program is a further computational contribution.

B.5.FM:5.4 - Find the limiting relation in a workshop plan

Twelve people have accepted a 60-minute workshop. There are twelve seats and one instructor. The proposed arrangement gives each person a four-minute attempt observed by that instructor, then two minutes of the instructor’s feedback before the next attempt begins. The initial plan lists attendance and materials.

Use the relation between attempted action, observation and feedback to ask whether the intended practice can occur in the session. The sequential arrangement requires 12 * (4 + 2) = 72 minutes before any introduction. The next question is which arrangement can supply the intended practice and feedback within the available time. Reducing attendance, increasing duration or changing the learning arrangement have different consequences. Merely pairing learners supplies the required feedback only if they can provide that contribution.

Now suppose twelve independent stations provide the required task-specific feedback and can be used concurrently. The serial calculation no longer describes the work. If the order allows station feedback and each station supplies the four-minute attempt and two-minute feedback in parallel with the others, assign one learner to each station for the same six minutes. Compare the remaining activities with the 54 minutes available. If the order specifies observation by the instructor, feedback from the stations alone leaves that part of the order open. If the intended event is instead a demonstration with no individual practice, the individual-feedback relation does not impose that practice on it. Clarify the event’s purpose before treating this scheme as applicable.

The same question-forming move can use a measurement scheme: a shared column label, such as temperature, leaves the relevant quantity, observing conditions and aggregation to be recovered before combining records. If the existing documentation establishes their suitability, use that answer. The scheme supplies a question, not a compulsory new measurement.

B.5.FM:6 - Bias-Annotation

The examples use small accounts so that the reader can inspect the construction. Complex systems can require learned representations, instruments and multiple specialist contributions. Their suitability depends on the inference and available means.

Source studies of human scientific work motivate some construction moves. Their transfer to AI agents concerns the work to perform and the result to supply; it does not assert identical cognitive mechanisms or learning requirements.

B.5.FM:7 - Conformance Checklist

  • The question identifies a consequence that would help a receiving use.
  • Selected participants and distinctions support that inference.
  • Proposed relations have interpretable participants, conditions and appropriate subject grounds.
  • Coupled quantities and operation rules are used consistently.
  • At least one useful consequence is worked through, or the missing contribution is identified.
  • The consequence is returned with the conditions needed for its application.
  • Further refinement, observation or assurance answers a remaining question that matters to use.

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

Recognizable failureRepair
Fit a model whose variables cannot express the proposed intervention.Recover the participants and relations through which the intervention could change the result.
Copy a familiar analogy while its operation has a different meaning in the case.Construct the needed correspondence and test the transferred consequence.
Aggregate cases before performing an operation whose permissions differ between them.Keep the permission-changing distinction until that operation is complete.
Increase simulation detail while an omitted interaction determines the answer.Obtain a limiting or contrasting case that exposes that interaction.
Give a specialist a broad modeling request that leaves the needed result unclear.Supply the provisional account and ask for the contribution that would change the next decision.

B.5.FM:9 - Consequences

A first model can turn an open request into an answer, a bound or a well-formed next contribution. It makes model-building choices available for criticism and allows others to continue the reasoning.

Its cost is the work of selecting and connecting distinctions. Keep an adequate simple account while its conditions suffice; develop it when the receiving question exposes a consequential limitation.

B.5.FM:10 - Architectural Rationale

Model construction and model use often develop together. Trying an operation reveals which distinctions are missing, while the revised distinctions permit another inference. The method therefore keeps selection, relation construction, expression and consequence in one connected reasoning move.

The heat case depends on separating temperatures and locating an intervention along a path. The vessel case requires coupling two interacting media. The counting case creates classes from permitted operations. Their shared method is the construction of an inferentially useful account; their subject premises remain different.

B.5 coordinates the overall inquiry. This method develops its model-building contribution. B.5.4 gives a narrower entry when an available concept needs a situational interpretation. C.29 supplies mathematical representation choice. A.3.3, C.16 and A.6.3.RT supply state, measurement and expression construction when those questions occur within model building.

B.5.FM:11 - SoTA-Echoing

Construction as a reasoning contribution. Adapt Nersessian’s 2025 account, §3: a useful analogy may have to be built, with its correspondence revised during use. The present method applies that contribution in :4.2–:4.4: select distinctions through a needed consequence, build compatible relations and use a small case to revise the correspondence.

Reusing a calibrated domain model is cheaper when it expresses the proposed change. Constructing another account becomes worthwhile when the available model cannot express a consequential interaction or operation; the vessel and prefix cases show those failures.

Qualitative consequences and application. The ISLE explanation by Etkina and Brookes connects observation, proposed explanation, predicted consequence, testing and application, first qualitatively and then quantitatively. Use that progression in :4.4–:4.6 when a physical prediction needs examination and application. A formal construction can instead proceed from its formation rules and a derivation, as in :5.3.

Finding a question through a scheme. Compare two practical starting points: follow a provisional question into a small model (:4.1–:4.5), or use an understood scheme to expose a question (:4.2.1). Give both routes the same workshop facts, knowledge of the attempt/feedback relation and a hand calculation. The first can begin with “Can this plan provide the intended practice?”, select the instructor’s time, derive 72 minutes and revise the arrangement. With independent stations it changes the model and withdraws the serial restriction. Both routes can obtain these results.

Use the scheme-based entry when an apparently adequate account, such as a seating plan, leaves the relevant question unclear. Its applicability table distinguishes an unknown relation from one that is inapplicable, inexpressible or in conflict with the case. In :5.4 the demonstration-only variant drops the individual-practice question instead of treating it as a missing provision. Recovering and trying a scheme has a cost: use the direct construction when the distinction and question are clear.

Gentner and Hoyos, Analogy and Abstraction, 2017, §§1.2–2, provide a historical structural-alignment account. Adapt relational rather than name matching in :4.2.1; the reviewed transfer effects depend on their task and comparison conditions.

Keet and Khan, Discerning and Characterising Types of Competency Questions for Ontologies, 2024, §§3–4, contribute purpose-sensitive questions and limits of a scheme’s expressiveness. Adapt those distinctions in the applicability table without imposing their ontology-specific taxonomy.

Vagnino and Walker, Schema drift, 2026, supplies a limitation: repeated comparison can change relational judgments, with rival explanations unresolved. This motivates the return to a changed relation.

Reconsider the scheme-based entry when it repeatedly produces irrelevant questions or when the direct construction supplies the needed distinction. Repair the correspondence or continue from the adequate question before broadening the inquiry.

Subject premises of the physical cases. OpenStax, University Physics 2, §1.6 supplies the conducting-layer and convection relations. Volume 2, §2.1 supplies the isothermal fixed-amount gas relation; Volume 1, §14.1 supplies the hydrostatic pressure relation. The chosen arrangements, simplifications and receiving questions are the present constructions.

Reconsider the construction approach when another supplies a more useful model at comparable effort, or when a recurring difficulty calls for an additional model-building move.

B.5.FM:12 - Relations

  • B.5 coordinates inquiry; B.5.4 constructs a supplied concept’s correspondence to a situation.
  • C.28.CM develops missing causal relations and alternatives, returning a conditional consequence or unresolved premise to the general model-building question.
  • C.29 selects and uses a mathematical representation. C.29.1, C.29.2 and C.29.3 supply transfer, computational formulation and realization.
  • A.3.3, C.16 and A.6.3.RT supply state, measurement and expression construction.
  • B.5.RC and B.5.RA recover an available construction or argument. B.5.RR revises reasoning; B.5.MPC.R repairs a failed joint physical answer.
  • C.11.DUA governs worthwhile further effort; A.15.9 obtains another practice’s needed result.
  • C.39, C.36.RP and E.10.INT support later method development, shared-method renewal and recovery of the interest guiding further work.

B.5.FM:End

B.5.MR - Compare Models by Refinement and Abstraction

Type: Method pattern Status: Stable

B.5.MR:1 - Problem frame

Use this when you need a model to determine something left open by another model, or need an abstraction that leaves some determinations open while retaining a useful conclusion. The practical question is which answers remain admissible and which conclusions can still be used. Two specifications of a design, two accounts of a method or two editions of the rules for constructing a model can each raise that question.

A useful first result identifies the inquiry, the assertions preserved and the answers admitted by each model. A strict refinement excludes an earlier admissible answer. A strict abstraction admits an answer excluded before, so a conclusion that depended on that exclusion needs reconsideration. When deciding between theories that answer different questions, B.5.TC helps identify a comparable use. When the change is in the actual system, examine the changed system directly.

B.5.MR:2 - Problem

More detail can narrow a choice, leave the answer unchanged, or contradict an earlier commitment. Omitting detail can leave the same assertions recoverable or lose a premise the reader needs. A change of wording, a new unit or a newly chosen discipline may also change what the reader takes the question to mean. How can the reader construct and compare models while establishing what each change permits them to infer?

B.5.MR:3 - Forces

A practitioner needs a comparison in ordinary terms. A consequential claim of preservation must cover all remaining possibilities. Model editions can use different representations. An apparent exclusion can arise from dropping a difficult case, changing the meaning of a quantity or switching from a design condition to a report of actual performance. An abstraction can serve a wider inquiry while losing a conclusion needed for a particular decision.

B.5.MR:4 - Solution

Begin with one question that both models answer. Which designs, executions or other alternatives does each model admit? To refine a model, choose something it leaves open. Show that at least one alternative remains and that every remaining alternative satisfies the earlier assertions under the chosen interpretation. To abstract a model, decide what to leave open and apply the same test with the starting model on the concrete side. The answers tell you whether the difference is strict and which conclusions still hold.

B.5.MR:4.1 - Recover the assertions and the answers left open

Identify the modeled entity or the range of candidate applications left open, the inquiry, and the conditions under which each answer will be read. Keep the force of the claims explicit when it matters. Permitted values, predicted values and observed values answer different questions. For a claim-bearing model recover its content, EntityOfConcern and effective interpretation under C.2.1. For a physical model establish which observations on it warrant which inference about the target. PHY.1 in Physical Thinking gives the similarity conditions for transferring a selected observable across changes of scale or operating conditions.

Recover what the model asserts about the participants: which quantities may vary, which relationships must hold, which designs qualify or which performances a Method permits. The relevant subject Method supplies their types and grounds. A stated condition may be an assertion of the model or an assumption under which it applies; distinguish these when they change the answer. If the expression leaves its assertion unrecoverable, use F.19 before treating it as a model at a higher abstraction level.

A completion is one way of settling what the model leaves open for this inquiry while satisfying its assertions. A candidate design, a possible behavior or a structure satisfying stated axioms can serve as a completion. The inquiry determines what answer can be read from it. Several different designs can give the same answer. A completion need not have been observed, built or authorized for use. Include probability claims when the inquiry concerns likelihood. Two models can allow the same outcomes and assign them different probabilities.

B.5.MR:4.2 - Test preservation and strictness

Identify the completions each model admits. Call the proposed refined model C and the model whose assertions it must preserve A. When their languages or detail differ, explain how every completion of C is read in the terms used for A’s answer, and why that reading serves the inquiry. Test that a completion of C exists and that each completion of C, so read, satisfies A’s assertions. When these tests hold, C refines A, and A is an abstraction of C, for this inquiry and interpretation. The two names give converse directions of the same comparison.

This relation includes equivalent answers. To establish strict refinement, also identify an answer admitted by A that no completion of C can produce. Only with this strict difference call C more concrete than A and A more abstract than C. Show a surviving completion of C so that exclusion cannot be attributed to inconsistent assertions.

If a model admits no completion, examine which assertions make it infeasible. If both models admit none, neither supplies a feasible answer. When each admits at least one completion, equal sets of observable answers establish agreement for this inquiry. If each admits an answer the other excludes, the models are incomparable by refinement. They may still share answers. If they share none, their assertions conflict under the common reading. When feasibility or the correspondence is unknown, identify what would settle it.

Within a chain of models that pass the feasibility and preservation tests under a common interpretation, models that admit the same answers share a level for this inquiry. On different branches, models can give the same answer and impose incompatible constraints. Test preservation separately for the pair in question. A different inquiry can distinguish models the first one treated alike. Before composing comparisons across languages, establish how their interpretations compose.

A claim of greater accuracy needs a reference and an error criterion. A bound can establish accuracy against a mathematical reference. For a claim about accuracy on an actual system, use observations under the relevant conditions. Refinement alone supplies neither empirical accuracy nor evidence of actual performance.

B.5.MR:4.2.1 - Refine a model for a further decision

Identify what the next decision needs determined: a value, a construction choice, a permitted performance or another answer left open. Obtain the subject grounds for that determination. Add or bind the corresponding assertion and compare the resulting model with the starting model by section 4.2. Explain the preserved assertions, show a surviving completion and identify any excluded answer.

An added assertion can repeat what already follows. For that inquiry the two models then admit the same answers. If the new model admits a previously excluded answer or contradicts an earlier assertion, identify what changed and reconsider the claim of refinement.

B.5.MR:4.2.2 - Construct or select an abstraction

Start from the conclusion the recipient must draw or the choice they must make. Try releasing a determination in the starting model. What additional completion would this admit, and could it change that conclusion or the grounds the recipient has to give? When the model describes several parts, try varying their arrangement while keeping the proposed facts about each part. Retain a relation between them if it rules out a joint possibility that would change the answer. Construct an abstraction from the determinations still needed, or select one whose assertions preserve them.

Compare the starting model as C with the proposed abstraction as A under section 4.2: C must have a completion, and every completion of C must satisfy A under the established interpretation. Then check the needed conclusion over the answers A admits. Identify any prior conclusion that no longer follows and the determination on which it depended; report when no conclusion is lost for the inquiry. If the needed conclusion is lost, retain that determination or choose a different abstraction.

Several abstractions can serve different inquiries about the same starting model; several concrete models can refine one abstraction. The comparison supplies no unique inverse construction. Leaving a variable open also does not prove that a result observed at one value holds at every newly admitted value. Wider empirical or methodological claims need their subject grounds. Retaining the same assertions in clearer wording is clarification of their expression; it does not change this model order.

B.5.MR:4.3 - Read the levels of model abstraction and refinement

Read L0 → L4 as levels of model abstraction and L4 → L0 as levels of model refinement. Both names describe one order. A more concrete model preserves the earlier assertions and rules out an answer the more abstract model allowed. Abstracting a model or refining a model is the work of constructing or selecting the model on the chosen side of that comparison. In a chain of applications the five names below identify what each model specifies.

Level, from more abstract towards more concrete modelsWhat the model specifies
L4, foundationalA formal or computational construction and the choices its own conditions permit.
L3, transdisciplinaryA principle interpreted across eligible disciplines. Bind it to the construction wherever that interpretation is warranted.
L2, disciplinaryA subject discipline and the professional method, constraints or interpretation used there.
L1, localConditions shared by a particular setting or recurrent local population.
L0, individualThe identity of the particular entity or occurrence being modeled. Its unobserved characteristics can remain open.

Use the levels when deciding what a result establishes. State the decision and what the model for that decision must specify. Identify the model actually available. An L0 model that identifies a delivery can contain its planned arrival. To decide whether that delivery met its deadline, use evidence that relates its arrival to the deadline in force. An authenticated indication that it arrived before the cutoff can settle the decision even when its exact arrival time remains unknown. To decide whether a scheduling rule at L2 guarantees all its deadlines, examine why the rule covers every permitted schedule. One admissible schedule that misses a deadline defeats the claim that every permitted schedule meets its deadline. For a target of 95 percent of actual deliveries on time, assess the eligible deliveries in the specified population and period. Count a late arrival when it occurred there. A calculation using the rule can check its consequences while leaving open who designed it. Carry the result to the decision through the grounds for that particular inference in C.39.QR:4.2–4.3. Accept the conclusion those grounds support and identify what would settle the outstanding claim.

Check each pair for one inquiry under §4.2. Establish which earlier assertions every remaining design or permitted performance satisfies. Show that at least one remains. If the step is strict, name an answer that can no longer be obtained. The same test applies to two models of one design or method, including when both are disciplinary models.

If a site adopts a disciplinary rule with the same interpretation and adds no constraint on the action in question, write “the site uses the L2 rule unchanged.” The L1 practice model records the site’s adoption of the rule for recurring work. If asked at what level the rule specifies the permitted action, keep L2. Claim a further level of refinement for that action only when the local model excludes a previously permitted answer. Several strict refinements can occur within one named level. If a rule permits a check at either site, specifying the first site excludes the second answer to “Where may this check take place?” If both sites have to be checked, dropping one abandons an obligation.

A disciplinary model can prescribe a method, a local model can specify how it may be used at one site, and an individual model can describe a particular performance. Evidence that the work occurred and followed the rule must come from that performance. Two models of a system can also stand in strict refinement at the same physical scale. Moving to a constituent invokes the constructive relation under B.1. A change of composition scale gives a refinement claim only if the models can also be read for the same inquiry and pass §4.2. Use C.39.SA:4 if choosing which constituents and which model distinctions to keep is itself part of the work.

Core, DPFs and LPFs supply models that can participate in such comparisons. A publication or discipline does not itself have one abstraction level. Binding a parameter can refine a model without changing its language; changing professional vocabulary can preserve all its admitted answers. A richer representation language can also express a model applicable to more situations. Compare the interpreted assertions for the inquiry.

B.5.MR:4.4 - Compare models of models by the same test

A metamodel states conditions on admissible models, such as which field or relation can occur and how it is interpreted. Conformance asks whether a particular model satisfies those conditions. Refinement of a metamodel compares two such sets of conditions for the same inquiry about admissible models. A model can conform to both editions. A model conforming to a metamodel and that metamodel conforming to higher-order construction rules gives two separate conformance judgements. C.37.MM helps keep their participants and governing editions recoverable when the models are passed on.

B.5.MR:5 - Archetypal Grounding

A project commissions a temperature recorder for one installation. The earlier specification permits records at whole-minute intervals of one or two minutes. The new specification permits only one-minute intervals and preserves the units, clock and operating conditions. A one-minute record is still eligible. A two-minute record is excluded. For the inquiry about permitted sampling intervals, this is strict refinement. If the recipient asks only whether every hour contains a reading, both specifications give the same answer. Whether the installed recorder met its specification last night requires observations of that recorder.

Suppose a receiving comparison needs to know whether each recorder specification ensures at least one reading in every hour, without deciding between one-minute and two-minute intervals. Reuse the earlier specification as an abstraction of the one-minute specification. Every completion of the latter still satisfies the former, and both permit a completion. The abstract specification retains the hourly conclusion over all its permitted intervals. It no longer entails that the interval is one minute. For an inquiry that distinguishes the intervals this is strict abstraction. For the hourly inquiry the answers remain equivalent.

Now consider two recorders required to use the same interval, either one or two minutes. Describing each by its allowed intervals and allowing the settings to vary independently admits the former pairs (1,1) and (2,2), as well as (1,2) and (2,1). For the inquiry about permitted pairs this is a strict abstraction. Each recorder still supplies an hourly reading under either setting. If the recipient must also be sure the intervals match, retain the common setting while leaving its value open. Both comparisons concern the same two recorders. The difference lies in what the models permit.

A work method screens requests under a criterion and then refers unresolved ones for a second judgement. A local revision adds a deadline to the referral while preserving the screening rule. A referral after the deadline was admissible under the earlier timing rule and now falls outside the local prescription. A second revision silently accepts some requests previously requiring referral. Compare that changed decision with the original rule before relying on it. An excellent record of one compliant case cannot settle the claim for the newly admitted cases.

To compare the local method with methods at other sites for their screening and referral duties, return to the prescription without the local deadline. It is an abstraction if every performance permitted by the local prescription satisfies it and at least one such performance is possible. The referral duty remains; the local deadline no longer follows. Removing that deadline from the model does not withdraw an actual site’s deadline or establish that its workers performed the referral. Those are different assertions needing their own grounds.

B.5.MR:6 - Bias-Annotation

A vivid individual case can conceal what the earlier assertion covered. Start with the intended inquiry and an admissible alternative. Looking only for a stricter result can hide agreement, a real conflict or uncertainty. Looking only for a simpler abstraction can conceal the loss of a conclusion the next decision needs.

B.5.MR:7 - Conformance Checklist

  • The inquiry, participants, force, assertions and common reading are recoverable.
  • A refinement claim has at least one admissible completion of C and covers every completion of C for the inquiry. An abstraction claim uses the converse comparison.
  • Call a model more concrete or more abstract only if the comparison exhibits a distinguishable answer that is admitted on the abstract side and excluded on the concrete side. Report when the models give the same answers for the inquiry or are incomparable under refinement.
  • The receiving conclusion has been checked over the answers the selected model admits. Any reported loss identifies the conclusion and its missing premise; absence of loss remains a possible result.
  • Claims of conformance, parthood, occurrence or empirical accuracy use the grounds for their own relations.

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

A longer document may repeat the same assertions in a more useful form. Test which answers have changed. A project can also specify an individual that does not exist. If no candidate survives an attempted binding, reopen the identification.

A model abstracted from one successful performance can admit other performances whose success has not been established. Use the subject Method to justify the wider claim before relying on it. A simpler drawing or a shorter paragraph can preserve the same model; compare its assertions before assigning a different abstraction level.

B.5.MR:9 - Consequences

A receiving practitioner can reuse preserved assertions, determine an open choice, or reopen a choice without losing track of the conclusions that depend on it. The comparison locates the premise to revisit when a model, correspondence or inquiry changes. A teacher can ask a learner to construct each direction and explain the retained and lost conclusions on an unfamiliar application.

B.5.MR:10 - Architectural Rationale

One comparison serves many kinds of modeled entity because it concerns the assertions a model makes for an inquiry. Its converse supplies abstraction while leaving the construction of a suitable model to the receiving need and subject grounds. Kind-specific composition, physical similarity and performed work retain their own tests. This division lets the same model answer questions at different scales without assigning its file or language a single level.

B.5.MR:11 - SoTA-Echoing

Specification theory compares models that satisfy stated sentences. It supports comparison across signatures when an interpretation specifies how a later model yields an earlier one. Under ordinary set inclusion, an empty class is included in every class. If the task is to show that a specification is infeasible, emptiness can settle it. A practitioner relying on a refined model to select a feasible design or action also needs a surviving completion. Section 4.2 therefore tests existence and preservation and asks which earlier possibility is lost when strictness matters. If the receiving inquiry changes what counts as the same answer, reconsider the interpretation and the comparison under it. This is a historical formal basis for the comparison. Sannella and Tarlecki, Specifications in an Arbitrary Institution, §§2 and 8

Probabilistic program development also uses refinement and abstraction as converse directions while retaining probability-sensitive guarantees. A comparison of outcome sets alone loses that information; section 4.1 therefore keeps the probability claims relevant to the inquiry. The formal construction is a historical anchor, not a claim that every Method is a probabilistic program. Morgan, The Generalised Substitution Language extended to probabilistic programs, §2

B.5.MR:12 - Relations

Use B.5.TC for comparisons of theoretical accounts, C.2.1 for the identity and grounding of epistemes, C.29 for a mathematical representation and its correspondence, B.1 for reasoning across holonic scales, and C.37.MM for coordinating and handing on models. E.10.D2 governs the use of a description as a specification. F.19 helps recover assertions from their expression. F.17:12.6 and F.18:4.5 give the names for both directions and their ordered levels.

B.5.MR:End

B.5.TU - Construct a Use of an Unfamiliar Theory

Type: Method-description pattern Status: Stable Normativity: Normative unless marked informative

B.5.TU:1 - Problem frame

Use this pattern when a theory offers a promising way to answer a question, but you cannot connect its objects and reasoning to an answer you can use. You may recognize the notation or reproduce a calculation while being unable to say what to supply, which operation matters, or what the result would let you do.

The work here is to construct one application of the theory. Begin with the question and the available account; obtain and interpret the contribution that question needs. The result can be a construction, prediction, explanation, bound or identified missing operation. A mathematical question about what can be constructed is a possible receiving use, as is an engineering decision.

First useful move. Begin with the question you are to answer. If choosing an application is part of the work, select a question the theory might settle. Find a source case or rule that could supply the needed contribution. Say what plays each required part in your case, work the decisive operation, and explain what its result changes. If you cannot make that connection, locate the first missing premise, interpretation or operation.

For example, a theory of composition lets you combine two operations. Does it let both consume one input, or does the combination require two separately supplied inputs? Recovering that distinction can change the proposed implementation before any code is written.

Use an adequate, understood application. A specialist or tool may supply a result you can interpret and use under its conditions. Reconstruct more of the theory when the needed application, criticism, adaptation or explanation remains unresolved.

B.5.TU:2 - Problem

A theory’s descriptions usually distribute its usefulness across definitions, examples, constructions and arguments. A reader may know each familiar word yet be unable to assemble these contributions for a new question. Conversely, a familiar calculation can conceal a change of question: the calculation solves the stated equations, while the receiving work needs a condition those equations omitted.

The difficulty has two connected parts. First, discover what the account makes possible and how to obtain that result. Then apply it to the question that justified the work. An answer can also reveal a new question or a useful limitation of the theory.

B.5.TU:3 - Forces

ForceConsequence for the method
A question focuses learning, while an unfamiliar account can change the question.Begin with one intended use and revise it when a construction reveals a consequential distinction.
A worked source case saves effort, while a new application changes some of its premises.Reuse the case and identify the changed contribution before carrying over its answer.
Operational fluency and understanding of derivations serve different work.Recover the depth needed to apply, criticize or alter the contribution.
A small case exposes connections, while a general claim reaches beyond that case.Keep the demonstrated use and the argument for greater reach distinguishable.
Available assistance can supply difficult operations, while the receiving use needs interpretation.Divide work at the missing contribution and retain the meaning of the returned result.

B.5.TU:4 - Solution

Connect the question, the theory’s constructive or inferential resources, and the use of the resulting answer. Enter where the unresolved connection begins; reuse contributions available. The following unfolding can be revisited when its result changes an earlier choice.

B.5.TU:4.1 - Choose an application worth constructing

State what an answer would help someone understand, obtain, predict, rule out or change. If the application is assigned, begin with that question. For a smaller case, identify the operation or inference its result will supply when you return to the assignment. The question “Can these two operations use the same input?” can expose a missing composition rule. Permission to use a formal input twice still leaves open whether a particular implementation can supply both operations.

Locate a source application serving that question or an account you could adapt. Identify which choices the source has made and which the present application leaves to you. When exploring a theory freely, try one of its characteristic operations and inspect what its result makes distinguishable or obtainable. That can give you a question worth pursuing in its own right.

Determine the contribution you need to learn or obtain. Applying a supported formula can need its inputs and use conditions; changing the formula can need its construction and argument. Explain the needed difference in work before selecting further study.

B.5.TU:4.2 - Recover what the theory lets you work with

For this application, identify the objects, relations, given information, permitted constructions and inferential rules. Read a definition together with an operation that uses it. Ask what can be supplied as an input, what can be produced, and which property or conclusion the rule establishes.

Follow the needed result backward to its prerequisites. Keep shared prerequisites and jointly required inputs visible. When a description names a construction without showing how to perform it, B.5.RC recovers its producing operations. When an inference remains unclear, B.5.RA recovers the reason and transitions needed by the receiving use.

Make an unfamiliar expression operative at the point of difficulty. Determine the arguments of a function, the objects related by a diagram, or the conditions under which a rule applies. A.6.3.RT helps construct a usable expression under the available notation.

B.5.TU:4.3 - Construct the application

Connect each consequential object and condition to the selected case. Some are supplied by observation or design; some are assumptions of the model; others belong to the theory’s mathematical construction. Keep their roles clear where they affect the conclusion.

Take the givens and the required output from the question. Where you must choose a representation, work back from what the recipient must be able to do. For example, a planner choosing an attainable combination of jobs needs to know which jobs fit together and which must be performed whole. For a question about excluding a target value, a bound over a larger set of plans can suffice if it covers every permitted plan, as in :5.3. For a theoretical question the construction can stay within the theory. For a physical use, identify which system, quantity or interaction the theoretical object represents. C.29 supplies the mathematical correspondence and the comparison of what it preserves, omits or introduces.

Compose the required operations. Check the connection between successive contributions: an operation’s output must supply the next operation’s required input. An integration procedure, for example, needs a function of its integration variable; a formula with unfilled path or parameter arguments does not supply that function.

If a source case cannot be adapted by the available rules, identify the missing contribution. Another formulation, a specialist result or a developed operation may supply it. A.15.9 supports obtaining and using bounded help; C.39 supports developing a way when none is known.

B.5.TU:4.4 - Obtain and inspect a consequence

Work the selected case far enough to answer the question or expose the gap. Use direct reasoning, a construction, a small computation or an available tool according to the work. Recover the step that makes the consequence follow and the premises it uses.

When computation is involved, interpret its inputs, operations and output. C.29.2 supplies a missing computational formulation; C.29.3 supplies the connection to the system performing it. A successful execution can help locate expression or implementation errors. The argument for what the computation establishes remains tied to the chosen formulation.

Compare with a simple consequence you can inspect when that comparison can reveal an error: a limiting case, a preserved quantity, an input count, a dimensional relation or a small enumeration. Select the relevant comparison; its purpose is to expose a possible failure in this application.

B.5.TU:4.5 - Apply the answer to the question

Read the answer back in the terms of the intended use. If it gives a construction, determine whether the required inputs and operations are available. If it gives a bound, use the exclusion or allowance that bound supports. If it gives a physical prediction, identify the model and operating conditions under which that prediction concerns the system.

Examine the correspondence at the point where it could change the action. Does a feasible mathematical answer violate a receiving condition? Could two cases treated alike by the formulation require different actions? If so, restore the distinction, change the formulation, or keep a weaker answer that remains useful.

For a new physical reliance, address the model assumptions whose failure could change that use. Reuse adequate knowledge and observations. Choose further checking or acquisition under C.11.DUA when their benefit and burden are the live decision; an unresolved stronger claim need not displace a sufficient conditional answer.

B.5.TU:4.6 - Return the result and choose the continuation

Return the interpreted answer and the conditions its receiver needs. An ordinary explanation, calculation or demonstration can carry it. Preserve a separate account when another participant or later use needs to reconstruct the application.

Stop when the contribution suffices. Otherwise identify what remains: a source explanation, missing operation, changed model, competing theoretical account or newly worthwhile question. B.5.RR follows the effect of a changed premise; B.5 coordinates a changed inquiry.

Use this result to choose the next learning or work contribution. When the work requires one participant to apply or alter the method independently, that capability needs its performed use under the relevant conditions. A supplied answer can serve work that does not require that independence.

B.5.TU:5 - Archetypal Grounding

B.5.TU:5.1 - Discover whether one input is enough

A practitioner wants to use two available operations, f: X -> Y and g: X -> Z, on one input. The letters name distinct atomic types. The question is whether the chosen composition rules can produce both results from that input.

In a cartesian account, a copying operation Delta_X: X -> X x X supplies the pair of inputs. First copy, then apply the two operations: (f x g) after Delta_X sends x to (f(x), g(x)). The input of the parallel operation is supplied.

Compare a resource-sensitive account generated only by f, g, identities, serial composition, tensoring and exchange of factors. Tensoring f with g takes X tensor X to Y tensor Z: it requires two inputs. Each given generator preserves the number of atomic factors, and serial composition, tensoring and exchange preserve that property. These rules therefore cannot construct X -> Y tensor Z. Supplying another input or adding an admissible copying operation changes what can be built. This is a result about the stated generated account.

Now apply the distinction. For a reusable data value interpreted through pure functions, both uses can receive that value. For a physical specimen consumed by an assay, obtain a physical way to supply what each assay needs. Dividing a specimen may supply those inputs if the assays admit the resulting portions. The word “copy” would leave that physical contribution unexplained.

The common method discovers the needed theory operation and returns its consequence to use. The cartesian construction and its contrast with tensor composition come from Baez and Stay, §2.3; the input-count argument makes the stated restricted case inspectable.

B.5.TU:5.2 - Use variational mechanics to answer a motion question

An engineer wants to understand what a variational account predicts for an ideal carriage coasting along a straight horizontal track. Adopt a one-dimensional nonrelativistic free-particle model: positive mass m, negligible resistance and no applied driving force during the interval. Its Lagrangian is L(q, v) = m*v*v/2. For this case, the action is the time integral of that quantity along a proposed path. The physical model supplies this choice of Lagrangian.

The mechanical rule selects paths of stationary action: for every small path variation that leaves the endpoint positions fixed, the first-order change of action must vanish. The calculation below finds that path and shows that, for this free particle, it minimizes the action. Reproducing the calculation uses differentiation and definite integration; the displayed action identity can also be obtained as a supplied mathematical result.

Let the carriage pass q=0 at time 0 and q=d at positive elapsed time T. Recover the operations hidden by “calculate the action”: choose a position function q(t), differentiate it to obtain velocity, evaluate L on those values, then integrate over time. This is the constructive use developed in SICM, §§1.3–1.4. The following one-dimensional case uses it.

Start with q_0(t)=d*t/T, and try paths q_a(t)=d*t/T + a*(t/T)*(1-t/T), where a is a length. Every path has the endpoint positions. Its velocity is v_a(t)=(d+a*(1-2*t/T))/T. Substitution and integration give S_a = m*(d*d+a*a/3)/(2*T). For m=1 kg, d=2 m and T=1 s, the straight path has action 2 J s; a=1 m gives 13/6 J s.

This comparison favors the straight path within the chosen family. The general argument is also short. For any continuously differentiable added displacement eta(t) that is zero at both endpoints, the cross term integrates to (m*d/T)*(eta(T)-eta(0))=0. Thus the change in action is (m/2)*integral(eta'(t)^2 dt), which is nonnegative. The straight path minimizes this action among those paths.

For a nonzero eta, write this positive change as K. Along the paths q_0+c*eta, the action is S[q_0]+c*c*K, whose derivative at c=1 is 2*K>0. Thus a nonzero displacement from q_0 cannot be stationary. The selected motion has constant velocity d/T.

The application has an interpreted answer: under the adopted model, passing those endpoint positions in that time entails constant velocity. A computational implementation must evaluate the path derivative in the velocity argument before integrating. It can reproduce the numerical action comparison; the displayed argument supplies the wider conclusion.

Suppose the engineer asks whether the same undriven model permits the two-metre trip to begin and end at rest. Its constant velocity would have to be zero throughout, so it cannot produce that displacement. This answers the feasibility question. If the engineer must also design a carriage that makes the trip, identify how it could accelerate and decelerate, model the forces available, and check the design against the required endpoints and time. A finer calculation in the undriven model would preserve the original obstruction.

B.5.TU:5.3 - Keep a useful bound when the optimizer cannot be enacted

A planner learning optimization must choose the highest-value combination of whole jobs that fits four available hours. At most one A-job is available, taking three hours for stipulated value 5. At most two B-jobs are available, each taking two hours for value 3. Durations and values add in this constructed problem.

A linear relaxation permits real counts 0 <= x <= 1, 0 <= y <= 2 with 3*x+2*y <= 4. It returns x=1, y=0.5, value 6.5. Recover the argument: the time condition gives y <= (4-3*x)/2, so 5*x+3*y <= 6+0.5*x <= 6.5; the returned pair attains that limit.

For the whole-job choice, two B-jobs fit and give value 6. Every whole-job value is an integer and the relaxation admits every whole-job arrangement. Its upper bound of 6.5 therefore establishes that none can exceed 6. The feasible choice and the bound together prove optimality. Direct enumeration gives the same conclusion here. With A selected, no B fits and the value is 5. Without A, at most two B-jobs fit. If the planner asks only whether 7 is attainable, the bound alone rules it out.

The use of the theory changes with the question. Selecting work needs an attainable arrangement; excluding a target can use a bound. The practitioner needs to recover that relation before deciding whether a further optimization step is useful. B.5:5.4 also works the changed five-hour case.

B.5.TU:6 - Bias-Annotation

The worked cases favor mathematical accounts with small, inspectable operations. Other theories can use qualitative or interpretive inferences; their warranted application conditions and criticism must come from the relevant practice. A convenient numerical example should not decide which kind of explanation the question needs.

Familiar terminology can make a supplied interpretation look independently recovered. Attribute the contribution when assessing learning or capability. In ordinary assisted work, use the supplied result at the scope its interpretation supports.

B.5.TU:7 - Conformance Checklist

  • The application has a question and a useful result to obtain or interpret.
  • The theory’s objects, operations and premises needed for that application are recoverable.
  • The construction connects supplied inputs to required outputs; a missing operation remains a gap.
  • A source-supported application and a newly proposed adaptation retain their respective grounds.
  • The worked consequence states what its construction, argument or computation establishes.
  • The receiving use preserves consequential conditions, including any difference between an attainable result and a bound.
  • Further study, evidence or specialist work serves a remaining useful contribution at an appropriate cost.
  • The return supports an action, understanding, construction or next question; sufficient use can stop.

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

Observed difficulty in the method’s casesRepair
Reuse a composition while overlooking how many inputs it consumes.Recover the permitted operations and supply their inputs; in :5.1, copying is the decisive additional operation.
Evaluate a familiar-looking expression before filling its arguments.Construct the path, derivative and substitution required by the operation, as in :5.2.
Improve a computation whose formulation omits the receiving condition.Recover that condition. The undriven model rules out the requested trip from rest to rest. A design for making the trip must account for how the motion changes.
Discard an infeasible optimizer together with its valid bound.Interpret each result separately; :5.3 retains the exclusion of value 7.
Require the same depth of study for using and altering a result.Locate the contribution the work needs, then recover or obtain the reasoning that enables it.

B.5.TU:9 - Consequences

The practitioner can move from a promising theory to a worked use, or state the contribution that prevents it. The result also makes division of work easier: one participant can supply a model, another a construction or calculation, and another the receiving interpretation.

The cost is recovering enough of the account to assemble and use the application. Reuse supplied explanations and operations where adequate. Detailed derivations, broader source comparison or empirical inquiry are worthwhile when their answers affect the intended work.

B.5.TU:10 - Architectural Rationale

The method joins two directions of reasoning. Working backward from the question reveals the needed contribution. Working forward through the theory tests whether the available objects and operations supply it. Returning the consequence to use exposes conditions a correct internal calculation can leave unresolved.

B.5.RC and B.5.RA recover constructions and arguments. Here they contribute to assembling an application whose meaning and needed output may be unsettled. C.29 constructs and tests mathematical correspondence; it can start before a mathematical object has been selected. This method adds recovery of how the unfamiliar theoretical account becomes usable at that point. A theory can also be used within its mathematical setting, as in the composition case.

A complete explanation of the theory can be the appropriate learning project. For one urgent use, however, an adequate supplied application or bounded specialist result may settle the question sooner. The choice depends on the work the receiver must perform, including any need to criticize or change the method later.

A small successful application provides something to use and a basis for further inquiry. Broader generalization requires its argument. If the application exposes a limitation in the theory, the resulting construction or counterexample can become material for developing its objects, rules or questions.

B.5.TU:11 - SoTA-Echoing

How much theory must be reconstructed for a first use? Adapt van Oostrum, Langer and Ay (2025), Introduction and §§1–2, 4: connect the operational question to stated model variables and inference, work an example, and recover deeper derivations when they are needed.

The alternative is to use an interpreted supplied implementation. Retain that cheaper route when it suffices; reconstruct dependencies when adaptation or explanation requires them. Sections :4.1–:4.4 make that choice explicit. The source provides a discrete active-inference account and a minimal implementation.

How can notation reveal what an application lacks? Adapt SICM’s Preface: recover function arguments, substitutions and composition where implicit conventions obscure the operation. A familiar conventional expression is cheaper when the reader can use it reliably. Sections :4.2–:4.4 therefore call for operative reconstruction at the unresolved step; :5.2 supplies a case.

The selected contribution is operation recovery. Its source’s requirement of automatic interpretability is appropriate for computational exposition; ordinary use may be settled by a clear hand-worked construction.

What does a theory’s formal structure contribute to an application? Adopt Baez and Stay, §2.3’s constructive comparison of cartesian and monoidal operations. A familiar “parallel composition” description can leave input duplication unresolved. Section :5.1 obtains the required operation or the obstruction under stated rules, then asks whether the receiving practice can supply it. This pays the cost of recovering only the consequential structure. The broader cross-disciplinary correspondences in that paper do not establish the physical copying operation in our case.

The common method is a synthesis of these contributions. Reconsider how to construct the application when a better approach requires less reconstruction, when a recurring failure requires another connecting operation, or when changed tools alter the contribution the receiver must understand.

B.5.TU:12 - Relations

  • B.5 coordinates the inquiry and a changed question. B.5.FM constructs a first model when consequential participants or relations remain unclear.
  • B.5.RC, B.5.RA and B.5.RR supply construction recovery, argument recovery and reasoning revision.
  • B.5.4 constructs a situational interpretation of an available concept. C.29 and C.29.1 supply mathematical correspondence and result transfer.
  • C.29.2, C.29.3 and B.5.MPC connect computation, realization and the physical question.
  • A.6.3.RT prepares an operative expression; C.2.8 helps characterize what a recipient can extract from an explanation under stated preparation and access.
  • A.15.9 supplies bounded professional help; C.11.DUA selects useful further effort; C.39 develops a missing way.
  • C.40 develops questions and ways together when the application opens that further work.

B.5.TU:End

B.5.TC - Compare Theoretical Accounts for a Question

Type: Method-description pattern Status: Stable Normativity: Normative unless marked informative

B.5.TC:1 - Problem frame

Use this when two theoretical accounts appear to give different answers, explanations or instructions for the work you are doing, and you need to decide how to use them. They may employ different objects, preserve different information or obtain a result by different operations. Comparing their vocabulary or final numbers has left the practical difference unclear.

The work here is to compare uses of those accounts. A theory supplies objects, relations and ways of reasoning; an application adds a question, an interpretation and the premises needed to obtain an answer. Compare those applications while keeping the underlying accounts understandable on their own terms.

First useful move. Begin with the question the recipient needs answered. Where the accounts offer answers to the same part, compare their reasoning under corresponding conditions. Where they supply different premises, establish how those premises contribute to the required answer. A route description that says where travel is possible and one that gives minimum travel cost can both be useful. The question determines which information and operations you need.

The result explains what each account contributes, the conditions of agreement or difference, and which use or inquiry should follow. You may select one sufficient account, combine complementary contributions, or retain an unresolved difference together with what remains usable.

Use a familiar comparison when its question and conditions fit. If only one application is unclear, B.5.TU helps construct it. If the disputed object is a numerical implementation of an understood model, begin with C.29.2. This pattern becomes useful when it is necessary to compare the accounts or locate the source of their apparent disagreement.

B.5.TC:2 - Problem

Two descriptions can use the same word for different quantities, or different words for a shared construction. One can answer a weaker question. They can agree on observations while disagreeing about an intervention. An approximate computation can also obscure agreement between the theories from which the computations were derived.

A comparison must recover enough of each application to distinguish these situations. It must also leave room for an account that opens a question the original comparison did not ask. The practical problem is to determine what the difference permits, prevents or changes for the work, without requiring a verdict on the theories in every possible use.

B.5.TC:3 - Forces

ForceTension
A shared question vs different conceptsComparison needs a shared use, while translating every term into one vocabulary can erase the difference being investigated.
Agreement vs scopeA worked case makes an account usable; an equivalence claim across cases needs the corresponding argument.
Explanatory reach vs effortA richer account can answer further questions while a smaller account supplies the present answer more cheaply.
Discrimination vs useful closureA difference may justify further work, or leave the needed result unchanged.
Common operations vs subject knowledgeThe comparison method travels across practices; its proofs, laws and causal premises come from the accounts being compared.

B.5.TC:4 - Solution

Fix the question → construct each account’s application → align the case and the meaning of its answer → locate the consequential difference → use what the comparison establishes, or pursue the difference that matters.

The sequence is revisable. Reuse an established application or correspondence. Return to the question when the accounts reveal that it combines different needs. Stop when the available result suffices for the intended use.

B.5.TC:4.1 - State the answer the work needs

Say what you want to explain, predict, construct or decide, and what would count as an answer. Specify the conditions that can alter that answer: for example, the initial state and time of a prediction, the allowed routes and quantity to minimize, or which intervention is contemplated.

Keep the account and its proposed use separately visible. Comparing a theory’s possible reach with a rival’s implemented calculation is a comparison of unequal contributions. Either construct the relevant application of both or state which contribution is unavailable. An unavailable application can be a reason to use another account while retaining the first for development.

If the accounts answer different questions, identify any shared question and ask what its answer supplies for the work in hand. They may agree about what was observed while supporting different decisions about a proposed change. Compare the remaining contributions for those uses. In open research a new question can be worth pursuing for what it makes possible. If an earlier question is still assigned, state what the comparison establishes for it and which part remains open. B.5:4.4 connects this result to problem development.

B.5.TC:4.2 - Recover an application of each account

For each account, recover the objects and relations used, what is supplied or assumed, the operation that obtains the answer, and how that answer is interpreted. Follow the reasoning far enough to reproduce the step on which the comparison turns. B.5.TU, B.5.RC and B.5.RA supply application, construction and argument recovery when needed.

Preserve the source’s distinctions during this work. If two accounts use state differently, explain which information each state retains and what continuation it determines. If a symbol has no counterpart, say what the account does with it before proposing a correspondence. Translate the required objects and operations; a word-to-word substitution alone cannot settle their relation.

An account may need information the work lacks. Separate a supplied premise, a proposed premise and a derived result in the explanation. Continue conditionally when that is useful: “Under this independence assumption the minimum is 3; if continuations depend on the incoming route, we must retain that dependency.”

A collaborator or tool can supply a calculation or proof. Recover the interpretation and conditions needed to compare its contribution. Learn or request the missing operation when you cannot follow the decisive step; a broad study of both theories is unnecessary when a smaller contribution settles the use.

B.5.TC:4.3 - Work the same case and align the answers

Work with the actual situation or a smaller case that retains the disputed operation or distinction. Give each account the corresponding inputs, derive its answer and express it in the terms of the question. Explain the correspondence when the inputs or outputs take different forms.

For a mathematical application, compare the retained distinctions and operations. C.29.1 supplies the preservation argument when a result is to be transferred. For a physical application, keep the phenomenon, operating conditions and meaning of the predicted quantity aligned. For a computation, separate the mathematical formulation from approximation, numerical tolerance and execution.

Use a familiar case when it helps locate a transcription or implementation error. To investigate a difference, choose a case on which it matters and explain why. For a conclusion spanning cases, identify the dependence that carries it through the claimed range. One derivation for an arbitrary member can establish agreement there. One admissible counterexample can settle a claim of agreement everywhere. Where the question concerns only the given case, its sufficiently grounded result can finish the comparison.

Agreement of reported numbers is informative only after their meanings and conditions are aligned. Conversely, different intermediate objects can lead to the same answer through an explained correspondence. Record only the derivation or explanation the receiving use needs.

B.5.TC:4.4 - Locate what causes the difference

Follow each answer back to the first step where the applications cease to agree. Use the following distinctions where they resolve that case.

What differsNext useful operation
The question or output meaningRestate the common question; keep other answers as complementary contributions.
A premise, boundary or retained distinctionWork the accounts under aligned premises, or show which case requires the additional premise or information.
A construction or inferenceRecover the competing steps. Derive their relation or exhibit where one fails under its stated conditions.
An approximation or executionCompare the mathematical result with the implemented procedure and its error under the relevant conditions.
The proposed physical or causal accountDerive the consequence on which they disagree; use the available domain knowledge and evidence for that consequence.

Several differences can interact. Aligning one premise can remove an apparent conflict; it can also expose a remaining one. Keep the remaining question named. If the answer depends on a missing correspondence or inaccessible operation, return that missing contribution rather than ranking the theories from their summaries.

Additional evidence is useful when it can change the needed conclusion. First use an available derivation, counterexample, observation or established result. If the difference remains consequential, compare the possible gain from a discriminating inquiry with its cost and feasibility under C.11.DUA. A difference that cannot change the use can remain unresolved. When it does change the use and cannot be settled, retain the conditional answers or obtain a sufficient weaker result.

B.5.TC:4.5 - Choose the use and preserve the reason

Return the comparison in the form the work can use. A short explanation can state the question, the decisive construction, what agrees or differs and the resulting continuation.

Common outcomes are:

  • One sufficient account. Use the account that answers the question under acceptable conditions and effort. State the limitation that would make another account necessary.
  • Agreement for a stated range. Reuse either account for that result, choosing by effort, available tools or the further construction it makes easier. Preserve the relation that supports the agreement.
  • Complementary uses. Give each account its question and contribution. When combining their results, establish the compatibility needed at the connection.
  • A consequential unresolved difference. Keep the conditional answers and the premise or observation that would discriminate them. Continue with an unaffected result, a sufficient bound or the worthwhile inquiry selected for that difference.

Accuracy, reach, computational effort, learning effort and the ability to change the construction can matter differently across uses. Compare the values that can change this choice. If their trade-off is unresolved, C.11 supplies the decision method.

Reopen when the question, premises, interpretation, available operation or relevant evidence changes. B.5.RR helps revise the affected reasoning. Reuse the comparison where its dependencies remain intact.

B.5.TC:4.6 - Separate recognition from assurance

Recognize the need from an unresolved disagreement or a choice between accounts. One worked comparison can reveal an omitted premise or a useful complementary answer.

Qualify the result for its intended use. A mathematical equivalence needs a derivation over its claimed domain. A physical prediction needs the corresponding model and observation basis. An implemented approximation needs an error account adequate for the question. Use the relevant subject Methods for these claims. Use B.3 when a named assurance claim about this result and use needs its assurance argument and qualification. Broader reliance is a reason to establish the broader claim, while an ordinary local use can stop with its sufficient local result.

If the comparison turns on whether one model refines another, check for the same inquiry that the receiving model admits a completion and that every such completion preserves the earlier commitments. For strict refinement, also identify a previously admissible possibility it excludes (B.5.MR). Keep the other grounds for preferring a theoretical account visible when that comparison leaves the models incomparable.

B.5.TC:5 - Archetypal Grounding

B.5.TC:5.1 - Routes, reachability and minimum cost

A planner asks what can be learned about a complete journey from X through Y to Z from accounts of its two stages. One recipient needs to know whether travel is possible. Another needs the least possible cost. Recover what each account retains that could answer those questions. In the first account, individual routes are distinct objects. Routes p and q go from X to Y and cost 1 and 4. Route r goes from Y to Z and costs 2. Routes with matching endpoints can be concatenated and their costs add, giving complete routes costing 3 and 6.

A second account keeps only whether travel between endpoints is possible. Both X-to-Y routes become the answer “yes”. Joining that answer to Y-to-Z reachability gives “yes” for X-to-Z. This account answers whether travel is possible. Reachability alone cannot determine the minimum cost. Keep the routes and their endpoints, but change the cost of p from 1 to 5. With q still costing 4 and r costing 2, the least complete cost changes from 3 to 6 while every reachability answer stays the same. For a question about the route actually taken, even the original network permits two different costs.

A third account keeps minimum costs. For finite nonempty sets of allowed first and second segments, assume every first segment can be followed by every second segment and costs add. Then the least combined cost is the sum of the two least costs. Every combined cost is at least that sum, and combining the two minimizing segments attains it. For the original costs, the minimum is 1 + 2 = 3. The calculation can therefore answer the minimum-cost question without retaining every route. Giving directions for a minimum-cost route also requires the minimizing segments to be recoverable.

Now change the allowed combinations. Let the second segments be r with cost 2 and s with cost 10. Only p followed by s, and q followed by r, are allowed. The minimum is min(1 + 10, 4 + 2) = 6. Independently minimizing the two stages gives 3, which no allowed route attains. The failure is the omitted compatibility relation. Retain the incoming-route distinction or calculate over the allowed pairs.

The planner can now choose what to recover from a partial description. With additive costs, the sum of the separate minima is a lower bound on every permitted complete route. To report it as the minimum, show that some permitted complete route attains both minima. This can hold even when other pairings are forbidden. To answer only whether a journey is available within a budget of 7, the allowed route costing 6 already suffices. For directions, identify the actual segments that make up an affordable route. Treating costs as times or expenditures adds the conditions under which those quantities add.

B.5.TC:5.2 - The same oscillator, different formulation and computation

Consider an ideal one-dimensional mass on a linear spring, with mass m > 0, spring constant k > 0, displacement q and velocity v. Friction and external forcing are absent. The question is its motion from q(0) = a and v(0) = 0.

The force account gives m q’’ = -k q. The variational account uses L(q,v) = m v²/2 - k q²/2. Its Euler-Lagrange equation is d/dt(∂L/∂v) - ∂L/∂q = 0; substitution gives m q’’ + k q = 0. Both therefore give q(t) = a cos(√(k/m) t) under these premises. For this motion question, the two constructions agree. The variational formulation can become preferable when another coordinate choice simplifies constraints; the force formulation may be the quicker account for this simple case.

Suppose a computation appears to disagree. Take m = k = a = 1 and use the forward Euler updates q_next = q + h v and v_next = v - h q. From q = 1, v = 0 and h = 0.1, it returns q_next = 1, v_next = -0.1. The energy (q² + v²)/2 rises from 0.5 to 0.505. In fact these updates multiply energy by 1 + h² at each step, whereas the differential equation conserves it.

The discrepancy is produced by the approximation used in the computation. Compare an adequate step size or another numerical method under C.29.2 for the requested horizon and error. If the real oscillator loses energy, examine friction and other physical interactions; that changes the model question. The equality of the two ideal derivations remains available within its premises.

B.5.TC:5.3 - Agreement in observation, disagreement under intervention

An indicator X and an output Y always follow a binary controller command U. Two causal hypotheses explain the observed pairs: A uses X := U and Y := X; B uses X := U and Y := U. In A, the indicator drives the output. In B, the controller drives both directly. Both yield X = Y = U in ordinary operation.

The question is what happens when X is forced to 1 while U remains 0. Represent this intervention by replacing the assignment to X. A gives Y = 1; B gives Y = 0. The same observed pairs leave that difference unresolved.

The next contribution could be the circuit description, an available intervention result or a worthwhile discriminating test. If the work only predicts the observed indicator from U in unchanged operation, this causal difference need not be settled for that use. If it proposes controlling Y through X, retain the unresolved consequence until the needed causal premise is supplied. C.28 governs that intervention claim.

B.5.TC:6 - Bias-Annotation

A shared question can favor the account that originally framed it. Retain a rival’s newly expressible question when it opens useful inquiry; compare that contribution on its own terms. Conversely, unfamiliar notation can make an ordinary operation appear novel. Recover the operation before crediting or rejecting the account.

The cases use small formal constructions so their decisive steps can be inspected. They demonstrate the comparison method, with domain premises stated in each case. A difficult real application can need specialist knowledge, uncertain premises and more than one iteration.

B.5.TC:7 - Conformance Checklist

  • The comparison names a question and explains what its answer changes.
  • Each application has recoverable meanings, inputs, premises, decisive operations and an interpreted answer.
  • The shared case corresponds across accounts; a missing correspondence remains visible.
  • Agreement or disagreement is traced to the relevant question, premise, operation, inference, implementation or physical account.
  • The conclusion has the scope established by its derivation, cases and applicable evidence.
  • A sufficient cheaper account, complementary use or useful conditional result remains selectable.
  • Further inquiry has a consequence for the intended use that can justify its burden.
  • The result states the next use and the change that would reopen the comparison.

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

FailureRepair
Comparing unlike outputs as rivals: reachability and minimum cost are both called a route answer.State the question each answers, then construct the common question or their complementary use.
Identifying theoretical accounts because a fitted case gives the same number.Compare the meanings and decisive operations; derive the range of agreement when a broader claim is needed.
Treating a numerical discrepancy as a physical-theory disagreement.Recover the formulation and approximation, as in the oscillator case, before changing the physical account.
Selecting a more elaborate account for capabilities the question does not use.Compare the adequate answers and their burdens; retain the further capability for the question that needs it.
Seeking more observations to resolve a difference that ordinary observations cannot distinguish.Derive the discriminating consequence and use the relevant causal or other domain method; retain an unresolved difference when further inquiry is unavailable or unwarranted.

B.5.TC:9 - Consequences

The practitioner gains a reasoned division of use between accounts, or a located disagreement that can guide the next inquiry. That result also supports collaboration: contributors can work on the missing mathematical operation, physical premise or computational approximation instead of repeating the whole dispute.

Reconstruction costs effort. Reuse an applicable comparison and stop at the explanation needed for the work. A comparison remains dependent on its question and premises; a changed use can make previously irrelevant distinctions decisive.

B.5.TC:10 - Architectural Rationale

The unit of comparison is an application because a theory’s objects alone leave its useful inference undetermined. Reconstructing that inference makes differences in representation, premises and operations comparable without first imposing a common ontology on every source concept.

Working a shared case provides a place to connect the accounts. Following the dependency that causes a difference then supports a broader argument or a discriminating example. These operations complement one another: a derivation establishes scope, while an example can reveal that the chosen scope misses the work’s question.

Separating agreement, complementary use and unresolved difference keeps the result productive. An account may remain preferable for a cheap prediction and insufficient for an intervention. Another may be harder to use now yet expose a construction worth developing. This preserves the connection between obtaining knowledge, applying it and improving the available ways of inquiry.

B.5.TC:11 - SoTA-Echoing

For comparing what different mathematical accounts let a practitioner compute, adopt the operation-based comparison illustrated by Fong and Spivak’s Seven Sketches in Compositionality (2019), §2.5.2–§2.5.3. Reachability and cost use different operations for combining steps and choosing among alternatives. Against comparison by shared route terminology, this makes the lost answer and composition condition visible in :4.3 and :5.1. The finite compatibility example is a construction here. Reopen its application when the quantity or allowed composition changes. Author manuscript.

For physical formulations that may agree, adopt the constructive comparison in Sussman and Wisdom’s Structure and Interpretation of Classical Mechanics, second edition (2015), §1.6: derive the equations under the stated force and potential assumptions. This answers more than a numerical fit and often costs less than a new simulation. Against selecting a formulation solely by familiarity, preserve the advantage of coordinates adapted to constraints. Sections :4.3–:4.4 and :5.2 separate that choice from numerical approximation. Reopen when interactions, constraints or the requested result change. Publisher’s text.

For comparing causal uses, adopt intervention construction from Pearl’s Causal inference in statistics: An overview (2009), §3.2.1, and adapt it here to expose the consequence on which two accounts disagree. Agreement in the observed distribution, a comparator for prediction, can leave that intervention consequence undecided. Sections :4.4 and :5.3 use this construction; C.28 supplies the broader causal method. Reopen when the causal premises or intended intervention change. Author’s paper.

For prediction, an alternative to choosing a single account is combining predictive distributions. Yao, Vehtari, Simpson and Gelman’s stacking method (2018) chooses weights through predictive performance when the candidate set need not contain the data-generating model.

Adapt that question-relative choice into :4.5’s permission to retain combinations. Reject using such predictive weights as a verdict about causal mechanism or mathematical equivalence; those are different comparison questions. The statistical method remains with its domain, including its scoring and validation conditions. Reopen when prediction under another distribution or a different use is required. Authors’ paper.

This pattern combines these constructive contributions into a common comparison method.

B.5.TC:12 - Relations

  • B.5 coordinates the reasoning cycle and return to a changed question. B.5.TU, B.5.RC and B.5.RA recover an application, construction or argument; B.5.RR revises the affected reasoning.
  • C.29 selects mathematical lens use; C.29.1 constructs the correspondence needed to transfer a result. C.29.2 and C.29.3 separate computational formulation from physical execution.
  • B.5.MPC connects mathematical, physical and computational contributions. C.28 governs causal and intervention claims.
  • C.38 constructs comparable ways to obtain one result. This pattern supplies a theoretical comparison when such a way depends on an unsettled account. C.11 and C.11.DUA govern a consequential choice and the worth of further inquiry.
  • F.0.2 uses a comparison of accounts when forming a semantic synthesis across sources. A.6.3.RT supports operative expression, and A.15.9 obtains a missing specialist contribution.

B.5.TC:End

B.5.QD - Develop a Question from a Result or Construction

Type: Method-description pattern Status: Stable Normativity: Normative unless marked informative

B.5.QD:1 - Problem frame

Use this when a result, counterexample or available construction changes what you could usefully investigate, but the next question is unclear. A failed conjecture may reveal a missing condition. A successful calculation may supply an operation that makes a previously impractical question approachable. The work is to turn that change into a question you can begin to answer.

First useful move. Recover the step at which the earlier reasoning failed, or the operation that has become available. Ask what it lets you distinguish, construct, explain or change. For example, a triangle refutes the claim that every connected graph can be divided into two groups with every edge crossing between groups. It also suggests asking for a construction that returns either the division or an obstruction.

The result is a question with an understood answer form, an attainable way into it and a reason to pursue or retain it. If the assignment is to formulate the question, this can complete it. If an earlier answer is still owed, explain what the new question contributes to it. Some investigations are free to develop a concept or a reusable operation before any eventual application is known.

Use an adequate question. If the question is clear and the missing contribution is a way to answer it, C.39 supplies that search. This pattern is useful when the result sought or the question’s conditions need to be developed.

B.5.QD:2 - Problem

“Find the next interesting problem” leaves the crucial work undone. Many variations merely change a number or a name. Others repeat a failed claim with a convenient exception, ask for information the available description cannot determine, or generate questions whose answers would add nothing to the inquiry.

A useful next question grows from a consequential change: an exposed dependency, a new object or operation, a newly distinguished case, or a result that can be used elsewhere. The difficulty is to construct that question while preserving what the earlier work established and keeping a feasible point of entry.

B.5.QD:3 - Forces

ForceTension
Continuity and noveltyEarlier reasoning supplies operations worth retaining; its original question can also hide the next useful distinction.
Refutation and recoveryA counterexample can invalidate a broad claim while leaving much of its construction available.
Reach and tractabilityA question can open a valuable field while its first attack must fit the contributors and means available.
Exploration and present useSome contributions have an immediate application; others make new questions or operations possible.
Variety and attentionSeveral alternatives can reveal a better question, while indiscriminate generation consumes the effort needed to work one.

B.5.QD:4 - Solution

Recover what changed → find the consequential dependency or new operation → formulate the question it opens → use a case, construction or argument to establish a useful point of entry → choose how to continue.

Enter with the result that changed the inquiry. Reuse a known formulation or derivation when it supplies the needed step. Return to an earlier step if an attempted answer reveals that the question is ambiguous, underdetermined or more expensive than its use warrants.

B.5.QD:4.1 - Recover the contribution of the earlier work

State the earlier question and what the work obtained. Identify the part that matters: a counterexample, an unresolved inference, a constructed object, a computational operation or a distinction the earlier description omitted.

For a failure, locate its scope. A counterexample to a lemma can expose a defect in one argument while leaving the main conjecture undecided. A counterexample satisfying the main conjecture’s premises refutes that conjecture. A program’s failure on a case may instead concern its implementation. Recover the relevant reasoning under B.5.RA or B.5.RR when this difference is unclear.

For a success, recover what can be done with the result. Explain its inputs, output and application conditions. A computation that produces cumulative totals, for example, may provide a way to answer many interval questions. Its reusable contribution is the relation between those totals and the intervals.

Keep independently supported results available. They can supply the construction, limiting case or partial answer for the next question.

B.5.QD:4.2 - Find the relation that can change the question

Follow the earlier result back to a consequential dependency, or forward to an operation it enables.

If a description gives the same information for cases that need different answers, construct two such cases. Their difference identifies information a stronger question may need. If an inference depends on an unproved step, state the missing step as a possible question. If an operation succeeds, ask which other inputs, outputs or combinations preserve its useful relation.

Use variations that have a reason in the work. The following are common ways to construct them.

What the work revealsHow to form the next question
A counterexample identifies a failed condition.Ask which condition would support the needed conclusion, or which construction identifies the cases where it fails.
A successful construction produces more information than the first answer used.Ask what further result can be obtained from that information and by which operation.
Different cases collapse to one description.Ask what additional distinction determines the answer, or what bound remains possible without it.
An argument needs an unavailable intermediate result.Ask for a lemma, witness or construction that supplies that step; state how it would be used.
A familiar operation becomes available in another setting.Ask whether its required relations hold there and what receiving task it can serve.

Ask what the variation preserves for the earlier question. A counterexample on a tree can refute a claim about all graphs. A theorem for trees can settle a request about all graphs if a valid reduction carries its conclusion back to every graph at issue. Without such a connection, keep the broader claim open. When research direction is yours to choose, you can pursue the tree question for its own mathematical interest. When the broader answer was requested, identify what remains due or obtain agreement to a different result.

These variations can be combined or repeated. Their purpose is to expose a useful answer.

When requirements appear incompatible, B.5.QD.CF recovers the premises producing the conflict and asks what other construction could satisfy the retained need. It distinguishes changing an assumed means or representation from changing a requirement, and can return a useful impossibility when the conditions must remain.

B.5.QD:4.3 - Give the question an answer form

Say what would answer the question: for example, a construction, an explanatory relation, a bound, a counterexample or a condition under which an operation works. State the objects, allowed changes and premises that can alter the answer.

Connect that answer to its possible use. “Find a partition” and “return a partition or an odd-cycle witness” make different contributions: the second also explains failure. “Predict the position” and “bound the reachable positions” may serve the decision at different effort.

Separate a proposed answer from the question. “Does this procedure always terminate on finite inputs?” remains a useful question when the proposed positive answer is false. The failing case can open the question of a termination condition or another procedure.

If a question combines several missing contributions, make the dependency visible. For a physical calculation, you may first need a model that determines a quantity, then a computation of that model, then an interpretation for action. B.5.MPC coordinates those contributions. Name the first unresolved connection so a person, AI agent or group can work on it using the available subject knowledge and tools.

B.5.QD:4.4 - Find an entry that reveals what the question requires

Choose an entry that exposes what must be done. A small case is useful when changing one condition reveals an obstruction or a lost distinction. If the relevant dependence already follows from an argument or a construction over arbitrary admissible inputs, use that reasoning directly. To distinguish two possible explanations of an occurrence, seek grounds about that occurrence. A new hypothetical case can show how the explanations differ.

Use the result to improve the question. A successful case can expose a reusable relation. A failed case can identify a missing premise, an incompatible demand or an operation to be developed. If two admissible cases give different answers from the same supplied information, ask for the missing distinction or a result valid for both.

A case establishes its result. A broader mathematical claim needs its derivation, and applying a physical model needs the relevant physical basis. The question can be useful before those answers are established: the first attempt should make the next contribution more identifiable.

Begin with available reasoning and information. Obtain further evidence only when its possible answers can change the useful inquiry enough to justify the effort under C.11.DUA. An existing bound or conditional answer may settle the use.

B.5.QD:4.5 - Choose an attainable inquiry

Compare the few questions that remain candidates. Ask what each answer would enable and where work could begin with the available capabilities, collaborators and resources. Include the cost of learning or obtaining a missing operation when it affects the choice.

A worthwhile first question may be narrower than the eventual aim: establish a limiting case, find one witness, recover a missing lemma or test a proposed connection. Explain how that result would contribute to the larger question. If the contribution is available, use it and select the next unresolved step.

E.10.INT helps distinguish useful interest from novelty, surprise or a local scoring heuristic. A question can be worth pursuing because it opens further constructions, changes what can be explained or makes another question approachable. Its eventual practical destination may remain unknown. When problems and ways of solving them must develop together, use C.40; retain a promising alternative when its prospective use justifies doing so.

Continue with the chosen question, the contribution that makes it attainable and the dependency it is meant to resolve. Stop when the requested result is in hand. In an open inquiry, a better use of the available effort can justify changing direction. For a fixed assignment, a reason to stop investigating identifies a limit on the answer unless the work already meets the assignment or its holder has changed it.

B.5.QD:4.6 - Separate question recognition from answer assurance

Recognize the opening from a changed possibility of inquiry. One worked counterexample or a useful new operation can be sufficient to begin developing the question.

Judge the question by whether it has a recoverable meaning, a possible contribution and a workable point of entry. Judge its proposed answer by the claim it makes. A conjecture, a proven relation, a simulated result and an observed physical effect support different uses. Apply their subject Methods and B.3 when the receiving use needs that assurance.

Reuse the question while its purpose and conditions remain applicable. Reopen it when a result changes its premises, available operations, attainable scope or intended use. A solved question can open another valuable one; an adequate answer can also end the present work.

B.5.QD:5 - Archetypal Grounding

B.5.QD:5.1 - From a false graph claim to a construction or obstruction

An engineer represents pairwise incompatibilities by a finite simple undirected graph. The proposed claim is that connectedness suffices to divide the vertices into two groups so every edge crosses between groups.

A triangle refutes the claim. Assign A to the first group and its neighbour B to the second. The third vertex C is adjacent to both, so neither group is available. The failure concerns the universal claim, not the ability to divide any graph: a four-vertex cycle A-B-C-D-A admits groups {A,C} and {B,D}.

Follow the failed operation. Along a path, successive vertices can alternate between the two groups. Returning around an odd cycle forces its final edge to join vertices assigned to the same group. That identifies an obstruction worth seeking.

The next question is: For a given finite simple undirected graph, can we construct the division or return an odd cycle that explains why it is impossible? The answer form serves both allocation and diagnosis.

B.5:5.1 supplies the broader construction. Traverse each component by breadth-first search and assign groups by even or odd depth. If every edge joins opposite parities, the assignment works. An edge joining equal parities combines with the two parent paths up to their last shared vertex to give a simple odd cycle. The construction therefore answers the new question for the stated graph class.

The new procedure also works on disconnected graphs by treating each component, including isolated vertices. For a real allocation, determine which combinations the graph rules out. A restriction on three items together can leave each pair permissible. The allocation question can then require a richer model. A two-colouring that satisfies all the actual restrictions still supplies a feasible allocation. A two-colouring that violates the triple restriction leaves open whether a different allocation works.

B.5.QD:5.2 - From a position to a sufficient state or useful bound

A model describes a point moving along one line in an inertial frame. During the next two seconds there is no net force; use the classical relation q(t) = q(0) + v(0)t. The supplied position is q(0) = 0. Someone asks where the point will be two seconds later.

Construct two cases allowed by this description. With v(0) = +1 metre per second, q(2) = +2 metres. With v(0) = -1 metre per second, q(2) = -2 metres. Position alone leaves the requested answer undetermined.

One next question is what information completes the state for this prediction? Under this model, initial velocity together with position suffices. Obtaining velocity could use an available displacement over a known interval of constant velocity. A.3.3 and C.16 develop state and measurement when those contributions are needed.

Another question is cheaper if the decision only asks whether the point stays within three metres of its starting position for the next two seconds. Suppose the available information bounds the initial velocity between -1 and +1 metre per second. Then the displacement magnitude is at most (1 metre per second)t throughout that interval, so the point stays within two metres. The bound answers the decision without acquiring a more specific velocity.

The two questions support different uses. If an actuator must meet the point at a specified position, the bound can be insufficient and the state question becomes useful. If the net force becomes nonzero during the interval, revise the model and its prediction. The construction of the question has located the relevant missing contribution in each case.

B.5.QD:5.3 - A successful cumulative computation opens an interval question

A program can construct cumulative totals for an integer array a. It starts with S[0] = 0 and sets S[i+1] = S[i] + a[i]. For a = [2,-1,3,4], the result is S = [0,2,1,4,8].

The original task needed the total 8. Recovering the operation reveals that each S[i] gives the sum before position i. This opens the question: Can we answer many interval-sum queries from the cumulative totals?

Specify an interval by indices l and r, with 0 ≤ l ≤ r ≤ n; it includes l and ends just before r. Splitting the first r elements at l gives S[r] = S[l] + sum(a[l],…,a[r-1]). Hence the interval sum is S[r] - S[l]. For the last two elements, l = 2 and r = 4, so the answer is 8 - 1 = 7. For l = r the answer is 0.

This is a general derivation under integer arithmetic with enough capacity to avoid overflow. Each query uses two stored totals and one subtraction after the array has been prepared. Whether preparation is worthwhile depends on how many queries and changes the application requires.

If a[i] changes by d, every S[j] with j > i changes by d. Frequent changes therefore open a further question: which data organization supports the required mixture of updates and interval queries? That question can be developed when the workload makes it relevant. The successful cumulative operation answers the unchanged-array question.

B.5.QD:6 - Bias-Annotation

The original formulation can anchor subsequent questions. Recovering its failed condition or unused operation helps reveal alternatives, but the new question should explain what it contributes. A more familiar or easier formulation can silently abandon the unresolved use.

Mathematical search often favors statements that can be proved. Question development also benefits from locating a false conjecture, an underdetermined description or a construction that cannot meet its conditions. Their usefulness comes from the inquiry they enable.

B.5.QD:7 - Conformance Checklist

  • The earlier work and its consequential result are recoverable.
  • A failure is located at the claim, premise, inference or implementation it affects; a success exposes its reusable operation or relation.
  • The new question states an answer form and the conditions needed to understand it.
  • For a question already assigned, the contribution of the new formulation to its answer is warranted. A separate research direction can be chosen by whoever holds that choice.
  • A case, existing derivation or other attainable contribution shows what the proposed inquiry could establish, including whether any result is still owed for the earlier question.
  • The question’s possible contribution and its attainable first step justify pursuing or retaining it.
  • The proposed answer is used with the scope and support appropriate to its claim.
  • Further work can stop when an available answer suffices; explanations and records are only as extensive as their receiving use requires.

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

FailureRepair
Appending exceptions until a refuted claim survives, while losing the original use.Follow the counterexample’s failed relation; formulate the condition or obstruction that helps answer the question.
Treating a failed lemma as a refutation of the main conjecture.Recover which argument used the lemma and what remains undecided; investigate an alternative step where useful.
Generating many syntactic variants and counting them as progress.Work a variation that changes an available construction, an answer or a useful distinction.
Asking for a unique prediction from information shared by physically different continuations.Exhibit the differing cases; obtain sufficient state information or return a useful bound.
Discarding a successful operation after it gives the requested number.Recover its relation to inputs and outputs when another use could benefit, as with cumulative totals.
Making proof of eventual usefulness a prerequisite for exploration.Identify the nearer inquiry or construction the question can enable and compare that contribution with its cost.

B.5.QD:9 - Consequences

Question development turns both failure and success into possible further work. It can preserve a useful construction, make a missing premise investigable or reveal a result that serves another practice. Contributors can divide the work around those identified dependencies.

There is a cost to opening alternatives. A few consequential variations and a revealing attempt often suffice. Some questions remain worth keeping until a needed operation, collaborator or use becomes available; others can be set aside after their first attempt shows little prospective contribution.

B.5.QD:10 - Architectural Rationale

A new question needs an operation of construction. The instruction to find an interesting question becomes usable when it points to a dependency that failed or an operation that became available. This also connects developing a theory with applying it: an application can expose a new question, and a theoretical construction can create an application that could not previously be attempted.

The answer form matters because it determines what work counts as progress. A witness of impossibility can be as useful as a successful construction for deciding an allocation. A bound can answer an operational question while a unique prediction remains unavailable. These alternatives are obtained by examining the earlier result and its use.

The small case and the broader question develop together. Working the case tests whether the question identifies a real difference; stating the broader question prevents the case from becoming the only thing learned. Retaining unaffected results makes this development cumulative.

Practical interest includes opening future inquiry. The method asks for the next intelligible contribution while leaving later uses open.

B.5.QD:11 - SoTA-Echoing

For developing a question after a failed proof or conjecture, adapt Lakatos’s proof-analysis method in Proofs and Refutations (I) (1963), §3 and the beginning of §4. Distinguishing a counterexample to a lemma from one to the main conjecture preserves recoverable reasoning; asking for the missing construction improves on protecting the claim by convenient restrictions alone. Sections :4.1–:4.3 and :5.1 use that contribution.

The historical dialogue supplies a method of criticism and question change; the resulting mathematical claims need their arguments. Reopen the choice when a different failure prevents recovery of the consequential dependency. Original article.

For obtaining questions from either an unfinished proof or available constructions, adapt the distinction between goal-directed lemma discovery and bottom-up theory exploration in Zhang and Tan’s Automated Conjecturing and Theorem Finding: A Survey (2026), §§3 and 5. The two approaches support different entries in :4.2. The surveyed filters for false, redundant or uninteresting conjectures help theorem search; using those filters as a general question filter would discard a useful counterexample.

Section :4.3 instead evaluates the question’s contribution separately from a proposed answer’s truth. Syntactic complexity and proof-related scores remain local heuristics. Reopen when a stronger generation method offers more useful questions at comparable effort for the receiving practice. Survey.

For finding further uses of a successful operation, adopt Blelloch’s constructive treatment of all-prefix-sums in Prefix Sums and Their Applications (1993), §1.1. It exposes an operation and its application conditions, improving on retaining only a program’s final answer. Section :5.3 uses cumulative addition to develop an interval question; its range-sum derivation is worked here.

Prefix operations over other associative operators can serve other questions, but subtraction requires the additional algebraic structure used in this example. The source’s parallel implementations are separate Methods. Reopen when the operations, numeric semantics or workload change. Author’s chapter.

For questions beyond a fixed objective, adapt Wang et al.’s Enhanced POET (2020), §§2–3, through C.40’s coupled development of problems and ways. Relative difficulty and transfer can make a question worth retaining even when it is poorly served by the present best method. Against requiring a known route to a final objective, :4.5 keeps a useful nearer contribution and examines its cost.

The reported computational environments demonstrate that search approach under their conditions; they do not establish a universal measure of interest or development. E.10.INT supplies the broader distinction. Reopen when retained questions cease to enable useful transfer or the contributors’ capabilities change. Paper.

B.5.QD:12 - Relations

  • B.5 coordinates the reasoning cycle. B.5.RA recovers an argument; B.5.RR revises reasoning after a premise or question changes. This pattern constructs a question that can start that revision.
  • B.5.TC can reveal a newly expressible question when comparing accounts. B.5.2 generates candidate explanations once that is the needed contribution.
  • B.5.MPC connects the physical, mathematical and computational contributions a question needs. A.3.3, C.16 and C.29.2 supply state, measurement and computational-formulation work where applicable.
  • C.39 obtains a missing way to produce a distinguished result. C.40 develops problems and ways together; this pattern contributes the question-construction step.
  • C.22.2 describes a problem claim when that description is needed. E.10.INT, C.11 and C.11.DUA help choose a worthwhile inquiry and the effort to spend.
  • C.36.RP supports continuing a shared practice by recovering and changing its ways of inquiry. A.15.9 helps obtain and use a bounded contribution from another practice when needed.

B.5.QD:End

B.5.QD.CF - Reformulate a Problem by Examining Its Conflicting Assumptions

Type: Method pattern Status: Stable Normativity: Normative

B.5.QD.CF:1 - Problem frame

Use this when an account makes needed outcomes appear incompatible and you need to find what could change without losing the purpose of the work. Two requirements may concern different operating conditions, yet the model gives them one setting. A familiar means of obtaining one result may obstruct another result, although that means has never been shown necessary.

First useful move. Identify which demands must hold together for the wanted result, and what makes you think they conflict. A shared condition may rule out the whole combination while every pair is compatible. For example, requiring one fixed setting to be at least 6 during work and at most 2 during quiet operation excludes every fixed value. Whether the device may change settings between conditions is a question about its design and use.

The result is a reformulated question or candidate construction whose retained requirements, changed premise and remaining obstacle are understood. Sometimes the useful result is an impossibility under the retained conditions, followed by a decision about which requirement can change.

The reader needs enough knowledge to interpret the requirements and the inference connecting them, or access to someone who can supply that interpretation. State the requirements in ordinary language and identify when they must hold together. Use a small case if it helps expose a conflict. Use an adequate existing solution. If the only unresolved question is choosing an accepted trade-off, compare the options; recovering premises is useful when it could reveal another option or change the grounds for that choice.

B.5.QD.CF:2 - Problem

An incompatibility identifies a limit of the statements used together. It does not identify the repair. A requirement may have been mistaken for a means, two situations may have been collapsed into one, or the desired result may be impossible under conditions that must remain.

Two shortcuts lose the useful question. Continuing with the proposed means can make an avoidable conflict look inevitable. Relaxing a condition until the account has a solution can make a different task look like a solution of the original one.

The work is to reconstruct why the conflict follows, find a consequential premise worth examining, and develop another construction or a supported limit while keeping the original need recoverable.

B.5.QD.CF:3 - Forces

ForceTension
Needed outcome and familiar meansA proven way is valuable, but familiarity can conceal an unsupported necessity claim.
Clear conflict and hidden conditionsA small conflicting set is easier to inspect; other requirements can defeat its proposed repair.
Exploration and commitmentA temporary relaxation can reveal a possibility before anyone has the means or authority to realize it.
Precision and effortA formal construction can settle a consequential inference; ordinary reasoning may locate the question.
Continuity and changeA narrower question may produce useful work while leaving the original need partly unanswered.

B.5.QD.CF:4 - Solution

Recover the need and the conflict → expose the premises producing it → examine an assumed necessity or shared condition → construct another question or way → return to the retained requirements.

Enter at the unresolved step. A short explanation beside the model can carry the result.

B.5.QD.CF:4.1 - State what must be obtained and where the conflict arises

Say what result is needed, for whom or for what later operation, and under which conditions. Separate that result from the proposed means of obtaining it. Keep a requirement that the work cannot change visible throughout the attempt.

Recover the incompatibility in its stated scope. Two propositions may contradict each other under one interpretation. Two physical operations may compete for the same resource at the same time. Two people may disagree about a premise or about which outcome matters. A trade-off may permit both outcomes to some degree. These situations require different reasoning; use this method where examining the asserted incompatibility can change the construction question.

Identify the participants and conditions shared by the conflicting statements. Does “the setting” mean the same setting in the same operating condition? Does “available” refer to immediate access or access after a permitted delay? B.5.FM helps construct a missing distinction; B.5.TC compares different accounts when their questions or output meanings are unsettled.

B.5.QD.CF:4.2 - Recover the inference and the status of its premises

Work backward from the conflict to the statements that produce it. Use B.5.RA if the argument needs reconstruction. Keep their different roles understandable: what the work requests, what was observed, what the model assumes, and which proposed operation is supposed to supply a result.

Pay attention to necessity. “To obtain A, D is necessary” means A implies D. “Doing D under conditions K obtains A” is a sufficiency claim. Success with D alone supplies no argument that every way of obtaining A requires D. The question may be whether another operation E obtains A while avoiding the condition that obstructs the other requirement.

A small set of jointly conflicting statements is often sufficient. For a finite constraint account, one can hold the requirements fixed and examine what happens when one assumption is omitted. A remaining solution identifies a candidate assumption to examine; it does not establish that the assumption is false or dispensable in the intended work.

Find a minimal conflicting set only when the smaller explanation changes the task. “Subset-minimal” means that removing any member of that set removes its inconsistency. It does not mean that the set is the smallest possible, that repairing it is cheapest, or that no other conflict remains outside it.

B.5.QD.CF:4.3 - Turn the consequential premise into a constructive question

Choose a premise whose change could matter and whose status is open to examination. Work the corresponding question:

  • An assumed necessary means creates the conflict. What operation could obtain the needed outcome without that means? Follow the result that the means supplied; use C.39 to find or develop a replacement operation.
  • One value is imposed across different conditions. Do the requirements concern distinguishable participants, times or situations? If so, what construction permits the required values in those conditions? If they concern the same participant and condition, a second name supplies no new possibility.
  • A restriction belongs to the representation or construction. What relation must a different representation or construction preserve, and how could it satisfy the retained requirements? B.5.FM constructs the relation; B.5.RR carries its change through the affected reasoning.

These are common entries. State what would answer the selected question: an alternative operation, a condition-dependent construction, a counterexample to necessity, or a derivation of impossibility.

A tentative assumption change lets you explore that question. Keep the conclusion conditional until the replacement premise or operation has the support its use needs. Reconsider a requirement explicitly when that is the selected change; a convenient answer to the changed requirement leaves the original one open.

B.5.QD.CF:4.4 - Construct a small answer and return it to the whole need

Use a construction or argument that can answer the question. For a proposed way of working, establish what obtains the needed result under its intended conditions. A case that includes the changed condition can expose an obstruction. When one set of grounds applies throughout the proposed range, show how it covers that range. A mathematical witness supplies a possible configuration. Establish the means of realizing it when the work calls for a physical or organizational result.

Return the change to the complete need. Recover the grounds for each retained requirement and for their joint satisfaction on the same admissible arrangement. Reuse grounds that still apply to that arrangement. Repairing a conflicting subset can leave a different conflict untouched. A switch between two individually feasible settings may take too long, and an archive that reproduces a calculation may violate a retained deletion requirement.

Keep three facts distinguishable: the revised statements are compatible; an operation is proposed that would supply their values; that operation has produced or otherwise established the result required for this use. Use the strongest available fact the question needs. An inquiry about what to design next may be answered by a conditional construction; deploying it can require further work.

If the conditions remain incompatible, show which of them imply that conclusion and what it settles. A proof that no permitted arrangement works completes an inquiry about feasibility. When a working arrangement has been commissioned, the proof explains why it cannot be supplied under those conditions. A decision to change an obligation, or to accept that finding as the deliverable, belongs to whoever holds that choice.

B.5.QD.CF:4.5 - Continue at the missing contribution, or use the answer

Use a sufficient answer. Otherwise say which part of the original need remains and what the next attainable result would change. B.5.QD develops that question; C.40.CD connects it with development of a way to answer it. A theoretical result can be worth pursuing because it makes further constructions or explanations possible, even before an application is known.

Compare the likely contribution of further work with its burden, including obtaining a capability or resource and the work displaced. Start with available arguments, results and specialist contributions. C.11.DUA applies when the worth of another information-gathering step is unsettled. The pattern requires no experiment to acknowledge that a proposal remains conditional.

Several contributors can divide this work by the result needed next: one recovers the disputed necessity, another constructs a replacement, and another interprets its consequences for the original work. They need the retained requirements and the meaning of each returned result. When this reasoning is a constituent of design or research, its local success must support the encompassing method’s result; compatibility may be insufficient for that result. Constituent and encompassing methods can be enacted during the same work under B.1.5.

B.5.QD.CF:4.6 - Separate recognition from assurance

An asserted conflict and a premise worth examining can be enough to start. Recognition does not require an exhaustive diagnosis or a proof that a repair exists.

Judge each resulting claim by what it says. An implication needs valid reasoning under its premises. A replacement operation needs the mathematical, physical or professional basis appropriate to its intended use. A requirement change needs the decision that permits it. The method supplies a way to find and formulate these questions; their answers come from the corresponding subject methods.

Reopen the result when a retained requirement, affected premise, available operation or intended use changes. Preserve independently usable parts while revising the affected inference.

B.5.QD.CF:5 - Archetypal Grounding

The following constructed cases supply the conditions needed for their reasoning. They demonstrate different reformulations and a case in which the original demand remains impossible.

B.5.QD.CF:5.1 - Distinguish operating conditions without inventing a machine

A proposed device has one fixed setting p. The task requires p to be at least 6 during work and at most 2 during quiet operation. In the proposed design, both requirements constrain the same fixed value; no such value exists.

Recover the extra premise: the setting is fixed across those operating conditions. Let p_work and p_quiet describe the two values. The account is:

  • p_work ≥ 6;
  • p_quiet ≤ 2;
  • p_work = p_quiet.

Keeping the two requirements and reconsidering the equality produces a construction question: Can the device select different settings in the two distinguishable conditions? The values (6,2) satisfy the revised inequalities. They identify what a switching construction would have to supply.

That answer is conditional. The device must be able to recognize the condition and reach the required setting in time, using the resources permitted by the task. If a transition takes three seconds while the retained requirement allows one second, this proposed transition fails. A faster operation, another construction or an authorized requirement change is needed.

If instead both inequalities concern the same operation at the same time, separating their names would misrepresent the task. The inequality 6 ≤ p ≤ 2 remains impossible. The result then identifies the requirements that cannot both be retained.

B.5.QD.CF:5.2 - Replace an assumed means while retaining two outcomes

A team must reproduce an earlier calculation and use new prices for new calculations. A file stores the quantity 3 and the price 10, so the earlier result is 30. Tomorrow the price becomes 12 and the new result must be 36.

The proposed practice keeps only one mutable price value. Reproducing the earlier result is taken to require keeping that value at 10; obtaining the new result requires changing it to 12. The conflict depends on that proposed means of recovering the earlier input.

Ask instead: What information and operation reproduce the earlier calculation without freezing the current price? For this case, the calculation is quantity times price. Retaining the input pair (3,10), the multiplication rule and the identity of the earlier calculation supplies its result 30. The pair (3,12) supplies 36. A versioned input or a retained calculation record can therefore replace the supposed need for one unchanged current value.

The scope matters. This construction suffices for the supplied arithmetic question. If the earlier result used a rounding rule, exchange rate or other input, that contribution must also remain recoverable. A claim about who approved the transaction asks another question and is not established by recomputing 30.

Now change the retained requirements: every copy of the earlier price must be destroyed, and no equivalent information may remain, but the system must later recover that price uniquely. The retained-input proposal violates the deletion requirement. The conflict has not been repaired under these new conditions. The next case isolates why this stronger combination can be impossible.

B.5.QD.CF:5.3 - Return an impossibility instead of hiding retained information

A device receives one bit x, either 0 or 1. Complete erasure in this formal task means that, afterward, its entire accessible state is the same s for both inputs; there is no external record or later input revealing x. A deterministic operation g must then recover the original bit for either input.

For the input 0, recovery requires g(s)=0. For the input 1, it requires g(s)=1. The same operation on the same state cannot satisfy both. The required erasure and universal recovery are incompatible under the supplied model.

An external copy or a different final state would allow other constructions, but each changes the complete-erasure condition. Renaming an external copy as a pointer preserves information rather than meeting that condition. Returning a default value changes the recovery requirement. Neither is a solution to the original task.

The result can end the construction search under these premises. If the work instead permits a retained distinction, develop that changed question. A later physical implementation also has a physical model and its own scope; the argument here establishes the finite information constraint stated above.

B.5.QD.CF:6 - Bias-Annotation

The familiar means can dominate the description of a need. Recovering the result it supplies helps make a replacement thinkable. Conversely, a wish for a harmonious answer can lead the practitioner to relax the condition that mattered. Returning to all retained requirements exposes that loss.

The easiest premise to remove may be the one with the strongest physical or practical basis. Diagnose its role without treating mathematical removability as permission to discard it.

B.5.QD.CF:7 - Conformance Checklist

  • The needed result and the scope of the incompatibility are recoverable.
  • The inference distinguishes requirements, observations, modeling assumptions and proposed means where their different roles change the answer.
  • A claimed necessity has its direction and basis; a proposed replacement supplies the result previously attributed to that means.
  • A changed participant or condition corresponds to the intended situation, rather than merely changing a name.
  • A proposed repair has grounds for the joint result required of the same arrangement, including relevant conditions outside the diagnosed conflict.
  • A compatible account, conditional construction, obtained result and authorized requirement change retain their different meanings.
  • A sufficient answer or impossibility can complete the question it settles. Any separate result owed, or decision to revise it, remains identifiable.

B.5.QD.CF:8 - Common Anti-Patterns and How to Avoid Them

Failure invited by conflict repairBetter move
“This way has always worked, so the result requires it.”Recover what the way supplies and ask whether another operation supplies that contribution.
A solver returns a solution after a hard requirement is removed.State the changed requirement and return to the original need; the witness answers the relaxed problem.
Two names are introduced for one quantity in one condition.Establish the distinction or retain the incompatibility, as in :5.1.
The small conflicting set is repaired while another affected requirement is ignored.Reapply the retained requirements; inspect the transition time or lost information that the change can affect.
A consistent description is presented as an implemented repair.State the operation and support needed to obtain the result.
Every conflict is promised a solution that preserves every demand.Return the supported limit or requirement-change question when no warranted repair exists.

B.5.QD.CF:9 - Consequences

The method can turn a conflict into a more useful construction question while preserving the purpose of the work. It also makes an impossibility usable: contributors can stop an unproductive search or decide which demand is open to change.

Recovering premises and returning a proposal to the full need costs effort. Concentrating on the inference that changes the next action keeps this effort bounded. Some conflicts remain unresolved because the replacement operation, relevant knowledge or authority is unavailable.

B.5.QD.CF:10 - Architectural Rationale

An incompatibility is relational: it depends on statements used together. That is why inspecting one requirement in isolation often misses the constructive opening. Separating a needed outcome from an assumed necessary means exposes a question about how else the outcome could be obtained.

The return to the original need prevents successful reformulation from becoming accidental goal substitution. A conditional construction, an achieved result and an impossibility make different contributions to the encompassing work. Keeping those contributions distinct allows division of work between people and AI.

Conflict-driven reformulation is a constituent of question development with its own recurring difficulty and operation. B.5.QD supplies the broader development of a question from either failure or success. This pattern unfolds the move from conflicting premises to an alternative construction or a useful limit, leaving subject construction and validation with their methods.

B.5.QD.CF:11 - SoTA-Echoing

For the question “How can incompatible demands reveal an alternative means?”, adapt the Theory of Constraints move from a required outcome to its assumed necessary means. Against choosing a side before examining that necessity, the selected method asks for a replacement that supplies the retained outcome. Sections :4.2–:4.4 and :5.2 carry this difference. Goldratt’s Letter #5 gives the original method argument; the ProConCloud account includes conditional and alternative changes. They are method proposals, not independent evidence of this pattern’s effectiveness.

Reject a guarantee of preserving every demand and a mandatory experiment for every case. The selected return to retained requirements can cost more than choosing a side, but is warranted when another construction could change that choice. Reopen this comparison if a stronger method finds such constructions with less burden or reveals a missing class of consequential assumptions.

For “What does a diagnosed formal conflict establish?”, adopt the distinction between an inconsistent subset and a correction subset from Gamba, Bogaerts and Guns, Efficiently Explaining CSPs with Unsatisfiable Subset Optimization, Definitions 1–3. Against treating a returned correction as the practical repair, :4.2 and :4.4 preserve its narrower meaning: removing those constraints permits consistency in that formal problem. Adapt the distinction to optional diagnosis here; subset minimality and optimization are required only when their extra result matters.

The source’s algorithms concern constraint problems, and their performance does not transfer to arbitrary disagreements. Reopen when a different constraint semantics changes what the diagnostic result means or a cheaper explanation suffices.

For “How should attempted construction change the problem?”, adapt the problem–solution co-evolution account in Parsons and Shukla, Beyond Problem Solving: Framing and Problem–Solution Co-Evolution in Data Visualization Design, §§4–5 and 6.4. Against fixing the problem once and testing only proposed solutions, :4.3–:4.5 return a failed construction to the consequential premise and then to the original need.

Their study of eleven selected experts supplies practice-specific observations, not a universal creative mechanism or a test of this method. The extra return is useful when the attempted construction changes the question; an adequate existing formulation needs no such work. Reopen when evidence or another practice reveals that the return loses a needed distinction or obstructs a better continuation.

B.5.QD.CF:12 - Relations

  • B.5.QD develops a useful question from a result or construction; this pattern specializes the conflict-to-question contribution.
  • B.5.RA recovers the argument; B.5.RR revises the reasoning affected by a premise change. B.5.TC compares accounts whose meanings or conditions may differ.
  • B.5.FM constructs a distinction and its relations. C.39 develops a way to obtain the needed result; C.40.CD develops that way and the problem together.
  • B.1.5 supplies the Method-parthood relation when this reasoning contributes to an encompassing method while its constituent operations are enacted.
  • C.11.DUA helps decide whether further information work can change a useful continuation enough to warrant its burden. A.15.9 helps obtain a needed contribution from another practice.

B.5.QD.CF:End

B.5.1 - Coordinate Development States: Explore → Shape → Evidence → Operate

Status: Stable

B.5.1:1 - Problem Frame

Use this state model when a development project needs a shared account of whether a U.Episteme or U.System is being explored, shaped, evaluated or operated. The gain is to make the development focus and the conditions for an intended transition visible. Without that distinction, a team may refine a design indefinitely or claim operational readiness before the required validation.

A development state describes the project’s treatment of its subject, not the assurance of every claim about it. A qualified explanation, proof or empirical result may answer its receiving question while development remains in an earlier state. Ordinary use of that result needs no new development-state assignment.

B.5.1:2 - Problem

How can a project coordinate concept development and operational readiness without confusing completion of its present task, the subject’s development state and the support for a claim?

B.5.1:3 - Solution

Use the four development states to name the current focus for the episteme or system under development. For an intended transition, identify the design, evidence and operational conditions that need to hold. The Canonical Reasoning Cycle (B.5) can supply the reasoning contributions; the state names do not prescribe an assurance ladder.

Start with the project decision. For a report on which components actually serve users, use evidence of their operation during the period. A current development-state record can suffice when its meaning establishes that use. To decide whether the service they form can begin operating, identify the configuration to be used and the conditions it must sustain. If you choose which constituents to examine, follow the ones whose state or interaction could change that decision. A qualification covering the intended arrangement can already settle the performance condition for that transition.

The Four Development States:

StateCore ActivityManager’s View: What It MeansPossible reasoning contributionsWhat the state leaves to the receiving claim and use
1. ExplorationGenerating possibilities. Frame the problem and compare candidate explanations or designs.“We are looking for a plausible direction and keeping the serious alternatives visible.”Candidate construction; abduction for explanatory conjectures (B.5.2)A qualified conjecture may be sufficient for the present question.
2. ShapingDefining a coherent form. Develop the selected direction and derive its relevant consequences.“We are making the design and its implications clear enough for the next intended use.”Construction and deductionLogical support concerns the consequence under its premises. A coherent design alone does not establish actual performance.
3. EvidenceEvaluating the relevant claims. Use applicable empirical or formal results and obtain missing evidence when it is required and feasible.“We are deciding whether the needed claims are supported in the intended conditions.”Empirical evaluation and formal reasoningExisting support can be sufficient.
4. OperationUsing in a live environment. Begin or continue the intended operation and monitor what its conditions require.“The system or episteme is in use, with the required operational conditions in place.”Reasoning about operating observations and needed changesReadiness and continuing use depend on the qualification, protective and authority conditions.

B.3.3 governs any assurance conclusion about the claim and receiving use. Retain a domain profile, proof obligation or validation requirement where that use requires it. Existing results count only when they cover the conditions; a missing required result can block the intended transition. A proposal to improve an excessive requirement does not waive a binding condition.

For Managers: Aligning States with Your Project Plan

Exploration can describe discovery, Shaping design, Evidence evaluation, and Operation live use and maintenance. Name the subject and the intended transition so that the team can tell what remains to be done. Completing a useful answer during Exploration does not mean that the developed system has entered Operation, nor that the answer must wait for every later project state.

Worked case. A service team completes B.5.2’s latency-spike inquiry with a qualified backup-interaction conjecture and live rivals. The possible causal probe is unavailable, so the explanatory result remains limited. An existing operational qualification supports a permitted diversion to a spare instance for this traffic and interval. The team can use that basis for the diversion without declaring the explanation validated or advancing a new design through Evidence.

If the team instead proposes a new deployment whose required load test is missing, that deployment remains blocked; the useful conjecture does not supply the missing qualification.

Suppose two live services each qualify to divert to the same spare. Can both divert together? If their traffic rates add and the spare is qualified for both traffic types together at every permitted mix up to the sum of their peak rates, its capacity covers the diversion. If the sum of the peaks exceeds the spare’s capacity, determine whether any permitted simultaneous mix exceeds its capacity for that mix. One such mix defeats a guarantee covering every permitted mix. Diversion during a particular interval may still work. For a report confined to use today, evidence of that use can settle the question.

B.5.1:4 - Conformance Checklist

  • CC-B5.1.1 (State Explicitness): A state-bearing U.Episteme or U.System coordinated through this development model MUST be tagged with its current state from {Exploration, Shaping, Evidence, Operation}. Identify the development subject; a separate bounded result need not be given that subject’s state.
  • CC-B5.1.2 (Sequential Progression): When advancing the development subject through this cycle, the project SHALL follow the state sequence. A departure MUST be justified against the intended transition’s prerequisites; it cannot waive binding proof, validation or operational conditions. Completing or using a sufficient bounded result without advancing the development subject is not a skipped state and needs no skip justification.
  • CC-B5.1.3 (Reasoning Cycle Alignment): A transition MUST have the reasoning contributions and results needed by its project and domain conditions. Before a hypothesis-led test, derive the consequences needed to interpret it. Reuse prior reasoning or evidence when it meets those conditions; repeat a phase only for an unresolved need. Phase completion alone SHALL NOT confer an assurance level or operational permission.

B.5.1:5 - Consequences

BenefitsTrade-offs / Mitigations
Project Visibility: The states give a shared language for the development focus and intended transition.Risk of Bureaucracy: Treating states as a universal evidence recipe can create unnecessary work. Use the transition conditions and reuse covering results.
Improved Focus: Exploration, design, evaluation and live operation have distinguishable immediate questions.A result can serve another use without changing the development subject’s state; keep those two judgements separate.
Reduces “It’s Done” Ambiguity: The team can say whether it completed the present answer, the design or the conditions for operation.A state label cannot replace the readiness criteria.

B.5.1:6 - Rationale

This pattern operationalizes the Principle of State Explicitness (P-9) for development coordination. The four states make the project’s focus and transition obligations inspectable. B.5 supplies reasoning contributions and B.3.3 qualifies assurance for a claim and use. Keeping those questions distinct lets a project use a sufficient result while continuing development of its subject.

B.5.1:7 - Relations

  • Uses reasoning contributions from: B.5 Choose the Next Reasoning Contribution (Canonical Reasoning Cycle); B.5.2 Generate and Compare Candidate Explanations (Abductive Loop) commonly supplies Exploration with qualified conjectures.
  • Uses for claim-specific assurance: B.3.3 Assurance Subtypes & Levels. Development states neither organize its levels nor establish the adequacy of a claim.
  • Coordinates with: B.4 Coordinate Repeated Adaptation (Canonical Evolution Loop). Its evolution phases and these development states are not a one-to-one mapping.

B.5.1:End

B.5.2 - Generate and Compare Candidate Explanations (Abductive Loop)

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain-name. Generate and compare candidate explanations (Abductive Loop).

Builds on. B.5 Choose the Next Reasoning Contribution (Canonical Reasoning Cycle), B.5.1 Exploration, B.5.2.0 U.AbductivePrompt, A.10, B.3.3.

Coordinates with. B.4.1 for needed route publication, A.16 for admissible language-state moves, A.6.P for relation wording, C.16.Q for evaluative meaning, and A.6.A for action-first wording. Use these wording-restoration contributions when the unclear meaning affects the explanatory question or its scope.

B.5.2:1 - Problem frame

Use this when. An anomaly, opportunity or probe question needs candidate explanations that can be compared on their present plausibility. State the explanatory question, develop candidates and look for serious alternative explanations. The first useful result is a qualified conjecture with its supports, fragilities and allowed use, or a justified abort, defer or split outcome.

An adequate present answer or action need not enter abduction to generate another research task. Use C.11 for a live choice among feasible actions and C.28 when a causal-support claim is needed. Abduction contributes candidate explanatory content; it is not the complete evidence synthesis or action decision.

Start from what the recipient needs explained and who is to choose the question. When the commission is to check a supplied explanation, first derive what it implies for that case and use any adequate evidence already available. When it is to find an explanation, the supplied candidate is one possibility to examine. An invitation to discover questions can give the investigator the further choice of what to pursue.

B.5.2:2 - Problem

Abductive work can fail in several ways:

  1. Inquiry stalls at surprise. A team encounters an anomaly, opportunity, or probe question but does not know how to form and compare candidate explanations.
  2. Origin is lost. Once a conjecture appears, the initiating prompt, rival candidates, and early plausibility grounds disappear from the record.
  3. Candidate space collapses too early. The first plausible-seeming explanation is treated as the explanation, even though alternatives were never exposed.
  4. Selection becomes opaque. A chosen conjecture moves downstream without a visible record of why it outranked alternatives.
  5. Untestable hypotheses survive too long. A candidate with no interpretable implication or possible discriminating contrast is treated as a useful explanation. Distinguish this from a meaningful conjecture whose possible check is presently unavailable.

B.5.2:3 - Forces

ForceTension
Generativity vs disciplineThe loop must admit non-deductive candidate generation without making arbitrary guesses look admissible.
Breadth vs typed entryAbduction should begin from more than anomaly alone, but not from any untyped prose fragment.
Rival diversity vs decision pressureSeveral candidates should remain visible long enough to compare them, while allowing one prime hypothesis to progress.
Speed vs traceabilityThe loop must be light enough for repeated use but explicit enough to preserve provenance and later review.
Plausibility vs evidenceA candidate may be worth pursuing before evidence is strong, but it needs explicit plausibility grounds.

B.5.2:4 - Solution - Abductive micro-cycle

B.5.2 begins from an account that meets B.5.2.0’s U.AbductivePrompt entry conditions, develops candidate explanations and compares them under explicit plausibility criteria. Return a qualified conjecture when the grounds support it, or an abort, defer or split outcome under §14.2. Preserve the prompt, candidates considered, supports, limitations and allowed downstream use. Abduction alone assigns no AssuranceLevel.

B.5.2:4.1 - Nature of abduction in FPF

Abduction develops candidate explanations, models or conjectures for a declared explanatory prompt and compares their plausibility. Prefer a candidate only to the extent that the comparison warrants that preference. A conjecture’s plausibility may justify keeping or using it for a bounded purpose; it does not establish its causal mechanism or a stronger empirical claim. Deduction, evidence synthesis and action choice keep their questions.

B.5.2:4.2 - Four-step micro-cycle

StepCore activityRequired publication outcome
1. Frame the promptState the initiating explanatory question precisely enough that the unexplained contrast, opportunity, or probe pressure is explicit.A prompt account with its open question, species, scope and motivating grounds under B.5.2.0; reuse an adequate existing account.
2. Generate candidate hypothesesDevelop candidates that could explain the prompt and look for serious rivals.The candidates considered, including any limit from not identifying a serious rival.
3. Apply plausibility filtersCompare candidates against explicit plausibility criteria.A short rationale stating why each considered candidate remains live, is deferred or is rejected, and what comparison those grounds support.
4. Return the supported resultSelect a conjecture when the comparison warrants it; otherwise return the applicable outcome in §14.2.A hypothesis-bearing U.Episteme with its prompt, selection rationale, any live rivals, supports, fragilities and allowed use when a conjecture is selected; otherwise the justified abort, defer or split outcome.

To construct a candidate, work back from the unexplained contrast. What relation could produce both the observed outcome under one condition and the comparison outcome under the other? Hold the proposed factor fixed and look for another way to obtain the contrast. It might arise from an interaction among components, from how the observation was made, or from an assumption in the account. In a theoretical inquiry, trace apparently incompatible results to their assumptions and vary one that could change what each result says. Keep a candidate when you can show what would follow from it for the prompt.

The loop is iterable. A selected prime hypothesis may later be replaced, narrowed, or reopened if deduction, probe work, or evidence reveals a better rival.

B.5.2:4.3 - Entry discipline via U.AbductivePrompt

AnomalyStatement remains a prompt species, but it is not the only one. B.5.2 also accepts the broader prompt species governed by B.5.2.0, such as ProblemCuePrompt, OpportunityCuePrompt, and ProbeCuePrompt.

B.5.2:4.4 - Plausibility filters

The filtering step is local and context-sensitive, but the criteria used SHALL be explicit. Typical filters include:

  • Parsimony. Does the candidate introduce only the additional structure that the prompt requires?
  • Explanatory reach. How much of the prompt does the candidate account for?
  • Consistency with established constraints. Does the candidate avoid collision with trusted pillars, mechanisms, or scope declarations?
  • Falsifiability / probeability. What implication, deduction or possible observation could discriminate the candidate from its rivals? Keep that question separate from whether a check is obtainable and worth performing now.
  • Scope fit. Is the candidate framed for the declared prompt scope rather than for an inflated or shifted target?

Select the filters needed to judge explanatory adequacy and preference for this prompt and intended use. Make their grounds, any decisive comparison and unresolved trade-offs explicit.

When a causal hypothesis cannot yield a discriminating implication because its mechanisms and rival accounts are unspecified, use C.28.CM to construct comparable causal models. Return their conditional consequences and unresolved premises to these plausibility filters. A useful hypothesis whose present question is answered needs no additional model to remain a candidate.

B.5.2:4.5 - Abductive Unfolding Structure Block

When the question concerns possible continuations of abductive work and their conditions, use A.22.CGUS’s ordinary branch. Open its formal branch only when the receiving use depends on the unfolding organization’s CGUS identity or membership; reuse of a hypothesis note alone does not require that branch.

AbductiveUnfoldingStructureBlock:
  unfoldingStructureRef: one independently identified A.22.CGUS structure
  abductivePromptRef:
  cueSetWithDownstreamPatternAlternativesRef:
  rivalHypothesisSetRef:
  hypothesisGenerationLoci[]:
  plausibilityConstraintRefs[]:
  evidenceReturnLoci[]:
  languageStateMoveRefs[]:
  poolPolicyOrSelectionRef?:

Use unfoldingStructureRef to designate the selected structure. Recover its constituents, obtaining relation occurrences, applied constraints and selection-use frame under A.22; qualify its loci and potential continuations under A.22.CGUS. Keep the describing record separate from that identity.

Use cueSetWithDownstreamPatternAlternativesRef when the prompt still carries several possible patterns for the next question. Use rivalHypothesisSetRef for the candidates compared and preserve the comparison limit when no serious rival was identified.

Use evidenceReturnLoci[] to say where later evidence, deduction, probe design, or assurance work can return; do not use those loci as evidence. Abductive plausibility comparison remains here. When a distinct result is needed, use C.18 for archive or front claims, C.19 for live-pool policy, G.5 for a selector’s selected-set declaration, or the method for the required comparison.

AbductiveSearchUnfoldingStructure is a local designation for an A.22.CGUS structure selected for an abductive-search question; it supplies no additional identity rule.

B.5.2:5 - Archetypal Grounding

Tell. Abduction develops candidate conjectures from an admissible prompt through generation, consideration of serious alternatives and plausibility comparison.

Show (System). An operations team sees a recurring latency spike that existing explanations do not cover. They publish an AnomalyStatement, compare rival causes against current telemetry and mechanism knowledge, and retain a qualified prime conjecture. They name a possible discriminating probe.

Show (Episteme). A research group notices that two accepted results no longer fit together under one framing. It publishes a ProbeCuePrompt, enumerates several rival explanatory reframings, rejects the ones that fail scope fit or yield no interpretable implication, deduction or possible discriminating contrast, and advances one candidate explanation as the next working hypothesis.

B.5.2:6 - Bias-Annotation

This pattern favors looking for serious alternatives, making plausibility grounds explicit and preserving prompt provenance.

B.5.2:7 - Conformance Checklist

  • CC-B.5.2-1 Every abductive run SHALL begin from a question account whose content and grounds meet B.5.2.0’s U.AbductivePrompt entry conditions.
  • CC-B.5.2-2 A conforming abductive run SHALL make the serious candidates considered recoverable. When no serious rival has been identified, state that limit and qualify any preference claim by the available comparison.
  • CC-B.5.2-3 Selection of a prime hypothesis SHALL state the plausibility criteria and grounds sufficient to justify its preference for the declared prompt and intended use.
  • CC-B.5.2-4 The selected prime hypothesis SHALL be published as a hypothesis-bearing U.Episteme with its scope, support and limitations. An assurance level, if a receiving use requires one, SHALL follow B.3.3’s applicable justified profile rather than the fact that abduction occurred.
  • CC-B.5.2-5 The prime hypothesis record SHALL preserve a link to the initiating prompt and to the filtering rationale that justified selection.
  • CC-B.5.2-6 A conforming conjecture SHALL expose an interpretable implication, deduction or possible discriminating contrast. The availability and value of a check SHALL be considered separately before selecting evidence acquisition. An unavailable probe neither creates an observation nor by itself forbids a separately supported present decision.

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

Anti-patternWhat it looks likeHow FPF prevents it
Authority candidateOne favored conjecture is advanced without considering serious alternatives or making its plausibility grounds explicit.CC-B.5.2-2 and CC-B.5.2-3 preserve the candidates considered and the grounds for any preference.
Untestable grand conjectureThe candidate sounds explanatory but has no interpretable implication or discriminating contrast.Use CC-B.5.2-6 to make its implications clear or refuse that abductive result. Do not confuse absence of a useful implication with temporary unavailability of a meaningful check.
Prompt amnesiaA later reader can see the conjecture but not the initiating anomaly, opportunity, or probe pressure.CC-B.5.2-1 and CC-B.5.2-5 keep prompt provenance attached.
Symptom patchingThe selected candidate only redescribes a visible symptom and leaves the prompt unresolved.The plausibility filter for explanatory reach forces the candidate to be compared against the whole prompt.

B.5.2:9 - Consequences

BenefitTrade-off / Mitigation
Disciplined generativity. Abduction stays inventive without collapsing into formless conjecturing.Requires prompt and filter publication; mitigation: the required record can remain lightweight.
Traceable hypothesis origin. Later review can reconstruct why a conjecture entered the reasoning cycle.Adds a small provenance-support load; mitigation: reuse prompt and candidate-set notes from adjacent patterns.
Downstream use. A hypothesis-bearing episteme gives the receiving question its scope, rivals, support and limitations.A candidate can remain useful without being confirmed or receiving a universal level; a stronger claim needs its evidence.
Admissible reopening. Rival candidates can be revisited when later work undermines the selected prime hypothesis.Demands editorial discipline so that abandoned rivals remain legible rather than vanishing.

B.5.2:10 - Rationale

For the hypothesis-led empirical inquiry described in B.5, B.5.2 supplies explanation-led abduction before deduction and induction. It keeps hypothesis generation explicit, connects it to typed prompt publications, and prepares the output for later assurance work without pretending that early plausibility is already evidence.

B.5.2:11 - SoTA-Echoing

Iterative comparison keeps a candidate explanation open to revision as rival explanations and plausibility grounds change. A short publication can preserve the prompt, rival candidates and comparison rationale.

B.5.2:12 - Relations

  • Supplies explanation-led abduction within: B.5’s hypothesis-led empirical inquiry, before deduction and induction.
  • Typically operates during: B.5.1 Exploration.
  • Consumes: U.AbductivePrompt publications from B.5.2.0, often reached through B.4.1 and A.16.
  • Returns: a hypothesis-bearing U.Episteme with conjectural content, supports, fragilities and allowed use when a conjecture is selected; otherwise the justified abort, defer or split outcome.
  • Provides inputs for: deduction, probe design and evidence synthesis when those questions are live. C.11 governs a separate feasible-action or acquisition choice; C.28 supplies needed causal-use support. Naming a possible experiment does not by itself fund or schedule its performance.
  • Uses: C.28.CM when causal mechanisms and alternatives must be constructed before their implications can inform the plausibility comparison.
  • Coordinates with: A.22.CGUS when the abductive prompt, B.4.1 cue publication, rival hypotheses, plausibility constraints, evidence-return loci, and downstream tests must be inspected as an AbductiveSearchUnfoldingStructure.

B.5.2:12.1 - Prompt-entry broadening via U.AbductivePrompt

B.5.2 accepts U.AbductivePrompt. AnomalyStatement is one species alongside cue-derived prompt species such as ProblemCuePrompt, OpportunityCuePrompt, and ProbeCuePrompt.

B.5.2:13 - Prompt, Candidate, and Hypothesis Package Discipline

Keep the prompt, the candidate set, and the selected prime hypothesis distinguishable in the publication. One paragraph can suffice when the question, rivals, selection grounds and outcome remain recoverable. Separate or link their expressions when independent revision or a receiving use needs that separation.

B.5.2:13.1 - Prompt package

A conforming prompt package should make explicit:

  • the prompt species under B.5.2.0 and its applicable conditions,
  • the open question that makes abduction necessary,
  • the declared scope under which the question is being posed,
  • the witnesses or provenance cues that made the prompt worth preserving,
  • and any limitation of an existing explanation or model that motivates the question.

Use the wording-restoration pattern when the explanatory question, its scope or its intended meanings remain unclear: A.6.P for a relation, A.6.A for action-first wording, or C.16.Q for an evaluative term. Use an adequate question account under B.5.2.0’s entry conditions.

B.5.2:13.2 - Candidate-set note

A candidate-set note preserves the candidates considered and the comparison they support. Make visible:

  • candidate identifiers or short names,
  • the differentiating claim each candidate adds,
  • the principal plausibility supports and liabilities of each candidate,
  • whether the candidate remains live, is deferred, or is rejected,
  • and the interpretable implications, deductions or possible discriminating contrasts relevant to the comparison, with an availability limitation when it changes the receiving use.

Keep the serious alternatives considered and the limits of the comparison recoverable, including when no preference is warranted.

B.5.2:13.3 - Prime-hypothesis record

For a selected prime hypothesis, make these contents recoverable:

  • the selected candidate,
  • the prompt it answers,
  • the criteria and grounds supporting its preference, with the limits of that comparison,
  • the scope within which it is being advanced,
  • the allowed downstream use or next question, which may concern deduction, a possible probe, a separately justified action or reconsideration; include availability limits when they change that use,
  • and any known fragilities visible at selection time.

These terms let the recipient choose a permitted continuation from the conjecture.

B.5.2:14 - Admissible Transitions, Abort Paths, and Reopening

The abductive loop keeps its outcomes distinct so the recipient can tell whether it receives a qualified conjecture, deferred rivals, or a prompt that needs reopening. None of these outcomes by itself establishes an assurance level or an evidence-acquisition commitment.

B.5.2:14.1 - Relation to B.4.1 and A.16

B.4.1 and A.16 can help preserve and clarify an initiating publication until it supplies an abductive prompt. B.5.2 begins only once the publication is ready to function as an abductive prompt. This boundary matters because it prevents two opposite errors:

  • premature abduction, where a cue is used to begin rival comparison before its question account meets B.5.2.0’s entry conditions;
  • delayed abduction, where an admissible prompt needs candidate comparison for the receiving question but remains in early cue form without that contribution.

B.5.2:14.2 - Abort, defer, and split cases

Not every abductive run should end in a prime hypothesis. Three non-selection outcomes are admissible:

  1. Abort. The prompt dissolves because the initiating anomaly or opportunity was misread, duplicated, or already answered elsewhere.
  2. Defer. The available candidates or grounds do not support a qualified conjecture or a warranted preference. Preserve any supported candidates and the unresolved explanatory or comparison question. A separately warranted present action may proceed under C.11.
  3. Split. When distinct questions require separate explanatory comparisons, distinguish those questions and their entry grounds. If the original question concerns how the contributions act together, identify what evidence or reasoning can connect their answers. Keep that question open until the connection warrants an answer.

B.5.2:14.3 - Reopening and rival reinstatement

A prime hypothesis may later lose support under deduction, probe results, or new evidence. When that happens, B.5.2 prefers explicit reopening to silent replacement.

A conforming reopening note should identify:

  • which prior prime hypothesis is being reopened,
  • whether a stored rival is being reinstated or a new candidate is entering,
  • what change in evidence, scope, or internal contradiction triggered the reopening,
  • and whether the explanatory question, its prompt account, or only the candidate ranking has changed. Apply B.5.2.0:4.2.1–4.2.2: a revised account may concern the same question; a changed question needs its entry grounds.

B.5.2:14.4 - Scope discipline during iteration

Compare the scope of the candidate with the explanatory question. To use an explanation of one occurrence for a recurring phenomenon, identify what makes the account apply across the occurrences that matter. One decisive case can already refute an explanation claimed for every occurrence. A new question about a different setting can be pursued under a commission to explore. For a fixed assignment, give the supported answer to the question asked and identify any change of assignment that needs agreement.

B.5.2:15 - Worked Examples

B.5.2:15.1 - Service degradation diagnosis

A service team notices recurring latency spikes during one operating window. The prompt species is AnomalyStatement: why does latency spike in the evening batch window despite unchanged nominal load?

Follow one slow request from arrival to completion. A stable count of arrivals can coexist with a growing downstream queue. A separate evening job could reduce the rate at which requests are served. A scheduled backup on the same storage path could also make a request wait. With other traffic held fixed, a cache invalidation regression could generate extra reads per arrival. Each mechanism can lengthen the wait, and several can act in the same window. A trace showing where this request waited may settle its own delay. To explain the recurring spike, establish how the observed requests contribute to the latency statistic and why the proposed relation holds over the relevant windows.

The evening timing and a plausible mechanism keep the backup-interaction conjecture in consideration. The longer queue can fit each proposed mechanism. To prefer one explanation, identify what that mechanism or combination predicts beyond the shared delay and compare those consequences with available observations or constraints. Keep explanations that the available grounds leave tied. A prospective test can still be worth doing. Isolating backup traffic and comparing latency against prior windows is a possible discriminator. When that probe is obtainable and its expected contribution justifies its cost and delay, it can be selected as separate work. The conjecture records no observation from that unperformed probe.

Now keep the same observations and rival set but make the probe window unavailable. The qualified conjecture and its uncertainty remain; if the available comparison cannot select a winner, defer that selection. No new test, waiver or study proposal is needed to finish the present abductive result.

In both variants, suppose an existing operational qualification independently supports a bounded diversion to a spare instance for this traffic and interval, with sufficient capacity and permission, across the causal possibilities still open for this decision. C.11 can support that service response on the available basis. Diverting traffic does not identify the cause; a causal claim about the mechanism needs the appropriate C.28 support. If that operational basis is absent, do not infer a justified diversion from conjecture plausibility.

B.5.2:15.2 - Opportunity-driven materials inquiry

A research group sees an opportunity rather than a failure: a new fabrication method appears to create a micro-structure with useful thermal behavior. The prompt species is OpportunityCuePrompt rather than anomaly.

Candidate hypotheses include:

  • the effect is caused by surface geometry,
  • it is caused by composition gradients,
  • or it is an effect of one measurement regime.

The geometry explanation is the prime conjecture because it fits more of the initial observations and suggests a clearer discriminating experiment. Keep the composition and measurement rivals visible. The possible experiment can inform a separate research choice; its description neither funds it nor makes it mandatory. Long-horizon research can be worthwhile on its declared contribution, without treating the conjecture as an established thermal-performance result.

B.5.2:15.3 - Probe-driven theory repair

A theory-maintenance group identifies a probe-worthy mismatch between two accepted claims. The prompt species is ProbeCuePrompt: what changed assumption would allow these two claims to coexist without contradiction?

The candidate set includes:

  • hidden scope restriction on the first claim,
  • mistaken invariance assumption in the second,
  • and a more general missing mediating construct.

Suppose the mediating construct accounts for both claims within their warranted scopes, while the scope-restriction and invariance alternatives each explain only one side of the mismatch. On those stated grounds, retain it as the prime hypothesis. Keep the scope-restriction rival available for comparison if later deductions expose a failure in that account; revise the preference when the new grounds warrant it.

B.5.2:16 - Authoring and Review Guidance

B.5.2:16.1 - For abductive-publication authors

For an abductive publication, make the prompt, serious candidates considered, plausibility grounds and outcome recoverable. If a prime hypothesis is warranted, explain its preference, allowed use and interpretable implication, deduction or possible discriminating contrast. Otherwise state the abort, defer or split outcome and its grounds under §14.2. Return to prompt-shaping or lexical repair when the question, scope or intended meanings remain unclear.

B.5.2:16.2 - For hypothesis reviewers

Hypothesis reviewers should not ask only whether the chosen hypothesis looks plausible. They should also ask:

  • whether the prompt was typed in an admissible way,
  • whether serious alternative explanations were considered and the candidate set and limits of comparison remain recoverable,
  • whether the stated criteria and their grounds support the asserted preference, including any unresolved trade-offs,
  • whether the selected hypothesis has an interpretable implication, deduction or possible discriminating contrast, with the availability and value of any check judged separately,
  • and how the comparison answers the original explanatory question, including the grounds for using a result obtained on a narrower set of cases.

B.5.2:16.3 - For integrators and assurance leads

Integrators receive a qualified conjecture or the justified abort, defer or split outcome. For a conjecture, preserve its prompt, candidates considered, supports, comparison rationale, fragilities and allowed use. Use B.3.3 only for a receiving assurance question, C.11 for a feasible-action or evidence-acquisition choice, and C.28 for causal support when needed. An unavailable probe can leave the explanation unresolved while an independently warranted bounded service action remains useful; do not turn the conjecture into a mandatory work item.

B.5.2:17 - Boundaries of abductive use

B.5.2:17.3 - Boundary to deduction and evidence

B.5.2 ends with a qualified prime conjecture or an explicit abort, defer or split outcome. Deduction, evidence acquisition, synthesis, assurance and action choice remain separate questions. Naming their possible contribution states a downstream-use boundary; it does not require a new experiment, guarantee its availability or prevent a present decision already supported on other grounds.

B.5.2:End

B.5.2.0 - Question Form for Entering Abduction (U.AbductivePrompt)

Type: Definitional (D) Status: Stable Normativity: Normative unless marked informative

Plain-name. Question form for entering abduction.

Use this when. A stabilized cue, opportunity, probe-related observation or anomaly raises an explanatory question for B.5.2. Publish the question, its scope and motivating grounds while rival explanations remain open.

What goes wrong if missed. A cue is forced into anomaly form, an opportunity is treated as a hypothesis, or a prompt-like sentence smuggles in the preferred answer before rival hypotheses can be compared.

What this buys. A common entry criterion for abduction: prompt species, open question, scope and motivating grounds remain recoverable while candidate explanations stay open.

Not this pattern when. When the object is a cue that still needs preservation or stabilization (A.16.1), a language-state threshold claim (C.2.4, C.2.5), a chosen hypothesis (B.5.2), or a selector decision about methods, substrates, or portfolios.

B.5.2.0:0 - Question, account and publication form

U.AbductivePrompt is a claim-bearing account of one open explanatory question. It records the question, its scope, prompt species and motivating grounds. It is a same-individual-dependent kind under U.Episteme: the account keeps C.2.1 identity, and §4.2.2 supplies its prompt-membership test. It may seed B.5.2 when those grounds and the applicable language-state thresholds support rival comparison. Expressions of accounts about different questions can follow the same reusable publication form.

B.5.2.0:1 - Problem frame

B.5.2 needs a question account that preserves its motivating grounds, including when they arise from an opportunity or probe rather than an anomaly.

B.5.2.0:2 - Problem

If anomaly is the only admissible input, pre-anomaly opportunity cues and route-derived prompt forms are excluded or misrepresented. If anything can enter, abduction loses its typed starting discipline.

B.5.2.0:3 - Forces

ForceTension
Breadth vs disciplineAdmit more than anomaly, but keep a bounded family of admissible prompt species.
Reuse vs type inflationUse one entry form for several prompt species while keeping their questions distinguishable.
Prompt vs hypothesisKeep the initiating prompt distinct from the downstream abductive outcome.

B.5.2.0:4 - Solution

U.AbductivePrompt classifies the question accounts used for entry into B.5.2. Use A.16, A.16.1 and B.4.1 when the initiating cue needs preservation, clarification or selection of its next reasoning contribution. Use A.16.0 only when the cue-to-prompt history needs an explicit trajectory account. Publish the account in an expression adequate for the receiving use; reuse an adequate existing expression. Select a reusable form or additional publication faces when that use needs them. Account membership and current entry depend on the content and grounds below.

B.5.2.0:4.1 - Starter canonical species and conditional extension species

  • starter canonical species:
    • AnomalyStatement
    • ProblemCuePrompt
    • OpportunityCuePrompt
    • ProbeCuePrompt
  • conditional extension species:
    • TaskFamilySpecializationPrompt
    • AdaptationProbePrompt
    • NonHumanUtilityPrompt
    • SubstrateDiversificationPrompt
B.5.2.0:4.1.1 - Specialization-sensitive prompt species

Use an extension species only when the motivating grounds support one of the bounded task-family, adaptation, utility or substrate questions defined below. Preserve the conditions needed to interpret that question; cue provenance or a trajectory account can carry those grounds.

TaskFamilySpecializationPrompt asks what explains a performance difference within the declared task family. AdaptationProbePrompt asks which rival explanations predict whether a proposed adaptation can reach the stated threshold. NonHumanUtilityPrompt asks what could explain the indicated utility advantage of a low-human-overlap approach. SubstrateDiversificationPrompt asks what explains the indicated limitation of the current substrate. For each species, B.5.2 may return a qualified explanatory conjecture or an abort, defer or split result. Preserve its motivating grounds and all conditions needed to interpret the question, including any applicable task-family, utility, threshold or budget conditions.

B.5.2.0:4.2 - Core shape

A conforming abductive prompt makes promptSpecies, its explanatory openQuestion, scope and motivating provenance explicit. The provenance may be carried by motivatingCueRef, witnessRefs or routeProvenance; include the applicable basis even when no routing history exists. A rendering may additionally include contrastSet and GammaTime.

A prompt is not yet a hypothesis. Prompt admission usually presupposes articulation high enough to publish a stable open question and closure low enough that rival answers remain live; those articulation and closure thresholds remain governed by C.2.4 and C.2.5, typically reached through cue or route provenance from A.16.1 and B.4.1. The published account must satisfy those entry conditions; its layout supplies no additional admission.

B.5.2.0:4.2.1 - Identify the explanatory question

Identify the question from what the inquiry asks someone to explain:

  • the subject and the fact, contrast or expected effect to be explained;
  • the population, conditions and time horizon in scope;
  • the explanatory demand: what remains unknown and what an answer would have to explain.

Resolve the terms against their intended referents and interpretation. These three elements identify the question together. A change of wording, notation or publication preserves it when those elements retain their meaning. Two questions differ when a change in any element changes what an explanation must answer. A list of rival hypotheses helps compare answers; it need not exhaust the possible answers and does not identify the question by itself.

When an observed case motivates the inquiry, recover what the person asking wants explained. A question about a delay in one job, a change in a service’s reported delay, and a pattern recurring under different workloads can all start from the same trace. To set a boundary left to you, vary a condition the trace held fixed. Would an explanation adequate for this trace still explain what the recipient asks about? Use the distinction that changes the answer to define the prompt’s scope. C.39.SA:4 develops this choice when the needed composition scales or model distinctions are unclear.

Distinguish making an existing condition explicit from changing that condition. Use the earlier expression and its recoverable context to establish which happened. If a table drops an essential condition, first restore the damaged expression. When the earlier question cannot be recovered, leave its continuity unresolved; do not carry an earlier answer across the gap as an answer to the new formulation.

Motivating evidence and promptSpecies qualify the entry. Changing them changes the question only when it changes the explanatory demand, subject or relevant scope. A new observation can change the grounds for comparing explanations of the same event. Correcting the reported event can instead remove the reason to seek that explanation or raise a different question. A budget change affects question identity when the question concerns performance under that budget; a change in the resources available to investigate the same event need not do so.

This rule identifies the explanatory content of the question. An occasion on which someone asks it has its occurrence identity.

B.5.2.0:4.2.2 - Identify the prompt account and check its use

A prompt account makes claims about one question identified under §4.2.1: what is being asked, its scope, how it arose and the grounds for treating it as open in the stated inquiry. The question is its exact EntityOfConcern. C.2.1 identifies that account as one U.Episteme through its claim content, the question and the effective ReferenceScheme.

Under FPFCoreReferenceScheme, that same episteme is a U.AbductivePrompt when its content records one recoverable explanatory question, a declared species with the conditions in §4.1, and the scope and motivating provenance in §4.2, while leaving rival answers open. Thus U.AbductivePrompt(E) implies U.Episteme(E) for the same individual. This is the same-individual-dependent membership rule.

An unfilled layout, an underspecified cue and an account that asserts its preferred answer as settled fail this test for different reasons: no particular account, an unrecoverable question, or an answer-bearing account.

Use §4.2 and §17 to judge whether that account supports entry into B.5.2 now. An account can remain identifiable after its grounds have failed or its question has been answered. Keep it available as the earlier entry and record the warranted continuation; its earlier admission does not authorize a new run without current grounds.

The same question may have several accounts with different claims or effective schemes. Additional evidence changes account identity only when it changes one of C.2.1’s identity constituents; adding an evidence relation alone need not do so. Expressions of different accounts can follow the same reusable publication form. E.24.PUB governs the selected account’s expression and publication; A.6.3.RT governs a prose-to-table transfer when that representation changes. A note containing several questions may express several prompt accounts in the same document.

When returning to an earlier abductive inquiry, determine what changed and what the receiving work still needs before choosing a continuation:

FindingWarranted continuation
Same question and account; different support or candidate rankingReconsider the affected rivals under B.5.2 when further explanatory comparison is needed.
Same question; changed claims in its accountIdentify the revised account under C.2.1; reassess current entry if the account will be used in B.5.2.
Changed explanatory demand, subject or relevant scopeState the new question and its relation to the earlier one; establish its entry grounds if it will be used in B.5.2.
Several distinct questions were bundledDistinguish their accounts. Use B.5.2’s split return when separate explanatory comparisons are needed; continue the needed questions under their entry conditions.
An expression lost a condition needed to recover the questionRestore the expression before reusing the account or its answers.
The initiating ground fails or an adequate answer is already availableAbort or retire the current attempt as appropriate; preserve the earlier account and the reason for stopping.

B.5.2.0:4.3 - Boundary rule

An account enters B.5.2 only when its question and declared prompt species meet the entry conditions in §4.1–4.2 and §17. For a choice among available probes, actions or specialist options, use C.11. Use C.38 to develop incomplete alternatives for the same intended result, C.11.DUA to examine an unclear evidence demand, and C.19 when the question is policy over a still-live candidate pool. C.18 records generation and comparison results; C.22.1 describes an adaptation signature. Neither performs the missing choice. An explanatory subquestion arising during planning can still enter B.5.2 on its grounds.

B.5.2.0:5 - Archetypal Grounding

Tell. An anomaly is one prompt species, not the only one.

Show (System). A control observation may raise competing explanations of an apparent response improvement without being framed as an anomaly. The abductive result qualifies those explanations; choosing a discriminating probe is a separate C.11 decision.

Show (Episteme). Suppose a revised theory appears to account for two previously separate results. An opportunity-style prompt asks what could explain this apparent gain in explanatory reach.

B.5.2.0:6 - Bias-Annotation

The pattern admits several prompt species while keeping the explanatory question and its motivating grounds explicit.

B.5.2.0:7 - Conformance Checklist

  • CC-B.5.2.0-1 Every U.AbductivePrompt SHALL declare its prompt species.
  • CC-B.5.2.0-2 A prompt SHALL NOT be confused with a finished hypothesis.
  • CC-B.5.2.0-3 Cue-derived prompts SHOULD preserve route provenance when it exists and contributes to their entry.
  • CC-B.5.2.0-4 Prompt publication SHALL include the explanatory question, its scope and the motivating provenance that make abduction appropriate.
  • CC-B.5.2.0-5 An account that asserts its answer as settled or suppresses plausible rivals SHALL NOT be used as the open prompt for that inquiry.
  • CC-B.5.2.0-6 When a specialization-sensitive prompt species is used, the prompt account SHALL make explicit the declared task family or utility target and the grounds for its explanatory question. Include every threshold, budget or other condition needed to interpret that question or its proposed use, and preserve the cue, witness or route provenance used.
  • CC-B.5.2.0-7 Before restarting an inquiry, or reusing its prompt after a change in wording, scope or motivating grounds that may affect the question or account, the user SHALL apply §4.2.1–4.2.2 to establish the affected continuity and entry conditions. Already established identity and unaffected grounds remain reusable while their basis holds; comparing another rival with an unchanged prompt requires no new continuity assessment.

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

  • Prompt equals hypothesis. Keep the prompt distinct from the abductive output.
  • A choice disguised as abduction. Recover the explanatory question, if one exists; send the probe, action or acquisition choice to its Method.
  • Route amnesia. A cue-derived prompt loses the early route provenance that explains why it entered here.

B.5.2.0:9 - Consequences

The benefit is a common entry criterion for cue clarification, abductive comparison and later return to the inquiry. The cost is distinguishing the question from its account when either changes; a new form, file or question identifier is unnecessary when the existing publication makes that distinction recoverable.

B.5.2.0:10 - Rationale

A typed prompt lets a preserved cue contribute its explanatory question to B.5.2 while retaining the grounds that made the question worth asking.

B.5.2.0:11 - SoTA-Echoing

An opportunity or a probe-related contrast can raise an explanatory question without being formulated as an anomaly.

As a foundational semantic comparison, Ciardelli, Why We Need a Question Semantics (author preprint, 2021; published chapter, 2022), distinguishes an issue from its expression and from the act of asking, and develops resolution conditions for questions. His Inquisitive Action Logic (2026) continues to treat questions as semantic content used within a formal system.

Here that distinction supports separating the question from an account about it. The local explanatory-question rule in §4.2.1 is an FPF construction; these sources do not supply its account-membership rule or a universal identity test for explanations. Sources: chapter record, 2026 paper.

B.5.2.0:12 - Relations

B.5.2.0:13 - Worked Prompt Species

B.5.2.0:13.1 - Anomaly statement as canonical prompt

In a constructed service case, latency rises from 8 ms to 40 ms under the same declared workload. The prompt asks what could explain that contrast, names the service and time window, and cites the measurements. Rival explanations may concern contention or a changed cache path; neither is asserted by publishing the prompt. B.5.2 compares their plausibility and may return a qualified conjecture or defer.

B.5.2.0:13.2 - Opportunity-style prompt

An opportunity cue may raise an explanatory question about an indicated advantage without a failure. For example, an unexpectedly stable response in one operating range invites rival explanations of that stability. Whether to exploit the opportunity is a separate action choice.

B.5.2.0:13.3 - Probe-style prompt

A probe-related observation may prompt an explanatory question: which rival explanations predict the measured contrast under the stated perturbation? If the question is instead which available probe is cheapest or most discriminating for the purpose, use C.11. The probe choice does not require an abductive prompt merely to acquire that input form.

B.5.2.0:13.4 - Specialization-sensitive prompt set

Use a specialization-sensitive species for its explanatory question in §4.1.1. For example, a measured performance contrast can prompt rival explanations tied to a declared task family and budget. Acquiring a specialist Method or competence bundle instead requires the applicable option or alternative-development decision. Retain task family, threshold, budget and cue provenance in whichever receiving use needs them; prompt publication does not select the acquisition.

B.5.2.0:13.5 - Same question, revised account and reused form

Continue the constructed service case in §13.1. The question asks what explains the rise from 8 ms to 40 ms for the named service, workload and time window. A paragraph and a table preserve the same question when both retain that contrast and scope. If the table also preserves the account’s claims and effective scheme, C.2.1 identifies the same account; E.24.PUB separately governs its new expression and availability. If the table omits the workload, restore that condition before treating its shortened question as equivalent.

New contention logs can support one rival more strongly while the latency question stays unchanged. An assertion about that new support can belong to a revised account, or to a separate evidence account linked to the unchanged prompt. Determine which content changed.

If corrected measurements establish that latency stayed at 8 ms, the current attempt to explain an actual rise loses its initiating ground. Asking why the monitor reported 40 ms is a different question about the report; its answer need not explain a real slowdown.

For an operator who asked whether the service slowed in that interval, the corrected measurement supplies the answer. For an inquiry into recurring false alarms, determine which other reports the same account could explain and on what grounds. A team commissioned to discover improvements to monitoring may select the discrepancy itself as its next question.

The reporting question and a question about an actual slowdown in another service can be expressed in accounts that use the same AnomalyStatement layout. Its shared columns do not identify one common question. Record each subject, contrast and scope so that the two accounts and their rivals remain distinguishable; they may occupy two rows of one note. One hypothesis that answers both questions would not make the questions identical.

B.5.2.0:14 - Prompt package discipline

A prompt becomes reusable in B.5.2 only when its initiating question is explicit enough to remain stable across downstream hypothesis work.

B.5.2.0:14.1 - Minimal prompt package

An abductive prompt should make explicit:

  • the prompt species,
  • the open question,
  • the motivating provenance used,
  • the contrast set, if one is already visible,
  • the scope in which the question is being asked,
  • and the witnesses or cue grounds that justify beginning abduction.

This package lets downstream conjectures be assessed against the same identified explanatory question.

For specialization-sensitive prompt species, preserve the declared task family or utility target, the conditions needed for the explanatory question, including any stated threshold or budget, and the motivating provenance used. Preserve alternative prompt shapes when they remain live and matter to entry.

B.5.2.0:14.2 - Claims about the question and an asserted answer

A prompt account states what is being asked and why, while leaving the answer open. It may cue one explanation among rivals. If the text instead asserts the answer as settled, it has moved past prompt status and should be treated under B.5.2 or another governing pattern that carries the asserted answer.

B.5.2.0:14.3 - Prompt provenance remains load-bearing

The motivating provenance is part of prompt admission. Preserve the route, cue or witness basis used; a prompt with no routing history does not need an invented route.

B.5.2.0:14.4 - Check prompt against silent promotion

An assurance reader should watch for the common mistake where authors silently upgrade a prompt into a hypothesis merely because the prose sounds explanatory. If the text already leans on one preferred answer as settled, either rewrite it back into an open question or explicitly apply the governing pattern that carries the asserted answer.

B.5.2.0:15 - Species boundary reminders

Use anomaly species for an explanatory question arising from a failure, contradiction or surprising departure from the current model. Use opportunity species for an explanatory question arising from an indicated advantage. Use probe species for rival explanations of an observation or predicted contrast associated with a stated probe.

For the four specialization-sensitive species, use the explanatory questions and conditions in §4.1.1. Questions asking which option to acquire, which probe to perform or which substrate to try follow the choice routes in §4.3.

Name each cue-derived entry as a prompt species, preserving the explanatory question it introduces.

B.5.2.0:16 - Boundary crossing and invalid drift

Entry into B.5.2 requires a question explicit enough to compare potential explanations under its scope. An underspecified question needs clarification before that entry. Continue stabilization or routing when needed for the receiving question.

Determine what a missing contrast or witness prevents. If it leaves the explanatory question or other membership conditions unrecoverable, U.AbductivePrompt membership is not established. If the account meets those conditions but lacks grounds for entry now, retain the account with that current-use limit under §4.2.2.

A common failure mode is drift from cue -> prompt -> hypothesis without anyone naming the boundary crossings. B.5.2.0 blocks that drift by keeping the prompt package distinct from both the earlier cue pack and the downstream prime hypothesis.

B.5.2.0:17 - Scope, rival-set, and comparative-validity discipline

Declare which cases and conditions the explanation has to cover. Choose a tractable subquestion when its answer could settle the inquiry, distinguish live explanations, or establish a premise the inquiry needs. Identify that contribution before sending the subquestion for comparison. If it leaves part of the commission open, return its result with that remaining question. A promising change of subject can be proposed to the person who set a fixed inquiry.

A prompt need not list hypotheses yet. Its explanatory demand and scope must make clear what a candidate explanation would have to explain; any already identified answer types can help clarify that demand.

A prompt may be narrowed to become more discriminating, but the narrowing must not smuggle in the answer it is asking about. Otherwise the prompt ceases to be an initiating question and becomes a disguised conclusion. If its formulation excludes plausible rivals without grounds, repair that restriction; if it asserts an answer as settled, treat the answer-bearing account under its governing pattern.

Prompts may be compared across contexts only when their species, scope, and provenance are explicit. A probe-shaped question and an opportunity-shaped question are not the same kind of abductive entry merely because both invite explanation.

One note may contain a bundle of closely related prompts. If so, the bundle members should be distinguishable and still allow downstream rival comparison without confusion.

An assurance reader can test prompt readiness with three questions:

  1. Is there an open explanatory question? An asserted answer is no longer a prompt; narrowing the scope must leave the answer open. An action-choice question needs its Method.
  2. Does the prompt species fit its initiating grounds? If those grounds are an opportunity or a probe-related contrast, forcing anomaly species misclassifies the question.
  3. Is the question explicit enough to generate and compare explanations for the needed use? Check the stated scope against what the recipient asked to understand. For a subquestion, establish what its answer can contribute there. The receiving investigator can generate the rivals in B.5.2.

B.5.2.0:End

B.5.2.1 - Instrument Abductive Hypothesis Generation with Novelty–Quality–Diversity (NQD)

Normativity: Normative binding to B.5.2 Abductive Loop. The local NQD-Generate Method in §4, or an equivalent declared generator, constructs the candidates. C.18 supplies generation, archive and front records; C.19 supplies the applicable exploration/exploitation policy.

Status: Stable

Method and records. Use A.17/A.18 for Characteristics and A.3.1/A.3.2 for the Method and its description. Distinguish its input and seed conditions, conditions for any actual generation Work, and the generated candidate’s later admission to comparison. C.18 records the identified generator and its results; filling that record performs no generation.

Terminology discipline. Use NQD consistently (Novelty–Quality–Diversity). Use Surprise and the IlluminationSummary report in comparison only under the declared policy (see §3, §5).

B.5.2.1:1 - Problem Frame

  • Conceptual binding: B.5.2 Abductive Loop (this pattern specifies the how for Steps 2–3).
  • Characteristics and records: use Creativity‑CHR under C.17 for the Characteristics in §3, C.18 for generation/archive/front records and C.19 E/E-LOG for EmitterPolicy.
  • Manager’s mental model (informative): Choose measurable characteristics for the quality, newness and spread used by the exploration. Identify which generated candidates were assessed and eligible. Return their front under the declared DominanceSet, together with any exploration archive required by the policy or the commission.
  • Further work: generated hypotheses may contribute to B.4 Canonical Evolution Loop when adaptation is needed. B.5 Canonical Reasoning Cycle selects the reasoning contribution needed by the question.
  • Decision-subject note. Later choices are attributed to one declared DecisionSubject at explicit DecisionSubjectGranularity. The Context supplies the measurement spaces and admissible policies that frame the decision.

B.5.2.1:2 - Intent & Problem

Intent. Use this pattern when the explanatory question needs instrumented exploration of candidate quality and variety. Declare the generation Method, comparison Characteristics and exploration policy; construct candidates and identify those worth pursuing. A declared equivalent generator may supply the construction. Use B.5.2 directly when ordinary generation and plausibility comparison suffice.

Problem. Candidate generation can produce too little variety to expose meaningful rivals, or candidates without interpretable implications. B.5.2 addresses these failures; this method makes candidate construction and comparison explicit through declared operations and Characteristics.

B.5.2.1:3 - The Creativity‑CHR

The NQD Characteristics used here are defined by C.17 and A.18:

  • Novelty@context (C.17 §4.1);
  • ΔDiversity_P (marginal; C.17 §5.1);
  • Q components (per A.18).

Surprise is an optional coordinate; IlluminationSummary is a retained-set telemetry report under C.17. Use either in comparison only when the C.19 policy names that use and its constituted basis; promotion into dominance requires an explicit policy. Use‑Value (alias: ValueGain) is informative for decision lenses (Decsn‑CAL) and MUST NOT enter NQD dominance by default (see C.17 §4.2).

For each coordinate used, declare its bearer, Characteristic, Scale, polarity, admissible operations, scope, window and evidence basis under C.17. Cite a constituted C.16 measurement result when the coordinate was measured, or a C.2.1 ascription under its declared rule. Candidate must-constraint eligibility and the conditions for performing generation are separate questions.

Lexical discipline. The items above are Characteristics in the sense of A.17/A.18; avoid reserved names such as “validity” or “operation.” Comparison basis. Compare each Q coordinate under its declared Scale, polarity and admissible order. Different units across coordinates do not by themselves require normalization for componentwise Pareto comparison. If the chosen comparator requires a transformation, declare it and preserve the order distinctions on which dominance depends (see CC-B.5.2.1-6). D and I. D = ΔDiversity_P(h | Pool) is a marginal retained-set reading under the same declared measurement policy. It is outside primary dominance unless explicitly promoted. IlluminationSummary reports the retained set; it is not a per-hypothesis primitive coordinate. A C.19 policy may name a tie-break or promoted use with the corresponding report and basis. Measurement invariants. The grids, distances and transforms used by the run MUST be declared, versioned and cited in provenance.

B.5.2.1:4 - Solution — NQD-Generate and its C.18 records

Method name (Plain/Unified Tech). NQD‑Generate — a U.Method that, given (i) a HypothesisSpace and (ii) a CharacteristicSpace with a CoverageGrid, returns a finite candidate package: a front over the eligible candidates assessed in the run under the declared DominanceSet, with any archive or tie-break telemetry required by the active policy or receiving use.

Minimal signature.

  • Inputs (declared in MethodDescription): HypothesisSpace, CharacteristicSpace, Seeds?, Budget (time/compute), EmitterPolicy (E/E-LOG policy id), QualityMeasures (Q components), NoveltyMetric? (required when generation, comparison or retention uses novelty), CoverageGrid/Granularity, CellCapacity K? (default=1), EpsilonDominance ε? (default=0), TieBreakPolicy? (S/I), DedupThreshold?, Policy(TimeWindow), DeterminismSeed?

  • Outputs: CandidateSet = {h_i: (desc_i, Q_i, N_i?, D_i?:=ΔDiversity_P(h_i | Pool), S_i?, UseValue_i?), genealogy_i?, provenance_i (including policyId from E/E-LOG and, when a DHC coordinate is consumed, DHCMethodRef.edition and the other active fields of C.21’s DHCReplayBasis)} where Q_i is a vector and provenance_i captures generator settings and evaluation sources.

The coordinate entries cite the constituted results used. When illumination is reported, carry IlluminationSummary separately as a report about its declared retained set. Unused optional readings need not be produced. If Use-Value is present, identify its objective or acceptance criterion and scope. For a gain claim, also identify the baseline and comparison or counterfactual Method; for a predicted reading, identify the model edition and assumptions under C.17.

N, D, S, and I are archive, tie-break, telemetry, or policy-promoted signals by default; only the declared DominanceSet enters the front. Use-Value is decision-side/supporting unless the Context declares it inside the active Q tuple / DominanceSet; when it is only recorded as a side measure, keep it outside dominance.

Choosing the spaces for the commission. A comparison of supplied hypotheses on agreed coordinates can use those inputs directly. If you are asked to design the search, begin with the contrast to be explained. Follow how it could arise, for example within one component, through an interaction, or in the work that produced the observation. Choose operators that can express the resulting alternatives. Could two permissible candidates receive the same proposed scores while explaining different observations or implying different answers to a question the recipient must settle? Preserve the relevant prediction or mechanism in the candidate account. Add a descriptor or comparison coordinate when the archive or the ordering must use the distinction.

Strategy (notation‑neutral).

  1. Seeding and constructors. Declare the explanatory question, hypothesis space and permitted variation operators in the MethodDescription. Initialize with admissible seeds: known explanations, random draws under that grammar or prior hypothesis-bearing epistemes with their grounds and limits. Name how an operator constructs a changed explanatory claim, for example by replacing a proposed mechanism or combining two mechanisms under a stated interaction assumption. When there are no seeds, use the declared finite enumeration or sampling rule.
  2. Construct and assess. Apply the selected variation operators to the seeds or retained candidates within the budget; record each resulting hypothesis and its parent/operator provenance. Then test candidate must-constraints for comparison and evaluate each required Q component. Keep an excluded candidate and its reason distinguishable from a candidate not yet generated. Maintain up to K retained entries per declared cell; obtain only the N, ΔDiversity_P and Surprise readings used under C.17, and any required retained-set illumination report. Apply the declared deduplication rule to the return for which it is valid. Keep distinct candidate identities or a way to recover them when the commission asks for every qualifying candidate. A common cell alone establishes only agreement on the cell descriptors.
  3. Budget‑bounded loop. Iterate until the budget or declared coverage-convergence condition is reached, or the applicable C.19 policy ends active exploration; report the front over the eligible comparison population under the declared DominanceSet and any applicable ε policy. To extend the front beyond that population, account for the remaining eligible possibilities under C.18:4.4. When the Context consumes the ordinary default, that means the declared Q components under DefaultId.DominanceRegime. Keep N, D=ΔDiversity_P, Surprise, and IlluminationSummary as archive/tie-break/telemetry signals unless one Context policy explicitly promotes one of them into dominance and records the policy id. Use-Value enters dominance only when the Context declares it inside the active Q tuple; otherwise it may appear as one decision-side/supporting side note.
  4. Traceability. Keep the generator settings, grids/metrics versions, seeds, policy, TimeWindow, filled cells and each exclusion’s reason recoverable in the generation and comparison account. Use C.18 for the archive and front returns. State how the final set was produced, including ε, K and deduplication. Keep any decision rationale required by the use in that account; reuse an adequate account.
  5. Algorithmic freedom (informative). Implementations MAY use MAP‑Elites/illumination, novelty search with local competition, Bayesian/surrogate‑assisted search, or deterministic enumerations; a tolerance that defines dominance belongs to the stated comparator. When ε or a knee-point rule is used only to thin an already computed front, preserve that front and identify the thinned return separately. For a promised approximation, establish the stated error guarantee over its domain. A coverage guarantee, for example, needs an attainable representative within the promised tolerance for every outcome it covers.

B.5.2.1:5 - Implementation & Binding into B.5.2 (two injection points)

Step 2 — Generate candidates. Before generation. Establish the Method’s applicable input/seed conditions. For actual generation Work, satisfy its independently applicable authority, assignment, scope, window, budget and permission conditions, including USM coverage and an enactable RSG state when the governing use requires them. A theoretical candidate comparison does not acquire a fictional performer or permission gate. A generated candidate’s ConstraintFit is assessed after construction and controls its admission to the specified comparison.

When the pattern is imported, use NQD-Generate for the selected generation contribution. Its candidate package carries conjectural content and the constituted coordinate results and provenance used. Report diversity to the extent supported by its declared reading; generation assigns no assurance level.

Step 3 — Plausibility filters. Compare the candidates whose predictions or mechanisms could answer the explanatory question. A candidate dominated on the chosen coordinates can predict an observation the front leaves unexplained. Restrict this comparison to the front when the exclusions preserve the answers needed here. Apply B.5.2’s plausibility criteria:

  • Falsifiability / probeability → require an interpretable implication or possible discriminating contrast under B.5.2. Keep a meaningful conjecture distinguishable from the present availability or worth of its check.
  • Explanatory power → prioritize candidates whose Q-improvements and attached rationales address the stated explanatory question.

Apply B.5.2 to return a qualified prime conjecture when its comparison warrants one, or an explicit abort, defer or split result. Deduction, evidence acquisition and action choice remain separate questions.

For the primary dominance test, identify the eligible assessed candidates and compute their front under the declared DominanceSet and applicable tolerance. When the Context consumes the ordinary default, that means the declared Q components. For tie-breaking, use only the constituted Novelty, ΔDiversity_P, Surprise or IlluminationSummary results named by the active C.19 policy. Optional archive or telemetry readings retain their declared use; promotion into dominance requires an explicit policy. Use-Value remains non-dominant unless the active Q tuple includes it.

Fallback when no narrower local policy is specified

Use the ordinary default DefaultId.DominanceRegime from G.Core/G.5 together with the active C.19 policy-side defaults; in ordinary Q-front use this means the declared Q components, with ConstraintFit=pass as the candidate admission condition for that front, assessed after generation. Tie-breakers: use only the constituted Novelty@context, ΔDiversity_P or Surprise results named by the active C.19 policy. IlluminationSummary remains report-only unless that policy names a tie-break or promoted use. Unused optional readings need not be produced. Archive: K=1, ε=0, deduplication in CharacteristicSpace. Policy family: one uncertainty-aware explore policy family with one declared regime key; UCB-class with moderate temperature and explore_share ≈ 0.3–0.5 is one didactic starter profile, not the semantic default family. Provenance (minimum): record DescriptorMapRef.edition, EmitterPolicyRef, TimeWindow, and the seeds used; include DistanceDefRef.edition when the run uses a distance definition.

Scope of the coordinate claims. Record the BoundedContext and TimeWindow that qualify each coordinate result.

Surprise: scope and default role. Use Surprise as a secondary tie-break only when the active C.19 policy names that use, among candidates otherwise Pareto-equivalent on the declared primary characteristics. A policy may explicitly promote Surprise into dominance with its constituted basis. If the policy does not use Surprise, omit that reading.

B.5.2.1:5.1 - Distinguish the returned results

Identify the population used for the front, the coordinates in the DominanceSet and the distinct answers the commission requires. Preserve its computed front before thinning. Report retained candidates under their archive policy when an archive is due (CC‑B.5.2.1‑4a). A shortlist answers a subsequent selection question. A budget stop records the end of the run. For a report on niches actually tested, include the applicable tests, including tests whose candidates were discarded. For an exact front over the full hypothesis space, establish how the rest of that space is covered.

B.5.2.1:6 - Conformance Checklist (normative)

CC‑B.5.2.1‑1 (CHR discipline). If this pattern is applied in a Context, that Context SHALL declare the Creativity‑CHR Characteristics used by the generation and comparison with A.18‑style templates (type, unit/range, polarity).

CC‑B.5.2.1‑2 (Instrumented generation). Step 2 of B.5.2 SHALL either (a) invoke NQD‑Generate or (b) justify a Context‑specific generator of equivalent effect (diversity + quality + novelty with measurable Characteristics).

CC-B.5.2.1-3 (Diversity coupling). Whenever a D reading is used, it SHALL be ΔDiversity_P computed against the current candidate Pool using the C.17 definition of Diversity_P under the same Context, CharacteristicSpace, kernel and TimeWindow.

CC-B.5.2.1-Eligibility. The MethodDescription SHALL state applicable input/seed conditions. Any actual generation Work SHALL meet its independently governed authority, assignment, scope/window and permission conditions. Assess each generated candidate’s must-constraints before admitting it to the comparison/front that consumes ConstraintFit; a result about that candidate SHALL NOT be a precondition for creating it. Preserve exclusions and their reasons.

CC‑B.5.2.1‑4 (Non‑dominated candidate front). The CandidateSet MUST include the front for the identified eligible comparison population under the declared DominanceSet. A claim of completeness for a wider domain SHALL account for that domain at the requested distinction between candidate identities and objective values (C.18:4.4). If the Context consumes the ordinary default, cite that consumed DefaultId.DominanceRegime rather than restating one local default doctrine. Every exclusion SHALL retain its reason.

For a dominance exclusion, identify the eligible rival and decisive coordinates when known. An argument showing that every jointly admissible account contains a dominating rival also suffices, even if the rival changes between accounts. Cite the rule for deduplication, archive retention or thinning when used. Preserve the complete computed front for its stated population before thinning and label the thinned result separately.

N, D=ΔDiversity_P, Surprise, IlluminationSummary, and similar signals enter dominance only under an explicit recorded promotion policy; otherwise they remain archive, tie-break, or telemetry signals.

CC‑B.5.2.1‑4a (Archive companion when retained exploration is in scope). If the active policy depends on retained exploration, stepping-stone retention, or open-ended search, the emitted candidate package MUST include the corresponding ExplorationArchive. Supply the archive when the commission calls for it. Where the commission permits a run without an archive and the policy allows that mode, cite the policy id for the choice.

CC-B5.2.1-5 (Hypothesis-led testing). Before claiming empirical corroboration, the practitioner SHALL derive the consequences needed to interpret the test and retain how the tested hypothesis was obtained. Generation SHALL NOT assign an assurance level, require a new experiment or prescribe the next reasoning contribution independently of the receiving question.

CC-B.5.2.1-6 (Coordinate comparability). Dominance SHALL use compatible readings on each declared coordinate and its polarity. Any required transformation SHALL be explicit and preserve the comparator’s relevant order distinctions; heterogeneous units across different coordinates alone SHALL NOT trigger mandatory normalization.

CC‑B.5.2.1‑7 (Use‑Value separation). If Use‑Value (C.17 §4.2) is recorded outside the active DominanceSet, it SHALL remain outside Assurance scores and MAY inform decision lenses (Decsn‑CAL). If the Context places Use-Value inside the active Q tuple, record that declaration together with its objective id / acceptanceSpec. Do not alter R/G semantics based on side-measure Use‑Value. (see C.17 §4.2 for Use-Value and ValueGain definitions)

CC‑B.5.2.1‑8 (Provenance). Each h_i in the CandidateSet MUST reference its provenance_i sufficient to reproduce scores given the same Policy(TimeWindow), score/metric versions, and DeterminismSeed?.

CC‑B.5.2.1‑9 (Secondary metrics). I (illumination) and S (surprise) SHALL be used only for tie‑breaking/reporting unless explicitly promoted by policy; the primary dominance test uses the declared DominanceSet, which under the ordinary default means the context-declared Q components.

CC‑B.5.2.1‑10 (Cell capacity & ε). If K>1 or ε>0 are used, the values MUST be declared and recorded in provenance; any thinning after recording the front SHALL be documented in the generation and comparison account.

CC-B.5.2.1-11 (Dominance set). If the Context consumes the ordinary default DefaultId.DominanceRegime, the active dominance set SHALL be the declared Q components and provenance SHALL cite that consumed default plus the active C.19 policy or lens id. Any Novelty@context or ΔDiversity_P tie-break SHALL be named by that policy and use a constituted result on a compatible basis; an unused optional reading need not be produced. Promotion into dominance SHALL be explicit and recorded with the policy id.

B.5.2.1:7 - Effort and first use

For engineers/managers (user cognitive load).

  • Added steps: selecting descriptor Characteristics and granularity; reading the returned front. Use the front for the requested coordinate comparison. For an explanatory question, include any candidate whose specific prediction or mechanism could change the answer.
  • Mitigations: a compact comparison note or table can suffice. Keep the required coordinate meanings and provenance available, and reuse applicable Context grids and metrics.
  • Reader quickstart (engineer-manager): (1) Recover what the recipient wants compared and which choices are yours. Use the agreed inputs or construct the needed hypothesis space, descriptors and Q characteristics as in §4. (2) Declare the generator, policy, budget and stopping rule, and any novelty metric it uses. (3) Run NQD-Generate. Inspect the front for the eligible population under the declared coordinates and any archive required by the policy or commission. (4) Apply B.5.2’s plausibility criteria to the original explanatory question.

B.5.2.1:8 - Placement in the Reasoning Cycle (ADI)

This pattern structures candidate hypothesis exploration within B.5.2. A receiving use determines whether deduction, evidence acquisition, assurance or action choice is needed next. Actual development transitions meet B.5.1’s project and domain conditions; a conjecture does not itself make that transition.

B.5.2.1:9 - Context‑Level KPIs (optional, informative)

Practitioners may monitor these indicators to improve practice; they do not serve as admission conditions:

  1. Profile-specific assurance progression (optional). When a receiving domain uses an assurance-level profile, report the fraction of cycles whose candidate meets a named level under that profile within the policy window. Name the claim, use and satisfying evidence; omit this KPI when no such profile is used.
  2. Frontier‑Hit Rate (FHR). % of cycles where the chosen candidate lies on the Pareto front of the eligible population compared at selection time under the declared DominanceSet; track novelty/diversity contribution separately as archive, tie-break, or policy-promoted evidence.
  3. Coverage Gain (ΔI, report). Change in the illumination summary of the retained archive over a cycle, measured with its stated descriptor grid and occupancy rule.
  4. Exploration Cost Ratio (ECR). Under one resource metric, divide generation cost by positive downstream analysis or evidence-acquisition cost savings relative to a stated comparison baseline. State whether the savings are measured or estimated and identify the comparison or estimation Method. If positive savings are not established, report the costs and the supported saving result or unresolved saving claim separately.
  5. Refutation Learning Yield (RLY). Among refuted candidates, report the percentage that added new coverage or contributed a specified increase in Surprise. For the Surprise branch, identify the constituted result and its baseline or reference set, and use a declared comparison rule on a compatible basis to determine whether the candidate counts.

B.5.2.1:10 - Worked micro-example: explanatory rivals and a separate next action

Question and case facts. In a constructed service case, O1 is a latency rise above eight concurrent requests, O2 an increase in blocked threads, O3 a higher cache-miss rate, and O4 normal latency in a serial replay. The question is what explains this contrast. These are stipulated teaching inputs, not empirical results about a real service.

Construction. Declare hypothesis grammar v1 with three mechanism flags: lock contention, cache churn and scheduler stalls. The seeds are A, a lock-contention explanation, and B, a cache-churn explanation. NQD-Generate enumerates two declared variations: combine A with B to construct C, an interacting lock/cache explanation; replace A’s mechanism with scheduler stalls to construct D. The finite budget is four hypotheses including the seeds. Provenance records each seed, constructor and resulting claim. The comparison’s must-constraints are that a candidate addresses these service observations using the declared mechanism grammar and makes a discriminating prediction. All four pass after construction.

Coordinates and comparison. Q has two ordered count Scales: predicted observations among O1–O4, maximized, and auxiliary assumptions not established by the case facts, minimized. Prediction coverage is calculated under each candidate’s stated auxiliary assumptions; it is not independent confirmation.

A predicts O1/O2/O4 with one unverified lock-scope assumption. The seed cache model B predicts O1/O3 from the stipulated inputs with no additional assumption. C predicts all four using the lock-scope and lock/cache-coupling assumptions. D predicts O1/O4 using unverified scheduler-threshold and recovery assumptions. Their complete comparison is:

HypothesisDescriptor (lock, cache, scheduler)Predicted observations ↑Unverified auxiliaries ↓NoveltyFront result
A: lock contention(1,0,0)310retained
B: cache churn(0,1,0)202retained
C: interacting lock/cache(1,1,0)421retained
D: scheduler stalls(0,0,1)222dominated by A, B and C

The declared DominanceSet is exactly the two Q coordinates, with ε=0. Novelty is Hamming distance on the three Boolean flags to the preceding archive containing A only; it is an integer count from 0 to 3 and stays outside dominance. The descriptor grid has one cell per flag tuple, K=1. Exact duplicate claims are removed; none of these four is a duplicate.

D’s scheduler cell is retained under the stated stepping-stone policy even though D is dominated. No D, Surprise or IlluminationSummary reading is needed in this example.

Of the four eligible hypotheses assessed here, A, B and C form the complete front. Each trades prediction coverage against auxiliary assumptions. C.18 records that front separately from the retained archive {A,B,C,D}, and its generation record names this NQD-Generate procedure and the seed/operator provenance. No front thinning is applied.

To see what these two counts preserve, consider a possible rival predicting O1, O3 and O4 with one unverified assumption. Its Q vector would equal A’s. The coordinates suffice to locate that vector in the stated ordering. A recipient asking about blocked threads in O2 needs to know which observations each candidate explains. Preserve the prediction for O2 and the proposed mechanism for that comparison. This hypothetical rival tests the choice of coordinates and contributes no new assessed candidate to the four-hypothesis run.

Qualified abductive result. For a bounded answer to why the blocked threads in O2 occur, B.5.2 compares candidates that explain O2 with at most one unverified auxiliary assumption. A meets that stated plausibility criterion; C needs two, while B and D leave O2 unexplained. A is the qualified prime conjecture, conditional on the lock-scope assumption. A leaves O3 open. Return to the original question about all four observations. Among the candidates compared, C accounts for all four on two unverified assumptions. The one-assumption limit used for the O2 enquiry does not eliminate C as an explanation of the full contrast. Check the assumptions or establish another ground for preferring an explanation at that scope. Evidence that the blocked threads never wait on the proposed lock would defeat A’s explanation of O2. Generation and the coordinate counts supply no assurance level or empirical corroboration.

Next-use choice. The separate C.11 question is which available diagnostic action fits a one-hour budget. Reading the existing lock traces takes one hour and addresses A’s open assumption; the combined intervention needed for C takes three hours. Under the declared criterion of addressing the blocked-thread question within that budget, choose the trace reading and decline C’s intervention for this action. C remains a front member and D remains an archive stepping stone. This choice authorizes no performance beyond its independently applicable permission conditions.

B.5.2.1:10a - Trade‑offs & mitigations

  • Cognitive effort. Interpreting Pareto sets and coverage maps adds overhead. Use the compact comparison view in §7 with its coordinate meanings and provenance.
  • Locality. Reuse novelty/diversity readings only where their declared comparison basis and supported use remain applicable. If a change affects that basis, obtain the needed new reading or establish a suitable mapping and its loss boundary.
  • Metric gaming & collinearity. Check whether using correlated Novelty and Surprise readings changes the intended comparison or pool treatment. Preserve both when their distinct meanings matter; revise an unsuitable joint-use rule through the declared policy and record the rationale.

B.5.2.1:11 - Related Patterns

  • Extends: B.5.2 Abductive Loop (Step 2/3 operationalization).
  • Driven by / feeds: B.5 Canonical Reasoning Cycle, B.4 Evolution Loop (Observe/Refine).
  • Uses: A.17/A.18 for characteristic discipline and B.5 for choosing reasoning contributions. May refer to Context‑specific MAP‑Elites/novelty‑search implementations in the MethodDescription. C.17 (Use‑Value / ValueGain, normative definition).

B.5.2.1:End


B.5.3 - Interpret Domain Vocabulary for an FPF Claim (Domain-Concept Bridge)

Status: Stable

B.5.3:1 - Problem Frame

Working domains use their vocabulary, while an FPF claim must preserve the kind and relations its meaning requires. A thermodynamicist uses terms such as “system”, “macrostate”, “control volume” and “free energy”.

The problem starts when the familiar word substitutes for identifying what the local claim denotes or asserts. The same expression can require different FPF interpretations in different claims.

B.5.3:2 - Problem

How can FPF let project teams keep domain vocabulary while preserving the FPF ontology? A dictionary-style alias is too weak because it only says that two labels are being associated. It does not determine what the local claim asserts or which FPF kind or relation that claim needs.

B.5.3:3 - Forces

ForceTension
Domain fluency vs. ontological parsimonyTeams need familiar words, but FPF must not grow a new root kind whenever a local term appears.
Same word vs. different claimThe same expression can make different local claims in different sources or schemes and can point to different FPF values. Spelling alone decides none of them.
Meaning recovery vs. role overuseSome domain uses concern a system-role kind or assignment; many concern another value or relation. Recover the claim before choosing the terminology.
Small result vs. hidden ontologyThe result should be as small as the use permits, yet expose any kind, relation, loss, and return condition instead of hiding them behind a synonym.

B.5.3:4 - Solution

Use this interpretation move when domain vocabulary leaves the FPF claim unclear.

  1. Start from the expression, source, edition, and relevant passage. Use F.0.1 to recover the source-local claim. Recover an F.17 cell and test its basis relation when the FPF claim needs them, including when an F.9 Bridge is claimed. Add a durable term row only when the receiving use needs that packaging under F.17.
  2. Ask which FPF value or relation the claim needs, then use the pattern that defines or constrains it. For example, the answer may concern a System, characteristic, Method, Work occurrence, episteme, system-role assignment, or evidence-use relation.
  3. Use C.3 when the claim needs a kind: recover its candidate domain and membership distinction. Use E.24.UK when another durable public FPF U-kind is proposed.
  4. If the recovered source-local claim answers the question, return it and stop. If a receiving use must relate two distinct local-sense claims, use F.9 to test whether a Bridge between their F.17 cells obtains. Shared spelling alone proves no such relation.
  5. For an F.9 bounded-use claim, state the proposed use, direction, correspondence rule, loss tolerance, and whether the claim is affirmative or negative. Evidence reliance requires the A.10 path, obtaining relations, and local RelianceDisposition for that use under F.9:4.2; apply B.3 when a named assurance claim is current. State other applicability or reopen conditions when they qualify the use. The semantic relation alone neither authorizes nor performs the use.
  6. When role wording is material, use E.10.ROLE and A.2 to distinguish a local system-role kind, classification, assignment, participation, responsibility, or ordinary language before making the claim.

The result can be one sentence. Use a note, row, or card only when a later reader or tool needs durable packaging. The package describes the result; it does not create the FPF value, local meaning, relation, or permitted use.

An alias says only that L is another name for V. A B.5.3 move instead says what the source means here, which FPF value the FPF claim uses, whether any relation obtains, and what the named receiving use may rely on. Thus a component called “sensor” may lead to a System claim, measurement-capability claim, publication claim, or system-role-assignment claim; the expression alone chooses none of them.

B.5.3:5 - Archetypal Grounding

A thermodynamics team models a heat engine.

  • For “thermodynamic system”, recover the entity selected by the team’s model and its boundary and state-variable claims. If the claim concerns the identified heat engine, retain that System identity.
  • “Macrostate” makes a source-local claim about a state description or characteristic bundle over, for example, pressure, volume, temperature, and particle amount. State the scheme and units; recover an F.17 cell and its basis relation when the receiving claim needs them, and add a durable term row only when reuse needs one.
  • In Reynolds and Colonna’s control-volume formulation, “control volume” denotes a selected region of space. Identify its boundary and the matter and energy transfers across it considered by the model.
  • “Free-energy objective” may name an objective claim, characteristic, or selection criterion. The claim must say which FPF value the decision uses.
  • If the engine control System is assigned a locally defined heat-source-controller system-role kind, establish an obtaining occurrence of the declared U.SystemRoleAssignment species. The source-local meaning, classification, assignment, Work, claim scope, and time window remain separate.

Physical-system claims in this example use A.1 for system identity. A.14 distinguishes the part and whole relations claimed; A.22 defines how to identify a selected organization of established constituents and direct relations. A.3.4 identifies an actual bounded change when one is claimed. Use B.1.6 for any work-resource aggregation needed here and C.16 for measured characteristics.

The control-volume boundary and exchange claims require the thermodynamic rule. If that rule is unavailable, retain the local description and name the missing rule rather than asserting the relation.

What this achieves:

  • Domain constraints become reviewable without turning every domain word into a root kind.
  • Verification can use the pattern that defines or constrains the recovered value: boundary discipline for a control volume, characteristic-space discipline for state variables, system-role-assignment discipline when an assignment is claimed, and publication-use or evidence-use discipline for reports and dashboards.
  • The heat engine remains the same System across the accounts that discuss it. Any F.9 relation states how two distinct local meanings correspond; the named receiving-use claim states which losses block that use.

The same expression can be reused in an architecture view, a requirements document, and a simulation model only after each local claim identifies its value. If the claims use distinct local meanings, test any required F.9 relation and its receiving use separately.

Conformance Checklist

  • CC-B5.3.1 (Recover the FPF value used by the claim): The result names the FPF value or relation used by the claim before treating a preferred expression as reusable.
  • CC-B5.3.2 (No kindhood by spelling): A local expression, dotted name, table row, or diagram label does not become a U-kind. Recover a needed kind’s candidate domain and membership distinction under C.3; use E.24.UK for another durable public FPF U-kind.
  • CC-B5.3.3 (Role boundary): When role wording changes the claim, E.10.ROLE first recovers whether it means a local system-role kind, classification, assignment, participation, responsibility, or ordinary language. Each resulting claim then uses its FPF pattern.
  • CC-B5.3.4 (Relation and use boundary): Claim an F.9 Bridge only when its endpoint cells and predicate make it obtain. Judge the named use separately under F.9:4.2, retaining its direction, correspondence rule, loss tolerance, polarity, and any required same-use reliance or assurance result. State other applicability and return conditions when they qualify the use; shared spelling proves none of them.
  • CC-B5.3.5 (Description boundary): When the claim depends on distinguishing the described entity, description episteme, publication form, or carrier, use the description or publication pattern to recover that distinction.

Common Anti-Patterns and How to Avoid Them

Anti-PatternWhat it looks likeBetter FPF move
Subtype explosionEvery domain expression becomes a new root kind.Keep the source-local wording when it suffices. Use C.3 for a needed kind and E.24.UK for a proposed durable public FPF U-kind.
Magic synonymA table says “sensor = component” and is treated as identity or permission.Recover each local claim and the FPF value used. If two distinct cells must be related, test the F.9 relation and judge the named use separately.
Role-for-everythingEvidence, status, local meaning, responsibility, and document use are all called roles.Apply E.10.ROLE, then name the value or relation and use the pattern that defines or constrains it. A local system-role kind or assignment is only one possible result.
Description collapseA diagram label is treated as the entity, interface, or method.Keep entity, description episteme, conventions for reading the representation, and publication form distinct.

B.5.3:6 - Consequences

BenefitsTrade-offs / Mitigations
Domain language stays usable: Experts keep familiar words without forcing every word into the kernel.Recovery overhead: A load-bearing expression needs its source-local claim and FPF value. Keep the returned explanation short; recover F.17 cells and their basis relations for claims that need them, including F.9 Bridges, and add durable rows only when reuse needs them.
Kind claims have grounds: A kind’s candidate domain and membership distinction are recovered under C.3; another durable public FPF U-kind requires E.24.UK admission.Modeling choices: The bridge may reveal that one local word hides several FPF values. Split them before they drive work.
Cross-document clarity: Accounts can be compared while keeping their represented values and uses distinct.Need for a use boundary: Do not reuse a source-local claim or semantic relation in another project, scheme, scope, or action without checking the changed values, tolerated loss, and reliance basis.

B.5.3:7 - Rationale

This pattern implements open-ended parsimony: FPF can use many domain vocabularies without turning every useful expression into a kernel kind. It recovers the source-local claim first, uses the pattern that defines or constrains the needed FPF value, and introduces an F.9 Bridge only for a relation between distinct local senses.

B.5.3:8 - Relations

  • Builds on: A.2, A.6.5, C.3, E.24.UK, F.0.1, F.1, F.2, F.3, F.5, F.8, and F.17.
  • Coordinates with: A.7, C.2.1, E.10.ROLE, E.17, A.13, A.15, B.3.3, F.7, F.9, and the domain-specific CHR, LOG, and CAL patterns that define or constrain the value or relation.
  • Used when: a project must recover what a source expression means for one FPF claim, or must relate two distinct local meanings for a named receiving use without confusing the wording, FPF value, semantic relation, and use.

B.5.3:End

B.5.4 - Recognize a Concept in a Situation

Type: Method-description pattern Status: Stable Normativity: Normative unless marked informative

B.5.4:1 - Problem frame

Use this when you understand a concept’s explanation but cannot connect it to an unfamiliar situation. You need to interpret what is happening before you can explain it, construct a model or choose the next observation.

Begin with the question this interpretation should help answer. Identify what you can point to or describe, recover the relations a candidate concept requires, and construct their correspondence in this case. The first useful result is an interpretation with a consequence that guides the next action.

This requires an accessible domain account and enough background to understand it. If the concept is unfamiliar, obtain that explanation first. If the interpretation is settled and only a calculation remains, use the calculation Method.

B.5.4:2 - Problem

A familiar textbook question supplies cues that an encountered situation may lack. Knowing what polarization means can coexist with being unable to use it while looking at water. Even recognizing the material leaves the surface, directions and relations to be identified.

The missing contribution is the passage from the encountered situation to a usable interpretation. A correct interpretation should make a difference to an explanation, prediction, construction or action.

B.5.4:3 - Forces

  • A concept directs attention toward the relations it requires, while the first description of a situation can obscure them.
  • A sketch can expose a correspondence; a premature equation can leave its variables uninterpreted.
  • A familiar example helps learning, while changed conditions reveal which relations the learner can recover.
  • A useful interpretation depends on domain knowledge, whose acquisition may cost more than the immediate recognition work.

B.5.4:4 - Solution

  1. Name the question. Say what the interpretation should enable: reducing glare, explaining a changed reading, arranging compatible activities or choosing an observation. This determines which distinctions matter.
  2. Describe the situation at a useful scale. Indicate the relevant region, objects, time and conditions. Separate available observations from your proposed explanation. Try another boundary or viewpoint when the first description hides an interaction. If choosing the concept is part of your task, ask what difference in the situation could change the answer. Look in the domain account for a relation that could explain that difference. For example, to decide which tests can run together, ask what prevents simultaneous operation before choosing a representation of conflict. If a concept is given, start from the relation it proposes.
  3. Recover the candidate concept through its relations. Consult its explanation, examples and conditions. Identify its participants, how they are related, and the consequences relevant to the question. When a live alternative would change the answer, identify a consequence that distinguishes them. Use the domain account to supply knowledge omitted by a short definition.
  4. Construct the correspondence. Point to what supplies each participant here and explain the relations between them. Use a sketch, gesture, annotated observation or short account. If mathematics helps, connect each variable or mathematical object to its interpretation and identify consequential simplifications.
  5. Derive and examine a consequence. Work out what should follow in this situation and compare it with relevant available observations or constraints. When an unresolved correspondence or condition can change the needed answer, examine it through a variation, counterexample or feasible trial, or retain it as unresolved. Where competing interpretations support the same sufficient action, keep that bounded answer.
  6. Return to the question. Give the explanation, construction, action or next observation supported. When a consequence fails, revisit the object boundary, relation, condition, representation or candidate concept that produced it. Identify the missing domain contribution if the available account cannot resolve the question.

The result can be an interpreted sketch and a next action. Record the reasoning when another participant or later use needs to recover it.

To judge what a reader can do, recover which choice the work left to them. A reader given a concept can still identify the participants, establish the correspondence and derive a consequence. For a claim about choosing the concept, look for work in which the reader made that choice with the assistance allowed in practice. An earlier attempt can supply it. If transfer to different conditions is claimed, use evidence that covers the relevant change.

B.5.4:5 - Archetypal Grounding

B.5.4:5.1 - Glare from water

You want to reduce glare in an image. Identify air, water, an interface patch, incoming light and the direction from that patch to the camera. Draw the local normal and incidence plane.

For unpolarized illumination of a smooth dielectric interface at Brewster incidence, reflected light is polarized perpendicular to that plane. To minimize the reflection from that patch, turn the camera filter’s pass axis perpendicular to the reflected polarization. This is the domain relation supplied by Feynman, I.33, §33-4.

The interpretation tells you what to adjust. Moving the viewpoint changes incidence; ripples change local normals, so a single planar sketch may need several patches. Inspect a changed view and determine whether the proposed adjustment follows.

B.5.4:5.2 - Recognize a conflict relation before colouring a graph

A laboratory must place three tests in two simultaneous-run slots. Its operating conditions say that A and B need the same exclusive fixture throughout a run; B and C need the same exclusive power unit; A and C can run together. There are no other constraints in this constructed case.

Represent tests by vertices and a pairwise inability to share a slot by an edge. The operating conditions imply edges AB and BC. The construction in B.5:5.1 produces slots {A,C} and {B}; reading the result back means that neither exclusive resource is double-booked.

Now change the conditions: A and C also require the same observer throughout a run. The observer can provide the required observation for only one of those tests at a time. This adds edge AC. The triangle needs three slots under these conditions; two-colouring no longer supplies an arrangement.

Consider instead three tests with independent fixtures whose shared resource is a 5 A supply. Each draws 2 A. Any pair can run together, but all three exceed the supply’s capacity. A graph with no pairwise conflict edges loses that group constraint. Retain the currents and the slot-wise capacity inequality when constructing the arrangement.

B.5.4:6 - Bias-Annotation

Answer-bearing demonstrations favour recognition from familiar wording. When independent selection matters, examine what the reader chose before the decisive cue was supplied. Representation familiarity can also encourage premature graph, table or equation use; compare the represented relations with the constraint that changes the answer.

When a teacher, colleague or AI supplies the decisive interpretation, retain that contribution in any account of what the learner performed.

B.5.4:7 - Conformance Checklist

  • The question determines which distinctions matter.
  • The interpretation identifies the participants, relations and conditions in the encountered situation.
  • A consequence connects the interpretation to an explanation, construction or action.
  • When a relevant condition changes, recover what follows from the relation in those changed conditions.
  • The domain account, prerequisites and permitted assistance are accessible to the intended reader.
  • An independent-recognition claim is supported by an attempt made before the decisive conceptual cue is supplied.

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

Definition recitation. Return to what supplies the definition’s participants and relations in this case, then derive a consequence.

Representation chosen before the constraint. Compare what the representation preserves with what the use needs. In the laboratory case, pairwise compatibility leaves aggregate current to be handled separately.

A demonstrated answer credited as independent recognition. Use the demonstration for learning. For assessment, recover the choice the reader made under the conditions of the claimed work.

B.5.4:9 - Consequences

The practitioner obtains an interpretation they can use and revise. A mismatch becomes a question about an object, relation, condition or domain account. A later calculation receives identified quantities; a model receives interpretable elements; further inquiry receives a next question or observation to pursue.

The cost is constructing and examining the correspondence. This work can be small when the relations are clear.

B.5.4:10 - Rationale

Concepts become useful through their relations to a situation. Recovering these relations and following a consequence connects interpretation to action. Reversing that passage after a failed consequence makes the interpretation correctable. A sketch and an equation can serve this work differently; their usefulness depends on the distinctions they expose.

B.5.4:11 - SoTA-Echoing

The working question is how to interpret a situation when a usable concept account is available but its participants in that situation are missing. For this entry, use the concept-led correspondence in steps 3–4 as a specialization of the broader first-model route in B.5:4.1.1. The broader route remains useful when the relevant relation has to be proposed.

Compare the two routes on :5.2 using the same operating conditions, an explanation of graph colouring, and a sketch plus the resource checks. B.5 first asks which tests and resources must remain distinguishable, then asks the engineer to propose their connection. An exclusive-resource conflict supplies AB and BC; a cheap consequence supplies {A,C}/{B}; challenging an omitted interaction can expose the shared-current constraint. That route can solve the case.

Here the reader’s stated difficulty lies inside that “propose their connection” move. Steps 3–4 work back from the understood relation: an edge joins two participants that cannot share a slot. Fill the two participants with A and B, and identify the fixture whose exclusive use makes the relation hold; repeat for B and C and check A with C. This supplies both the graph and the reason for each edge before colouring.

In the 5 A variant, the same correspondence question asks what the empty graph represents: permission for each pair. Comparing it with the required permission for the whole group exposes the missing sum, 2 + 2 + 2 > 5.

Both routes yield the same correct schedule; this specialization supplies the relation and its operating-condition check inside the broader instruction.

The trade-off is participant-by-participant work where the broader instruction leaves that work to the reader. It uses the same domain account and case data; retain it only while constructing the correspondence is the difficulty. When the reader has that correspondence, :1 returns to the calculation. When no usable relation has been selected, B.5’s first-model route retains the wider search.

These case comparisons establish the additional instruction and its consequence; comparative learning speed and transfer remain empirical questions.

Sirnoorkar, Bergeron and Laverty (2023), §III supplies the target-to-representation, internal-reasoning and interpretation-back account used in steps 4–6. Its discussion of problem assessment, model construction and interpretation makes the broader modeling route an alternative. The adaptation here unfolds the target-to-representation work from the relations in an understood concept.

The cited account’s empirical basis is two physics problem-solving cases; the scheduling comparison above is a constructed comparison of the instructions.

Kashyap and Singh (2026), §II and case B shows redrawing alongside spatial reinterpretation and continuing grounding errors in electrostatics problem solving. Adapt that contribution in step 2 and :5.1: change a viewpoint when it can reveal a needed relation, then check the relation’s physical conditions.

Reconsider this choice if an intended reader cannot fill a decisive relation from the available concept account, or if the broader modeling instruction supplies the same recoverable correspondence with less effort. Obtain the missing explanation, or use the broader modeling route when it supplies the needed correspondence. The optics law remains supplied by the linked Feynman account, and the laboratory consequences follow from their stipulated operating conditions.

B.5.4:12 - Relations

  • C.3 supplies kind recovery, classification applicability and judgment when a classification question arises.
  • C.29 helps select and interpret a mathematical representation, including its preserved and lost structure.
  • B.5 connects the interpreted question to construction, inference, observation and a useful continuation.
  • A.7.1 supplies consequence-guided ontological repair when a working claim gives a defeated engineering result.

B.5.4:End

B.5.PI - Initiate Inquiry from Work

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

B.5.PI:1 - Problem frame

Use this pattern to make room for a useful question in work that people or agents treat as ordinary. Reports arrive, calculations run, repairs succeed, and nobody asks whether the way of obtaining or using those results needs examination. Use it also when someone says that an explanation misses something but cannot yet say what. A known error, an anomaly label and a request for help are not prerequisites.

Start at a small occasion connected with the work: preparing a handover, demonstrating a result, explaining a consequential choice, or resuming work after a change. Recover what the result is supposed to enable and examine one available episode of obtaining and using it, including the adjustments that made it succeed. A performer can do this while preparing their work; a colleague or team can arrange the occasion. It takes access and attention, even if only briefly.

A suitable long mantra can give that occasion a connected set of questions before a difficulty is felt. Section 4.2.1 explains how to choose it and use it to find a question, while keeping the substantive Method and its conditions. The useful result is a question with an attainable next move, an early cue retained for further consideration, or a reasoned continuation without change. Here, inquiry includes a short question to a colleague or consultation of an existing explanation; it need not become a research project. The method helps bring an unexamined part of work into consideration.

Use an adequate existing answer. When the question is already clear, use its subject method. When a known useful method goes unnoticed at the right moment, A.15.11 helps arrange that encounter. Continuous monitoring, statistical anomaly detection and a full audit have their methods; they are not mandatory implementations of this one.

B.5.PI:2 - Problem

A worker receives enormous values from a familiar calculation and says, “It sometimes does that.” A team meets every deadline through repeated manual repair. An assistant answers a colleague’s objection with a familiar recommendation, then treats the colleague’s inability to name a better answer as closure. The work continues without a question about the unexplained part.

More searchable advice cannot help until something makes that advice worth seeking. “Ask for help when there is a problem” assumes the recognition that is missing. “Look for anomalies” leaves both the occasion for looking and the relevant comparison unspecified. A passed checklist establishes only the conditions it checked.

The difficulty is to let ordinary work generate a question without requiring a prior diagnosis, a permanent observer or an expert who knows the answer. The opposite error is to manufacture a defect whenever something differs from expectation, or to turn every small uncertainty into an expensive investigation.

B.5.PI:3 - Forces

NeedDifficulty
Begin before a problem is recognizedA worker absorbed in producing a result has no independent reason to search for another method.
Learn from successful workAn adaptation can reveal a dependency worth changing, or be the best available way to do the job.
Preserve an emerging concernFamiliar terminology and a listener’s expertise can replace what has not yet been expressed.
Obtain a meaningful comparisonA rare value can be valid; a routine outcome can fail its intended use.
Keep the whole work goingAttention, advice and investigation consume resources and can disrupt the action they support.
Share the work of inquiryA participant can supply a cue without knowing its cause; another contribution must make interpretation or action possible.

B.5.PI:4 - Solution

At an ordinary work occasion, recover the use and what it takes; compare; keep what the account misses; form a question or retain the cue; obtain a worthwhile next contribution; return to the whole work. These moves form one connected method. Enter where a contribution is missing, return when a comparison changes the question, and stop when the receiving use is settled. The links below supply operations, not an obligatory chain of pattern applications.

B.5.PI:4.1 - Give the work an occasion to become a question

Select a bounded occasion that does not depend on someone first reporting trouble. At an ordinary handover, for example, ask the producer to show one result and how its recipient will use it. Recover what the producer had to do, including work that the official account omits. In preparing your work, follow one result through its intended use instead of merely checking that you have produced it.

Choose an occasion with some prospect of a useful comparison: a consequential decision, a result passed to another person, a recurrent activity whose effort is poorly understood, or an available contrasting case. A small agreed sample can expose something that reviewing only failures would miss. Do not require every occurrence to undergo this examination. Keep the immediate work and its constraints in view.

Choose the occasion in light of what you have been asked to find. One handover can yield a worthwhile question when you are free to explore. For a question about why a difficulty recurs in the practice, follow the work that produced the result and what happened when others received it. The same visible outcome might arise from a fixed constraint, a choice by the producer or a recipient’s adjustment. Look for something that distinguishes these explanations, such as the information available before a choice or how the result was used. A rule covering all the relevant work can explain a recurring dependency. Its use on a particular occasion and the frequency of an outcome call for grounds about that work.

A performer may adopt this as a habit; a teacher, team or tool maintainer may make it available through A.15.11. For example, an existing handover conversation can include “Show what the recipient can do with this, and what you had to add to make that possible.” This question does not anticipate a specific error. A publication alone does not establish the habit or supply the conversation. If a result, its use or an attentive participant is unavailable, identify which comparison or conclusion needs that access. Use what the occasion already establishes, or preserve the cue when that is all it supports.

B.5.PI:4.2 - Compare before deciding what is wrong

Connect the intended use with an accessible episode. Try using the result, ask its recipient to demonstrate the use, compare an available prediction with what occurred, or work through a nearby case whose consequence can be established. Include the adjustments that made a successful outcome possible. Keep observations, memories and constructed cases distinct.

Ask what makes an apparent difference acceptable or inevitable. “This always happens” states frequency; it does not establish adequacy. “The procedure was followed” supports conformance; it does not establish that the procedure answered the receiving question. Conversely, unfamiliarity does not make a result defective. A symbol that looks like a numerical answer may be an agreed status marker; an adjustment may preserve a necessary constraint.

Use subject knowledge to interpret the comparison. When that knowledge is missing, the question may concern what the result means or which conditions justify its use. Do not invent the missing observation or explanation. If the available account explains the difference and supports the intended use, continue the work without creating a problem.

An anomaly is a difference relative to an account, expectation, comparison class or intended use that merits consideration. Make that reference clear when it affects the next move. Statistical rarity, a breached requirement, a felt mismatch and an unused possibility are different reasons to look. Problematization develops or questions what is taken for granted so that a consequential question becomes possible. It can change the comparison itself: something previously normal can become questionable under a better account. Anomaly detection therefore need not be completed before problematization starts.

B.5.PI:4.2.1 - Use a mantra to look for an unrecognized problem

An explanation of a Method, or of several connected Methods, shows which answers belong together and why their conditions matter. A long mantra recalls those connections in a short form. Applying it to ordinary work can reveal an unanswered consequential question before anyone experiences a failure. The reminder supplies a place to look; subject knowledge and comparison determine what the apparent gap means.

Choose the mantra by the result being examined. For a project account, A.1.STM connects intended use, functioning, construction and creators. For a physical question whose answer depends on mathematics and computation, B.5.MPC connects the physical account, interpretation, mathematical consequence, computation and return.

Recover the supplying Method’s purpose, applicability, dependencies and order of justification. From the proposed system boundary, A.1.STM examines the larger whole and the joint functioning of its parts to derive the system’s contribution before turning to construction and creation. Another Method can connect different subjects and require a different order. If the working question is answered by a sufficient contribution, use that answer instead of adding a traversal.

Apply the questions to an episode of the work or a possible case relevant to it. An existing explanation, drawing, calculation or demonstration may supply enough material. Follow the connections that the decision consumes: what must each answer mean, what does the next operation need from it, and under which conditions can they be used together? Use the mantra’s logical direction while admitting supported answers at their appropriate places and returning when a later condition changes an earlier premise. When a short phrase cannot explain the connection, obtain the developed Method or the missing subject knowledge.

Keep a missing answer, an incompatible pair of answers and an adequately supported answer distinguishable. A blank can mean that the condition is unknown, irrelevant here, or absent in the situation; determine which consequence matters before calling it a defect. Work one discriminating consequence where useful: would the result still answer its use if this assumed connection failed or this ordinary condition changed? A constructed possible case can expose an unsupported general promise; it does not show that the failure has occurred.

Turn the consequential gap into an inquiry: what claim or condition needs to be established, why its answer could change the work, and what attainable observation, explanation or construction could resolve it? Continue through sections 4.3–4.5. C.22.2 is useful when the next operation needs an inspectable problem-side formulation; a Problem claim retains C.22.PFR’s conditions. Preserve a cue when that is all the occasion supports, and continue without change when the supplied grounds are adequate.

A felt difficulty can lead to the same questions by tracing what the work should enable and where its account fails. The mantra makes selected consequential dependencies available before that symptom is noticed. Keep the resulting question and useful continuation.

B.5.PI:4.3 - Keep the part that the familiar account loses

Retain the episode, expression or contrast that cannot yet be explained. B.5.EA helps a participant develop a distinction when familiar words conceal it. The listener should try the proposed interpretation on the original case: if following the offered advice would leave the concern untouched, reconsider the interpretation.

Use the conversation, document or work already available before asking the participant to collect more evidence. Ask for a missing fact when it is needed; do not require the participant to supply the diagnosis that the joint work is meant to develop.

For example, advice to make a help form clearer does not answer why someone who sees no problem would open it. Preserve that difference even when neither participant can yet state a complete alternative method. An objection warrants examination of the account; it does not make the objector’s causal explanation true.

An early cue is something noticed as worth retaining before its meaning or continuation is settled. It is not yet a confirmed anomaly or a formulated question. Keep the passage, observation or rough expression that lets someone return to it. The existing conversation may suffice.

A.16.1 supplies deliberate preservation when otherwise the cue would be lost; B.4.1 can make possible continuations explicit after stabilization when someone needs that contribution. Neither requires every exchange to acquire a new form or route record.

Stop here if only the cue is recoverable and further articulation is unproductive. Identify an attainable return occasion when one is available, without inventing a commitment or declaring the concern resolved.

B.5.PI:4.4 - Ask from the situation before naming a solution

State what the work should enable, what comparison or experience raised the question, under which conditions, and why the answer could matter. Ordinary words are enough: “How can this figure help price the next batch when it has no numerical value on some days?” is a usable question without the phrase “division by zero”. Search a library or ask a colleague using the situation and needed result. A PatternID is one way to obtain an answer after its relevance becomes intelligible, not a prerequisite to inquiry.

Let the first answer inform your choice of the next question. A calculation can be correct for the wrong quantity. An explanation can answer an easier question than the one the recipient needs. In an open inquiry you can choose a different question for what it promises to reveal. In a fixed assignment, ask what an answer to the proposed question could establish for the original use. Return that contribution to the recipient, or explain why a change of assignment is worth considering. B.5.QD develops a consequential question when the initial one needs reconstruction. B.5.QD.CF examines assumptions behind an apparent conflict.

An adequate known explanation, instruction or correction may finish this use. If the question needs a new construction, explanation or test, B.5 connects the reasoning contributions. Keep later investigation and problem formulation under their conditions; a provisional question need not be promoted immediately to a fully specified Problem or research programme.

B.5.PI:4.5 - Obtain a continuation that can be used

Choose what is missing: an existing answer, one discriminating comparison, accessible expertise, a capability to develop, or a larger inquiry. Judge the effort against what the answer could change in the encompassing work. C.11.DUA examines burdens imposed by advice; C.11.CRC compares an attainable change with continuing as now. They help choose an intervention, not decide whether a participant is allowed to voice an unresolved concern.

Carry an answer back to the receiving use. Does it let the recipient act, understand or ask a better question? If a small comparison can discriminate between plausible explanations, make that comparison before prescribing a larger change. If the performer understands the needed action but cannot execute it, obtain support or a suitable learning method; repeating the question does not develop the capability.

If no worthwhile improvement is available, retain the adaptation with its relevant conditions. If inquiry cannot be afforded or a needed observation is inaccessible, say what remains unknown and what that means for the use. Inability to investigate does not certify adequacy. A retained cue and an available later occasion can be the bounded result. Where consequences require a decision now, obtain it through the applicable subject and authority rules rather than letting unresolved uncertainty authorize continuation.

B.5.PI:4.6 - Keep the opening usable while the whole work continues

After use, examine whether this occasion brought something consequential into consideration and whether the result justified its burden. Change an unhelpful question, move a disruptive occasion, obtain a missing response, or remove a ritual that produces only ticks. Passing an execution checklist can support selected claims; it does not close concerns outside those claims. A known-condition checklist is designed through A.15.11, while the present method keeps a way to question what that list leaves unexamined.

Make it possible to respond. A worker with no access to receiving outcomes cannot inspect them. A request that nobody can answer does not supply assistance. When raising a concern is punished, changing the conditions of joint work may be necessary; asking for greater personal vigilance does not repair those conditions. Use the smallest attainable support that answers the need, without assuming a permanent observer.

Producing a result, keeping it usable and learning from the attempt can be enacted together in an action. B.1.5 and B.1.5.EW help recover the relevant Method composition and how those actions enact encompassing work, including the constituent capabilities and receiving use.

In a time-critical or bodily action, a pause, later replay or another participant’s observation may preserve the whole better than an added question during execution. Human learning and changes to an AI system’s access, instructions or training require their respective methods. An answer obtained with supplied guidance is not evidence of later independent recognition.

B.5.PI:5 - Archetypal Grounding

These are constructed cases with stated conditions.

B.5.PI:5.1 - An on-time handover hides recurring work

A team hands over a completed daily schedule. Nobody requests an audit: the recipient receives the schedule on time. While preparing an ordinary handover, the producer follows one entry from the incoming list to the recipient’s use. They show that they retype twelve equipment names from memory because the incoming abbreviations differ from the recipient’s names. The deadline is met because the producer knows both conventions.

The listener first says, “Make the deadline reminder clearer.” Applying that suggestion would leave all twelve retypings and the reliance on one person’s memory unchanged. The producer cannot name a better method, but can point to those transformations. Keeping that contribution changes the question from punctuality to whether the recipient can identify the equipment without repeated reconstruction. The producer’s skill remains a successful adaptation, not evidence of misconduct.

The next question is small: “Can we make the correspondence available without losing distinctions the recipient needs?” In this case an authoritative list exists. The two participants compare twelve entries with it; ten have a unique correspondence, while two abbreviations denote different equipment in different buildings. A single global replacement would conceal that difference. They retain the building context, give the recipient the resolved names and leave the two unresolved entries for the person who can supply their locations. The receiving schedule is checked by identifying the intended equipment, not by counting replaced labels.

For repeated handovers, an available mapping keyed by name and building may remove some reconstruction. Whether to prepare and maintain it depends on use and effort. A one-off schedule with no further receiving difficulty can keep the manual translation. In either case the inquiry returns to the schedule: the recipient can use the supplied identities, or knows which entries need a location. It need not create a new organization-wide programme.

For a request confined to whether today’s schedule arrived on time, the recorded delivery time can suffice. For a request to discover a dependency in preparing the schedule, the producer can choose to investigate the reliance on memory. If the review concerns how often recipients have had to correct a name, follow what the recipients actually received and did. All twelve retypings happened before delivery. The authoritative list can establish which codes require a building wherever those conventions apply, even while the frequency of actual corrections remains unknown.

If the recipient instead demonstrates that both naming conventions are understood and the retyping merely changes typography, the proposed identity problem disappears. Ask whether the extra effort is worth removing; do not preserve the first diagnosis because it motivated the comparison. If neither receiving use nor the authoritative list is accessible, retain the dependency on memory as an early cue and obtain access when worthwhile. No claim of safe replacement follows from that cue alone.

B.5.PI:5.2 - A familiar calculation produces an unusable figure

A daily report divides total operating cost by completed units. On a day with zero completed units, the software displays an infinity marker. The preparer treats it as normal because it happens regularly. During a handover for pricing the next batch, the preparer tries to explain what price decision that entry supports. The gap becomes apparent through the use, before anyone names a division rule.

An existing mathematical explanation establishes that the quotient has no real-valued result when the denominator is zero. That answer removes a false numerical reading; it does not choose a pricing method. The receiving question now concerns which costs, output and period can support the proposed price. Obtain the appropriate accounting and modeling contribution rather than replace the marker with an invented number.

If the receiver shows that the marker means “no production”, is never used in pricing, and the pricing calculation uses appropriate separate inputs, the unfamiliar display need not be a defect. The relevant use is explained. Altering the software to remove the unusual value would answer a different question.

B.5.PI:5.3 - An objection cannot yet become a named problem

A reader says, “This guide misses something,” and points to its instruction to ask for help when trouble occurs. The assistant proposes a more visible help button. The reader objects again but cannot name the missing method.

The assistant returns to the available exchange and tests its advice. A person who regards the work as ordinary would still have no reason to use the button. This comparison preserves a difference between reaching help and finding a reason to seek it. The assistant can examine ordinary work occasions instead of requiring the reader to prove a new diagnosis.

If the reader can only point to the phrase and must leave, keep that passage and the unresolved concern in the existing conversation. A usable question may come later. Neither a polished paraphrase nor the reader’s departure proves that the concern has been answered.

B.5.PI:5.4 - A successful calculation leaves a physical connection unexamined

A designer has a graph program that returns a valid two-colouring for three gears listed as a chain: contacts AB and BC. Its tests pass, and nobody has complained about the result. At an ordinary design discussion, the designer uses B.5.MPC’s mantra to explain what the result says about the proposed arrangement. The question is whether all three gears can rotate while the stipulated meshes remain engaged.

The physical-to-mathematical connection asks what each edge represents and whether the contact list preserves the relevant physical contacts. Showing the successful program run leaves that question open. Inspecting the available design establishes, for this constructed case, a third external mesh CA. The assumed idealized model has fixed parallel axes, positive pitch radii and external meshes, with rotation viewed from one side. Under those conditions every mesh requires opposite rotation directions. Around the three-contact cycle the alternating directions conflict, so nonzero coupled rotation is excluded. B.5.MPC:5.2 develops the argument and its interpretation.

The first useful question was therefore “Does this list include every contact that constrains rotation?” rather than “How do we improve the colouring program?” The program can remain correct for its input. A corrected contact representation returns the physical obstruction; the designer can compare a changed arrangement or a different justified contact model. Deleting the extra edge only in the graph would leave the proposed physical obstruction untouched.

Change one condition: the apparent CA line is only a drawing crossing, and the design establishes no mesh between C and A. The chain representation then preserves the stipulated contacts. Retain its compatible-direction result under that model. Tooth engagement, torque and motion under load remain separate questions only when the receiving decision needs them. If the contact cannot yet be established, retain that uncertainty and obtain the needed inspection; a drawn proximity alone settles neither outcome.

The mantra exposed a connection worth examining before a felt failure. The contact evidence and kinematic argument supplied the answer. This illustrates the inquiry operation and its bounded continuation.

B.5.PI:6 - Bias-Annotation

An expert can mistake the absence of their preferred method for a defect. A familiar institution can instead normalize costly adaptations or silence a contribution because it has no accepted vocabulary. Test both interpretations against what the work enables. The person who notices a difference need not know its cause; the person who supplies an explanation needs to show that it answers the original use.

B.5.PI:7 - Conformance Checklist

For guidance or an application claiming this method, examine the consequential conditions:

  • The entry can occur without a recognized error, a diagnostic term or a request for an audit; its occasion, access and attentional demand are recoverable.
  • The comparison retains the receiving use and what it took to obtain the result, including successful adaptations when they matter.
  • When a mantra guides the comparison, its Method fits the question; its connections and justification order are applied to a recoverable case. A found gap becomes a qualified question or cue, while adequate answers and irrelevant conditions permit a stop.
  • A proposed interpretation is tested on the original case; the participant is not required to invent a diagnosis before their concern can be examined.
  • An early cue can remain open without being mislabeled a confirmed anomaly, Problem or selected investigation.
  • The continuation can obtain a usable contribution, identify missing means, or stop without change under stated conditions.
  • Conformance, result achievement, adequacy for the receiving work and completeness of the description remain different claims.
  • The result returns to the encompassing work. Its grounds show what the occasion establishes there, including any claim about recurrence. A claim about later independent use has its own basis.

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

Wait for the worker to complain. Use an ordinary demonstration or handover to connect a result with its use before a complaint exists.

Normalize by repetition. Compare the recurring feature with the use it serves; frequency alone settles neither harm nor benefit.

Solve the listener’s substitute question. Apply the proposed remedy to the originating episode and retain what it leaves untouched.

Require a named defect before listening. Work with a recoverable fragment or early cue. Interpretation and warrant can follow separately.

Turn every difference into a project. Use an adequate explanation, make a small useful comparison, or retain the present arrangement. An inquiry must earn its additional burden.

Recite a mantra and declare a diagnosis. Apply its substantive questions to the case, recover their needed grounds and investigate the consequential gap. An unanswered prompt alone establishes no defect.

Treat a passed checklist as comprehensive adequacy. State what was checked and keep consequential concerns outside the list available for inquiry.

B.5.PI:9 - Consequences

An apparently routine task can yield a question that a search service, colleague or pattern library can help answer. Successful adaptations and inarticulate objections can contribute without being recognized defects. The work gains a connection between doing, questioning and obtaining another method.

This consumes attention and sometimes exposes a need that cannot yet be met. False leads and imposed interpretations remain possible. Its use depends on accessible work, interpretation and an attainable response.

B.5.PI:10 - Rationale

Detection presupposes something to compare and attention to a difference. Ordinary work can supply both at an occasion where its result must mean something to another action. Recovering successful adjustments reveals dependencies that an output check alone omits. Asking what makes those dependencies necessary allows both criticism and justified retention.

The whole method is longer than a reminder because its intermediate results differ. A selected occasion makes a comparison possible; the comparison may supply an early cue; articulation can develop a question; the question makes a relevant answer findable; use of that answer tests whether the original work was helped. The sequence can shorten, loop or stop as the available contribution changes.

B.5.PI:11 - SoTA-Echoing

The practice question is how ordinary work becomes open to useful inquiry before its performer recognizes a problem. The synthesis combines problem detection, questioning of assumptions and examination of successful work.

Interpretation, not only signal strength. Klein, Pliske, Crandall and Woods, Problem detection (2005), is a historical account of how context and interpretation affect recognition. It motivates comparing accounts and revisiting explanations in §§4.2–4.3.

A technical detector is an alternative when a suitable representation and criterion exist. Ruff et al., A Unifying Review of Deep and Shallow Anomaly Detection (2021), makes those technical choices explicit. Its detector families do not decide what an unexamined work practice should regard as worth questioning. Use such a detector for its stated object, rather than substitute statistical rarity for practical inadequacy.

Question the premise that makes a situation ordinary. Alvesson and Sandberg, Generating Research Questions Through Problematization (2011), supplies a historical method of articulating and challenging assumptions, including one’s own. Adapt that operation in §4.2 and §4.4. Their research-literature setting does not make novelty or academic audience interest sufficient practical value. A routine explanation remains preferable when it settles the use.

Examine what successful work required. Marques et al., Learning from normal work in complex sociotechnical system—Case in midstream operation (2025), uses facilitated accounts of ordinary work, adaptations and constraints. This informs the non-incident entry in §4.1 and the handover case. The situated industrial study does not demonstrate spontaneous inquiry by an unsupported performer; neither its interview duration nor a permanent facilitator is prescribed here.

Tucker, Edmondson and Spear, When Problem Solving Prevents Organizational Learning (2002), supplies a historical contrast: local workarounds can sustain output while leaving recurrent conditions unchanged. Retain the adaptation’s contribution before deciding whether to alter those conditions.

A noticed discrepancy is not yet learning. Bascandziev, Thought Experiments as an Error Detection and Correction Tool (2024), shows the importance of representation and reasoning in bounded force-and-motion tasks. Theobald et al., Do reflection prompts promote children’s conflict monitoring and revision of misconceptions? (2024), distinguishes effects on monitoring from later learning and transfer. These comparisons support separating encounter, interpretation and later capability in §4.6; they do not establish the same learning mechanism in humans and AI systems.

Reconsider the arrangement when a simpler ordinary interaction supplies the same contribution, repeated comparisons leave the original concern untouched, attention costs exceed the attainable benefit, or missing access makes the intended operation impossible. More prompts alone do not resolve these failures.

B.5.PI:12 - Relations

  • A.15.11 arranges an encounter with a potentially useful method, including this inquiry method, and supports known-condition execution checklists. It does not supply the question developed here.
  • B.5.EA develops a correctable expression; A.16.1 preserves an early cue; B.4.1 makes grounded continuations explicit when needed. Their results can remain provisional.
  • B.5.QD, B.5.QD.CF and B.5 develop questions, examine conflicting assumptions and connect reasoning contributions after or during this entry.
  • A.1.STM and B.5.MPC supply developed Methods and their long mantras for different receiving questions. This pattern uses a suitable reminder to initiate inquiry before a complaint; each supplying Method retains its subject knowledge, order of justification and conditions.
  • C.22.PFR, C.22.2 and E.18.1 govern problem-side distinctions, inspectable problem formulation and carrying an accepted formulation into work. They do not require every early cue to be such a formulation.
  • C.11.DUA/.CRC help choose a worthwhile continuation; A.15.7 selects a next action under current conditions. E.11.PUA returns a selected pattern’s result to its receiving use and can reopen inquiry here.
  • B.1.5 and B.1.5.EW recover simultaneous constituent and encompassing methods; E.23.CDI frames capability development when the needed contribution cannot yet be performed.

B.5.PI:End

B.5.SD - Construct an Answer through Substantive Discussion

Type: Method pattern Status: Stable Normativity: Normative

B.5.SD:1 - Problem frame

Use this pattern when a discussion is meant to produce an explanation, model, proposal or plan for inquiry that another practitioner can use, but orderly participation has not yet supplied that result. Begin with the receiving question and the reasoning needed to answer it. Arrange capable participants to construct the answer together, making the important relations and uncertainties examinable.

For example, individual module tests have passed, but a reviewer needs grounds for the assembled configuration. Collecting the test reports or asking each participant for an opinion does not yet explain whether their results compose.

A competent expert’s answer, an already adequate model or a short clarification may settle the question. Use it. This method does not require a workshop and does not replace engineering, research, strategy or another practice that supplies the subject reasoning.

B.5.SD:2 - Problem

Communication can succeed while the receiving task remains impossible. A board of notes contains many relevant claims but no relation between a changed assumption and the proposed decision. A facilitator can distribute speaking time without possessing the competence needed to construct that relation.

The reverse mistake is to dismiss facilitation or participation because subject expertise matters. A technically skilled participant can also suppress a valid objection, leave terms ambiguous or prevent the group from examining the answer. The problem is the missing combination of constructive subject work and a process that permits it.

B.5.SD:3 - Forces

Several participants can contribute knowledge that no one initially holds together. Their contributions need interpretation and integration, not merely collection.

A clear question limits effort, yet the question may change when a hidden assumption is exposed. The group needs enough structure to return a usable answer.

Participation and neutrality matter to the fairness of discussion. A warranted technical conclusion also requires discriminating between supported and unsupported claims. Fair hearing does not assign equal evidential weight to every statement.

An inquiry can improve the answer, but waiting for every uncertainty to disappear can defeat its use. The method needs a bounded result, a supported limit and a useful continuation.

B.5.SD:4 - Solution

B.5.SD:4.1 - Name the receiving question and the kind of answer needed

Identify who will use the result and what they need to settle or do. Ask for the decision or inquiry as they face it. A participant may bring one disputed case to a discussion about a rule for future cases. Find out which choices the group is being asked to make and which the eventual user must be able to make. The case can reveal a missing distinction. To offer a rule to that user, establish where the distinction changes the answer.

Distinguish the result required. An explanation relates what is known and why; a proposal states what could be done and on which grounds; an inquiry proposal identifies an unresolved question and a way to answer it; an agreement records accepted contributions. A discussion can produce more than one, but one does not substitute for another. Use LDR.2 when the unresolved result is acceptance of contributions rather than subject understanding.

Set a completion condition. For a configuration review, the receiver may need to know which claim is supported for the configuration, which remains unsupported and which observation would settle the gap. “Everyone understands the issue” is not enough if the receiver still cannot distinguish those claims.

Recover an adequate existing answer before assembling new work. If the relevant model already supplies the needed explanation under current conditions, explain its application and stop. If the receiving use differs, identify the difference that changes the inference instead of rejecting the whole earlier result.

B.5.SD:4.2 - Select the construction and its capable performers

Ask what operations produce the required answer in this subject. An engineering comparison may need requirements, models of alternatives, consequence estimates and an applicability judgement. A source-supported argument may need interpretation of the original claim, its evidence and the receiving use. A causal question needs an appropriate causal method, not an attractive sequence of events.

Obtain the method and people or agents capable of performing it. Name the missing professional contribution concretely: “Determine whether changing parameter P invalidates the earlier test,” rather than “bring expertise.” If no available method can produce the required answer, C.39 helps develop the missing construction or return the result that cannot yet be obtained. A meeting technique cannot fill that absence.

Arrange integration as work. Someone must connect the contributions into the answer the receiver needs. This may be a subject expert, a capable facilitator with the necessary subject knowledge, an AI system qualified for the task, or several participants whose contributions fit. The label “facilitator” neither guarantees nor rules out that competence.

Keep necessary roles distinct. A process facilitator can preserve questions, participation and agreement on how to proceed. A subject integrator constructs the reasoning. A decision maker accepts a course of action under the applicable authority. One performer can hold compatible responsibilities, but do not grant subject authority from control of the discussion.

When the discussion forms part of a decision-support inquiry, obtain the engagement conditions for participation, representation, consent, usable channels, confidentiality and faithful return. Establish whose concerns and contributions can be represented, what participants have accepted, which disclosures are permitted and where the result must return. A facilitation Method can supply adequate subject integration when the performer is capable.

In other practices, obtain the required participation and authority conditions from their owners. A joint mathematical proof, for example, can require capable integration and protected participation without a decision-support engagement. The construction here remains the warranted connection between the claims and the receiving answer; it does not supply professional permission or replace protected participation.

B.5.SD:4.3 - Make the proposed reasoning inspectable

Begin with the objects, claims and conditions the answer concerns. Recover ambiguous terms only where they change the question. Establish which configuration, period, population or use a claim describes; retain the source and limitation where reliance depends on them.

Then connect the claims. Use B.5.RA:4.4a to recover an argument implicit in prose or dialogue, or to examine an already clear argument and the support an objection challenges. For each important conclusion, ask what supplies its ground and what relation permits the next inference. For a proposed action, ask how its contributions produce the receiving result. Trace dependencies in both directions: from the result to what it needs, and from a supplied finding to what it warrants.

In a multi-component system, distinguish the claim that each component works from the claim that they work together. Recover interfaces, interactions, loads and shared conditions that can defeat composition. In an organizational proposal, distinguish one participant’s spare time from joint availability at the moment of handover. In a learning design, distinguish exposure to instruction from the operation the learner will later perform.

Use the form best suited to the subject: a calculation, diagram, connected prose, prototype, table with explained relations or another working product. Choose a form that exposes the reasoning. A canvas or checklist can also help notice an omitted concern.

At intervals, have the receiver or another capable participant trace a consequential question through the developing answer. Which conclusion follows? From which grounds? What action does it permit? A break in that trace locates more useful work than another general round of opinions.

B.5.SD:4.4 - Work with objections as contributions to the answer

Invite a participant to state the claim, relation or consequence they challenge and why it matters to the receiving use. Restate the objection in terms they recognize before trying to answer it. Preserve an unfamiliar but potentially consequential objection long enough for a qualified contributor to examine it.

Distinguish several responses. A misunderstanding can need explanation. A factual conflict can need source comparison or observation. An unsupported inference can need a model, test or narrower conclusion. A disadvantage can require another proposal. A value conflict can need D.4 or a governing decision. An incompatible contribution belongs with LDR.2. These are different continuations, not labels for dismissing the objector.

Connect the answer back to the objection. Show which premise, relation, result or limitation changes. If the answer resolves only part, retain the rest. A participant’s changed view may help the group act, but persuasion is not the test of technical truth. Conversely, an accurate explanation can leave a legitimate refusal unchanged.

Where confidentiality prevents full inspection, obtain a permitted qualified judgement and state its usable scope, or narrow the reliance. Do not invent a transparent basis. If a required independent judgement would be compromised by the discussion arrangement, obtain it through its proper method.

B.5.SD:4.5 - Obtain only the further construction needed for an answer

Locate the consequential gap. Identify the question an additional calculation, experiment, consultation or design operation would answer. Compare the attainable contribution with its cost, delay, risk and displaced work under C.11.DUA.

Consider several continuations. A joint test may answer the interaction question. A narrower claim may be sufficient for current use. A revised design may remove the uncertain interaction. Another available result may apply. Deferral may be warranted if the required basis cannot be obtained. Use present adequate knowledge before demanding new evidence.

Arrange the selected inquiry’s method, capable provider, resources and permission. Its completion does not imply permission for the later action. Return its findings through their conditions of applicability, then reconstruct the connected answer. If the new evidence changes a premise that affects other conclusions, use B.5.RR to follow and revise the affected reasoning while preserving independent support. Then return that revised contribution to the connected answer.

A useful result can be an open question with a feasible next construction. State what is already supported and what cannot yet be relied on. Do not call the whole issue resolved because the group agreed how to investigate it.

B.5.SD:4.6 - Return the answer and test a consequential change

Give the receiver the connected result in a usable form, with the decisive grounds, unresolved matters and conditions that change its use. Let the receiver perform the intended interpretation or next action, rather than merely approve the meeting summary.

When a proposed explanation will be used under varying conditions, try a change that could affect its warrant. If a test window disappears, which claims and proposed decisions lose their basis? If the population, interface or load changes, which earlier findings still apply? Follow that connection. An existing argument that covers the variation can answer directly. For a decision confined to this occasion, return the sufficient grounds for it.

Finish when the receiving question has a warranted answer and feasible continuation, including a justified stop. If participants repeat views while the connection remains missing, change the construction, obtain the absent competence or return the blocker.

B.5.SD:4.7 - Use AI for substantive construction within its competence

A qualified AI can be the integrator rather than a minute-taker. Give it the receiving question, permitted sources, applicable methods and decision boundary. Require the same usable reasoning and scope that the task needs from any performer. An agent’s fluent synthesis can be examined through its grounds and the receiver’s use; fluency alone supports no technical claim.

If its demonstrated capability covers the subject inference and the effective arrangement permits autonomous action, it may construct and use the answer without a human repeating every step. If independence, access or a reserved decision remains necessary, obtain that contribution. Several agents derived from the same mistaken source do not automatically supply independent evidence.

Cheap computation can justify exploring more alternatives internally. It does not justify sending the receiver a larger unfiltered pile of suggestions. Compare the decision value and burden of presenting a result. Retain the answer that improves the receiving work, together with the limitation needed for its use.

B.5.SD:5 - Archetypal Grounding

B.5.SD:5.1 - Component evidence does not yet support the assembled claim

Suppose a review group needs to decide whether an evidence package supports configuration C7. One module has passed a test in C6; another has a successful report. The facilitator collects both reports and every participant’s concerns. The reviewer still lacks a basis for C7.

The integrator asks the relevant specialist which parameter changed and whether the old observation covers its effect. The specialist identifies an interface interaction outside the old test conditions. The discussion now has a missing relation: the individual results do not establish the joint behaviour under C7’s load.

The participants construct three continuations. They could test the joint configuration, narrow the acceptance claim to the already supported use, or redesign the interface so the earlier evidence becomes applicable under justified conditions. A qualified engineer supplies the required model and test judgement. The lab can provide a window for the first option, and the decision maker accepts the inquiry cost.

The reviewer can now answer the question about the evidence in hand. It supports the reported component results under their test conditions and leaves C7’s joint behaviour under load open. The accepted inquiry specifies which interaction to observe in C7, under what load, and how the outcome would bear on acceptance. Commissioning the test settles the plan for obtaining that evidence.

Now remove the lab window. The account exposes the dependent test and decision. The group revisits the narrower claim, another provider or a later release; it does not preserve an unavailable test by leaving it in the minutes. The component results remain useful for the claims they support.

Suppose instead that a C6 result had established the required joint behaviour. A qualified comparison showing that C7 preserves the configuration and conditions on which that result depends can settle the review from existing evidence. A comparison covering only the tested module settles the transfer of that module’s result.

B.5.SD:5.2 - A community disagrees over an explanatory article

Independent practitioners are writing an article to help volunteer coordinators choose a model for staffing decisions. One proposes adding the hours each volunteer offers. Another objects that a total can hide who is available together. The group needs a way for readers to decide when each matters.

The facilitator asks what the reader has to settle. To report the total hours pledged by distinct volunteers, the coordinator can add their hours for the same period. To promise a two-hour repair clinic, the coordinator needs a receptionist and a technician together. Keep the total at six hours. If both are available from 9 to 12, they can cover a clinic from 9 to 11. If only the receptionist is there from 9 to 12 and the technician from 12 to 15, they cannot. The first comparison explains what the total preserves. The two schedules expose what it loses for the joint service.

The revised article asks the coordinator to start with the work being promised. Who must do what, and which performances have to coincide? Could the same summary allow one arrangement in which the promise can be kept and another in which it fails? For the clinic, a confirmed common slot with both required roles can answer the question directly. Full individual calendars are one way to establish that slot. A reader counting pledged hours can use the sum. The discussion has given readers a way to choose the distinction their own model needs.

A contributor may accept that explanation and decline further editorial work. LDR.2 handles the commitment if it matters.

If the group lacks the modelling competence needed to assess the two cases, it returns the question to a qualified practitioner. A well-facilitated consensus would not fill the gap.

B.5.SD:6 - Bias-Annotation

Lenses: Governance, Architecture, Ontology/Epistemology, Pragmatics and Didactics. Scope: Discussions that promise a substantive result for a named receiving use.

The method favours connected reasoning and can undervalue early exploration if applied as premature closure. Preserve exploratory contributions while the question is being formed; require a warranted answer only at the point of reliance. Do not dismiss an objection because it is expressed awkwardly, or privilege a confident human or AI voice over the relevant grounds.

B.5.SD:7 - Conformance Checklist

A conforming use makes clear:

  • who needs which answer and what adequate completion permits;
  • which subject operations and capable performers produce it;
  • how the decisive claims, evidence, conditions and conclusions connect;
  • how a consequential objection changes the answer or remains unresolved;
  • why further inquiry is worthwhile and feasible when selected;
  • what the receiver can use now and what reopens after a changed premise.

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

Invited mistakeBetter action
Count speaking turns or completed canvas boxes as the answer.Trace the receiving conclusion through the reasoning.
Treat all facilitators as content-free moderators.Establish the capabilities the facilitator supplies; obtain another contribution only where needed.
Treat agreement as evidence for a subject claim.Use the corresponding professional inference or inquiry.
Generalize from separately successful components.Examine the interaction and conditions on which whole-use depends.
Add more sources or AI agents without filling the missing relation.Name the absent construction and obtain the contribution that performs it.

B.5.SD:9 - Consequences

The receiver obtains an explanation or proposal that can be examined and changed without reconstructing the whole meeting. Uncertainty is located where it matters, and useful earlier findings survive a changed condition.

This requires subject competence and integration work. It may reveal that the group cannot yet produce the intended answer. Participation methods remain important, but their value is assessed with the substantive result they are meant to help obtain.

B.5.SD:10 - Rationale

The method makes the connection between contributions a working object. Examining the receiving inference and a changed condition exposes the operation still missing. This lets a group obtain the right expert, narrower claim or inquiry instead of repeating an ineffective meeting form.

B.5.SD:11 - SoTA-Echoing

The practice question is how a discussion produces a usable substantive result. The selected line combines competent facilitation with explicit subject construction and a receiving-use test. The alternative is professional facilitation that already supplies both. Retain that adequate arrangement. Use this pattern when the integration operation is missing.

Adopt the distinction from the IAF Core Competencies, revised 2021: facilitation includes helping a group obtain useful outcomes, inquire into underlying issues and select suitable methods, while respecting professional boundaries. Adapt the contribution in sections 4.2–4.6 by making the subject inference, receiver and consequential variation explicit.

The practitioner essay the author’s essay on facilitators (2020) provides a critical case of orderly communication substituting for connected thought. Adopt its distinction between constructing a connected model and checking whether important concerns have been considered and related. Adapt that distinction in 4.3. Assess subject competence independently of the professional title, and examine the construction’s reasoning rather than relying on checklist completion. A competent facilitator can also perform subject integration. The essay is conceptual criticism, not comparative effectiveness evidence.

Against a meeting that already produces the required answer, no additional procedure is selected. Against a missing relation, the additional subject work is justified by the receiving use; its cost is made explicit. Reopen if the answer is adequate, if an unexamined condition defeats the result, or if another construction supplies the same warrant with less burden.

B.5.RA supplies argument recovery and examination, including reasoning expressed in dialogue; B.5.RR supplies revision after a premise or question changes. C.39 supplies development of a missing obtaining operation or connection. These are sufficient returns when they answer the whole question. This Method retains the different joint-construction question: how capable contributors produce one usable substantive answer, route objections to the needed work and return that answer through its receiving use.

B.5.SD:12 - Relations

LDR.1 obtains capable participants and the conditions for their contributions. LDR.2 settles incompatible commitments exposed by the answer. LDR.4 uses the answer to prepare a proposal and first use.

B.5.RA recovers and examines the relevant argument; B.5.RR revises the affected reasoning after a changed premise or question. Their results supply the argument contributions used in sections 4.3 and 4.5.

FPF C.39 supplies the general development of a way to obtain a result when an operation or connection is missing. C.11.DUA appraises the further inquiry and its receiving value. C.28 supplies causal reasoning when the intended conclusion is causal.

The subject practice supplies the needed Method and its applicability conditions. Engineering configuration, strategy, human learning and corporate decisions retain their different methods and acceptance conditions. C.41.OF may supply an execution aid.

When this work is a decision-support inquiry, PSDA.12 recovers participants and attributed concerns and PSDA.13 establishes professional inquiry and dissent conditions. Other practices retain their participation and authority requirements. PSDA.1–9 supply formulation, model and decision-analysis constructions when their question is live. A sound analytical answer and consent to use or act on it remain separate results.

B.5.SD:End