Mobile Readability — Judgment Card

Purpose

Telegram/mobile reports should help Phillip classify an issue quickly: decide, verify, monitor, or ignore. The layout should reduce re-reading and scrolling.

Reusable card

## {Priority} — {Issue}
**결론:** {judgment in one sentence}
**변화:** {what changed vs prior state}
**영향:** {why it matters}
**근거:** {2 facts + 1 inference max}
**오늘 할 일:** {decide / verify / monitor / ignore}
**주의:** {main uncertainty}

Updated mobile-first card

3-Line Executive Verdict Stack

모바일/Telegram 첫 화면에서는 아래 3줄이 항상 먼저 보여야 한다.

## {Lane/Topic} — {Issue}
**결론:** {판단 한 줄}
**이유:** {변화/영향 한 줄}
**다음 행동:** {verb} {object} · by {time/event} · owner {person/team}

- 근거 1: {fact}
- 근거 2: {fact}
- 불확실성: {single blocker}

Rules

• Put judgment before background.
• Keep one card to 6–9 visible mobile lines when possible.
• Use stable labels across domains.
• Separate Fact from Inference when the issue is judgment-sensitive.
• Use charts only when they beat text for trend/comparison.
• Move raw evidence, long tables, and multi-chart analysis to appendix or webapp detail view.
• First viewport should show 결론 / 이유 / 다음 행동 together.
• Metadata badges must not push the verdict stack below the fold.
• Action line should always include actor and timing.

Related

• [[2026-06-06]]
• [[2026-06-12]]