Reference
Data Records
Report System record types, fields, side effects, and where operators see each record.
First created Last updated
reportsrecordsschemareference
Overview
This reference maps operator surfaces to the records they read or mutate. It is not a database schema dump; it explains which record matters for which workflow.
Record map
flowchart LR incident["Incident report"] --> revision["Incident report revisions"] incident --> watch["Watchlist entry"] incident --> ban["Ban entry"] incident --> cross["Cross-ban decision fields"] ban --> appeal["Network ban appeal"] appeal --> appealRev["Appeal revisions"] profile["Person profile"] --> link["Person profile links"] link --> incident profile --> audit["Profile audit log"]
Records and surfaces
| Record | Primary fields operators see | Surfaces |
|---|---|---|
| Incident report | Report number, status, severity, summary, platform, people fields, violation fields, evidence, witnesses, actions, appeal process, cross-ban fields. | New Report, Report Detail, Manage Report, All Reports, My Reports. |
| Report revision | Revision number, change kind, actor email, changed fields, field changes, created time. | Report Detail. |
| Watchlist entry | Scope, type, status, summary, linked report, partner, network scope when applicable. | Watchlists, Bans, Report Detail. |
| Local ban action | Action types, local action type, ban type/scope, action date, action end. | Manage Report, All Reports, Bans, Report Detail. |
| Cross-ban decision | Recommendation flag, decision, reason, decided time, network ban scope. | Cross-ban Requests, Report Detail. |
| Network ban appeal | Appeal reason, status, review notes, submitting partner, timestamps. | Network Ban Appeal, Ban Appeals, Cross-ban Requests. |
| Appeal revision | Previous reason, new reason, changed time. | Network Ban Appeal, Ban Appeals. |
| Person profile | Display name, aliases, handles, real names, emails, notes, links, audit log. | Person Profiles. |
| Person profile link | Profile ID, incident report ID, subject role. | Person Profiles, linked Report Detail. |
Inputs that mutate records
| Input/control | Record changed |
|---|---|
| Submit report | Incident report, first revision, local watchlist/ban side effect. |
| Manage Report Save | Incident report and revision history. |
| Add/Edit/Remove local ban | Incident report action fields and local action type. |
| Cross-ban decision confirm | Incident report cross-ban decision fields and network ban side effect when approved. |
| Submit/update/resubmit network appeal | Network ban appeal and appeal revisions. |
| Approve/deny network appeal | Network ban appeal decision fields and review notes. |
| Create/edit/delete person profile | Person profile and profile audit log. |
| Link/unlink report to profile | Person profile link and profile audit log. |
End-to-end operator runbook
- Identify record: Start with the route and row type.
- Find source: Use Report Detail for incident facts and revisions.
- Trace side effects: Check Watchlists, Bans, Cross-ban Requests, Appeals, and Profiles for linked state.
- Verify mutation: After any save, reopen the relevant surface and check the record changed.
- Capture handoff: Name the record type, report number, affected route, and reviewer.
Common mistakes
Do not treat person profiles, watchlist entries, or appeal reasons as replacements for the incident report. The incident report remains the source record for facts.