Feature status and availability
Read audience, availability, and maturity as three independent labels before relying on a ModFlow workflow.
- Audience
- moderator · senior reviewer · team lead · server admin · public appellant
- Availability
- free
- Maturity
- stable
Last reviewed
On this page
Three independent status axes
| Axis | Question answered | Examples |
|---|---|---|
| Audience | Who is the guide for? | Moderator, senior reviewer, team lead, server administrator, public appellant |
| Availability | Under what access condition can it be used? | Free, Premium, Premium preview, Feature-flagged, Private-beta access |
| Maturity | How complete and settled is the behavior? | Stable, Beta, Alpha, Experimental, Partial, Deprecated |
Use status in a workflow
Check audience
Confirm the job and permission boundary match the person acting.
Check: The workflow begins with the intended operator role.
Check availability
Confirm the selected server's current access, entitlement, and feature flag where applicable.
Check: The entry point should be available for this server now.
Check maturity
Read limitations and recovery before relying on an alpha, experimental, partial, or deprecated surface.
Check: Expectations match implemented behavior.
Trust current state
Use the current guide header and in-product response over stale screenshots or remembered access.
Check: The latest verified status controls the decision.
Use a feature availability decision tree
Is the guide intended for your role?
Read the audience badges.
Check: The job matches the documented operator.
Is the server approved?
Confirm selected-server private-beta/runtime access.
Check: The server can enter ModFlow.
Is the capability included?
Read Free/Premium or current feature gate.
Check: Entitlement is known.
Is a rollout flag required?
Read feature-flag/preview status.
Check: The surface is currently exposed or intentionally hidden.
Do you have the exact permission?
Check Discord and ModFlow team permission.
Check: The viewer can perform the intended read/write.
Is the current state valid?
Check target hierarchy, workflow state, source visibility, and record readiness.
Check: The operation can proceed now.
Is the maturity acceptable?
Read Alpha/Beta/Partial limits and recovery.
Check: Expectations match implementation.
Interpret common combinations
| Labels | Meaning | Operator response |
|---|---|---|
| Free + private-beta + Alpha | Included for approved servers, but still early and subject to limits. | Use documented workflow and verify outcomes. |
| Premium preview + Partial | Controlled access can exist while some states/side effects remain incomplete. | Read recovery and avoid broad reliance. |
| Feature-flagged + Beta | Core workflow may be mature enough for controlled use but can be hidden by rollout state. | Trust current server response. |
| Premium + locked | Current server entitlement does not include the feature. | Use documented alternative; do not bypass. |
| Placeholder/reserved | No approved operating procedure is published. | Do not experiment on live data; use stable alternatives. |
| Deprecated/compatibility-only | Old path/name is not the current guide contract. | Use current command/page. |
Find actively changing features
Actively changing product areas are intentionally absent from stable workflow guides. Reserved guides lists only their names and future curriculum locations; it does not publish commands, options, screenshots, or behavior claims.
Report status drift
Capture the guide header
Record audience, availability, maturity, and last-reviewed date.
Check: The documented expectation is precise.
Verify the live surface
Use autocomplete or the selected-server page once.
Check: The current actual state is captured.
Describe the mismatch
State expected versus actual result with server, route/command, time, and safe identifiers.
Check: Maintainers can reproduce it.
Avoid live experimentation
Do not probe excluded or high-impact writes to discover behavior.
Check: No member/data is harmed.
Send through the published contact
Exclude credentials and private content.
Check: The report reaches the product owner without exposing private data.
Current status matrix
| Feature | Status boundary |
|---|---|
| Dashboard Jail and appeal conversations | Available where enabled; delivery still depends on Discord permissions and the server setup. |
| Native expanded event logging | Event coverage varies by deployed version. Check the available categories and test delivery. |
| Watchlist core | Dashboard and Discord workflows are in beta; check availability and permissions for your server. |
| Assignments | Controlled preview while workflows and connections continue changing. |
| Ban Review | Beta/partial and awaiting deployment-specific Discord rehearsal. |
| MIRA | Coming soon, default-disabled, and gated. |
| Moderator Scorecards | Default-off controlled preview. |
| Automation Rules | Configuration only; runtime evaluation is not confirmed. |
| Jail Escape Protocol | Default-off experimental feature; no supported public workflow. |
| Generic multi-server controls | Placeholder; trusted-network sharing is narrower and separate. |