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 setup requirements, invocation inputs, interfaces, schedules, 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: saved values for :requires setup slots and setup form fields.
Invocation inputs: values supplied each time the flow is run, declared under :invocations.
Promote: advanced operation to assign a release to the live installation target (flows promote).
Interfaces: manual, HTTP, webhook, and MCP surfaces over invocation contracts.
Schedules: time-based automation over invocation contracts.
Triggers: deprecated legacy source for old manual, schedule, and webhook/event definitions.
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`	Setup contract declared in the flow definition (`slots`, types, auth/setup input expectations).
`:invocations`	Per-run input contract declared in the flow definition.
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.