What is a declarative workflow?

Definition

A declarative description states what must be achieved rather than prescribing every action in a fixed sequence. An agent or workflow engine interprets that description using available inputs, tools and operating rules.

The description still needs clear acceptance criteria and enforceable boundaries. Expressing a requirement in natural language does not prove that an executor preserves it, completes the work or satisfies a regulatory or security obligation.

ELI5

A declarative workflow describes the result you need and the rules that matter. It does not necessarily list every action to take along the way.

For example, a review task can require a checked report with supporting evidence while allowing the assistant to choose how to investigate. Someone still needs evidence that the requirements were met.

Does declarative mean there are no constraints?

No. Outcomes, dependencies, permissions and acceptance criteria can be explicit even when execution details are flexible.

Does a written workflow contract guarantee compliance?

No. The actual execution and its evidence must be checked against the relevant requirements.

  1. Dan Barrett, Raymond Weitekamp and Jose Montes de Oca against black beside the headline Declare the Outcome.
Definition card for declarative workflow: What is a declarative workflow?

A declarative workflow describes the intended outcome, dependencies and constraints while leaving some execution details to the system that carries it out.