Season 2 · Episode 9

Group Red Flag Detector

4 builds shipped in 30 minutes, live.

The brief

Build a tool that lets a group review a plan together and anonymously flag concerns before it goes ahead. Someone shares a plan — a project, a trip, a decision, whatever the group is about to commit to. Each person in the group should be able to flag specific parts of it as a red flag, anonymously, so people actually say what they are worried about instead of staying quiet to avoid conflict. The tool then needs to surface those flags back to the group in a useful way — what got flagged, how many people flagged it, where the group actually has concerns. This is about surfacing honest, anonymous concern across a group before a decision is locked in, not just a comments section.

What “Group Red Flag Detector” meant

Every CampAI episode sets one theme and one constraint: 30 minutes, live, with AI doing the heavy lifting. Season 2's builders took “Group Red Flag Detector” in 4 different directions — the submissions below are what actually shipped inside the window, with the models used and the problems hit written up by the builders themselves.

Submissions

Every build

🏆 Winner

FAULTLINE — a blind, anonymous group review tool that exposes red flags before a plan gets locked in.

by rookepoole · 16 ratings

A host creates a room and adds a plan manually or imports a PDF, DOCX, TXT, Markdown, CSV, JSON, HTML, or RTF document. FAULTLINE breaks the plan into reviewable sections and shares them with separate no-sign-in guest profiles over WebRTC. Everyone reviews independently and anonymously, flagging specific sections with severity, concern type, and an optional explanation. Crucially, nobody sees anyone else's concerns during review, preventing the first objection from anchoring the group. Once everyone is ready, the host reveals the results and FAULTLINE ranks the plan's real fault lines by anonymous reviewer count, severity, and section.

SECONDED

by Auny 🧡 · 16 ratings

A concern is heard when a second person has it too. Paste a plan, one line per line, and share the room code. Reviewers tap lines to flag them with an optional one-line why, and everyone must flag at least two lines before sealing, so having flagged at all identifies nobody. The owner reveals once two people have sealed. A line's flag text unseals only when two independent people flagged it; a lone flag stays a black redaction bar reading "sealed · 1 of 2", for everyone, the owner included, forever. Tally marks and a heat bar show frequency, the footer names the heaviest lines. Then the owner must answer every seconded line (fix / accept / stop) before the stamp flips from NO GO to GO.

Red Baron

by Air Planes · 16 ratings

Open the link. Type a name. You’re in. File a Plane if you’re starting it — six short steps, then it’s in the hangar. Everyone else taps that plane. Left side is the plan. Right side is the concern board. Flag the part that bothers you. Your name never shows. The red bar on that part gets longer. Hottest bar is where the group actually has a problem. That’s the point — not a comment thread.

Flagship

by ₥AN$A · 16 ratings

A proposal owner pastes or writes a plan (trip, project, decision); it's auto-split into sections. They get a share link for the group and a private owner-only dashboard link. Group members open the share link and tap any section to anonymously flag it as a "concern" or "dealbreaker," optionally with a short note — no login, one flag per person per section (tracked via a per-device anonymous ID, enforced server-side with a unique constraint). The owner dashboard shows the proposal text re-rendered as a heatmap — sections with more flags glow redder — with flag counts and notes attached. Notes only unlock once a section hits 2+ flags, so no single flag is attributable to one person. The dashboard polls live so results update as the group responds. Stack: Next.js (App Router) + Tailwind + Postgres, deployed on Railway.

All episodes All builds Leaderboard