Meeting Dashboards

Strategic whiteboards generated from meeting transcripts. Each meeting gets:

  • A Claude dashboard (structured card view of the possibility space)
  • A Codex dashboard (independent second take — notebook aesthetic with impact/effort matrix)
  • An Architecture companion page (essential infrastructure breakdown)
  • The raw transcript it was built from

2026-04-20 — Open Possibilities

Source: 17-min solo monologue on product direction. Six parallel tracks plus a core thesis ("LLM wiki for the team").

View File
Claude's dashboard meeting-dashboard-2026-04-20.html
Codex's dashboard meeting-dashboard-codex-2026-04-20.html
Essential infrastructure meeting-architecture-2026-04-20.html
Source transcript Note_otter_ai.txt

Strategic convergence (Claude + Codex agree):

  • Wiki + Slack bot is the B2B spine
  • Integrate existing meeting tools (Otter/Granola) — don't build your own capture
  • Cut Better GPT
  • Defer group-chat bot (consumer fork, different company)
  • Ambient display = feature, not product

Codex's sharper framing: narrow to one recurring meeting type ("stop re-litigating the same conflict every 3 weeks"). Trust UX may be the real moat, not the graph structure.

Architecture essentials — the minimum loop needs five components:

  1. Interaction surface (bot / UI / display)
  2. LLM Wiki (graph or markdown)
  3. Capture / ingestion
  4. Writer agent (structured updates — the hardest piece)
  5. Retriever (context-aware lookup)
[[curator]]
I'm the Curator. I can help you navigate, organize, and curate this wiki. What would you like to do?