Quarantine Process¶

Containment procedure — instantiates Boundary Permeability Control

A holding buffer that separates uncertain or risky crossing objects for a defined period until they are tested, cleared, treated, expired, or rejected.

A Quarantine Process handles the crossing attempts that can't yet be resolved. What makes it this mechanism is that it does not decide at the boundary at all — it diverts the uncertain object into an isolated holding state and waits, letting time and testing surface a risk that a snap admit-or-reject decision would miss. Its defining move is converting "decide now, under uncertainty" into "decide later, with evidence." Every other sibling makes a call at the line; the quarantine process buys time behind it, and it is the sole owner of the holding buffer that the whole archetype's harder cases fall into.

Example¶

A plant-import station receives nursery stock from overseas. Rather than admit the plants on sight (risking an undetected pest) or destroy them outright (wasting legitimate stock), inspectors place them in a post-entry quarantine glasshouse for a defined incubation period. During the hold the plants are watched and tested for pests and pathogens that only become detectable over time. Clean stock is released into the country; infested stock is treated or destroyed; anything still ambiguous stays held for another cycle. The value the boundary gains is entirely in the delay: a threat that would have crossed invisibly on day one reveals itself by week three, and the decision is made on evidence rather than on a guess at the gate.

How it works¶

Divert, don't decide. The uncertain object is moved into an isolated buffer instead of being admitted or rejected at the boundary.
Hold for a defined period. The wait is deliberate and bounded — long enough for latent risk to surface, not open-ended.
Test to clear. Observation or testing during or after the hold produces the evidence the eventual decision needs.
Resolve. The object ends in release, treatment, expiry, or rejection — the deferral finally becomes a decision.

Tuning parameters¶

Hold duration — long enough to reveal the risk versus the cost of delay. The central dial: too short misses slow-emerging threats, too long strands the crosser.
Isolation strictness — how completely the held object is separated. Tighter isolation contains more but costs more space and handling.
Clearance-test rigor — how thoroughly the object is tested before release; a weak test makes the whole hold theater.
Buffer capacity — how many objects can be held at once before quarantine itself becomes the bottleneck.
Timeout disposition — the default when the hold expires unresolved: release or reject. Sets which error the process makes under backlog.

When it helps, and when it misleads¶

Its strength is handling the genuinely uncertain without a premature admit-or-reject, since time itself surfaces latent risk that no instant test could.

Its failure modes are the two ways a hold goes wrong. Held too long, it imposes real cost — spoilage, stranded people or goods, a full buffer that becomes its own bottleneck; released too early, usually to clear a backlog, it defeats its entire purpose. And a hold with no clearance test attached is just delay dressed up as caution. The classic misuse is quarantine as indefinite limbo — objects or people held without a resolution path — or clearing everything on timeout without ever inspecting. The discipline that guards against this, in the spirit of the precautionary principle^[1] it embodies, is to attach a real clearance test, bound the hold, size the buffer to demand, and define in advance what happens when the clock runs out.

How it implements the components¶

Quarantine Process fills the hold-and-resolve components:

quarantine_buffer — the isolated holding state itself, where uncertain objects wait; this mechanism owns it.
inspection_or_validation — the clearance test performed during or after the hold.
safe_rejection_or_deferral_path — the deferral is the mechanism, resolving to release, treatment, expiry, or rejection.

It makes no crossing decision at the boundary and runs no filtering ruleset — those are Border Checkpoint and Intake Filter; it holds rather than admits.

Instantiates: Boundary Permeability Control — quarantine is the hold-under-uncertainty buffer behind the boundary.
Sibling mechanisms: Border Checkpoint · Intake Filter · Semipermeable Membrane · Firewall · API Gateway · Customs Process · Cleanroom or Airlock · Clinical Screening · Content Moderation Gate · Data Import Validator · Data Loss Prevention

Notes¶

Quarantine is the archetype's answer to a specific gap: what to do when the boundary cannot yet tell safe from unsafe. It complements rather than competes with the deciding gates — a Border Checkpoint or Clinical Screening refers its genuinely-uncertain cases into quarantine, which holds them until a decision is possible. Its worth is bounded by the clearance test it wraps: without one, it adds delay without adding information.

References¶

[1] The precautionary principle — where a crossing may cause serious harm and the evidence is not yet in, the burden falls on showing it is safe before allowing it. Quarantine operationalizes this by holding the uncertain until testing resolves it, rather than defaulting to admit or reject under ignorance. ↩