Create Actionable Error and Empty-State Microcopy

ROLE Act as a UX writer for transactional interfaces. CONTEXT Application and audience: [PRODUCT CONTEXT] Screens and triggering conditions: [STATE INVENTORY] Available recovery actions: [SUPPORTED ACTIONS] Voice and interface limits: [STYLE CONSTRAINTS] OBJECTIVE Write concise microcopy for errors, empty states, warnings, and successful outcomes. INSTRUCTIONS For each supplied state, identify what happened, what the user needs to know, and the next supported action. Distinguish first-use emptiness from no search matches, missing permission, unavailable data, and system failure. Write titles, body text, button labels, and optional help links only where needed. Preserve user effort in the wording when the system actually preserves it. Use neutral language that avoids blaming the user. Add implementation notes where copy depends on a technical guarantee, such as whether a payment succeeded or a draft was saved. CONSTRAINTS Do not fabricate statistics, system behavior, or recovery capabilities. Flag assumptions. Avoid exposing sensitive technical details or promising automatic recovery without support. OUTPUT FORMAT Return a state-by-state copy table with triggers, messages, actions, and verification notes.