# Roundtable Review Visualization Redesign Brief

## Context
Live page: https://atlas.shipsolo.io/roundtables/kanban-collab-20260617.html
Current source package: `/root/.hermes/reports/roundtables/kanban-collab-20260617/`
Current generator: `/root/.hermes/scripts/site_atlas_roundtables_generate.py`
Current output: `/root/.hermes/reports/site-atlas/roundtables/kanban-collab-20260617.html`

Owner clarified: “复盘” here means **roundtable meeting itself**, not site business/data review.

## Goal
Redesign the roundtable review visualization so every Agent meeting becomes a readable decision artifact, not just a static text page.

## Product jobs
The page should answer:
1. Who participated?
2. What did each Agent think?
3. What were the common agreements?
4. What were the disagreements?
5. What did Host decide?
6. What actions came out?
7. Which actions should become Kanban tasks?
8. What evidence/raw transcript backs the conclusion?

## Required views
- Meeting header: topic, date, status, participants count, rounds count.
- Participant map: Agent role cards grouped by function.
- Consensus board: common agreements, with confidence/source count.
- Disagreement /裁决 board: dispute → options → Host裁决 → rationale.
- Agent viewpoint matrix: Agent / position / priority / veto / action implication.
- Action item board: owner, priority, whether converted to Kanban, status.
- Raw evidence drawer/section: MEETING_NOTES + round results deep links.

## Visual direction
- Same Site Atlas cockpit family, but more “decision review room”.
- Dense, readable Chinese UI.
- Use color sparingly: consensus=green, disagreement=yellow, veto=red, action=blue.
- Avoid generic dashboard table-only layout.
- Must be responsive.

## Deliverables
Write to durable report root:
`/root/.hermes/reports/roundtables/kanban-collab-20260617/design-v1/`

Minimum files:
- `PROTOTYPE.md`
- `DESIGN.md`
- `roundtable-review.html`
- `HANDOFF.md`
- `DESIGN_VERDICT.json`

## Constraints
- Do not change Kanban source of truth.
- Do not require external fonts/assets.
- Do not invent Agent opinions; use current `MEETING_NOTES.md` and `round2-results.json`.
- If OpenDesign is unavailable, BLOCK with exact reason; do not claim DESIGN_GO from a local fallback.