Skip to content

Keeper Inbox Triage Doctrine

Keeper inbox triage is a manual operational hygiene workflow over canonical Keeper tasks. It turns captured work into a clean day-to-day system without autonomous cleanup.

Workflow

Captured conversational tasks enter inbox_state='inbox' and review_state='unreviewed'. The operator reviews them in Keeper Console Inbox, Fast Triage, or Bulk Cleanup mode, or conversationally with "show inbox" and "review next".

Allowed destinations:

  • active: real work that belongs in the normal task system.
  • focus: work selected for today; also sets today_focus=true.
  • waiting: blocked or waiting on a person/system.
  • someday: retained intentionally but not active.
  • archived: soft archive only; no physical delete.
  • duplicate: marked as a duplicate candidate; no automatic merge.
  • garbage: marked as likely garbage; no automatic archive.

Duplicate And Garbage Semantics

Duplicate detection is heuristic and read-only. Keeper compares normalized title tokens, repeated conversational fragments, and low capture confidence. The signals are evidence for review, not authority to mutate. Merge duplicate actions mark review metadata or duplicate_of; they do not combine records or delete either task automatically.

Likely garbage means a task title resembles a conversational fragment such as "thanks" or has very little normalized substance. Garbage tasks must still be soft archived by an explicit user action.

Focus Queue Semantics

Focus Today is a queue, not an autonomous scheduler. inbox_state='focus', today_focus=true, and optional focus_rank make the task visible in the focus view. Keeper may show focus overload metrics, but it does not rebalance or remove tasks without a user request.

Governance

Console mutations call only canonical Keeper HTTP endpoints. Conversational triage mutations resolve visible task references and require Lich approval before the post-approval runtime calls Keeper. Lich records decisions; it does not execute Keeper mutations.