Dashboard Idea — Executive Escalation Ladder

Purpose

Use the dashboard to allocate Phillip's attention by judgment state, not by source/domain. The first question should be: does Phillip need to intervene now?

Lane model

1. Escalate — immediate Phillip judgment required; delay has cost.
2. Decide — recommendation is clear; approval or rejection needed.
3. Verify — judgment is blocked by a missing fact.
4. Monitor — no action now; promote only if trigger occurs.
5. Archive / Ignore — remove from morning attention; keep short reason to prevent repeated noise.

Minimal card header

priority_lane: escalate | decide | verify | monitor | archive
judgment_state: ready | blocked | watch | closed
why_now: "one sentence"
deadline_or_trigger: "time or event"
user_action_required: true | false
owner_agent: zain | news | stock | insurance | coder | orchestrator

Mobile/webapp rule

• Telegram shows Morning answer + Escalate first.
• Webapp home sorts by lane, not timestamp.
• Evidence, long tables, and charts stay in detail view unless they explain lane movement.
• Lane movement history is useful: Monitor → Verify → Decide explains why an issue became important.

Anti-patterns

• Treating every important issue as urgent.
• Hiding missing facts inside long evidence sections.
• Keeping stale monitor items on the morning screen without triggers.
• Using decorative charts that do not change lane, confidence, or action.

Related

• [[2026-06-07]]
• [[Judgment_Card]]