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

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.

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

No cue is enough. Each row points to facts and claims to inspect; B.2’s existing-whole/new-whole comparison, A.1 recognition, and the system-kind criterion decide the result.

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.

The old drone evidence remains relevant, but it is not enough for the swarm-level assurance claim.

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.

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 has already left a whole-reidentification question before B.2.2 is used.
CC-B2.2-2A positive system-result claim requires B.2’s candidate new whole to pass the A.1 criterion and the U.System criterion. 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

Referenced in the corpus

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