#Advanced Mereology: Components, Portions, Aspects & Phases

A.14 · Stable · Kernel mereology and part-whole relation discipline pattern · Part A - Kernel Architecture 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: Kernel mereology and part-whole relation discipline pattern Status: Stable

At a glance. Use A.14 when a part-whole claim must distinguish component, member, portion, aspect, or phase before downstream architecture, work, assurance, or U-kind admission relies on that claim.

Use this when. Use this pattern when a text says that something is part of something else, a collection member, some amount of the same stuff, an aspect of one holon, or the same holon during a time interval, and a wrong relation kind would change identity, aggregation, responsibility, evidence, or structural grounding.

What goes wrong if missed. Teams count members as components, portions as components, aspects as separate wholes, or phases as separate objects; constructive traces and Working-Model relation claims then ground the wrong EntityOfConcern.

What this buys. One human-facing mereology catalogue that lets B.3.5 and C.13 ground structural claims without inventing a new public relation vocabulary.

Not this pattern when. Not this pattern when the current question is only a constructive trace (C.13), Working-Model assurance grounding (B.3.5), meta-holon transition (B.2), temporal dynamics without a phase-of claim, or a general U-kind admission question (E.24.UK).

FPF’s holonic modelling relies on part–whole relations to build structural and conceptual holarchies for admitted holons such as systems, epistemes, work occurrences, bounded contexts, disciplines, and methods. But U.Holon is not a synonym for every bounded object. U.Role is a governed root U-kind, not an admitted holon kind. U.Method is a non-agentive holon kind, but submethod assembly is owned by method-composition patterns, not by A.14 structural component mereology. Role relation structures, method relation structures, method descriptions, work plans, and work occurrences enter A.14 only through their direct governing patterns and admitted carriers. Early drafts distinguished structural vs. conceptual parthood (e.g., ComponentOf, ConstituentOf) but practical modelling kept hitting two recurrent gaps:

#Keywords

• mereology
• part-of
• ComponentOf
• PortionOf
• PhaseOf
• composition.

#Relations

#Content

#Problem frame - why an advanced mereology?

FPF’s holonic modelling relies on part–whole relations to build structural and conceptual holarchies for admitted holons such as systems, epistemes, work occurrences, bounded contexts, disciplines, and methods. But U.Holon is not a synonym for every bounded object. U.Role is a governed root U-kind, not an admitted holon kind. U.Method is a non-agentive holon kind, but submethod assembly is owned by method-composition patterns, not by A.14 structural component mereology. Role relation structures, method relation structures, method descriptions, work plans, and work occurrences enter A.14 only through their direct governing patterns and admitted carriers. Early drafts distinguished structural vs. conceptual parthood (e.g., ComponentOf, ConstituentOf) but practical modelling kept hitting two recurrent gaps:

1. Quantities vs. parts. Engineers routinely need “some of the fuel”, “the first 10 pages”, “a 30% subset of data”. This is not a component; it is a portion of a stuff‑like whole, governed by measures and conservation.

2. Change vs. replacement. “The prototype before calibration” may be a proper temporal restriction of one unchanged pump. By contrast, “v2 of the spec” first opens C.2.1 identity and, for two different epistemes, its independent edition-continuity test; “shift 1 vs. shift 2” first opens A.15.1 Work-part or occurrence law. None of those labels selects PhaseOf by itself.

This section introduces two normative sub‑relations of partOf that close those gaps and lock them to the rest of the kernel:

• PortionOf — metrical, measure‑preserving parthood of stuffs and other measurables.
• PhaseOf — temporal parthood of the same carrier across an interval.

It also restates guard‑rails that keep role values outside holon mereology and keep method values outside A.14 structural component mereology, while allowing method holarchy through method owners such as A.3.1 and B.1.5. Describing epistemes such as U.MethodDescription and U.WorkPlan keep their C.2.1 identity: content or publication-unit inclusion may use ordinary episteme parthood, a proper interval of one unchanged episteme may use PhaseOf, and changed C.2.1 identity discriminators identify another episteme whose historical continuation is tested separately through EpistemeEditionRelation. It also clarifies how MemberOf fits: membership and collection-as-whole grounding start with A.14, C.13, and B.3.5 as appropriate; acting collective systems require U.System admission plus role, method, work, and evidence owners; whole reidentification uses B.2 only when existing-whole explanations fail.

Publication note (Working-Model first). Read A.14 together with E.14 Human-Centric Working-Model and B.3.5 CT2R-LOG: publish the direct relation claim in the Working-Model layer and, when assurance is sought for a structural claim, link that assertion downward to one current C.2.1 construction-trace episteme in the Compose-CAL Γ_m sum, set, or slice form. The trace reports exact participants, direct relation occurrences, the applicable construction rule, and identity or reidentification conditions. It creates none of them; order and time remain outside mereology.

#Problem — what breaks without these distinctions?

If we only have “generic partOf” (plus Component/Constituent), four classes of errors appear:

1. Conservation errors. Treating “20 L of fuel from Tank A” as a component leads to nonsense: adding and removing such “components” does not respect quantities; Γ_sys proofs violate Σ‑balance.

2. Temporal smearing. Flattening “before/after” for one enduring carrier into a timeless whole collapses history; treating two changed epistemes or two Work occurrences as temporal pieces of that carrier collapses identity and occurrence history. Γ_time and Γ_method cannot repair either mistake after the fact.

3. Identity confusion. Modelling a “new version” as a component or phase lets a label decide identity. For an episteme, C.2.1 first decides whether the identity triple is unchanged and tests edition continuity separately; for another enduring holon, its direct identity owner decides whether the same individual persists or a reidentification question opens.

4. Role leakage. Functional/organisational roles sneak into part trees (“the PumpRole is part of the plant”), violating A.15 and making structural reasoning brittle.

#Forces

#Solution — extend the mereology catalogue, keep it clean

A.14 defines two additional sub‑relations of partOf and re‑affirms the firewall between mereology and the role/recipe layer:

1. PortionOf — for measured parts of a whole (stuffs and other extensives).
2. PhaseOf — for temporal parts of the same carrier.
3. No role values in holon mereology; no method values in structural component mereology. U.Role is not an admitted holon kind. U.Method is a method holon, but its submethod assembly is governed by method-composition owners, not by A.14 ComponentOf or structural partOf. A U.MethodDescription is an Episteme: C.2.1 governs its identity and any distinct-edition relation, while A.14 can govern its content parthood or a proper temporal restriction of the unchanged episteme. U.Work parts and occurrence boundaries use A.15.1 relations rather than generic A.14 phasing; neither case replaces method holarchy.
4. MemberOf stays, but collection identity and acting-collective claims use direct owners. MemberOf remains available to state exact collection-membership occurrences. After the collection, its identity rule, and those memberships are independently grounded, Γ_m.set may narrate their construction account and B.3.5 may link that account when publication assurance is current. Neither the gathering narrative nor its trace creates a membership. An acting collective system uses U.System admission plus role, method, work, and evidence owners. Whole reidentification uses B.2 only when existing-whole explanations fail.

The classical pair ComponentOf (structural, discrete) and ConstituentOf (conceptual, logical/epistemic) remain as in the kernel; A.14 only clarifies how to tell them apart from Portion/Phase (§ 6).

#Formal cores (normative semantics)

#PortionOf — metrical part of a measurable whole

Intent. Capture “some of the same stuff/extent”, governed by a measure that adds up.

Applicability. Any U.Holon that carries an extensive measure μ on the chosen scope (examples: mass, volume, length‑of‑text, byte size, wall‑time budget).

Primitive. PortionOf(x, y) means: x is the same kind of stuff/content as y, but less.

Axioms (A14‑POR‑*)

• POR‑1 (Partial order). PortionOf is reflexive, antisymmetric, transitive on its domain.
• POR‑2 (Metrical dominance). If x ProperPortionOf y then 0 < μ(x) < μ(y) for the agreed μ.
• POR‑3 (Additivity on disjoint portions). If x ⟂ y (no overlap) and both PortionOf y, then μ(x ⊔ y) = μ(x)+μ(y) and x ⊔ y PortionOf y.
• POR‑4 (Kind integrity). x and y must share the same measure kind and unit (or a declared conversion).
• POR‑5 (Boundary compatibility). For physical wholes, the whole’s boundary encloses the union of its portions; cross‑boundary “leaks” are interactions, not portions.

Didactic tests. ✔ “5 kg from a 20 kg billet” — PortionOf. ✔ “Pages 1–10 of the report” — PortionOf (μ = page or token count). ✘ “The pump module of the plant” — ComponentOf, not PortionOf. ✘ “The Methods section of the paper” — ConstituentOf, not PortionOf.

#PhaseOf — temporal part of the same carrier

Intent. Capture “the same holon during a sub‑interval”, preserving identity through change.

Applicability. Any U.Holon that persists across time with a recognised carrier identity.

Primitive. PhaseOf(x, y) means: x is y restricted to a proper time interval.

Axioms (A14‑PHA‑*)

• PHA‑1 (Strict partial order). PhaseOf is irreflexive, asymmetric, and transitive on proper temporal restrictions of one unchanged carrier. In particular, PhaseOf(y,y) is false: a whole-lifetime or self-reference is not a proper temporal part.
• PHA‑2 (Coverage). The whole is the union of its maximal, non‑overlapping phases over its lifetime interval.
• PHA‑3 (No paradoxical overlap). Phases of the same carrier do not overlap in time; overlapping variants require PhaseOf on aspects or different carriers.
• PHA‑4 (Identity through change). Properties may vary between phases, but the carrier’s identity criteria hold continuously (e.g., same serial number, same legal identity, same theorem statement).
• PHA‑5 (Escalation to MHT). If identity criteria break (e.g., metamorphosis with new objectives), declare a Meta‑Holon Transition (B.2) rather than a PhaseOf.

Didactic tests. ✔ “PumpUnit#3 before calibration” — PhaseOf(Pump#3_pre, Pump#3). ✔ “Specification episteme E during τ₂”, with the C.2.1 identity triple unchanged and a proper interval current — PhaseOf(E@τ₂, E). ✘ “Spec v2” — if a C.2.1 discriminator changed, identify another episteme and test EpistemeEditionRelation(E_v1,E_v2) separately; the label proves neither identity nor continuity. ✘ “Shift 1 of the same batch run” — use A.15.1 TemporalPartOf_work, EpisodeOf_work, OperationalPartOf_work, or another exact Work-part or occurrence relation whose predicate obtains. ✘ “Prototype vs. production unit” — likely different carriers; use ComponentOf/ConstituentOf or MHT per criteria.

#CT2R‑LOG & Compose‑CAL handshake (normative link)

• A structural relation claim published in the Working-Model layer SHALL, when assurance is required, link through tv:groundedBy to one current C.2.1 construction-trace episteme in the Γ_m.sum | Γ_m.set | Γ_m.slice form (see B.3.5 and C.13). The direct relation pattern decides whether the occurrence obtains and how it is identified; the candidate's direct identity or reidentification rule decides continuity. The trace only reports that basis.
• PhaseOf is temporal parthood; it SHALL NOT be grounded through Γ_m. Its assurance follows identity-through-time criteria (CC-PHA-1..3) and Γ_time ordering (B.1.4).
• MemberOf remains non-mereological (CC-MEM-2). A set trace is truthful only after one exact collection, its identity rule, and the exact direct membership occurrences are grounded; no ComponentOf inference follows.

Two quick identity tests apply before relying on a trace. The same listed constituents can form a different whole when their direct assembly relations or rule differ. Conversely, a permitted constituent replacement can preserve the same whole. An equal input list, a repeated trace, or validationMode=axiomatic decides neither case.

#Choosing the right relation (decision table)

Firewall reminder. If your sentence is about who does what, how it is done, or what happened when (role, method, or run), use the direct A.15/A.15.1 owner. For an episteme, A.14 may govern content parthood or a proper interval of one unchanged C.2.1 identity; changed claims, EntityOfConcern, or effective reference scheme identify another episteme, and any historical continuation uses C.2.1 EpistemeEditionRelation only when its predicate obtains.

#Archetypal Grounding

#Bias-Annotation

A.14 corrects parthood bias: ordinary words such as part, member, phase, aspect, section, version, module, function, role, and ingredient can all sound like "part of" while naming different relation kinds. The repair is not a larger part tree. Recover the EntityOfConcern and choose the relation kind: component, constituent, portion, phase, member, role assignment, method description, work occurrence, evidence relation, or transformation relation.

It also corrects representation bias. A BoM row, figure, graph edge, table row, document section, dashboard item, or architecture view may publish a part-whole claim, but the publication form is not the part-whole relation itself. The live A.14 claim is about the relation between holons, epistemes, carriers, portions, phases, or collection members, with mathematical or publication descriptions kept in their own slots.

#Conformance Checklist - type guards

#Global firewall and scope

#PortionOf guards

#PhaseOf guards

#Grounding and validation (normative)

Note. Property names and trace semantics are defined in the CT2R‑LOG / Compose‑CAL.

#MemberOf minimal semantics (non‑mereological)

#CT2R‑LOG handshake (Working‑Model → Assurance)

#Relation-use decision procedure

Step 0 — Firewall check. If your sentence is about who does what, how it is done (role or method), or what happened when (run or work occurrence), you are not in A.14 merely because ordinary speech names a thing. Use the role, method, work, or evidence owner. For an episteme, A.14 may participate in content parthood or a proper temporal restriction of one unchanged C.2.1 identity. Changed episteme content, EntityOfConcern, or effective reference scheme opens another episteme and the separate C.2.1 edition-continuity test; a dated Work part stays under A.15.1.

Step 1 — Is it measured stuff? If yes, pick PortionOf. Confirm μ is declared (CC‑POR‑1/2). Test additivity on a toy split (CC‑POR‑3). If flows cross a boundary, remodel as interactions, not portions (CC‑POR‑4).

Step 2 — Is it a discrete inside part? If yes, pick ComponentOf (physical) or ConstituentOf (conceptual). Do not use PortionOf here.

Step 3 — Is it the same carrier restricted to a proper time slice? If yes, pick PhaseOf. Verify that the proposed part is not the whole carrier, its interval is a proper sub-interval, and identity and non-overlap conditions hold (CC‑PHA‑1/2/3). A whole-lifetime or self-reference needs no phase object. If identity criteria break, escalate to B.2 (CC‑PHA‑4).

Step 4 — Is it a membership statement? Use MemberOf only; avoid any part‑inferences (CC‑MEM‑2). If you need a collection as a whole, use C.13 (Γ_m.set) and B.3.5 when assurance grounding is current. If you need collective action, first admit an acting collective U.System, then use the role, method, work, and evidence owners.

Quick spot-tests.

#Interplay with Γ‑flavours (how these relations behave under aggregation)

#Common Anti-Patterns and How to Avoid Them

• Member as component. A person, team, document, or object belongs to a collection and is then counted as if it were structurally integrated into the whole.
• Role as part. A system plays a role, and the role label is placed inside a part tree.
• Method as part. A method value, recipe, or algorithm is treated as a component instead of using method, method-description, work, or transformation owners.
• Portion without measure. Some amount of fuel, data, time, or text is named as a portion without a measure kind, unit, and additivity condition.
• Phase as replacement or lineage. A proper restriction of one enduring carrier is treated as another component, or a changed episteme, version label, or Work segment is treated as PhaseOf without applying C.2.1 or A.15.1 first.
• Diagram or trace as relation. A visual breakdown, graph, table, construction trace, or validationMode is used as proof that parthood obtains or that the whole has one fixed identity. Recover the direct relation occurrence and the candidate's identity or reidentification rule first; use the publication and trace only as inspectable accounts.

#Pedagogy aids (non-normative)

Two‑minute checklist for practitioners

1. Do I see "process", "procedure", "policy", or "script" used to mean enactment? — then A.15/A.15.1. If it names an episteme, use A.14 only for its content parthood or a proper interval of the unchanged C.2.1 identity; use C.2.1 for another episteme and any edition-continuity claim.
2. Does every PortionOf have a declared μ and unit?
3. Do phases cover a lifetime without overlap for the same aspect?
4. Are any roles/recipes appearing as parts? If yes, stop and refactor.

#Consequences

Benefits

• Predictable composition. Σ‑additivity for portions and identity‑through‑time for phases make Γ‑proofs straightforward.
• History without confusion. Temporal slicing is explicit and audit‑ready; no paradoxical overlaps.
• Cleaner integration with roles and recipes. The firewall prevents “functional object” creep into structure.
• Compatibility with engineering practice. Mirrors product breakdown (components) vs functional breakdown (roles) vs material stocks (portions) vs proper temporal restrictions of one enduring carrier (phases), while leaving episteme editions and Work segmentation to their direct owners.

Trade‑offs / mitigations

• Modelling energy. Authors must pick μ and declare units; provide a short μ‑catalog per project.
• More relation names. Two extra sub‑relations increase vocabulary; mitigated by the decision table (§ 6) and spot‑tests (§ 9).
• Escalation discipline. Deciding PhaseOf vs MHT requires judgement; A.14 provides criteria, and B.2 captures true re‑identification.

#Rationale

A.14 exists because part-whole words carry identity, aggregation, measure, time, and assurance commitments. The pattern keeps those commitments in the relation kind instead of letting everyday nouns, diagrams, or breakdown tables decide ontology. Component, constituent, portion, phase, and member claims can then support holon, episteme, architecture, and evidence work without smuggling role, method, work, or publication claims into mereology.

#SoTA-Echoing

• Metrical mereology advances (e.g., recent work on quantity‑based parthood and additivity) motivate PortionOf with explicit μ and Σ‑laws, preventing the classic “stuff as components” fallacy.
• Temporal parts & identity through change (renewed treatments in analytic metaphysics and formal ontology) motivate PhaseOf with coverage/non‑overlap and escalation when identity criteria fail.
• Engineering ontologies (BORO lineage, Core Constructional practice, ISO 15926 family) keep a strict separation between functional breakdowns (our Roles) and product breakdowns (our Components), with stock/consumable modelling (our Portions) handled by quantities, not by component trees.
• Knowledge-episteme edition histories in contemporary MBSE and open-science practice motivate explicit endpoint identities and provenance-preserving composition. FPF uses the C.2.1 identity triple and independently obtaining EpistemeEditionRelation for distinct editions; A.14 retains PhaseOf only for a proper temporal restriction of one unchanged episteme.
• The net effect is a minimal‑sufficient catalogue: two added sub‑relations close real modelling gaps while preserving parsimony, didactic clarity, and Γ‑compatibility across domains.

#Relations

• Builds on: A.1, A.7, B.1, B.2, C.13, and B.3.5 for holon identity, strict distinction, gamma-flavour separation, meta-holon transition, constructive grounding, and Working-Model assurance.
• Coordinates with: A.15, A.15.1, A.3.1, A.3.2, and A.3.4 when the source wording is about role assignment, method, work, or transformation rather than parthood.
• Used by: architecture, description, evidence, and U-kind admission patterns when their structural claim depends on a clean parthood relation.

#A.14:End

---

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