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

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

B.2.4:0 - Use This When

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

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

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

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

Not this pattern when.

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

B.2.4:1 - Problem Frame

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

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

B.2.4:2 - Problem

Without this specialization:

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

B.2.4:3 - Forces

Force	Tension
Capability facts vs whole identity	Exact capability 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 relation	Functioning often crosses parts and bearers; it is not parthood by wording.
Transformation-flow structure vs mathematical description	Flow 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 work	A 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 improvement	The pattern must preserve real novelty without turning every improvement into MHT.

B.2.4:4 - Solution

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

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

Name the exact existing whole and its direct identity or reidentification rule.
Identify each exact capability envelope, obtaining functioning relation, or selected in-life transformation-flow structure under its subject pattern. Keep method, method description, work plan, work occurrence, module allocation, characteristic, and architecture facts separate when they are current.
State the exact claim made about those facts. Name evidence or measurement only as a separate relation that supports, challenges, or leaves that claim unresolved.
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 a residual whole-reidentification question remains, use B.2 for it. B.2 then identifies one exact candidate new whole, applies the complete A.1 and kind-specific criteria, and compares that candidate with the existing whole.

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

B.2.4:4.2 - Subject-Pattern Test

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

Exact fact or claim under concern	Subject pattern if sufficient	B.2.4 remains current only when
Capability envelope	`A.2.2` for the capability of an exact System holder, `C.16` for measured characteristics; `A.10` only for evidence use	the exact envelope and holder facts leave a candidate-whole question that the existing whole cannot explain
Function or functioning relation	`A.6.F` recovers the exact claim and its direct subject pattern; `A.3.4` for an actual transformation and `C.16` for a measured characteristic	the obtaining relation and whole-level facts leave a residual new-whole question
Transformation-flow structure	`E.18` for the selected structure, `A.3.4` for actual transformations, `C.30.TFS-REL` for bounded architecture use; `C.29` only for a mathematical representation use	the selected in-life structure changes which whole can carry the current claim
Method relation or method family	`A.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 direct pattern for any separately claimed family relation and `C.29` only when a lens is used	the exact method facts change the whole, not merely the way of doing
Method description or procedure text	`A.3.2` and `C.2.1` distinguish the MethodDescription and its episteme identity; use `E.17` or `E.24.PUB` for a current publication occurrence, form, or carrier, `C.2.P` for unresolved source-expression or source-to-use wording, and `A.10` or `G.6` only when evidence provenance is relied on	an in-life whole-reidentification question remains after the description is separated
Work plan or work occurrence	`A.15.2`, `A.15.1`	exact planned or performed work facts leave a new-whole question; the plan or occurrence is not the whole by label
Module, component, or bearer allocation	The direct allocation or parthood pattern; `A.6.M` for unresolved module/interface wording; `C.30`, `A.22` or `C.30.ASV` only for the corresponding claim	exact allocation and architecture facts defeat the existing-whole explanation
Metric, score, threshold, robustness, or quality claim	`C.16`, `A.19`; `A.10` only for evidence use	the underlying characteristic facts, not the score or support record alone, defeat that explanation

B.2.4:4.3 - Existing-Whole Explanation

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

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

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

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

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

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

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

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

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

B.2.4:5.1 - Production Cell Capability

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

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

B.2.4:5.2 - CI/CD Capability

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

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

B.2.4:5.3 - Theory Explains New Phenomena

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

B.2.4:5.4 - Bias-Annotation

Bias risk	Failure	Mitigation
Capability as emergence	A new capability label or supporting report declares a new whole.	Recover the exact capability facts and direct pattern, separate their evidence, and perform B.2’s ordinary existing-whole comparison.
Function as part	A function block or functioning relation becomes physical or organizational parthood.	Separate functioning relation, bearer allocation, selected structure, and part-whole claims.
Method chain as whole	A 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 structure	A diagram or graph is treated as the in-life transformation-flow structure.	Use the mathematical, description, publication, and selected-structure patterns before B.2.
Metric jump as MHT	A benchmark, KPI, robustness, or threshold gain declares whole reidentification.	Use C.16, A.19, A.10, and B.2 existing-whole explanation before MHT.

B.2.4:6 - Conformance Checklist

Check	Requirement
`CC-B2.4-1`	B.2.4 is used only when exact 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-2`	Ordinary capability, function, functioning, transformation, method, work, module, characteristic, evidence, and architecture claims return to subject patterns.
`CC-B2.4-3`	No generic `U.Emergence`, `U.Function`, `U.MetaMethod`, or capability-root kind is created.
`CC-B2.4-4`	Method, method description, work plan, and work occurrence remain separate.
`CC-B2.4-5`	Mathematical or publication descriptions of transformation-flow structure do not replace the in-life structure.
`CC-B2.4-6`	If B.2 remains current, it handles the one exact candidate new whole, complete recognition, whole comparison, and any optional record; B.2.4 introduces no result species.

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

Anti-pattern	Symptom	Repair
Capability by declaration	A leader names a new capability, but the exact capability facts remain component-level or unknown.	Use A.2.2 for the capability facts, C.16 for their measured characteristics, and A.10 for support; use B.2 only if the existing-whole explanation fails.
Function as part	A function block is treated as a physical or organizational part.	Use A.6.F for function-like wording, E.18 for transformation-flow structure and C.30.TFS-REL for its bounded architecture use, A.6.M for module wording, and C.30, A.22, or C.30.ASV for the current architecture, selected structure, or structural-view claim.
Method chain as whole	A sequence of methods is called a new holon.	Recover the exact method relation and any current work occurrence; use B.2 only when a result holon is current.
Diagram as flow structure	A diagram or graph is treated as the transformation-flow structure itself.	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 whole	A KPI improves and MHT is declared.	Use C.16, A.10, and existing-whole explanation first.

B.2.4:8 - Consequences

Positive consequences:

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

Costs:

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

B.2.4:9 - Rationale

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

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

B.2.4:10 - SoTA-Echoing

Source line	Practical implication for this pattern
Capability and functioning approaches	An A.2.2 capability envelope states what its named System holder can do under conditions; it is not automatically a new whole. Evidence supports or challenges the claim about the envelope but does not create it.
Functional architecture and transformation-flow practice	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 and work ontology in FPF	Method, method description, work plan, and performed work occurrence must stay separate when capability evidence is interpreted.
TAME and agency-as-characteristic-space work	Agency-like evidence is multi-characteristic and thresholded by concern; B.2.4 does not create a binary agency kind.

B.2.4:11 - Relations

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