Core Concepts

Quick Answer

Canonical lifecycle vocabulary:

Working copy: editable authoring state used by pull/push/validate.
Draft target: default bindings/config target after push.
Run: one execution using draft-target bindings/config by default, with code version resolved from the active release unless explicitly overridden.
Release/promote/installations: advanced rollout model for explicit promotion and scoped runtime targets.

Flow definition: versioned EDN map describing triggers, steps, and orchestration.
Draft target: default bindings/config target for flows run <slug>.
Installation: advanced runnable target for a flow (live or installation-specific instances).
Bindings/config: values for :requires slots and runtime inputs.
Promote: advanced operation to assign a release to the live installation target (flows promote).
Triggers: manual, schedule, or webhook/event start a run.
Versioning: releases are immutable; runs are pinned to the resolved release at start time.
Run concurrency: :concurrency controls overlap and version handoff behavior.

Concept	Meaning
`:requires`	Contract declared in the flow definition (`slots`, types, auth/input expectations).
Bindings/config	Concrete target-specific values mapped to those requirements (`draft`, `live`, installation).
Configure check	Readiness check for missing/invalid bindings and required inputs before run.
Usage tracking	`connections usages` / `secrets usages` inspect binding references across targets.

Delete guard behavior follows binding references, not just flow source text.