When something goes seriously wrong in the network (a ban, a rule change, or
a loss of trust in the team) it gets an incident record. Each record is a
plain, third-person account written after the fact: what happened, how the
team handled it, what the outcome was, and what changed as a result.
Incident records are not the full internal report. They do not reproduce
chat logs or screenshots, and they describe people by their role in the
events rather than by name. Their purpose is accountability: members should
be able to see why a rule exists and how the team has handled, and sometimes
mishandled, past situations.
| Severity | Meaning |
|---|
| Low | Resolved in-chat; nothing beyond a warning. |
| Medium | Required admin action and/or a member left. |
| High | Bans, rule changes, or damage to trust in the team. |
| Status | Meaning |
|---|
| Open | Still being handled. |
| Monitoring | Handled; watching for recurrence. |
| Closed | No further action expected. |
| ID | Date | Chat(s) | Severity | Status |
|---|
| 260819 | 19 to 20 August 2026 | CatShark TreeHouse | High | Monitoring |
