Part Whole Unity Criterion Design¶
Make the rule for when parts count as one whole explicit, testable, and consequentially bounded.
Unity Test is the accepted target prime for queue position 42: the rule that decides when parts count as one whole rather than many. This draft treats unity testing as a reusable solution archetype for part-whole governance, not as a synonym for union, partition, boundary drawing, or identity matching.
Disposition¶
draft_full_archetype — direct searches of accepted archetypes, pilot accepted gap-fill outputs, variant additions, alias/merge maps, and the component/mechanism index found no existing parent archetype for the unity-test pattern. Prior uploaded-queue outputs cover many algebraic and set-theoretic neighbors, but they do not answer the part-whole question of what relation and threshold make a candidate collection count as one whole.
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A system must count, govern, analyze, merge, preserve, repair, own, or act on a collection of parts, but it has not stated the rule that determines whether those parts are one whole or merely many related items.
Applicability expression5 distinct conditions
groundedpartly groundedopen
5 conditions, all required.
5Required in every casenumbered 1–5
These hold no matter which pattern applies.
Governed composite unit · grounded
Several parts are counted or governed as one unit.
The source archetype describes the situation as follows: A collection of parts is being counted as one unit in a dataset, inventory, legal record, system model, plan, or narrative. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeUnity Test— The rule that decides, in a given system, when a collection of parts counts as one whole rather than many.
Contested wholehood · open
Stakeholders disagree whether the parts compose one whole.
The source archetype describes the situation as follows: Different stakeholders disagree about whether parts compose one system, organization, incident, asset, object, story, or process. The normalized requirement above isolates the load-bearing portion used in this condition set.
Multiple unity relations · grounded
Several candidate relations could compose the parts into a whole.
The source archetype describes the situation as follows: Parts are connected by multiple possible relations, such as proximity, ownership, function, causal coupling, boundary, lineage, membership, or continuity. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeUnity Test— The rule that decides, in a given system, when a collection of parts counts as one whole rather than many.
Criterion-dependent unity · grounded
The same collection can be one whole under one unity criterion and many under another.
The source archetype describes the situation as follows: The same collection could be one whole under one kind of unity and many under another. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeUnity Test— The rule that decides, in a given system, when a collection of parts counts as one whole rather than many.
Nested whole ambiguity · open
Nested or overlapping wholes make boundaries or accountability ambiguous.
The source archetype describes the situation as follows: Nested or overlapping wholes make counts, boundaries, or accountability ambiguous. The normalized requirement above isolates the load-bearing portion used in this condition set.
Other requirements and context (1)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Supporting contextA downstream action depends on one-versus-many status: merge, split, assign responsibility, measure, insure, repair, govern, or archive.
A system must count, govern, analyze, merge, preserve, repair, own, or act on a collection of parts, but it has not stated the rule that determines whether those parts are one whole or merely many related items. In this archetype, the relevant contextual consideration is: A downstream action depends on one-versus-many status: merge, split, assign responsibility, measure, insure, repair, govern, or archive. It helps interpret the situation or strengthens the practical case for examining the archetype.
Coverage
3 of 5 conditions grounded · 2 open.
Boundary note¶
This draft should be reviewed with criteria_of_individuation, identity_test, inclusive_membership_union_design, exhaustive_disjoint_partition_design, shared_subset_intersection_mapping, system_scope_definition, and future vector_space / well_foundedness_well_ordering outputs so the family preserves crisp boundaries among membership, identity, unity, and formal structure.
Common Mechanisms¶
8 documented mechanisms across 5 implementation forms.
The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.
Assessment, Review & Assurance · 3 mechanisms
- Borderline Whole Review Protocol — A review path for the cases the threshold cannot cleanly decide — nested, overlapping, temporary, or right-at-the-line wholes.
- Part Inventory and Granularity Review — Enumerates the candidate parts and fixes the granularity at which they are judged, before any unity relation is applied.
- Wholehood Threshold Test — Applies a stated cutoff to the strength of the binding relation and returns a clean one-whole / many-parts verdict for clear cases.
Control, Automation & Runtime · 1 mechanism
- Unity Reassessment Trigger — Watches declared conditions and reopens a settled unity verdict when parts, relations, or boundaries change enough to threaten it.
Decision, Gate & Allocation · 1 mechanism
- Unity Relation Selection Checklist — Walks the candidate binding relations and picks the one (or few) that could actually make these parts one whole of this kind.
Record, Log & Register · 1 mechanism
- Unity Verdict Decision Log — Records each unity verdict, the evidence behind it, and what it licenses, so one-versus-many status is auditable rather than intuitive.
Representation, Specification & Plan · 2 mechanisms
- Part-Whole Dependency Map — Diagrams the relations and boundaries among candidate parts so the strength and shape of their coupling is visible before any verdict.
- Unity Test Specification Sheet — A reusable design form that declares, for one kind of whole, what is being tested for and what a positive verdict licenses.
Compression statement¶
Part-Whole Unity Criterion Design is the intervention pattern of declaring candidate parts, selecting the relation that could make them one, setting the required threshold, marking boundaries or continuity evidence, and recording what a positive verdict licenses so systems do not silently aggregate heaps into wholes or fragment real wholes into unrelated pieces.
Canonical formula: Whole(P, K) ⇔ R_K(P) meets threshold T_K, where P is the candidate part collection and K is the kind of whole being tested.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Composition: Arranges components into a cohesive whole.
- Criteria of Individuation: The rules a system fixes for what makes something one entity — when parts compose a single whole, when two presentations are the same entity, and which kind supplies a thing's persistence — together constituting its inventory of countable individuals.
- Unity Test: The rule that decides, in a given system, when a collection of parts counts as one whole rather than many.
Also references 23 related abstractions
- Aggregation: Deliberately collapsing many items into a single summary, choosing which information to discard to gain tractability.
- Boundary: Defines system limits.
- Classification: Sorting entities into discrete categories by explicit rules, turning unbounded variation into a finite, reusable map for downstream reasoning and action.
- Complement: Everything in a declared universe that is not in a designated subset.
- Completeness: No gaps in structure.
- Connectedness: A whole that cannot be split into parts with no relation crossing between them.
- Consistency: A set of commitments cannot jointly derive a contradiction.
- Containerization: Wrap a unit with its dependencies behind a standardized exterior so substrate-blind handlers can move it intact.
- Continuity: Smooth change without jumps.
- Disjointness: Two or more populated collections share no element.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Functional Unity Test · domain variant
Boundary Unity Test · boundary variant
Causal Coupling Unity Test · mechanistic variant
Governance Unity Test · institutional variant
Narrative Unity Test · interpretive variant
Editorial Notes¶
Problem Classification¶
Classification: Representation, Classification & Model Misfit → Ontology, Identity, State & Part–Whole Modeling
Problem kernel: no unity rule distinguishes one whole from related parts
Rationale: Earliest causal condition: A system must count, govern, analyze, merge, preserve, repair, own, or act on a collection of parts, but it has not stated the rule that determines whether those parts are one whole or merely many related items.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A system must count, govern, analyze, merge, preserve, repair, own, or act on a collection of parts, but it has not stated the rule that determines whether those parts are one whole or merely many related items. That is a ontology identity state and part whole modeling problem because The representation lacks explicit entities, aspects, states, proposition modes, or unity rules needed to say what exists and what the model is about.
Review outcome: Independent reviewer agreement; high confidence.