# containment_rules

## Purpose

This document defines facility-wide containment policies, containment status transitions, monitoring requirements and emergency response procedures.

These rules apply to all SCP entities managed by the facility unless explicitly overridden by documented special containment procedures.

---

## Containment States

### contained

An SCP is considered contained when:
* The SCP remains within its containment chamber.
* All containment requirements defined in the **containment_ordinary** and **containment_special** tables are satisfied.

### breached

An SCP is considered breached when at least one of the following conditions occurs:
* The SCP breaches its containment chamber.
* Personnel safety or facility integrity is directly threatened by the SCP activity.

When status is 'breached':
* An log in **incident_log** must be created.
* SCP status must be changed to 'breached'.
* Task in **task** table must be made for a coresponding MTF squad to deal with the breached SCP.

### unknown

An SCP is considered breached when at least one of the following conditions occurs:
* Its current location cannot be verified.
* Monitoring systems have failed for an extended period.
* Available information is insufficient to determine containment status.

When status is 'unknown':
* `current_act` in scp_status must be NULL.
* A containment review must be initiated.
* The SCP shall be treated operationally as breached until status is restored.

---

## Containment Procedures

### Ordinary Containment

Ordinary containment procedures define standard containment conditions.

Ordinary containment includes:
* Physical barriers.
* Monitoring systems.
* Guard count.
* Environmental controls.

### Special Containment

Special containment procedures define additional containment requirements.

Special containment may include:
* Behavioral restrictions.
* Emergency actions.
* Personnel limitations.
* Experimental restrictions.
* Unique containment mechanisms.

---

## Monitoring Requirements

### none

No continuous monitoring is required.

Typically used for:
* Inactive SCPs.
* Unmonitorable SCPs.

### passive

Monitoring occurs through periodic inspections or scheduled reviews.

Requirements:

Typically used for:
* Safe SCPs

### active

Continuous monitoring is required.

Typically used for:
* Euclid and Keter SCPs

### restricted

Restricted monitoring is used when exposure to monitoring data presents operational risk.

Typically used for:

* Memetic and psychological SCPs

---

## Environmental Control


When environment_control is FALSE (0):
* Environmental conditions are not considered part of containment.

When environment_control is TRUE (1):
* SCP must have some enviromental control to remain contained

---

## Guard Requirements

General guidelines:
* Safe SCPs may require no dedicated security personnel.
* Euclid SCPs should have at least one assigned security guard.
* Keter SCPs should have at least two assigned security guards.

Assigned security personnel serve two primary functions:
1. Access control; ensuring that only authorized personnel may enter the containment area.
2. Initial containment response; acting as the first line of defense in the event of a containment breach.

---

## Experiment Interaction

### Experiment Authorization

Experiments may only be approved when:
* `status` value in **scp_status** is 'contained'.
* Required personnel are available.
* **experiment_dclass** and **experiment_personnel** must be filled with coresponding personnel.

### During Experiment

During an experiment:
* `current_act` value in **scp_status** must be set to 'experiment'

### Experiment Failure

An experiment failure occurs when:
* The experiment objective cannot be completed.
* Safety requirements are violated.
* Unexpected SCP behavior prevents continuation.

---

## Incident Logging

The following events must generate an incident_log entry:

* Containment breach.
* Security system failure.
* Environmental control and monitoring failure.
* Any other security failiure and breach.

Severity should be determined by operational impact.

---

## Activity Logging

The following events should generate activity_log entries:

* SCP status changes.
* Personnel access to SCP records.
* SCP transport operations.
* Experiment initiation.
* Experiment completion.
* Maintenance activities.
* Facility and zone access.