# Roundtable Follow-up Brief — Kanban Collaboration Best Practices P0

Source meeting: `/root/.hermes/reports/roundtables/kanban-collab-20260617/MEETING_NOTES.md`
Atlas review page: `https://atlas.shipsolo.io/roundtables/kanban-collab-20260617.html`

## Owner instruction
孟健确认圆桌会议结论可继续推进。要求继续落地最佳实践。

## P0 decisions to implement
1. Contract-first: define `site-kanban-v1 metadata contract` before any Kanban schema migration.
2. Kanban remains the only execution source of truth.
3. Site Atlas remains read-only; it visualizes status and evidence, never writes state.
4. Telegram is interrupt/approval layer only.
5. New boards enter Atlas only via board registry/allowlist.
6. Roundtable review should be visualized as meeting artifacts: participants, consensus, disagreements, Host decision, action items, raw evidence.
7. Site/business data review should use evidence-parent → specialist child reviews → moxi fan-in verdict.

## Required P0 outputs
- `/root/.hermes/reports/site-atlas/contracts/site-kanban-v1.md`
- `/root/.hermes/reports/site-atlas/contracts/state-dictionary-v1.md`
- `/root/.hermes/reports/site-atlas/contracts/review-dag-v1.md`
- Atlas implementation reading contract-shaped metadata and board registry
- QA report proving Atlas can show true status from Kanban metadata and does not use Telegram/Atlas as state source