Priority-Based Admission¶

Status: draft
Scope: cross_prime
Structural signature: A constrained admission boundary where not all candidates can enter or be served simultaneously, and candidates differ in priority-relevant attributes.
Failure modes: priority_misclassification, gaming_priority_labels, opaque_gatekeeping, bias_amplification, priority_inversion, starvation_of_low_priority_cases, administrative_bottleneck, legitimacy_loss, emergency_exception_sprawl, silent_denial, brittle_priority_rules, queue_jumping_pathology, overfitting_priority_policy_to_past_cases
Domain examples: emergency_medicine, incident_response, cloud_and_compute_scheduling, network_quality_of_service, public_services_and_benefits, education_and_admissions, grant_funding_or_review_processes, customer_support_or_operations_intake, scarce_resource_allocation

Intent¶

Priority-Based Admission preserves scarce capacity for higher-priority flows, cases, users, tasks, or obligations by admitting candidates according to an explicit priority policy rather than treating all candidates as equal.

The archetype is useful when a system cannot admit or serve everyone at once, and when candidates differ in urgency, value, risk, entitlement, readiness, severity, dependency, or potential harm from delay. The intervention is not simply denial. It is governed allocation at an admission boundary.

In compact form:

When not all candidates can be admitted and candidates differ in priority-relevant ways, classify candidates and admit them according to explicit priority criteria at the cost of delay, exclusion, classification burden, and fairness tension.

Primes¶

Composed of: Boundary, Admission Control, Prioritization, Classification, Resource Management, Threshold, Fairness Policy, Review Or Appeal Path

Structural Signature¶

This archetype is a strong candidate when the following conditions co-occur:

A system has an admission boundary: intake, queue entry, service access, resource allocation, escalation, review, processing, or activation.
Demand exceeds immediate admission capacity, or admitting all candidates would create overload, risk, unfairness, or degraded outcomes.
Candidates differ in priority-relevant attributes such as urgency, severity, dependency, readiness, risk, value, deadline, entitlement, or vulnerability.
The system can observe or infer these attributes well enough to classify candidates.
Nonadmitted candidates can be deferred, queued, rejected, routed elsewhere, served later, or handled through a defined alternative.
The priority policy can be communicated, audited, corrected, or governed.

Priority-Based Admission is especially relevant when equal treatment at the point of arrival would produce unequal or unsafe outcomes.

Intervention Signature¶

Classify candidates by explicit priority criteria, then admit, defer, reject, route, or sequence them according to the priority policy.

The intervention changes the system from:

undifferentiated candidates -> admission by arrival, pressure, politics, or chance

to:

candidates classified by priority -> governed admission -> defined handling for nonadmitted candidates

The key move is not just prioritization in the abstract. It is the use of priority at an admission boundary where capacity is scarce.

Causal Logic¶

When a constrained system treats all candidate load as equal, scarce capacity may be consumed by lower-priority cases while higher-priority cases wait. First-come-first-served can seem neutral while producing avoidable harm. Informal pressure can displace explicit criteria. Powerful actors can capture capacity. Operators may improvise under stress, producing inconsistent or biased decisions.

Priority-Based Admission works by changing the allocation rule.

The admission boundary is made explicit. The system identifies where entry, escalation, service, processing, or resource use is decided.
Priority-relevant attributes are named. The system states what makes one candidate more urgent, important, risky, or entitled than another.
Candidates are classified. Each candidate is assigned to a class, score, rank, or route.
Capacity is allocated by policy. Higher-priority candidates receive admission, reserved capacity, faster routing, or earlier service.
Nonadmitted candidates receive defined handling. They may wait, appeal, be rerouted, receive lower-tier service, or be rejected cleanly.
The policy is monitored. Classification errors, gaming, bias, starvation, and impact distribution are reviewed.

The archetype converts unstructured contention into governed allocation.

What It Is Not¶

Priority-Based Admission is not Access Control. Access control determines whether a subject is allowed to access a resource at all. Priority-Based Admission allocates scarce admission capacity among candidates that may all be eligible in principle.

Priority-Based Admission is not Rate Limiting. Rate Limiting governs how much or how often flow may be admitted. Priority-Based Admission governs which candidates enter when capacity is scarce.

Priority-Based Admission is not Load Shedding. Load Shedding sacrifices lower-priority load under overload. Priority-Based Admission may prevent overload by admitting higher-priority candidates first, but it does not necessarily drop load.

Priority-Based Admission is not Queueing. Queueing structures waiting. Priority-Based Admission decides which candidates are admitted, routed, or sequenced based on priority. A priority queue may instantiate it.

Priority-Based Admission is not Scheduling. Scheduling arranges tasks or resource use over time. Priority-Based Admission decides who or what gets access to scarce capacity in the first place, though scheduling may implement that decision.

Priority-Based Admission is not Triage in the narrow sense. Triage is a major mechanism family or neighboring archetype, often associated with urgent care, crisis response, or severity sorting. Priority-Based Admission is broader and includes non-crisis allocation of scarce capacity.

Priority-Based Admission is not arbitrary gatekeeping. A mature admission policy names criteria, tradeoffs, appeal paths, and safeguards.

Composition¶

Priority-Based Admission is composed from several lower-level abstractions:

Boundary — There must be a point where admission, routing, service, or escalation is decided.
Admission control — The system must be able to accept, defer, route, reject, or sequence candidates.
Prioritization — Candidates are ranked or classified by explicit criteria.
Classification — The system maps observed attributes to priority categories or scores.
Resource management — Scarce capacity must be allocated among competing candidates.
Threshold — Admission may require meeting a score, severity, urgency, readiness, or entitlement threshold.
Fairness policy — The system must decide what counts as acceptable distribution of benefit and burden.
Review or appeal path — The system needs a way to correct classification errors or contest decisions.

The composition matters. Prioritization without an admission boundary is only preference. Admission control without fairness policy can become arbitrary exclusion. Classification without review can entrench error. Scarce capacity without priority rules can be captured by arrival order, power, noise, or chance.

Mechanism Families¶

Common mechanism families include:

Emergency or clinical triage — Patients are prioritized by severity, urgency, survivability, or need.
Priority queues — Items are served according to rank or class rather than simple arrival order.
Quality-of-service classes — Network, computing, or service traffic receives differentiated priority.
Service-tier admission — Users, cases, or workloads enter different service lanes based on tier, need, or entitlement.
Cloud or compute priority scheduling — Critical workloads receive scarce compute before lower-priority jobs.
Grant or application scoring — Applications are ranked by criteria before limited funding, slots, or review capacity is allocated.
Admissions or eligibility ranking — Candidates are admitted based on readiness, fit, need, merit, lottery-weighting, or policy goals.
Incident-response severity routing — Incidents are routed and escalated according to severity and business impact.
Scarce-resource allocation protocols — Limited resources are assigned based on explicit criteria.
Expedited review or fast-track processes — High-priority cases bypass ordinary intake delay under defined conditions.

These mechanisms differ by domain, but they preserve the same intervention logic: scarce admission capacity is allocated by explicit priority criteria.

Parameter Dimensions¶

Concrete mechanisms usually require tuning along dimensions such as:

Priority criteria — What attributes determine priority?
Priority class count — How many tiers or categories exist?
Scoring weight — How much does each criterion matter?
Admission threshold — What score, class, or condition is required for entry?
Reserved capacity fraction — How much capacity is protected for high-priority candidates?
Waiting-time adjustment — Does priority increase with time spent waiting?
Tie-break rule — How are candidates handled when priority appears equal?
Exception policy — When can ordinary priority rules be overridden?
Review or appeal window — How can errors be challenged?
Reclassification cadence — How often is priority reassessed?
Transparency level — How much of the rule is visible to candidates?
Fairness constraint — What distributional limits must be preserved?
Starvation prevention rule — How are lower-priority candidates eventually served?

These are parameter dimensions, not the archetype itself.

Invariants to Preserve¶

Priority-Based Admission should preserve explicit invariants:

Priority criteria are explicit — The system should know what counts and why.
Admission decisions are auditable — Decisions should be explainable enough to review.
Critical cases are not blocked by lower-priority cases — The intervention should actually preserve capacity for what matters most.
Nonadmitted candidates receive defined handling — Rejection, deferral, waiting, rerouting, or appeal should be explicit.
Classification errors can be corrected — Mistakes should not become irreversible harm where correction is possible.
Policy does not create unacceptable discrimination or harm — Priority should not encode unjust exclusion.
Reserved capacity is not silently consumed — Protected capacity should remain available for the intended class.
The policy remains aligned with the system goal — Priority rules should not drift into self-serving gatekeeping.

If these invariants cannot be preserved, the intervention may become arbitrary, biased, or illegitimate.

Tradeoffs¶

Priority-Based Admission accepts unequal timing or access in order to allocate scarce capacity more purposefully.

Typical tradeoffs include:

Lower-priority candidates are delayed or excluded even when they may have legitimate need.
Fairness disputes arise because priority criteria are contestable.
Classification errors can harm candidates by assigning them the wrong priority.
Administrative overhead increases because candidates must be assessed.
Gaming or misrepresentation may increase as actors try to appear high-priority.
Simplicity declines compared with first-come-first-served.
Legitimacy risk increases if affected parties do not trust the criteria.
Existing bias may be entrenched if priority attributes reflect unequal systems.
Neutrality of arrival order is sacrificed in favor of explicit priority.

The archetype is therefore not merely efficiency improvement. It is an allocation decision under scarcity.

Contraindications¶

Priority-Based Admission is a poor fit when priority cannot be determined or legitimate.

Use cautiously or avoid when:

candidates are genuinely equal in priority,
priority-relevant attributes cannot be observed or verified,
classification errors would be catastrophic,
the priority policy lacks legitimacy,
nonadmitted candidates have no safe alternative path,
the system requires strict equal treatment, lottery, or random allocation,
priority labels are easy to game,
admission capacity is not the binding constraint,
the policy would encode unacceptable bias,
the system lacks accountability for admission decisions.

In such cases, lottery allocation, first-come-first-served, capacity expansion, rate limiting, buffering, scheduling, or direct rule redesign may be more appropriate.

Failure Modes¶

Common failure modes include:

Priority misclassification — Candidates receive the wrong priority.
Gaming priority labels — Actors exaggerate urgency, severity, or entitlement to gain admission.
Opaque gatekeeping — Admission decisions cannot be explained or reviewed.
Bias amplification — The priority rule reproduces or worsens existing inequalities.
Priority inversion — Lower-priority candidates are admitted ahead of higher-priority ones.
Starvation of low-priority cases — Some candidates never receive service.
Administrative bottleneck — Assessment consumes so much capacity that admission slows.
Legitimacy loss — Affected parties reject the policy as unfair or arbitrary.
Emergency exception sprawl — Too many exceptions undermine the rule.
Silent denial — Nonadmitted candidates are effectively rejected without acknowledgement.
Brittle priority rules — The criteria fail under novel cases.
Queue-jumping pathology — Priority channels become tools for privileged bypass.
Overfitting priority policy to past cases — The rule matches old patterns but fails in new conditions.

These failure modes should be treated as part of the archetype's design space.

Worked Example¶

An incident-response team receives more alerts than it can investigate in real time. In the past, analysts handled alerts mostly by arrival order or by whoever complained the loudest. This allowed low-impact alerts to consume attention while high-risk alerts waited.

The team introduces Priority-Based Admission.

Alerts are classified by severity, affected system, customer impact, exploitability, and confidence.
Critical alerts bypass the ordinary queue.
Medium-priority alerts enter the standard investigation queue.
Low-priority alerts are batched for later review.
Analysts can manually escalate an alert, but every escalation is logged.
False positives, missed critical alerts, and queue starvation are reviewed weekly.

The team does not eliminate scarcity. It changes how scarce investigation capacity is allocated. High-risk alerts are admitted first, lower-priority alerts are still handled through defined paths, and the priority policy is auditable.

The key move is not merely sorting alerts. It is governing admission into scarce human attention according to explicit priority criteria.

Cross-Domain Instances¶

Emergency medicine — Patients are admitted or treated according to urgency, severity, and expected benefit under limited capacity.
Incident response — Alerts or incidents are routed and escalated by severity and impact rather than simple arrival order.
Cloud and compute scheduling — Critical workloads receive scarce compute capacity before lower-priority jobs.
Network quality of service — Traffic classes receive different admission or service priority.
Public services and benefits — Applications or cases may be prioritized by vulnerability, urgency, eligibility, or statutory criteria.
Education and admissions — Limited seats or opportunities are allocated according to explicit criteria, sometimes including readiness, need, merit, or policy goals.
Grant funding or review processes — Applications are ranked before limited review capacity or funding is allocated.
Customer support or operations intake — Requests are admitted or escalated based on severity, account tier, deadline, or business impact.
Scarce resource allocation — Limited goods, appointments, licenses, or services are allocated through explicit priority rules.

These examples are structurally related because each allocates scarce admission capacity through priority classification rather than undifferentiated arrival.

Notes¶

Priority-Based Admission should be reviewed alongside Access Control, Rate Limiting, Load Shedding, Scheduling, Queueing, Triage, Constraint Envelope Adjustment, and Graceful Degradation.

The main conceptual risk is collapse into nearby concepts:

If the entry decides whether someone may access at all, it becomes Access Control.
If the entry governs rate or frequency, it becomes Rate Limiting.
If the entry removes or sacrifices load under overload, it becomes Load Shedding.
If the entry arranges service order over time, it becomes Scheduling or Queueing.
If the entry focuses on urgent medical or crisis classification, it may become Triage.
If the entry lacks explicit criteria and review, it becomes Arbitrary Gatekeeping.

This entry exists partly because admission_control and prioritization repeatedly appeared as solution-side labels in earlier Pilot Batch 001 archetypes. It may later be promoted, split, or demoted to a lower-level component depending on how often this structure recurs.