Data Records Reference

Use This Reference Carefully

Use this guide when a safety, accountability, or follow-up record needs careful handling. In this guide, Data Records Reference narrows that work to plain-language map of the records created, updated, linked, and audited by the report system. Because this is a reference page, read it as part of the Report System learning path rather than as an isolated checklist.

A report is a written memory of something important. The goal is to protect people, keep facts clear, and leave enough context for future reviewers. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What This Reference Collects

This page is for checking details. Use it to confirm names, routes, records, fields, or certification points before relying on memory. The intended readers are Support leads and Senior operators. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /reports, /reports/manage?id=:incidentId, /reports/watchlists, and /reports/profiles.
• Records or contracts involved: Incident reports, Watchlist entries, Appeals, Profiles, and Revisions.
• Main care point: Watch for incomplete facts, unfair wording, privacy exposure, or a decision that another reviewer cannot understand later.
• Proof worth keeping: report ID, saved status, revision history, person profile, evidence note, reminder, reviewer decision, and handoff owner.

How To Find The Right Entry

1. Search for the exact name or route: Begin by naming the Report System situation, the owner, and the exact item involved in Data Records Reference.
2. Read the surrounding note, not only the matching line: Use /reports, /reports/manage?id=:incidentId, /reports/watchlists, and /reports/profiles to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Compare the reference with the live screen, file, or service evidence: Keep Incident reports, Watchlist entries, Appeals, Profiles, and Revisions in view so the work stays tied to the records or contracts it can affect.
4. Save the evidence that proves the entry was checked: Before handing off, save proof such as report ID, saved status, revision history, person profile, evidence note, reminder, reviewer decision, and handoff owner so another reviewer can understand the facts without relying on memory.

Confirm The Reference Still Matches Reality

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on people, privacy, fairness, evidence, and the trustworthiness of the record.
3. Proof is findable: The handoff points to evidence that another reviewer can understand the facts without relying on memory.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Choose the right path. Use this reference when you need to confirm a route, role, record, or certification expectation before acting. This anchors the work to the correct scope before any record changes.
2. Step 2 - Confirm scope and records. Find the dashboard surface or record type involved in the current task. Pause here and confirm the note is factual, fair, and reviewable.
3. Step 3 - Do the operating action. Compare what you see in /reports, /reports/manage?id=:incidentId, /reports/watchlists, /reports/profiles with the expected access, state, and records described here. This keeps the report useful to the next reviewer instead of only to the person writing it.
4. Step 4 - Verify the result. If something does not match, stop the workflow and capture the route, event/report ID, user role, and visible error state. The next action should still protect privacy, evidence, and due process.
5. Step 5 - Hand off remaining work. Return to the related operating guide after the reference question is answered. This leaves a handoff trail another operator can understand.

Record map

Record	Plain meaning	Created or changed from
Incident report	Main safety case record.	/reports/new, /reports/manage
Report revision	History of report changes.	Saves and status updates
Watchlist entry	Staff attention or enforcement marker.	Report action fields, watchlist surfaces
Local ban	Partner-scoped restriction.	Report action or ban surface
Network ban	Shared network restriction.	Network decision workflow
Cross-ban request	Request to share/enforce beyond one partner.	Cross-ban workflow
Network ban appeal	Appeal against network-scope restriction.	Appeal submission page
Appeal revision	History of appeal changes or resubmissions.	Appeal edits and decisions
Person profile	Identity grouping record.	Profiles page
Profile link	Connection between profile and report.	Profiles page
Profile audit entry	Changelog for profile edits and links.	Profile mutations

Field groups to understand

Group	Examples	Why it matters
Identity	Names, handles, emails, alternate accounts.	Prevents mistaken identity.
Incident	Date, place, violation types, detail.	Explains what happened.
Evidence	Witness notes, screenshots, links, statements.	Supports or challenges claims.
Action	Warning, watchlist, ban, appeal process.	Explains consequences.
Scope	Local, event, community, network.	Defines who is affected.
Audit	Revisions, profile audit entries, appeal revisions.	Makes later review possible.

Support lead rule

When changing report implementation, trace the whole path:

dashboard page -> runtime module -> dashboard-data helper -> API/RPC -> database record -> revision/audit record -> certification cleanup