← Agent Learning knowledge zain-design review_required

Dashboard Idea — Action Affordance Footer

무엇을 학습 Turn each decision card into an executable judgment unit. The footer tells the reader what to do next, by when or by what trigger, and who owns it. **A card should not end with more interpretation; it should end with the…
어디에 정리 07_Zain_Design/Dashboard_Idea/Action_Affordance_Footer.md
앞으로 어떻게 쓸 것인가 검토 후 재사용 후보로 승격

Dashboard Idea — Action Affordance Footer

Purpose

Turn each decision card into an executable judgment unit. The footer tells the reader what to do next, by when or by what trigger, and who owns it.

Core rule

A card should not end with more interpretation; it should end with the next executable affordance.

Use the footer as a stable action surface across Telegram/mobile and the unified-report-webapp.

Reusable footer

→ Next: {verb + object + output} · by {time/event/trigger} · owner {person/agent}

Examples:

  • → Next: decide add/hold KR stock candidate · before market open · owner Phillip
  • → Next: delegate sanctions wording check memo · by 10:00 KST · owner insurance
  • → Next: No action — trigger not crossed; recheck Friday · owner stock

Field model

action_affordance:
  lane: decide | verify | monitor | escalate | archive
  next_action: string
  verb: decide | verify | delegate | wait | archive | escalate
  object: string
  output_artifact: string
  due_or_trigger: string
  owner: Phillip | oke | coder | stock | insurance | news | zain
  action_state: new | changed | unchanged | none

Dashboard behavior

  1. Extract all footers into Today’s Action Queue.
  2. Sort by owner Phillip, due today, escalation, blocked verification, then monitor triggers.
  3. Keep footer visible at the bottom of expanded card/detail view.
  4. Convert lane to CTA:
    • Decide → Record decision
    • Verify → Assign verification
    • Monitor → Set/review trigger
    • Escalate → Open escalation packet
    • Archive → Archive with reason

Mobile rules

  • Footer should be one line whenever possible.
  • Never use bare verbs like 검토 or 확인; attach object and output.
  • No action is valid when paired with a trigger or recheck date.
  • Do not hide the footer inside evidence/detail drawers.
  • If the footer exceeds two lines, simplify the action rather than shrinking the text.

Anti-patterns

  • CTA inflation: every insight becomes an urgent task.
  • Owner ambiguity: user cannot tell whether Phillip or an agent should act.
  • False deadlines: arbitrary due times create artificial urgency.
  • Footer/detail mismatch: action contradicts the judgment or lane.
  • Task-manager creep: footer becomes a full workflow system instead of a judgment handoff.

Related

  • [[2026-06-10]]
  • [[Decision_Delta_Strip]]
  • [[Evidence_Drawer]]
  • [[Executive_Escalation_Ladder]]

Study Room

내일 학습·스터디 큐

내일 학습 큐가 아직 추출되지 않았습니다.

스터디 대화

코칭뿐 아니라 학습 내용에 대해 에이전트별 토론·스터디 지시를 남기는 공간입니다. 저장된 메시지는 다음 학습 큐 조정의 근거가 됩니다.

아직 스터디 대화가 없습니다.

인사이트로 Second Brain에 저장

스터디 대화와 approved 큐를 원문 덤프가 아닌 Phillip의 큐레이션 인사이트 노트로 승격합니다.