Priority-Band Triage Rule¶
Decision rule — instantiates Reference Tracking Bandwidth Alignment
Allocates scarce tracking bandwidth by priority band, keeping critical references inside the envelope while lower bands queue, degrade, or wait.
A Priority-Band Triage Rule accepts that the loop cannot track everything demanded of it and decides, explicitly and in advance, what gets tracked first. It sorts the incoming references into a small number of priority bands and grants each band a different claim on the loop's limited bandwidth: the top band is tracked in full and on time, middle bands are tracked with reduced fidelity or added latency, and the lowest bands queue, degrade, or wait until capacity frees. Its defining idea is bandwidth rationing by declared priority: rather than let an overloaded loop fail everywhere at once and blame the executor, the rule concentrates scarce tracking on what matters and makes the neglect of the rest a deliberate, visible allocation rather than an accident.
Example¶
A carrier's edge router carries voice calls, live video, web traffic, and bulk backups over a link that periodically congests. Treated as one undifferentiated flow, congestion garbles calls and stalls video indiscriminately. The router runs a Priority-Band Triage Rule (quality-of-service classes): voice packets get the highest band with a guaranteed low-latency queue, interactive video the next, ordinary web the default band, and backup traffic the lowest "scavenger" band that may only use whatever bandwidth the higher bands leave idle. Setup to outcome: when a backup job and a spike of web requests hit during a busy hour, the link saturates — but calls stay crisp and video stays smooth because their bands are served first, while the backup slows to a trickle and finishes overnight. The loop's total bandwidth did not grow; the rule simply decided, ahead of time, which references were allowed to consume it under contention.
How it works¶
The rule needs three settled things. A banding scheme: how references are classified into priority tiers, and by whom. A service policy per band: what each tier is promised — full tracking, degraded tracking, bounded delay, or best-effort. And a contention rule: what happens when demand exceeds capacity, i.e. which bands yield and in what order. Classification happens up front so that under load the decision is already made and no deliberation competes for the scarce resource. The lowest bands' treatment is a fallback: their references are explicitly allowed to lag or wait rather than being pretended into the envelope.
Tuning parameters¶
- Number of bands — how many priority tiers exist. More bands allow finer discrimination but complicate classification and invite disputes over placement.
- Band guarantees — what each tier is promised under contention. Firmer top-band guarantees protect the critical few but reserve capacity that may sit idle.
- Reserve vs. share — whether high bands get dedicated capacity or merely first claim on shared capacity. Dedicated is stronger but wasteful; shared is efficient but riskier under simultaneous load.
- Starvation floor — the minimum service the lowest bands are guaranteed so they never wait forever. Higher protects fairness; lower maximises protection of the top.
- Reclassification cost — how hard it is to move a reference between bands, trading responsiveness to changing importance against gaming.
When it helps, and when it misleads¶
Its strength is graceful degradation: under overload the system loses the least important tracking first, on purpose, instead of failing everywhere — the discipline behind medical triage and network quality-of-service alike. It keeps the loop honest by making prioritisation an explicit contract rather than an emergent accident of whoever shouts loudest.
Its failure modes cluster around the banding itself. A low band can be starved indefinitely — priority inversion and outright starvation are the classic hazards, where a high-priority item is blocked behind, or a low-priority need is never served because higher demand never lets up.[n1] Worse, triage can become a laundering device: relabel inconvenient demand into the bottom band and call it "handled" while it is really just ignored. The guarding discipline is a hard starvation floor for every band, a fairness review of the classification, and an audit trail so that what the bottom band did not get tracked is recorded as unmet demand, not erased.
How it implements the components¶
multi_band_tracking_policy— it is the banding policy itself: distinct priority tiers, each with its own tracking treatment.reference_shaping_rule— it shapes demanded motion by prioritising it, gating lower-band changes so the trackable envelope is spent on the highest-value references first.untrackable_reference_fallback_policy— the lowest bands' queue/degrade/wait behaviour is the explicit fallback mode invoked when total demand exceeds bandwidth.
It does NOT implement tracking_error_decomposition or reference_change_control_contract — logging which fallback fired, why the demand was untrackable, and against which declared envelope belongs to Untrackable Demand Exception Record, its nearest fallback-axis twin. This rule *decides the allocation in real time; it does not keep the audit ledger.*
Related¶
- Instantiates: Reference Tracking Bandwidth Alignment — supplies the priority-rationing branch of the fallback family.
- Sibling mechanisms: Untrackable Demand Exception Record · Trackable Envelope Chart · Actuator Saturation Alarm · Feedforward Prepositioning Plan
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Priority-Band Triage Rule operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it allocates scarce tracking bandwidth by priority band, keeping critical references inside the envelope while lower bands queue, degrade, or wait.
Independent corroboration: The frozen evidence defines Priority-Band Triage Rule as 'Allocates scarce tracking bandwidth by priority band, keeping critical references inside the envelope while lower bands queue, degrade, or wait', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: The banded sorting of cases by urgency and scarce treatment capacity originates in military and emergency medicine; the encyclopedia mechanism translates that triage lineage into a general reference-tracking rule.
Related originating lineages:
- Disaster Management & Risk Reduction — Priority-band triage is rooted in emergency management's allocation of scarce attention and response capacity by severity.
- Engineering & Design — The engineering_design tradition materially shaped Priority-Band Triage Rule through its own practice of physical-system design, process control, reliability, and safety engineering.
- Military & Strategic Studies — The military_strategic_studies tradition materially shaped Priority-Band Triage Rule through its own practice of staging, escalation, prioritization, and sustainment under contested conditions.
- Operations Research — Priority-Band Triage Rule is most plausibly rooted in the operations_research tradition because its characteristic form depends on queueing, optimization, scheduling, prioritization, and constrained allocation. The assignment tracks that formative lineage, not the many settings in which the mechanism can now be applied.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of medicine healthcare. National Library of Medicine: Triage in Medicine—Concept, History, and Types documents the defining practice, history, or theory described in the selected origin rationale. Other domains are retained only where the blind reviews identify material co-development or translation; broad later application is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among formative lineages.
Attribution caveat: The blind-review boundary with operations research, disaster management is substantive: those traditions materially developed, translated, or operationalized part of the mechanism. The cited provenance places its defining lineage in medicine healthcare.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] Priority inversion / starvation — in scheduling, priority inversion is when a high-priority task is blocked by a lower-priority one holding a needed resource, and starvation is when a low-priority task never runs because higher-priority work keeps arriving. Both are the standard cautions for any strict priority scheme and motivate starvation floors and priority-inheritance protocols. ↩