Skip to content

Intake Inspection and Quarantine Protocol

Protocol — instantiates Invasive Entrant Containment

A screening and temporary isolation procedure for new imports, accounts, code, materials, practices, or organisms before full admission.

The Intake Inspection and Quarantine Protocol is a screen-and-hold procedure applied to each first-time candidate at the admission boundary: inspect it against a checklist of risk traits, hold it in a limited-privilege isolation for a defined observation window, then admit, reject, or conditionally release. Its defining idea is that it acts on an individual newcomer at the moment of admission, and it buys safety by a temporary, reversible hold rather than by shutting the door. It is not ongoing governance of traffic on an open route, and it is not a barrier against an entrant that has already spread — it is the antechamber every new arrival passes through once, before it is trusted with full reach inside the protected system.

Example

An engineering team keeps pulling in third-party libraries, and one compromised dependency would run with production privileges. The team installs an intake protocol for every new dependency. First, inspection: provenance and maintainer history, the permissions the package requests, a diff of its transitive dependencies, and a known-vulnerability scan against the trait checklist. Second, quarantine: the package is installed only in a sandboxed build with no network egress and no access to secrets, then left to soak in staging for a fixed window while its actual behavior is watched. Third, the gate: it joins the production allowlist only after a clean soak, otherwise it is pinned to a reviewed version or rejected.

A newly popular logging library sails through inspection on reputation but requests filesystem and outbound-network scopes it has no reason to need — a trait cue. Held in the sandbox, it phones home to an unfamiliar host on first startup. It is rejected before it ever touches production. The system stayed open to new libraries; it simply made each one earn admission.

How it works

The distinctive machinery is a three-outcome gate — admit, hold, reject — wrapped around a mandatory isolation environment in which the candidate runs without full privilege or reach for a set observation period. The inspection step applies the entrant trait profile as a pass/fail screen; the quarantine step exercises the candidate under confinement so latent behavior surfaces before admission, not after. A proportionality rule tiers the rigor: low-risk, well-provenanced items clear on a fast path, while novel or high-privilege ones get the full soak. Every decision is reversible until admission, which is what lets the protocol be cautious without being closed.

Tuning parameters

  • Quarantine duration — a longer soak catches slow-manifesting risk but delays every admission and tempts teams to bypass the gate.
  • Screening depth vs. throughput — manual review versus automated scanning; deep review raises catch rate but throttles intake.
  • Isolation tightness — how much capability the held item is granted. Tighter confinement is safer but starves observation of realistic behavior.
  • Risk-tiering threshold — what share of candidates take the fast path versus full quarantine, trading throughput against coverage.
  • Timeout disposition — fail-open or fail-closed when the observation window expires without a verdict.

When it helps, and when it misleads

Its strength is that it closes the boundary-admission gap without closing the boundary: it is the operational form of a precautionary[n1] hold that stays reversible, so the system keeps taking in new things while denying any of them instant, unearned trust. It is the right tool exactly when admission is a discrete, per-item event you can pause.

Its failure mode is that quarantine only catches what manifests during the hold: a sleeper that stays dormant through the soak is admitted clean, and the tidy pass/fail record makes that false clearance look like proof of safety. The classic misuse is quarantine theater — a hold with no real observation, or a gate so onerous that teams route around it and grow a shadow inventory of unscreened imports. The guarding discipline is to scale hold length and scrutiny to a genuine risk tier and to actively exercise the item during the hold rather than merely parking it.

How it implements the components

  • protected_system_boundary — it operationalizes the admission line, defining what counts as "inside" (the production allowlist, the trusted zone) versus the quarantine antechamber that precedes it.
  • entrant_identity_and_trait_profile — the inspection checklist is the trait profile turned into a pass/fail screen applied at the moment of intake.
  • collateral_impact_and_legitimacy_guardrail — the temporary, reversible, risk-tiered hold keeps screening proportional, so the protocol buys time without permanently excluding legitimate novelty.

It does NOT govern repeated crossings on an already-open pathway (arrival_pathway_map, cross_boundary_coordination_protocol) — that is its nearest twin Movement Permit or Access Gate, which authorizes ongoing traffic and has no quarantine hold; and it does NOT catalog and rank every route (native_control_gap_assessment) — that is Pathway Risk Register.

Editorial Notes

Form Classification

Form family: Experiment, Test & Rehearsal

Rationale: Intake Inspection and Quarantine Protocol operates as a bounded trial, probe, simulation, or rehearsal that generates evidence from performance because it a screening and temporary isolation procedure for new imports, accounts, code, materials, practices, or organisms before full admission

Independent corroboration: The frozen evidence defines Intake Inspection and Quarantine Protocol as 'A screening and temporary isolation procedure for new imports, accounts, code, materials, practices, or organisms before full admission', so its operative form is Experiment, Test & Rehearsal.

Nearest alternative: Decision, Gate & Allocation — Mandatory quarantine deliberately exercises the candidate under confinement, so testing dominates the eventual admission decision.

Review outcome: Independent reviewer agreement; medium confidence.

Origin Attribution

Primary origin: Medicine & Healthcare

Origin pattern: Convergent development

Present-day reach: Universal

Rationale: Screening and temporary isolation before admission has its oldest characteristic institutional lineage in public-health quarantine.

Related originating lineages:

Review resolution: Both independent reviews place the primary lineage in medicine_healthcare. The queued differences (reported_ambiguity, alternate_origin_disagreement, origin_mode_disagreement, encyclopedia_synthesis_disagreement) concern secondary metadata rather than primary provenance. The final retains agricultural_science, computer_science, security_intelligence only where a reviewer supplied a formative-lineage rationale; this does not convert downstream applicability into origin. origin_mode=convergent because the reviewers document independently established or materially co-developing traditions. domain_reach=universal records application breadth separately from provenance.

Attribution caveat: Quarantine has ancient public-health roots but independently mature agricultural and security forms; this generalized protocol intentionally spans them.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Reconciled after independent review; medium confidence.

Notes

[n1] The precautionary principle holds that when an action risks serious or irreversible harm, the burden of proof falls on showing it is safe before proceeding. Intake quarantine is the reversible, per-item form of that stance: hold and observe until the candidate has earned admission, rather than admit and hope.