# Workflow control and implementation guide

## Before connecting an action

Assign a named operational owner. Define permitted inputs, access rights, retention and escalation routes. Observe actual handling time, rework, missed messages and queue movement. Decide what constitutes an acceptable false positive and false negative for the specific workflow.

## Pattern choices

| Workflow | Appropriate first pattern | Human decision | Required evidence |
| --- | --- | --- | --- |
| Inbox screening | Text classifier with queue proposals | Override and review suspicious text | Target-channel messages and labels; error cost |
| Document extraction | Extraction with field validation | Confirm uncertain or consequential fields | Permissioned documents and a reference set |
| Internal policy lookup | Retrieval with source citations | Check unsupported answers | Current approved documents and ownership |
| Management briefing | Deterministic metrics plus assisted drafting | Approve interpretation | Reconciled measures and current reporting scope |
| Sales follow-up | Draft-only assistance | Approve audience, wording and send | Consent/contact rules and current account context |
| Complaint response | Retrieval and draft assistance | Approve response and commitments | Policies, verified facts and escalation rules |

These are proposed operating patterns, not demonstrations of deployed systems. Only the inbox screening model is implemented and measured in this project.

## Four implementation stages

1. Map the process and baseline it. Identify reversible actions and decision dependencies.
2. Validate on permissioned target-channel records. Compare a simple baseline, the candidate model and alternatives. Use a separate held-out set and an explicit evaluation protocol.
3. Run in shadow mode. Capture proposals, disagreement, overrides and failure cases without changing external records.
4. Connect a bounded action with rollback. Monitor false positives, missed cases, review effort, incident rates and actual time released.

## Minimum acceptance record

Record model/data versions, evaluation period, population, error definitions, acceptable error limits, accountable reviewer, escalation trigger, permitted action, rollback procedure and next review date. Check language and channel performance separately where the business uses multiple languages or platforms.

## Demo boundaries

The website does not send messages, delete records, connect to live inboxes or infer customer eligibility. Review logs omit message content and exist in memory only. The local vocabulary guard is a conservative demonstration rule, not a certified language or anomaly detector. Evaluate real production requirements independently.