Part Inventory and Granularity Review¶
Enumeration procedure — instantiates Part-Whole Unity Criterion Design
Enumerates the candidate parts and fixes the granularity at which they are judged, before any unity relation is applied.
A unity test is only as meaningful as the pieces it is run over, and "the pieces" is rarely obvious. The Part Inventory and Granularity Review is the step that pins them down: it lists the candidate parts of a possible whole and, crucially, decides the grain at which those parts are counted — because the same material can be one part or a thousand depending on where you stop dividing. Its whole discipline is choosing that grain deliberately, tied to the kind of whole in question, rather than inheriting it by accident from whatever schema, sensor, or spreadsheet happened to record the parts. It does not judge whether the parts bind into a whole and it does not name the relation that might bind them; it produces a clean, grain-consistent roster that every later test can trust.
Example¶
An archaeological dig recovers a scatter of 214 ceramic fragments from a single pit. Before anyone asks "is this one vessel or many?", the finds team runs a granularity review. At the finest grain, the inventory is 214 sherds. But the kind of whole being tested is a reconstructable vessel, so the review re-inventories at a coarser, kind-appropriate grain: it groups sherds by fabric, thickness, and curvature into candidate part-sets — a rim group, a base group, several wall groups — and records that a chip that flaked off a larger sherd in the lab is not a separate part. The output is not a verdict but a roster: "these fourteen part-groups, at vessel-reconstruction grain, are the candidates a unity test may treat as belonging to one pot." Choosing that grain up front is what stops later analysts from double-counting flakes or lumping two vessels because both left many small sherds.
How it works¶
- Enumerate at the finest available grain first, so nothing is silently omitted, then record the source of each part (which schema, sensor, or observation produced it).
- Choose the working grain against the kind of whole. Coarsen or split the raw list until each listed part is a meaningful candidate part of that kind — merging artifacts of recording, separating things a single record conflated.
- Fix boundary conventions for parthood, e.g. whether a fragment-of-a-fragment counts once, so the count is stable if the review is re-run.
- Freeze the roster as the shared input other mechanisms build on.
Tuning parameters¶
- Grain depth — how finely parts are enumerated; finer grain surfaces hidden distinctions but inflates count and effort, coarser grain is cheaper but can pre-decide unity by lumping.
- Inclusion threshold — how marginal a candidate part can be and still make the roster; loose inclusion avoids missing parts but pads the list with noise.
- Source reconciliation strictness — how aggressively duplicate parts arriving from different records are merged; strict merging cleans the count but can erase real distinctions.
- Re-enumeration cadence — one-shot roster versus periodic recount as new parts surface.
When it helps, and when it misleads¶
Its strength is that it removes the most common silent error in part-whole work — an unstated, inconsistent grain — and gives every downstream step a roster whose count means the same thing each time. It also forces the "lumpers and splitters"[n1] question into the open early, where it can be decided on purpose.
Its failure mode is that the grain choice can quietly pre-empt the verdict: enumerate coarsely and you have half-declared the parts to be one whole before any relation is tested; enumerate too finely and you fracture a real whole into a heap that no threshold can reassemble. The classic misuse is letting the data schema pick the grain — counting whatever rows the database happens to store as "the parts." The guarding discipline is to justify the grain against the kind of whole under test, not against convenience, and to keep the finest-grain enumeration on file so a coarser roster can always be re-expanded.
How it implements the components¶
candidate_part_inventory— its primary output: the enumerated, source-tagged, grain-consistent roster of candidate parts.wholehood_scope_and_kind— it engages the kind of whole only insofar as the kind sets the appropriate grain; the roster is tuned to the kind rather than to raw records.
It does NOT implement unity_relation_specification (the Unity Relation Selection Checklist) or boundary_or_container_marker and the mapping of coupling, which belong to its nearest twin the Part-Whole Dependency Map; this review lists the parts at a chosen grain, whereas the map draws the relations among them.
Related¶
- Instantiates: Part-Whole Unity Criterion Design — supplies the roster of candidate parts the whole design operates on.
- Consumes: Unity Test Specification Sheet — takes the declared kind of whole as the constraint that sets the grain.
- Sibling mechanisms: Unity Test Specification Sheet · Unity Relation Selection Checklist · Wholehood Threshold Test · Borderline Whole Review Protocol · Unity Verdict Decision Log · Part-Whole Dependency Map · Unity Reassessment Trigger
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: The mechanism reviews a candidate part inventory for omissions, source provenance, meaningful granularity, and consistent parthood boundaries.
Nearest alternative: Representation, Specification & Plan — It emits a fixed inventory and conventions, but those are the findings of a bounded review.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Part Inventory and Granularity Review is most directly rooted in philosophy's traditions of conceptual analysis, ontology, logic, epistemology, and normative reasoning. The lineage fits its defining practice: Enumerates the candidate parts and fixes the granularity at which they are judged, before any unity relation is applied.
Related originating lineages:
- Biology & Ecology — Taxonomy independently developed the enduring lumper-versus-splitter problem of category granularity.
- Systems Thinking & Cybernetics — Part Inventory and Granularity Review also draws materially on systems thinking and cybernetics' treatment of feedback, control, emergence, and multilevel system behavior, which shaped this mechanism rather than merely adopting it as an application.
Review resolution: Both independent reviews agree on primary origin philosophy; reconciliation resolves reported_ambiguity, alternate_origin_disagreement, origin_mode_disagreement. Formative alternate lineages retained: systems_cybernetics, biology_ecology. The broader reach of later applications is kept separate as domain_reach=universal; origin_mode=cross_disciplinary_synthesis records how the formative lineages relate. Confidence is conservatively reconciled to medium, and encyclopedia_synthesis=true preserves the reviewers' boundary judgment.
Attribution caveat: The enumeration procedure is an encyclopedia operationalization of old mereological and taxonomic debates.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] "Lumpers and splitters" — the long-running taxonomic tension between grouping specimens into few broad categories and dividing them into many fine ones. The same tension governs granularity: where you stop dividing partly decides whether a collection reads as one whole or many. ↩