Borderline Whole Review Protocol¶
Adjudication protocol — instantiates Part-Whole Unity Criterion Design
A review path for the cases the threshold cannot cleanly decide — nested, overlapping, temporary, or right-at-the-line wholes.
Every unity threshold leaves a gray band, and some collections are genuinely neither cleanly one nor cleanly many — they are nested wholes, overlapping wholes, temporary wholes, or cases sitting exactly on the cutoff. The Borderline Whole Review Protocol is the escalation path for precisely these. It is not another attempt to sharpen the threshold; it is a policy for what to do when the threshold cannot decide: which tie-breakers apply, who adjudicates, what provisional dispositions are allowed (nested, overlapping, temporary, unresolved), and how consistently like cases must be treated over time. Its contribution is a repeatable way to handle ambiguity without either forcing a false crisp answer or leaving each hard case to whoever happens to catch it. It works around the cutoff rather than setting it, and it deliberately does not record the final verdict or draw the container boundary.
Example¶
An insurer is underwriting a corporate campus and must decide whether a cluster of buildings is one insured property or several. The threshold test has already flagged the case as borderline: the buildings share a boundary wall and a central plant (arguing one) but have separate street addresses, separate tenants, and separate fire-suppression zones (arguing many). The borderline protocol takes over. Its tie-breaker hierarchy says: when physical and functional signals conflict, defer to the loss-event criterion — would a single realistic peril (a fire, a flood) plausibly damage them together? Because a fire wall and independent suppression make joint loss unlikely, the protocol dispositions them as overlapping wholes: one site for premises liability, but separately-rated buildings for property loss — and it tags this outcome to the named policy that produced it, so the next campus with the same signals is adjudicated the same way rather than re-argued from scratch.
How it works¶
- Confirm the case is genuinely in the ambiguity band the threshold test declined, not a clear case someone wants to relitigate.
- Apply the tie-breaker hierarchy — an ordered set of secondary criteria (loss-event, governance, downstream-consequence) that resolve conflicts the primary relation left open.
- Choose a disposition kind from the allowed set — nested, overlapping, temporary, split, or explicitly unresolved-pending-evidence — rather than being forced to one-or-many.
- Enforce like-case consistency by matching the signal pattern against previously adjudicated borderlines, so the protocol converges rather than drifting.
Tuning parameters¶
- Tie-breaker ordering — which secondary criterion dominates when signals conflict; reordering changes systematically which way borderlines fall.
- Allowed-disposition set — how many outcome kinds are permitted (strict one/many versus a rich menu of nested/overlapping/temporary); richer sets fit reality better but complicate downstream handling.
- Escalation trigger — how close to the cutoff a case must be to enter the protocol; a wide entry gate reviews more cases carefully but costs adjudication effort.
- Precedent weight — how strongly prior borderline rulings bind new ones; heavy weight yields consistency, light weight adapts faster to new patterns.
When it helps, and when it misleads¶
Its strength is that it makes ambiguity governable: instead of borderline cases being resolved inconsistently across time and departments — the archetype's classic symptom — they run through one named policy that treats like cases alike and can legitimately say "nested" or "temporary" instead of forcing a distortion. This is the machinery for a concept's penumbra[n1], where the core rule runs out and a settled practice must take over.
Its failure mode is that a tie-breaker hierarchy can quietly become a second, hidden threshold — one that decides the hard cases by fiat while looking like principled adjudication, and that can be gamed by whoever sets the ordering. It can also over-produce "unresolved" dispositions, letting genuinely decidable cases languish. The guarding discipline is to keep the tie-breakers few, public, and audited against the outcomes they actually produce, and to require every "unresolved" disposition to carry the specific evidence that would settle it.
How it implements the components¶
borderline_case_policy— its primary output: the tie-breaker hierarchy, allowed disposition kinds, and consistency rule for cases the threshold cannot cleanly decide.unity_threshold_condition— it operates on the ambiguity band around the cutoff, applying secondary criteria where the primary threshold is silent; it works the margin of the condition rather than setting it.
It does NOT implement boundary_or_container_marker — the container within which the relation is measured is drawn by the Wholehood Threshold Test — and it does NOT implement unity_verdict_record, which the Unity Verdict Decision Log owns. Its nearest twin is that threshold test: the test renders clean pass/fail for clear cases, while this protocol governs only the gray band the test refuses.
Related¶
- Instantiates: Part-Whole Unity Criterion Design — supplies the policy for cases the criterion cannot cleanly resolve.
- Consumes: Wholehood Threshold Test — receives the ambiguous-band cases the test declines to decide.
- Sibling mechanisms: Unity Test Specification Sheet · Part Inventory and Granularity Review · Unity Relation Selection Checklist · Wholehood Threshold Test · Unity Verdict Decision Log · Part-Whole Dependency Map · Unity Reassessment Trigger
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: The mechanism confirms a case lies in the ambiguity band, applies secondary evidence criteria, and determines an allowed whole-membership disposition, so its operative form is adjudicative review.
Nearest alternative: Decision, Gate & Allocation — The review ends in a disposition, but that choice is the result of evaluating a borderline case against evidence and consistency criteria.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Adjudicating whether nested, overlapping, temporary, or borderline entities count as wholes belongs to metaphysical and mereological analysis.
Related originating lineages:
- Law & Governance — Case-by-case adjudication and precedent supply the review protocol for hard boundary cases.
- Library & Information Science — Classification practice confronts ambiguous part-whole membership in controlled knowledge systems.
Review resolution: Mereology supplies the agreed primary one-versus-many problem. Hart's legal penumbra and classification governance materially shape the ordered adjudication, provisional status, and precedent form, making this a cross-disciplinary synthesis with multi-domain—not universal—reach.
Attribution caveat: The underlying unity criterion is philosophical, while the procedural form is a modern synthesis.
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] H.L.A. Hart's distinction between the settled core of a rule and its uncertain penumbra, where the rule's general terms run out and cases must be decided by something beyond the plain criterion. Borderline wholes live in exactly this penumbra. ↩