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

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:00:10 UTC

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 capability, functioning, or transformation-flow facts, established under their subject patterns, raise a B.2 whole-reidentification question.

The first useful question is whether those facts can be explained by the existing whole. If that explanation is sufficient for the receiving use, retain the whole; use the pattern for any remaining capability, functioning, transformation, Method, Work, module, characteristic, or architecture question. Use B.2 for a remaining consequential whole-reidentification 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. Name the existing whole and its identity or reidentification rule.
  2. Identify each capability envelope, obtaining functioning relation, or selected in-life transformation-flow structure under its subject pattern. Keep method, method description, work plan, work occurrence, module allocation, characteristic, and architecture facts separate when they are current.
  3. State the 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.
  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.

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.

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-1B.2.4 is used only when capability, functioning, or selected in-life transformation-flow facts leave a B.2 whole-reidentification question after subject-pattern explanations are tested.
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-4Method, method description, work plan, and work occurrence remain separate.
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

Referenced in the corpus

15 literal mentions in other sections. Read their context to establish the relation.