Glossary
Understand the user-facing workflow, access, evidence, review, and status terms used throughout ModFlow.
- Audience
- moderator · senior reviewer · team lead · server admin · public appellant
- Availability
- free
- Maturity
- stable
Last reviewed
On this page+
Workflow terms
Moderation workflow definitions| Term | Definition |
|---|
| Signal | A report, command, message, alert, or record that starts staff review. |
| Evidence | Visible material preserved with source identity for an authorized review. |
| Decision | Human judgment recorded by an authorized reviewer. |
| Execution | A separate attempt to apply the requested Discord action. |
| Record | The stored state and timeline used to reconstruct what happened. |
| Appeal | A request to review a moderation decision without exposing private staff discussion. |
| Ban Review | A senior-review flow that keeps a decision separate from the action that follows. |
Access and status terms
Access and documentation definitions| Term | Definition |
|---|
| Server scope | The one selected Discord server whose records and permissions apply. |
| ModFlow team | A server-configured mapping from Discord roles to specific ModFlow capabilities. |
| Redaction | Intentional omission of restricted detail while preserving a safe usable summary. |
| Audience | The operator role for whom a guide or workflow is intended. |
| Availability | The access condition, such as free, preview, feature-flagged, or private-beta access. |
| Maturity | How complete and settled the documented behavior is, independently of availability. |
| Provenance | The source identity and context that explain where a record or evidence item came from. |
Case and evidence terms
Case terminology| Term | Definition |
|---|
| Case ID | Internal identity used by APIs, links, buttons, and related records. |
| Case number | Human-facing number allocated within one Discord server. |
| Occurred at | When the incident/action happened for chronology. |
| Created at | When ModFlow stored the record; can be later than occurrence. |
| Case activity/timeline | Attributable events showing how the Case changed over time. |
| Source message | Discord message identity used as provenance for evidence/context. |
| Conversation window | A limited set of nearby source messages captured for context. |
| Evidence visibility | The staff/senior/team boundary controlling who can inspect an evidence item. |
| Restricted/redacted | Detail intentionally hidden while a safe workflow summary remains. |
| Key evidence | Evidence explicitly marked for reviewer attention; not automatic proof. |
| Review Queue | Cases waiting for authorized staff review. |
| Claim/reassign | Assign responsibility for reviewing a Case to a person/team. |
| Escalation | Routing work to a higher-authority review path without deciding it automatically. |
Moderation and execution terms
Action terminology| Term | Definition |
|---|
| Initiator/requester | The moderator or system that requested an action. |
| Executor | The bot/system/actor that applied the action. |
| Timeout/mute | Discord native timeout plus matching voice-mute workflow where relevant. |
| Jail | Configured role/channel restriction workflow with an active jail record. |
| Temporary ban | Real Discord ban with a stored future expiry attempt. |
| Purge days | How many recent days of messages Discord is asked to delete during a ban. |
| Undo | Reversal of the invoking moderator’s latest still-effective mute, jail, or ban on a member. |
| Decision | Authorized human judgment recorded in a workflow. |
| Execution | Separate attempt to apply the requested external action. |
| Idempotency/action key | Workflow mechanism that can return an existing matching execution instead of duplicating it. |
| Partial success | Primary result completed while a secondary effect failed or remains pending. |
| Retryable | Recorded state that explicitly permits another attempt after the cause is corrected. |
People, data, source, and privacy terms
Data terminology| Term | Definition |
|---|
| Native record | Event/action observed or created directly through ModFlow’s runtime. |
| Imported record | Normalized supplemental observation from an approved external source. |
| Provider | Source bot/system that produced an imported observation; not automatically the human actor. |
| Confidence | Parser certainty for an imported interpretation; not truth, guilt, or risk. |
| Activity | Metadata-only operational event history separate from the Moderation Log. |
| Retention | How long data is expected to remain available under the documented current policy/default. |
| Coverage gap | A known time, source, or event range that may be missing because of retention, downtime, access, or query limits. |
| Export | Point-in-time permission-limited downloaded copy of supported server data. |
| Consent notice | Information shown about a recorded session’s purpose and capture behavior. |
| Consent state | The participant’s recorded response through the implemented session control. |
| Artifact | Produced recording, transcript, file, or evidence item whose availability and visibility are separately tracked. |
| Least privilege | Grant only the minimum page/record/action capability required for the job. |
Access and feature-status terms
Status terminology| Term | Definition |
|---|
| Free | Included by the current public access catalog; other approval/permission/maturity checks still apply. |
| Premium | Requires the current Premium entitlement; not a readiness guarantee. |
| Premium preview | Can be exposed for controlled review even when commercial enforcement/availability is limited. |
| Feature-flagged | A production or rollout control can independently enable or hide the feature. |
| Private-beta access | The server has the approval state required to enter the current runtime. |
| Stable/Beta/Alpha/Experimental/Partial | Maturity labels describing completeness and confidence, independent of price/access. |
| Placeholder/reserved guide | A documentation location with no operating instructions while the feature is excluded or unfinished. |
| Compatibility alias | Legacy internal route/name that may still work but is not the current documented entry point. |
New workflow terms
Terms introduced by newer workflows| Term | Meaning |
|---|
| MIRA | ModFlow Investigative Reasoning Agent, a coming-soon AI-assisted Case review feature that cannot execute moderation. |
| Native event log | A configured Discord/ModFlow event rendered to a selected Discord destination. |
| Outbox | Durable pending-delivery state used for retries and delivery health. |
| Watchlist signal | A review input that may remain silent; it is not proof or a sanction. |
| Watchlist alert | A routed review item that can be acknowledged, snoozed, resolved, or closed as a false positive; Case handoff is explicit. |
| No Contact | A configured relationship rule that can support separation and voice enforcement. |
| Assignment or squad | A staff work item and its selected responsible group, subject to source visibility. |
| Provider connection | A revocable OAuth authorization used to list and import selected external files. |
| Source artifact | A retained snapshot or derivative with provenance used during review. |
| Participant-facing identity | The name or team label shown to a participant; internal audit attribution remains available to authorized staff. |
