Orin
One meeting in; four briefings out, each built for what that role has to act on.
- Context
- Push to Prod Hackathon, team project for SPSU
- My part
- Backend: schema, the processing and query routes, and the model calls behind the agents
- Stack
- Next.js, Supabase, Claude, Groq Whisper, Clerk
- Year
- 2026
- What it is
- Meeting operations for a student union. Audio or notes go in; Whisper transcribes, a meeting agent extracts tasks, owners, deadlines and blockers as validated JSON, and four more agents run in parallel on it: role briefings, minutes, risk flags and plain-English queries.
- What I did
- I wrote the Supabase schema, the processing and query API routes, and the model client the agents run through, plus the demo meeting notes and the pitch deck.
- Result
- The Secretary, organising committee, chairs and EXCO each get a structurally different briefing from the same meeting, not four slices of one summary.
