Unity Relation Selection Checklist¶
Decision checklist — instantiates Part-Whole Unity Criterion Design
Walks the candidate binding relations and picks the one (or few) that could actually make these parts one whole of this kind.
Parts can be linked by many things at once — they sit near each other, share an owner, serve a common function, are causally coupled, descend from a common source, or flow continuously into one another — and not all of those relations confer wholeness. The Unity Relation Selection Checklist is the step that names which relation is doing the binding. It runs down the menu of candidate relations, asks of each whether it is the kind of tie that makes parts one rather than merely associated, and selects the one (occasionally two) that will carry the unity claim for this kind of whole. It does not measure how strong that relation is or set a pass mark — that comes later. Its single contribution is to answer "in virtue of what would these parts be one?" so the test is not run on the wrong tie.
Example¶
A botanist is standing in a grove of quaking aspen where 47 trunks rise from the hillside. Are these 47 trees or one organism? The checklist forces the relation question before any measuring. Proximity? The trunks are close, but proximity binds nothing — a mixed forest is close too, and no one calls it one plant. Function? They photosynthesize alike, but so do unrelated species. Genetic and root continuity? Aspen spread clonally from a single root system, so every trunk that shares that connected root mass is genetically identical tissue of one plant. The checklist selects root-system continuity as the binding relation and explicitly discards proximity and functional similarity as non-binding for the kind "organism." Only now does it make sense to ask the threshold question — how much root connection, confirmed how — because the relation the threshold will be applied to has been correctly chosen.
How it works¶
- List the candidate relations present among the parts: proximity, shared ownership or governance, functional integration, causal coupling, common lineage, boundary sharing, continuity.
- Screen each for wholehood-conferring power given the kind of whole — the same relation can bind one kind and not another (shared ownership makes one legal unit but not one physical object).
- Select the binding relation(s) and record the rejected ones with the reason they were rejected, so the discards are auditable.
- Hand off the chosen relation to the thresholding step, which will decide how much of it is enough.
Tuning parameters¶
- Relation menu breadth — how many candidate relations are considered; a fuller menu avoids missing the true binder but lengthens the review.
- Single- vs multi-relation stance — whether unity may rest on one relation or must satisfy several jointly; requiring several is stricter but can make no whole qualify.
- Kind-sensitivity — how tightly relation eligibility is keyed to the declared kind; tight keying prevents cross-kind errors, loose keying is faster but leakier.
- Discard-logging depth — how fully rejected relations are documented; thorough logging aids later disputes at the cost of effort.
When it helps, and when it misleads¶
Its strength is that it prevents the commonest unity error — binding parts on a relation that merely co-occurs with wholeness (usually proximity or surface similarity) rather than one that constitutes it. Naming the relation explicitly also makes the later threshold argument tractable, because you know what you are measuring. The relation menu echoes the Gestalt grouping principles[n1] — proximity, similarity, common fate, good continuation — which is a useful reminder that perceived grouping and genuine unity are not the same thing.
Its failure mode is choosing a relation because it is easy to see rather than because it binds: proximity and shared labels are cheap to observe and chronically over-selected. A subtler misuse is quietly switching the binding relation between candidates so that whatever answer is wanted comes out. The guarding discipline is to fix the binding relation by kind on the specification sheet's terms and require an explicit, logged reason to change it, so the same relation governs every candidate of a kind.
How it implements the components¶
unity_relation_specification— its primary output: the named, justified binding relation (and any co-required relations) that the unity claim rests on.wholehood_scope_and_kind— it consults the kind of whole to decide which relations are even eligible to bind, keying relation selection to kind.
It does NOT implement unity_threshold_condition — deciding how much of the chosen relation is enough belongs to its nearest twin the Wholehood Threshold Test; this checklist names *which relation binds, that test sets how much is enough. It also does not draw the boundary_or_container_marker, which the Part-Whole Dependency Map supplies.*
Related¶
- Instantiates: Part-Whole Unity Criterion Design — selects the relation the whole unity criterion is built on.
- Consumes: Part Inventory and Granularity Review — needs the candidate parts before it can ask what relates them.
- Sibling mechanisms: Unity Test Specification Sheet · Part Inventory and Granularity Review · Wholehood Threshold Test · Borderline Whole Review Protocol · Unity Verdict Decision Log · Part-Whole Dependency Map · Unity Reassessment Trigger
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Unity Relation Selection Checklist operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it walks the candidate binding relations and picks the one (or few) that could actually make these parts one whole of this kind.
Independent corroboration: The frozen evidence defines Unity Relation Selection Checklist as 'Walks the candidate binding relations and picks the one (or few) that could actually make these parts one whole of this kind', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Assessment, Review & Assurance — Unity Relation Selection Checklist includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is a case-specific gate, selection, routing, prioritization, or resource disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Stanford Encyclopedia of Philosophy, Parts and Wholes documents that mereology makes the relations that bind parts into wholes, and competing principles of composition, an explicit philosophical problem. This is direct, mechanism-specific evidence for philosophy as the best-evidenced historical home of the operation—Walks the candidate binding relations and picks the one (or few) that could actually make these parts one whole of this kind.—rather than evidence merely that the operation is useful there. The retained alternates record genuine adjacent lineages; later portability is represented separately by domain_reach=universal.
Related originating lineages:
- Mathematics — Mathematical modeling, proof, and abstract-structure practice supplies a parallel or contributing lineage for the mechanism's defining operation: walks the candidate binding relations and picks the one (or few) that could actually make these parts one whole of this kind.
- Organizational & Management Science — Organizational Management supplies a historically relevant adjacent lineage or formative practice for the operation—Walks the candidate binding relations and picks the one (or few) that could actually make these parts one whole of this kind.—but the adjudicated evidence more directly locates the defining lineage in philosophy.
- Systems Thinking & Cybernetics — Systems science's feedback, boundaries, control, and regulation tradition contributes a separate formative lineage to the mechanism's unity relation selection checklist logic.
Review resolution: The blind reviewers disagree on primary lineage (organizational_management versus philosophy). The defining operation is: Walks the candidate binding relations and picks the one (or few) that could actually make these parts one whole of this kind. The researched Stanford Encyclopedia of Philosophy, Parts and Wholes establishes that mereology makes the relations that bind parts into wholes, and competing principles of composition, an explicit philosophical problem. That source therefore supports philosophy as the historical origin. organizational management remains in the uncapped alternates where it contributes a formative practice, but application or governance is not itself proof of origin. origin_mode=convergent records lineage construction; domain_reach=universal separately records later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
Notes¶
[n1] Gestalt grouping principles — proximity, similarity, common fate, good continuation, and closure describe how perception fuses elements into a figure. They are a caution as much as a menu: perceptual grouping can suggest a whole where no wholehood-conferring relation actually exists. ↩