> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elevatedsignals.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# The quality-event lifecycle

> How Invariant enforces a defensible deviation → CAPA → closure spine.

Invariant enforces one quality-event lifecycle server-side, so records cannot be short-circuited to
a falsely "closed" state.

```
Deviation ──▶ Classify ──▶ Investigate ──▶ Structured RCA ──▶ Linked CAPA
                                                                   │
                                                                   ▼
                                          Actions (with evidence) ──▶ CAPA "done"
                                                                   │
                                                                   ▼
                                       Effectiveness verified (independent, signed)
                                                                   │
                                                                   ▼
                                              Signed close (independent approver)
```

## Enforced gates (not conventions)

* A deviation **cannot close** without a documented RCA conclusion + a linked disposition.
* CAPA **effectiveness cannot be signed** before all actions are complete.
* A CAPA **cannot close** before effectiveness is verified.
* **Maker-checker:** the author/requester/owner cannot approve, close, or reopen their own record.
* **Reason for change** is required on every mutation of a previously recorded regulated value.
* Every controlled transition writes an **atomic, hash-chained audit entry** in the same transaction.

These gates are the difference between a system that *records* quality work and one that *enforces* it.