The workflow is a versioned, observable artefact. Events are integration primitives. Infrastructure is code, and code is the source of truth. The operating model is what keeps automation current with the systems it orchestrates.
§ 01 ·
Intelligent automation is the discipline of treating workflows, integrations, and infrastructure as first-class artefacts: versioned, observable, tested, deployed through a pipeline, owned end-to-end. Automation is the same kind of artefact as application code. Automation is treated the same way.
Three layers drive the discipline.
Each layer has its own discipline. Each layer is required. None of the three is sufficient on its own.
Design observability in from the start, not after the workflow goes into production. Pattern: automation as a first-class artefact: versioned, observable, tested, owned.
Two failure modes recur.
Both are first-class-artefact gaps. Both close with the same tooling application code uses.
§ 02 ·
Throughout this page, a first-class artefact is one that is versioned, reviewed, tested, deployed through a pipeline, owned end-to-end. NOETRONIQ treats workflows, infrastructure, and automation itself as first-class artefacts by the same discipline application code uses.
Four primitives drive the discipline.
Workflows persist. Workflows running for days, with thousands of steps, survive any single step's failure because the durable execution pattern persists workflow state and resumes from persisted state.
Workflows are first-class artefacts:
Events are integration primitives. Event schemas are contracts. Schema registries are the source of truth. Breaking changes trigger new versions. Deprecations notify consumers.
Three roles divide the ownership.
Infrastructure is code. Code is the source of truth. Plans, applies, drift detection are the three stages of the same artefact. Infrastructure tests run in the same pipeline as application code.
Platforms are paved roads. Workflow engines, event brokers, infrastructure-as-code are available by default. Automation practice is a property of the platform; the practice keeps automation current with systems it orchestrates.
§ 03 ·
§ 04 ·
Fit the engine to the team's skill set, the team's operating model, the organisation's platform. Three common profiles:
Choice is a fit decision, not a correctness decision.
The durable execution pattern persists workflow state, resumes workflows from persisted state when steps fail, and prevents duplicate step runs unless workflows explicitly retry. Implementations include Temporal, AWS Step Functions, Azure Durable Functions, and academic and open-source projects. Reference implementation: Temporal.
Automation is a first-class artefact. Tests are a property of the artefact. Tests run in the pipeline. Coverage includes:
Pipelines gate deploys. Artefacts gate pipelines.
The human-in-the-loop pattern fits high-stakes, judgement-dependent, externally-consequential decisions. The rest of the workflow runs automated. The human-in-the-loop becomes a bottleneck only when the human sits on decisions automation could handle. Bottlenecks signal human-in-the-loop placement has gone wrong.
Right next steps ground in the team's existing operating model.
Next steps are fit decisions, not correctness decisions.
§ 05 ·
An automation that lives on a single laptop carries a single point of failure. Discipline: workflow as code. Workflows:
An automation that is observed by running it and watching output produces wrong results for six months before anyone notices. Discipline: observability as a property of the workflow.
Observability is a property of the workflow, not an add-on.
An event schema owned by the producer is a schema the consumer cannot evolve against. Schemas are contracts. Contracts are shared artefacts. Schema registries are the source of truth. Breaking changes trigger new versions. Deprecations notify consumers.
Infrastructure as code that has not been tested is hand-written, unverified infrastructure. Discipline: plans, applies, drift detection. Infrastructure tests run in the same pipeline as application code.
A workflow that is not durable loses state when steps fail. Discipline: durable execution.
Non-durable workflows cannot be trusted for workflows that matter most.
A human-in-the-loop that has become the bottleneck slows workflows without adding value. The human-in-the-loop fits high-stakes, judgement-dependent, externally- consequential decisions. The rest of the workflow runs automated.
An automation that is not a first-class artefact is not versioned, not reviewed, not tested, not deployed through a pipeline. Automation is the same kind of artefact as application code. Automation is treated the same way.
§ 06 ·
Reference for infrastructure-as-code discipline. Coverage of workflow (write, plan, apply), state management, module design is the most practical available.
Reference for distributed systems discipline. Coverage of event logs, change-data-capture, stream processing is the most rigorous available. The book addresses every automation problem in a distributed system.
Academic reference for workflow patterns. The catalogue of 40+ patterns (sequence, parallel split, exclusive choice, deferred choice, milestone, cancel case, and others) is the most rigorous treatment of workflow semantics. The reference is dense. Patterns are universal.
Standards-body framing for events. Spec is the canonical format for event metadata (id, source, type, time, data). Format is the contract. Registry is the source of truth.
Open-source fork of Terraform. The fork fits organisations wanting infrastructure-as-code without vendor lock-in. Patterns are the same. Governance is open.
Most production-tested durable execution platform. The model (workflow, activity, signal, query) is the most useful abstraction for long-running workflows. The platform is the reference implementation of the durable execution pattern.
Weighing an intelligent automation initiative, evaluating a workflow engine, or making an existing automation more than a script on someone's laptop? Useful at the boundary between workflow and implementation. A short conversation is the right next step.
Learn more