Recourse — Adversarial Claims Adjudication

Recourse convenes five specialized AI agents in a single Band room to adjudicate disputed insurance claims — and the debate itself becomes a legally-defensible, tamper-evident audit trail. A human claims officer keeps the final word. The problem: appeals on denied claims are usually decided by one overworked reviewer, under time pressure, with no one arguing the other side — and no record of how the call was made. How Band is the coordination layer (not a wrapper): all five agents live in one Band room and act through the official Band Agent API. Context, task handoffs and state changes flow through the room — the Coordinator drives turn order, agents respond only to @mentions (the visibility model is respected), and structured agent-to-agent handoffs move the case from argument → policy → challenge → resolution. The room transcript is the system of record the human officer signs off on. The 5 agents: Coordinator (opens the case, routes handoffs) · Blake (argues for the insured) · Morgan (cites the exact policy clauses via RAG) · Alex (devil's advocate, fights to deny) · Sam (writes the signed, reasoned resolution). Defensible by design: clauses cited by number (§7.3, §12.1), full transcript SHA-256 hashed, deterministic payout math, human approve/override. 🎬 Commercial: https://youtu.be/HhmUWdQ2ZSs 🖥️ Live walkthrough (agents debating end-to-end): https://youtu.be/2hd0-p9l4DE 🔗 Live app: https://recourseband.duckdns.org 💻 Code (MIT): https://github.com/kasbsquall/recourse Stack: Band Agent API · GPT-4o (AI/ML API) for Blake/Morgan/Sam · Hermes-2-Pro (Featherless) for Alex · FastAPI + async SQLAlchemy + SSE · Next.js 14 · PostgreSQL + pgvector (RAG, all-MiniLM-L6-v2) · Docker on a VPS behind OpenLiteSpeed. Track 3 — Regulated & High-Stakes.