Cover security and operational gates

Separate runtime and operator roles for typed workflow that classifies inbound email → draft reply → human approve → send. Runtime may only perform the narrow actions that ops coordinator clearing a 200-message backlog without auto-sending refunds needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to model labels 'issue refund' and workflow auto-calls payment tool.

Redact prompts/PII at collection. Secrets enter via a manager or workload identity — never source, fixtures, or exception strings. Incident WF-AUTOSEND-19 should be impossible if these controls hold. Output allowlists and schema checks stay in force on error paths.

Rehearse the rollback or kill switch timed against a clock. Record actor, reason, prior revision/secret/flag, and verification query. Invariant reminder: send step requires approval token; classifier never triggers send directly.

Abuse cases unique to this lab include the privilege path implied by model labels 'issue refund' and workflow auto-calls payment tool. Prove a read-only role cannot mutate. Break-glass tokens expire; leftover tokens fail the drill. Dependency pin/digest story matters when images or models move under you. Document how to rotate the credential that typed workflow that classifies inbound email → draft reply → human approve → send uses without a full outage window longer than your dual-run plan. Security evidence is part of ship, not an appendix nobody reads.

List network egress destinations and justify each. Ensure debug endpoints are off by default in the shipping config. Verify that error responses do not echo secrets or raw stack frames to clients. For multi-tenant paths, add a cross-tenant probe fixture. Time the rollback drill twice — once with the author, once with a peer. Store the drill transcript beside the threat notes for the incident id. In this chapter the product is typed workflow that classifies inbound email → draft reply → human approve → send, the human stakeholder is ops coordinator clearing a 200-message backlog without auto-sending refunds, and the incident id you design against is WF-AUTOSEND-19. Re-state the oracle in your notes — fixture thread reaches awaiting_approval with draft; send blocked until Approve(id) — and keep the invariant visible: send step requires approval token; classifier never triggers send directly. Track unapproved_send_count == 0 and median_time_to_draft ≤ 45s as the scoreboard. Surface under change control: POST /v1/workflows/email-triage/runs. If you only have forty minutes, finish the fixture for model labels 'issue refund' and workflow auto-calls payment tool before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.