Static wireframes for visual confirmation only — nothing is wired to a backend. A real person takes the floor and talks to three character personas — Li Ka-shing, Vladislav Doronin, and Shane Lauft — in a live group debate, all voiced by one model (the megaprompt engine). These two pages capture what the user sees and how the front and back ends fit together.
The live discussion: a manageable cast roster (add / retire voices anytime), opening self-intros, a slide-out backstage-deliberation panel, one response per character, @-address, a per-turn token/cost meter, and a Send button that becomes ■ Stop. Roster, picker, @-chips, drawer, theme + Send/Stop are live.
The topology — browser ↔ local SSE server ↔ one megaprompt context (the whole cast) ↔ the API ↔ the same artefacts the batch schemes emit — plus a step-by-step of one human turn: confer, then respond.
Why one model + a user in the loop still caches cheaply: the prefix rule, TTL, and the keep-confer vs drop-confer cases — colour-coded turn by turn.
<think>; the one model stages it all.@name → direct answer, confer skipped.event-log.json + transcript.md on close (now with deliberation + per-turn cost events) → replays in the existing viewer, feeds the audit.wireframe · 2026-05-30 · for design confirmation, not implementation