Using only the supplied synthetic closure register, request ledger and approved policy, produce an implementation checklist for two INACTIVE Lawmatics workflows: neutral closure to staff task, then approved tagged-task completion to email. Separate documented native capabilities from proposed custom fields and manual checks. Never use outcome, satisfaction, rating, complaint history or fee value for selection. Flag opt-outs, missing permission, privacy holds, repeated contacts, cooldown conflicts, reopened matters, historical enrollments and uncertain sends. Do not infer approval from task closure unless it is the dedicated approved task with the documented reviewer decision. Do not claim cross-matter atomic dedup is native. Return mapping gaps and a test matrix; if reliable pre-send safety checks are missing, choose staff task plus manual send. Do not connect accounts, activate workflows, send messages, write customer reviews or publish replies. The send workflow requires BOTH a dedicated approved-task completion event AND a current approval=true field backed by a recorded reviewer decision, decision time and policy version. Missing, stale, conflicting or revoked approval stops the send. Held or declined tasks must have the trigger tag removed before they are closed; approval remains false.
