Skip to content

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.

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

  • Borderline Whole Review Protocol
  • Part Inventory and Granularity Review
  • Part-Whole Dependency Map
  • Unity Reassessment Trigger
  • Unity Relation Selection Checklist
  • Unity Test Specification Sheet
  • Unity Verdict Decision Log
  • Wholehood Threshold Test

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.

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