Mod Vanguard

VISIT HERE: https://github.com/d3v07/modcase_reddit

Inspiration

Mod Vanguard was inspired by the messy reality of subreddit moderation. When a busy community gets a burst of reports, the hardest part is often not the final action. It is reconstructing context, seeing who is already handling the case, checking how similar situations were handled before, and keeping the whole team consistent.

I wanted to build a tool that helps moderators move faster without taking judgment away from them.

$$ \text{Better moderation} = \text{context} + \text{coordination} + \text{consistency} $$

What it does

Mod Vanguard is a Devvit Web command center for Reddit moderation teams. It turns reports, moderator actions, appeals, and decisions into structured casefiles.

It includes a shared dashboard, report pressure clustering, casefile review, claim and handoff controls, searchable Decision Memory, Appeals Desk, Rule Ops analytics, Audit export, and Signal Intake health checks. The app keeps final decisions human-in-the-loop while making the surrounding workflow clearer and easier to audit.

How I built it

I built Mod Vanguard with TypeScript, React, Devvit Web, Hono, Zod, and Devvit Redis. The React frontend powers the moderator dashboard and review surfaces, while the Hono server handles typed API routes, Reddit event adapters, validation, idempotency, and storage.

The app uses shared Zod contracts so local preview data and runtime responses follow the same shapes. I also created synthetic demo content with 100+ moderation cases so the product can show realistic queue pressure without using real private user data.

Challenges I ran into

The biggest challenge was balancing speed with safety. I wanted the app to reduce moderator workload, but not create automatic enforcement, hidden decision logic, cross-subreddit data joins, or public moderator rankings.

Another challenge was keeping the local demo and real Devvit runtime aligned. Reports, menu actions, scheduler runs, Redis state, and browser preview all needed to flow through the same contracts so the demo stayed realistic instead of becoming a separate mock-only path.

Accomplishments that I am proud of

I am proud that Mod Vanguard feels like a complete moderation workflow instead of a single isolated feature. A moderator can start from a report burst, open a casefile, claim the work, review precedent, record a decision, handle an appeal, inspect rule trends, and export an audit trail.

I am also proud of the safety boundaries: subreddit-scoped storage, explicit moderator actions, auditability, deterministic workflows, and no external API dependency for the core demo.

What I learned

I learned that moderation tools need to optimize for trust as much as speed. Moderators need to know where data came from, whether the event stream is healthy, who owns a case, and why a prior decision matters.

I also learned that good internal tools need strong contracts. Shared validation, idempotent event handling, and scoped storage make the product easier to reason about and safer to extend.

What's next for Mod Vanguard

Next, I would harden the live Devvit playtest path, expand runtime coverage for more moderation events, add deeper configurable rule taxonomies, and improve modmail-related workflows.

I would also like to add richer team settings, better export controls, more accessibility checks, and more subreddit-specific customization while keeping the core principle the same: Mod Vanguard should organize context and coordination, while moderators stay in control of final decisions.

Built With

• api
• css
• devvit
• eslint
• hono
• javascript
• library
• node.js
• prettier
• react
• reddit
• redis
• scheduler
• tailwind
• testing
• tsx
• typescript
• vite
• vitest
• web
• zod