Unity Reassessment Trigger¶
Monitoring trigger — instantiates Part-Whole Unity Criterion Design
Watches declared conditions and reopens a settled unity verdict when parts, relations, or boundaries change enough to threaten it.
A unity verdict is true as of the evidence that produced it, and the world does not hold still. Parts are added or removed, the binding relation weakens, a boundary moves, a downstream use becomes more consequential — and a collection that was rightly one whole silently becomes many, or vice versa. The Unity Reassessment Trigger is the standing monitor that guards against that drift. It declares, at verdict time, the specific conditions under which a settled verdict must be reopened — a coupling metric falling below a watch-level, a part count changing by more than a margin, a boundary redraw, an ownership transfer — and when a trigger fires it reopens the affected verdict record for re-testing. It does not itself re-run the whole test or define what the verdict licensed; it is the alarm that says this ruling can no longer be trusted as standing.
Example¶
A corporate group reports its subsidiaries as one economic entity for consolidated accounts, a unity verdict resting on control above a threshold. The reassessment trigger is armed against that verdict: watch conditions declared as effective control dropping below the consolidation cutoff, disposal of a subsidiary above a size margin, or a change in the shareholder agreement that alters control rights. For two years nothing fires and the verdict stands untouched. Then the group sells a majority stake in a large subsidiary to a partner, retaining only a minority interest. The disposal crosses the size margin and control drops below the cutoff — two triggers fire at once. The trigger does not re-decide consolidation; it flips the verdict's status to reopened and routes it back for re-testing, so the subsidiary is not silently consolidated for another reporting cycle on the strength of a ruling the sale has invalidated. Without the trigger, the stale verdict would have persisted by default — the quiet way a real whole fragments or a fragmented thing keeps being counted as one.
How it works¶
- Arm watch-conditions at verdict time, expressed as movements relative to the original threshold — how far the binding relation may weaken, how much the part set may change, before the verdict is suspect.
- Monitor cheaply and continuously against those conditions rather than re-running the full test on a schedule.
- Fire on breach — flip the affected verdict record's status to reopened and route it back for re-testing, carrying the specific condition that fired.
- Escalate on stakes changes, not only on relation changes: a verdict whose downstream consequence has become more consequential is reopened even if the parts held.
Tuning parameters¶
- Watch-level margin — how far below the original cutoff the relation may drift before firing; a tight margin catches drift early but fires often on noise, a loose one is quiet but lets wholes go stale.
- Trigger sensitivity to stakes — whether rising downstream consequence alone reopens a verdict; sensitivity catches under-scrutinized wholes but can flood the queue.
- Debounce window — how long a breach must persist before firing, to avoid thrashing on transient dips.
- Coverage — which verdicts get armed at all; arming everything is safe but costly, arming only high-stakes wholes is efficient but leaves blind spots.
When it helps, and when it misleads¶
Its strength is that it converts unity from a one-time ruling into a maintained status: verdicts expire on evidence rather than by calendar, and the two silent failures the archetype warns of — a genuine whole fragmenting unnoticed, a heap still counted as one — are caught when the underlying conditions actually move. It is the mechanism that keeps a settled record honest over time, the standing answer to the Ship of Theseus question of whether enough has changed that this is no longer the same one whole[1].
Its failure mode is miscalibrated sensitivity: set the margins too tight and it cries wolf until reviewers mute it; too loose and it provides false assurance while wholes rot quietly past the point of validity. A subtler misuse is arming triggers but never staffing the re-tests they fire, so "reopened" verdicts pile up and the monitor becomes theater. The guarding discipline is to tie every watch-condition to a specific movement relative to the original threshold, debounce transient noise, and ensure a fired trigger routes to an owner who actually re-runs the test.
How it implements the components¶
unity_threshold_condition— it monitors the binding relation against watch-levels set relative to the original cutoff, firing when the relation drifts past a declared margin.unity_verdict_record— it reaches into the existing verdict record to flip its status to reopened, keeping the record's standing current rather than frozen.
It does NOT implement identity_and_persistence_consequence — what a positive verdict licenses is declared on the Unity Test Specification Sheet — and it does NOT implement borderline_case_policy (the Borderline Whole Review Protocol's). Its nearest twin is the Unity Verdict Decision Log: where that log passively stores verdicts, this trigger is the active monitor that reopens them.
Related¶
- Instantiates: Part-Whole Unity Criterion Design — keeps settled verdicts valid as parts, relations, and boundaries change.
- Consumes: Unity Verdict Decision Log — reaches into its stored verdicts to reopen the ones a trigger invalidates.
- Sibling mechanisms: Unity Test Specification Sheet · Part Inventory and Granularity Review · Unity Relation Selection Checklist · Wholehood Threshold Test · Borderline Whole Review Protocol · Unity Verdict Decision Log · Part-Whole Dependency Map
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Unity Reassessment Trigger is defined in the frozen evidence as: Watches declared conditions and reopens a settled unity verdict when parts, relations, or boundaries change enough to threaten it. Its operative deployed or enacted form is therefore Control, Automation & Runtime.
Nearest alternative: Monitoring, Sensing & Alerting — Monitoring, Sensing & Alerting can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; 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—Watches declared conditions and reopens a settled unity verdict when parts, relations, or boundaries change enough to threaten it.—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:
- Law & Governance — Legal doctrine, regulatory governance, and procedural accountability supplies a parallel or contributing lineage for the mechanism's defining operation: watches declared conditions and reopens a settled unity verdict when parts, relations, or boundaries change enough to threaten it.
- Mathematics — Mathematical modeling, proof, and abstract-structure practice supplies a parallel or contributing lineage for the mechanism's defining operation: watches declared conditions and reopens a settled unity verdict when parts, relations, or boundaries change enough to threaten it.
- Organizational & Management Science — Organizational Management supplies a historically relevant adjacent lineage or formative practice for the operation—Watches declared conditions and reopens a settled unity verdict when parts, relations, or boundaries change enough to threaten it.—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 reassessment trigger logic.
Review resolution: The blind reviewers disagree on primary lineage (organizational_management versus philosophy). The defining operation is: Watches declared conditions and reopens a settled unity verdict when parts, relations, or boundaries change enough to threaten it. 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:
References¶
[1] Plutarch. "Theseus". In Plutarch’s Lives, Vol. I, translated by Bernadotte Perrin. Harvard University Press and William Heinemann (1914). Presents the Ship of Theseus as a dispute over whether a vessel remains the same after its timbers are progressively replaced. registry ↩