# Runbook Direction

Alternatives considered: a calendar puts dates ahead of the task; a kanban board spends narrow-screen space on lanes; a compact queue with a detail reader puts actual work first. Choose the queue. This is a direction for this brief, not a universal operational template.

Composition: horizontal identity strip, a short task heading and search/action row, a quiet list occupying most of the width, and an unframed detail reader. Mobile replaces the side reader with a native dialog. Task names dominate; the heading stays 24px. Sora carries the UI; Space Mono carries date metadata. Cool white, near-black ink, coral for the active view, and a muted blue working-state marker give functional distinctions. Separate with whitespace first; use a light row rule for scan alignment, no repeating decorative card grid.

Use native inputs and dialogs plus the locally licensed Lucide icons. Motion is a brief state feedback transition, with static reduced-motion behavior. Scope includes long names, search with no result, edit/create validation, completion, recoverable removal, local persistence, real JSON export, and responsive detail/focus behavior.