Reported puzzles
-
Awaiting data
Internal
Moderation Queue
Reported puzzles stay metadata-first until an operator explicitly inspects answer-bearing content. Use this triage list to sort severity, reason, and safe reporter context before taking action.
Queue readiness polish highlights launch-safe access, warning visibility, and explicit inspect boundaries so public content safety evidence is easy to read back during moderation/report queue checks.
Loading moderation queue...
Publish review
-
Awaiting data
Access
-
-
Data notes
-
No warnings loaded
Launch blocker
Reported puzzle triage list
Each row surfaces operator-safe metadata only: status chips, severity, report reason, reporter-safe metadata, and puzzle review context.
Use the warning list and access summary before opening inspect so queue triage stays metadata-first by default.
Secondary queue
Publish review queue
Pending public publish requests stay visible beside reports so operators can compare review state before launch.
Linked reports, severity, and readiness cues stay visible here without exposing answer-bearing puzzle content.
Operator notes