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 21:50:06 UTC

B.2.2:0 - Use This When

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

First useful move. Test the candidate against A.1’s six common components. Then test whether it is physically embodied and has an organization that makes it eligible to act in work or transformation while preserving its identity—the U.System criterion.

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 to recover the whole-reidentification question and identify the candidate new whole. Use B.2.2 when that candidate is to be tested under the already admitted U.System kind, then return its recognition result to B.2’s comparison.

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.