# location_state

## Purpose

This document defines the runtime operational behavior of all facility locations.

It describes how location states change over time, what triggers those changes and how those changes affect facility operations.

---

## Location State Behavior

### States
- normal
- locked_down
- maintenance
- compromised

### Transitions

#### normal/maintenance/compromised -> locked_down
- Hostile activity, an SCP breach, or another security threat has been detected.
- The location has been isolated from the rest of the facility.
- Entry is prohibited to all personnel except Mobile Task Force units.

#### locked_down/compromised -> normal
- The threat or breach has been successfully resolved.
- The location is returned to operational status.

#### normal -> maintenance
- The location is undergoing maintenance, repair, or reconstruction.
- SCP experiments within the affected location are prohibited for the duration of the maintenance period.

#### maintenance -> normal
- Maintenance, repair, or reconstruction has been successfully completed.
- The location is returned to operational status.

#### locked_down/compromised -> normal 
- Threat or breach has been succesfully resolved. 
- Location is returned to operational status.

#### locked_down/compromised -> maintenance
- The threat or breach has been successfully resolved.
- Repair operations have commenced. 

#### any -> compromised

One or more of the following conditions may apply:
- Containment integrity has been violated.
- Structural damage has occurred.
- Hostile forces have gained access.
- Hazardous conditions have been detected.

---

## Hazard Type Behavior

### Purpose

Hazard type defines the nature of the active threat affecting a location.

### Few Examples

- biological
- structural
- mechanical
- hostile

### Rules

- `hazard type` value may change as incident conditions evolve.

---

## Response Type Behavior

### Purpose

Response type defines the active operational procedure being executed in response to a location state change.

### Few Examples

- quarantine
- decontamination
- combat
- evacuation
- repair

### Rules

- `response_type` value may change as incident conditions evolve.

---

# LOGGING REQUIREMENTS

Every state transition must generate:

- **activity_log** entry (standard transitions)
- **incident_log** entry (security, containment or hazardous events)

---

# NOTES

- State changes are event-driven and should never be applied manually without triggering logs.
- Location state represents current operational conditions only and must not be used as a replacement for historical incident records.