# breach_scenario

## Purpose

This document defines the operational sequence and system behavior during an SCP containment breach.

It describes how database entities interact during breach detection, escalation, response and recontainment.

---

## Trigger Conditions

A breach scenario begins when:
- Updates `status` value in **scp_status** to 'breach'.
- Containment integrity is confirmed as compromised.
- SCP is verified outside approved containment conditions.

---

## Phase 1: Breach Detection

### System Actions
- `status` value in **scp_status** = 'breached'
- `current_act` value in **scp_status** = 'emergency'
- `started_at` value in **scp_status** = NOW()

### Logging

**incident_log**: 'containment_breach'

---

## Phase 2: Location Lockdown

### System Actions
- Updates `state` value in **location_state** accordingly.
- Restrict affected `location` zones to MTF units only.
- All experiments must be 'paused' or fully 'aborted'.

### Logging

**incident_log**: 'containment_breach'

---

## Phase 3: Security Personnel Deployment

### System Actions

- Assign relevant MTF units to breached location.

### Task Generation
Automatically create tasks:
- `type = containment_response`
- assigned to:
  - MTF personnel

### Logging
**activity_log**: 'mtf_deployment'

---

## Phase 4: Containment Response

### Possible Outcomes

#### Successful Recontainment

- **scp_status.status** = 'contained'
- **scp_status.current_act** = 'idle'
- **scp_status.started_at** = NOW()

---

#### Partial Containment (ongoing threat)

- **scp_status.status** = 'contained'
- **scp_status.current_act** = 'emergency'

Used when SCP is forced back into containment but remains unstable.

---

#### Failure

- **scp_status.status** = 'breached'
- SCP remains breached.
- Additional MTF units may be deployed.

---

## Phase 5: Incident Closure

Incident is considered closed when:
- SCP is fully contained.
- No active emergency state exists.
- All related tasks are completed.

System Actions:
- Close all active **task** entries related to breach.
- Updates `state` value in **location_state** accordingly.

---

## Notes

- A breach does not imply total escape; it indicates loss of containment integrity.
- Transport, experimentation, and maintenance operations must never trigger breach state.
- All breach scenarios must be fully traceable via logs without manual reconstruction.