B.2.2:0 - Use This When

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

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

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

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

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

Not this pattern when.

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