AI Automation — humans mostly out of the loop
Chatbots and copilots serve a present human. Automation runs while nobody watches: ticket triage, document extraction, data enrichment, report generation, monitoring. Different presence, different design center — with no human catching errors in real time, reliability engineering is the whole game, and everything follows from Topic 58's compounding math:
Workflows over agents (Topic 59's rule at maximum strength — automation tasks are usually knowable structures: chain them, gate them, keep the model inside code-decided rails). Verify everything verifiable (schema validation via constrained decoding — Topic 54 — is the automation workhorse; execution checks where possible). And the pattern that makes automation shippable at all — confidence-based triage, Topic 38's router applied to autonomy itself:
Auto-handle the high-confidence cases; queue the low-confidence ones for humans. A system that's 90% reliable overall is unshippable as full automation — but often 99.5% reliable on the 70% of cases it's confident about, which ships beautifully as "automation with a review queue."
That yields the autonomy spectrum every automation should be consciously placed on: human-in-the-loop (approve each action — for consequential/irreversible work), human-on-the-loop (review queues, sampled audits, exception handling — the workhorse tier), human-out-of-the-loop (reserved for verified-or-cheaply-reversible operations only). Moving rightward is earned by eval evidence (Topic 75), and the deployment gate is beautifully concrete: automation ships when its measured error rate on the auto-handled slice beats the human baseline error rate — humans make mistakes too, and "better than the status quo, measured" is the honest bar, not "perfect."
Two boring-but-decisive notes: classic automation engineering applies unchanged — idempotency, retries with backoff, dead-letter queues for poisoned inputs; the LLM is just a fallible worker in a pipeline your existing engineering instincts already know how to harden. And economics: most automation is offline and latency-indifferent → Topic 36's batch tiers cut the bill in half by default. The market note: this is the unsexy, enormous category — document processing and categorization at scale won't demo virally, and it's where a large fraction of real AI value (and contract revenue) actually concentrates.
Summary
Automation = workflows with gates, constrained outputs, and confidence-triaged autonomy: auto-handle the confident slice, queue the rest, ship when measured error beats the human baseline, run it on batch economics with classic pipeline hardening.
Mental model
A mailroom that sorts 70% of parcels automatically with near-perfect accuracy and places every uncertain parcel on the supervisor's desk — versus one that guesses on everything and misroutes silently. Only one of these gets trusted with more mail.
Mistakes to avoid
framing the decision as "automate or don't" instead of "automate which confidence slice"; and skipping the human-baseline measurement — you can't beat a bar you never measured, and humans are worse than teams assume.
Exercise
Pick one recurring drudge task you actually do (triaging notifications, categorizing expenses, extracting fields from documents). Design its automation: the workflow steps with gates, the confidence signal you'd triage on, where it starts on the autonomy spectrum, and the eval that would earn it a rightward move. Then build the first chain with constrained outputs — it's a Topic 59 pattern plus a schema, one evening of work.