Furries PH Docs
Dashboard
Report system docs

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

RecordPrimary fields operators seeSurfaces
Incident reportReport 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 revisionRevision number, change kind, actor email, changed fields, field changes, created time.Report Detail.
Watchlist entryScope, type, status, summary, linked report, partner, network scope when applicable.Watchlists, Bans, Report Detail.
Local ban actionAction types, local action type, ban type/scope, action date, action end.Manage Report, All Reports, Bans, Report Detail.
Cross-ban decisionRecommendation flag, decision, reason, decided time, network ban scope.Cross-ban Requests, Report Detail.
Network ban appealAppeal reason, status, review notes, submitting partner, timestamps.Network Ban Appeal, Ban Appeals, Cross-ban Requests.
Appeal revisionPrevious reason, new reason, changed time.Network Ban Appeal, Ban Appeals.
Person profileDisplay name, aliases, handles, real names, emails, notes, links, audit log.Person Profiles.
Person profile linkProfile ID, incident report ID, subject role.Person Profiles, linked Report Detail.

Inputs that mutate records

Input/controlRecord changed
Submit reportIncident report, first revision, local watchlist/ban side effect.
Manage Report SaveIncident report and revision history.
Add/Edit/Remove local banIncident report action fields and local action type.
Cross-ban decision confirmIncident report cross-ban decision fields and network ban side effect when approved.
Submit/update/resubmit network appealNetwork ban appeal and appeal revisions.
Approve/deny network appealNetwork ban appeal decision fields and review notes.
Create/edit/delete person profilePerson profile and profile audit log.
Link/unlink report to profilePerson profile link and profile audit log.

End-to-end operator runbook

  1. Identify record: Start with the route and row type.
  2. Find source: Use Report Detail for incident facts and revisions.
  3. Trace side effects: Check Watchlists, Bans, Cross-ban Requests, Appeals, and Profiles for linked state.
  4. Verify mutation: After any save, reopen the relevant surface and check the record changed.
  5. 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.

All docs