#Holon Aggregation and Part-Whole Construction

B.1 · Stable · Part B holonic construction pattern · Normative unless a section is explicitly informative · Part B - Trans-disciplinary Reasoning Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

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

Use this pattern when a project needs to say how several admitted objects are considered as a whole, or when a whole-level claim depends on parts, membership, component structure, constructional grounding, or a selected aggregation rule.

#Relations

#Content

#Use This When

Use this pattern when a project needs to say how several admitted objects are considered as a whole, or when a whole-level claim depends on parts, membership, component structure, constructional grounding, or a selected aggregation rule.

Typical moments:

• a product, plant, dataset, paper, model family, organization, fleet, batch, or research program is discussed as a whole;
• a dashboard rolls part measurements into a whole-level characteristic;
• a team says that a method, role, graph, or algebra "decomposes" something and may be smuggling part-whole claims;
• a collection needs whole-level characteristics without becoming an acting collective system;
• an aggregation claim is being used for architecture, assurance, evidence, or MHT reasoning.

First useful move. Recover the claim kind before choosing notation: part-whole construction, membership, collection-as-whole grounding, role relation structure, method relation structure, work occurrence holarchy, selected architecture structure, or mathematical description.

What goes wrong if missed. Γ, graph, algebra, decomposition, factor, component, step, phase, and collection wording become one universal composition language. Roles and methods become parts; work occurrence evidence is inferred from method structure; a graph is mistaken for the structure; a collection becomes an acting whole by label.

What this buys. B.1 gives one doorway into part-whole construction while keeping its neighbors clean: A.14 owns relation vocabulary, C.13 owns constructional grounding, B.3.5 owns Working-Model assurance grounding, A.15.1 owns work-occurrence holarchy, and C.29 owns mathematical-lens use.

Not this pattern when.

• If the question is the local relation word, use A.14.
• If the question is constructive part-whole grounding, use C.13.
• If the question is assurance grounding for a working model, use B.3.5.
• If the question is role or method relation structure, use the role or method owner and C.29 when a mathematical lens is relied on for the current claim.
• If the question is performed-work occurrence parts, use A.15.1.
• If the question is whole reidentification or emergence-family wording, use B.2 or B.2.P.

#Problem Frame

B.1 is not a universal algebra pattern. It is the holonic construction doorway for part-whole and collection-as-whole claims.

The older Γ material remains useful only after the ontology-side claim has been recovered. Γ, graph, algebra, tuple, matrix, embedding, and neural representation can express or check a selected structure; they do not decide by spelling that the current object is a holon, that the relation is parthood, or that a role, method, step, or work occurrence is a part of a holon.

#Problem

Without B.1:

1. Mereology and notation collapse. A graph or algebra is treated as the part-whole structure itself.
2. Roles and methods become parts. Role factors, method parameters, guards, steps, and compositions are read as holonic parts because the same word "decomposition" appears.
3. Work occurrence is inferred from plan. A method decomposition or schedule is treated as evidence that performed work had those parts.
4. Collections become acting systems. A set, list, batch, fleet, or community receives agency, responsibility, or capability without A.1 and role-method-work admission.
5. Emergence becomes rhetoric. A whole-level gain is explained by "synergy" or "more than the sum" without checking existing-whole explanations or B.2 whole reidentification.

#Forces

#Solution

Use B.1 as a discriminator and construction frame.

#Holon Aggregation Claim Frame

When part-whole construction is current, recover:

HolonAggregationClaim@Context:
  candidateWholeRef: U.Holon
  candidatePartRefs:
  boundedContextRef:
  identityOrRecognitionRule:
  partRelationRefs:
  constructionBasisRef?
  selectedStructureRef?
  wholeLevelCharacteristicRefs?
  assuranceGroundingRef?
  neighboringNonPartRelationRefs?
  mathLensOrRepresentationRef?

This is a claim frame, not a U-kind and not an acting record. It says what must be named before the aggregation claim is relied on.

Use:

• [A.14](/generated/patterns/A.14) for ComponentOf, ConstituentOf, PortionOf, PhaseOf, MemberOf, aspect, and related vocabulary;
• [C.13](/generated/patterns/C.13) for constructional grounding such as sum, set, slice, or another accepted construction;
• [B.3.5](/generated/patterns/B.3.5) when a working model relies on the part-whole claim for assurance or evidence;
• [C.16](/generated/patterns/C.16) when the current output is a whole-level characteristic;
• [A.1](/generated/patterns/A.1) and [A.15](/generated/patterns/A.15) when the whole is claimed to be an acting collective system.

#Didactic Firewall

#Work Occurrence Holarchy

Performed work is different from structural composition.

A work occurrence can have temporal parts, episode parts, operational parts, concurrent sub-runs, retries, resource roll-ups, and effect composition. That is a work-occurrence holarchy governed by A.15.1, not evidence that the method or role expression is a holonic part-whole structure.

Use A.15.1 when the claim needs occurrence identity, temporal coverage, Gamma_time, Gamma_work, episode policy, overlap policy, resource aggregation, or performed-work evidence.

#Mathematical And Representation Apparatus

Use Γ, graph, algebra, tuple, matrix, embedding, or neural representation only after the object under concern and selected relation are named.

Acceptable uses:

• a mathematical lens for a selected structure;
• a constructional expression for a part-whole claim already admitted by A.14 and C.13;
• a representation of dependency relations;
• a checking apparatus for invariants or conservative bounds.

Blocked uses:

• graph wording as parthood admission;
• algebraic factorization as role, method, or work parthood admission;
• source notation as a new U-kind;
• one fold rule as a universal replacement for the direct owner.

#Existing-Whole Before MHT

Before declaring B.2 whole reidentification, ask whether the whole-level gain can be explained inside the existing whole:

• better parts;
• corrected part relation;
• improved measurement;
• role or method relation repair;
• work occurrence evidence repair;
• functional or architecture selected-structure repair;
• source, publication, or representation correction.

Use B.2 only when the whole itself must be reidentified.

#Archetypal Grounding (Worked Cases)

#Bias-Annotation

#Evidence Corpus

A corpus can be a collection-as-whole under MemberOf and C.13 set construction. Its whole-level characteristics may include coverage, source freshness, bias exposure, or evidential diversity.

The corpus does not become an acting system. A review board, script, or research team may be an acting system in role. The corpus may be an episteme or publication-side object under direct owners.

#Method With Steps

A machining method has ordered steps and parameters. Those steps are method relation or method-description material. They do not prove that a performed machining run occurred, nor that the run had the same parts.

If the current claim is the method structure, use method owners and C.29 when algebra is selected. If the current claim is the actual run, use A.15.1.

#Bias-Annotation

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

Positive consequences:

• B.1 can still use useful aggregation apparatus without letting apparatus choose the ontology.
• Holonic part-whole claims become reviewable.
• Role, method, work, math-lens, and publication descriptions stop leaking into mereology.
• B.2 has a cleaner entry condition: whole reidentification, not ordinary improvement rhetoric.

Costs:

• Users must identify the claim kind before choosing a notation.
• Some Gamma-heavy examples require a direct owner before the notation is used: work occurrence evidence uses A.15.1, work-resource aggregation uses B.1.6, mathematical-lens reliance uses C.29, and whole reidentification first uses B.2.P and then B.2 when the problem remains current.
• Work occurrence analysis requires evidence and timing, not just a method plan.

#Rationale

The practical force of B.1 is conservative. Whole-level reasoning is useful, but it must be grounded in accepted part-whole relations, constructional discipline, and direct pattern ownership. This lets FPF speak across physical systems, epistemes, work occurrences, bounded contexts, disciplines, and collections without growing a new type for every composed expression.

Mathematical apparatus remains available. It becomes more useful after the governed object is known: graph for dependency representation, algebra for selected composition rules, tuple for slot relation expression, matrix or embedding for analysis, and C.29 when a mathematical lens is relied on for the current claim.

#SoTA-Echoing

#Relations

• Builds on: A.1 for holon admission, A.14 for relation vocabulary, C.13 for constructional grounding, and B.3.5 for Working-Model assurance grounding.
• Coordinates with: A.15 and A.15.1 for method and work, A.22 and C.30 for selected structure and architecture, C.16 for whole-level characteristics, C.29 for mathematical lenses, and B.2 for whole reidentification.
• Refined by: B.1.1, B.1.2, B.1.4, and B.1.6 for selected dependency, system aggregation, contextual-temporal aggregation, and work-resource aggregation cases.

#B.1:End

Last Updated: 2026-08-04 — upstream FPF commit 7ba40a95 (github.com/ailev/FPF)