Cap Reopen Rule¶
Decision rule — instantiates Bounded Backlog
Defines the exact condition under which a closed intake reopens, so a full backlog resumes accepting work on evidence of recovered capacity rather than on pressure or favoritism.
Cap Reopen Rule governs the other transition — not how a backlog closes when it fills, but how it reopens once it has drained. It exists because a cap that closes cleanly can still reopen badly: the moment pressure builds, someone reopens intake "just this once," or a well-connected requester gets let in early, or the queue reopens the instant it dips one item below the cap and immediately floods again. This rule replaces that improvisation with a pre-committed condition: intake resumes only when defined evidence of recovered capacity is present — utilization fallen well below the cap, drain rate sustained, relief capacity actually online. Its defining feature is that the reopen threshold is deliberately lower than the close threshold, so the system settles rather than oscillates, and the decision to reopen is a rule-following act rather than a discretionary favor.
Example¶
A city building-permit office limits pending applications to 300 per review cycle; beyond that, intake for the cycle closes and applicants are told the next window's date. The failure the office kept hitting was reopening badly — as soon as reviewers cleared a few permits and the count dipped to 299, the portal reopened, a rush of waiting applicants flooded in within minutes, and it slammed shut again, an exhausting on-off flicker that felt arbitrary and invited "can you just squeeze mine in" phone calls.
The office adopts a Cap Reopen Rule: intake does not reopen at 299. It reopens only when pending falls to 200 or below (a deliberate gap beneath the 300 cap), and the reviewers have sustained their clear-rate for a full week, or a budgeted temporary reviewer has been confirmed as added capacity. When those conditions are met, the next window opens on a published date for everyone at once. The flicker stops; reopening becomes predictable and fair, tied to real recovered throughput rather than to whoever pushed hardest.
How it works¶
What distinguishes a reopen rule from an ad-hoc "let's open back up" is that it is a condition fixed in advance:
- Set a reopen threshold below the cap. Reopening triggers at a utilization meaningfully under the closing limit, not at the cap's edge, so there is real headroom before the next inflow arrives.
- Require sustained recovery, not a momentary dip. The condition tests drain rate over a window or confirmed added capacity — evidence the system can actually absorb new work, not just a transient blip.
- Reopen for everyone by the same rule. When the condition is met, intake reopens on a stated basis for all waiting parties at once, removing the discretion that becomes favoritism.
- Tie reopening to relief when drainage alone is too slow. If the backlog will not fall on its own, the rule can condition reopening on escalated relief capacity arriving rather than on wishful patience.
Tuning parameters¶
- Reopen threshold — how far below the cap the backlog must fall to reopen. A large gap prevents immediate re-flooding but keeps intake closed longer; a small gap reopens sooner but risks thrashing.
- Sustain window — how long recovery must hold before reopening. A longer window guarantees genuine recovery but delays legitimate intake; a shorter one is responsive but fooled by brief lulls.
- Relief-versus-drain balance — whether reopening waits for natural drainage or for added capacity. Waiting on drainage is cheap but slow; conditioning on escalated relief reopens faster but spends resources.
- Announcement lead — how much notice a reopen carries. A published date lets waiting parties prepare and spreads the inflow; an instant silent reopen advantages whoever happens to be watching.
When it helps, and when it misleads¶
Its strength is that it stops a bounded system from flapping — repeatedly reopening and re-closing — by building a gap between the close and reopen thresholds, exactly the logic of hysteresis in control systems.[n1] It also removes the moment where discretion creeps back in: reopening on a fixed, announced condition is fair and predictable in a way that "the manager decided to reopen" never is.
Its failure mode is a reopen condition that is never actually reached — a threshold so conservative or a backlog draining so slowly that intake stays shut indefinitely, hardening a temporary cap into a silent permanent closure that no one decided to make. Set with no relief pathway, the rule can trap a system that simply cannot drain itself. Its classic misuse is quietly overriding the rule under pressure — reopening early for a favored case — which restores precisely the arbitrariness the rule existed to remove. The guarding discipline is to pair the reopen condition with an escalation path so a stuck backlog triggers added capacity rather than an indefinite freeze, and to hold the rule against one-off exceptions.
How it implements the components¶
Cap Reopen Rule realizes the exit-from-full side of the archetype — the transition back to accepting work:
reopening_or_relief_rule— it is the rule for leaving the full state: the pre-committed condition, with headroom, under which intake resumes.capacity_escalation_path— when drainage alone will not clear the backlog, the rule conditions reopening on escalated relief capacity being confirmed rather than on wishful waiting.capacity_basis— the reopen threshold and sustain window are grounded in real drain rate and recovered throughput, so reopening reflects genuine capacity, not pressure.
It does not sense or display the fill level that tells it recovery has happened — that backlog_visibility_signal is produced by Queue Capacity Alert, which this rule consumes — and it does not itself refuse arrivals while closed, the admission_gate owned by Bounded Queue Capacity.
Related¶
- Instantiates: Bounded Backlog — the reopen rule governs the archetype's return from a closed, full state to accepting work.
- Consumes: Queue Capacity Alert — the utilization and drain-rate signal that tells the rule whether its reopen condition has been met.
- Sibling mechanisms: Bounded Queue Capacity · Queue Capacity Alert · Ticket Backlog Cap · Waitlist Cap · Finite Inbox Policy · Intake Pause
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Defines the exact condition under which a closed intake reopens, so a full backlog resumes accepting work on evidence of recovered capacity rather than on pressure or favoritism, making its operative form a standing rule, threshold, contractual commitment, or policy constraint governing future conduct.
Independent corroboration: The frozen evidence defines Cap Reopen Rule as 'Defines the exact condition under which a closed intake reopens, so a full backlog resumes accepting work on evidence of recovered capacity rather than on pressure or favoritism', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Systems Thinking & Cybernetics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Control theory supplies hysteresis: separate closing and reopening thresholds prevent rapid oscillation around a single boundary.
Related originating lineages:
- Operations Research — Queueing and capacity models supply backlog depth, sustained drain rate, and verified relief as reopening evidence.
- Organizational & Management Science — Intake governance supplies precommitment, equal access, announced reopening, and escalation when the queue cannot drain.
Review resolution: Systems and cybernetics are primary because separate close and reopen thresholds implement hysteresis to prevent oscillation. Queueing theory supplies capacity and drain-rate logic, while organizational intake governance supplies fair reopening and escalation; their combination is a multi-domain Encyclopedia synthesis.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The Cap Reopen Rule is the natural counterpart of an Intake Pause: the pause governs closing intake under overload, this rule governs reopening it. A pause without a reopen rule is exactly how a "temporary" closure becomes permanent by neglect — which is why the two belong together, one deciding when the door shuts and the other the precise, non-discretionary condition under which it opens again.
[n1] Hysteresis — in control systems, the deliberate use of two different thresholds (one to switch on, a lower one to switch off, or vice versa) so a system does not rapidly oscillate around a single set point. A thermostat that heats to 21°C but does not call for heat again until 19°C is the everyday example; a reopen threshold set below the closing cap applies the same principle to a backlog. ↩