# Protected Files

Truth document. Use for: documenting critical files that need approval before modification.

This doc answers *what is protected and why breaking it hurts* — nothing more. Don't duplicate function-level detail here (signatures, inputs/outputs): it drifts from both the code and the owning feature doc. The owning feature doc is the canonical reference for how the code works; link to it.

```
# Protected Files

Critical files requiring approval before modification.

## File List

# Category 1 - Description
path/to/critical/file1.js
path/to/critical/file2.js

# Category 2 - Description
path/to/another/file.js

## Risk Summary

| Category   | Risk if Broken  |
|------------|-----------------|
| Category 1 | Specific impact |
| Category 2 | Specific impact |

## Why Protected

### Category 1: [Name]

**Purpose:** What these files do, one or two lines
**Owning doc:** [docs/features/{feature}.md] — canonical reference for how this code works
**Invariants:**
- The behavior that must not break, stated as a constraint (not a function tour)
- Important point 2
```