# Data Flow

## Overview

This document describes how data moves through the Site-19 Database System.

---

## Personnel Data Flow

Personnel data remains mostly static, with dynamic updates occurring in the state layer.

- Personnel record is created in **personnel** table
- Runtime status is tracked in **personnel_state** table
- Application layer updates state based on **task_description** table
- Clearance level determines accessible operations and SCP visibility

---

## D-Class Personnel Data Flow

D-Class follow a controlled lifecycle model:

- D-Class is registered in the **dclass** table
- D-Class are assigned a 30 day operational lifespan. Upon expiration, their status transitions to terminated.
- Runtime status is tracked in **dclass_state**
- Application layer updates state based on **task_description** table

---

## SCP Data Flow

SCPs follow a controlled lifecycle model:

- SCP is registered in the **scp** table
- Runtime status is tracked in **scp_status**
- Containment parameters are defined in **containment_ordinary** and **containment_special** tables
- Application layer updates state based on **task_description** table

---

## Access Control Flow

All data access is controlled by a clearance based permission model:

- Clearance level is verified before any read/write operation
- SCP access is restricted by clearance level
- Personnel actions are validated against role permissions

---

## Application Interaction Flow

The web application (will) serves as the primary interface between user and the database:

- User request operations via web interface
- Application validates authorization via clearance level
- SQL operations are executed based on allowed actions
- Results are returned and logged in logging tables

---

## Audit and Traceability

All critical operations are designed to be traceable:
- State changes and tasks include timestamps
- Any event is logged in logging tables

---

## Summary

The system operates on a controlled data lifecycle model where static entities define structure, state tables track runtime conditions and the application layer governs all of the interactions.