07 · Journal · Automation & WorkflowsVol. 10 · Q2 2026kleiotechnology.com

Automation and workflows, built around the humans.

Temporal, n8n, Airflow, hand-rolled. Humans removed from loops that don't need them, kept in loops that do.

Habakkuk 2:2

Write the vision, and make it plain upon tables, that he may run that readeth it.

Back to journal Talk to us

§ I — Cover concept

The context behind the article.

Journal 027

5 min

Image direction

Automation & Workflows

5 min

Article

Temporal, n8n, Airflow, hand-rolled. Humans removed from loops that don't need them, kept in loops that do.

Why it belongs in the journal

This entry exists to make the operating logic visible: not just the system we would build, but the constraint, tradeoff, or failure mode that forced the architecture to matter in the first place.

§ II — Article

Automation and workflows, built around the humans.

Automation is a design discipline

The interesting question in automation is not "what can we automate?" It is "where exactly should the human appear, and what do they need at that moment?"

We design workflows from that question. The technology is downstream.

Tools we reach for

Temporal for long-running, durable, signal-driven workflows
Airflow for scheduled data pipelines where the DAG matches the mental model
n8n for integration-heavy automations that benefit from a visual editor and inspectable runs
Hand-rolled state machines when no tool fits and the surface area is small

Designing the human checkpoint

A good automation has explicit hand-off points. The human sees what the system did so far, what it is proposing to do next, why it thinks that, and what happens if they say no. If those four things are not visible at the checkpoint, the checkpoint is decorative.

Failure modes we plan for

Idempotency for retried steps. Compensation for partially completed workflows. Replay for incident investigation. Dead-letter handling for events nobody owns yet.

Good automation makes the human's job feel calmer, not faster.

§ III — Reading note

What the article is really about.

Operating tension

Temporal, n8n, Airflow, hand-rolled. Humans removed from loops that don't need them, kept in loops that do. In practice, the hard part is usually not implementation syntax but aligning delivery, controls, and operator trust so the thing can survive contact with a real team.

Kleio view

We treat these articles as public design memos: short, opinionated, and anchored in systems that have to be bought, operated, and defended long after launch week.

§ III — Continue reading

Three adjacent articles.

Cloud Computing

Modernization is a pipeline, not a rewrite.

We killed a $400K rewrite in week two and replaced it with a three-tier modernization pipeline. Eleven modules extracted, 19,000 lines of dead code retired, drift down 62% — without a single big-bang cutover.

Audit before you automate.

An association almost spent $180K automating a workflow that ate twenty-four hours per year, while an 8,680-hour problem sat untouched. The fifteen-minute audit that caught it is the cheapest piece of work in any AI engagement.

Agentic AI

MCP servers are the orchestration layer, not the demo.

Most AI tooling lives one paste away from the systems it could help with. Model Context Protocol servers close that gap without giving up the security posture an enterprise can defend.

Back to journal