execution_lifecycle

Scope: Execution lifecycle state machine.
Audience: Contributors and reviewers.
Guarantees: States and transitions are explicit.
Non-Goals: Alternate lifecycles.
Why: This doc exists to record its single responsibility for review.

Overview

This doc defines the execution lifecycle state machine.
Read Architecture for component context.
Read Core Concepts for vocabulary.

Contracts

States and transitions are listed below.
The lifecycle uses a single linear progression.
Deviations are failures.
- init -> plan
- plan -> act
- act -> observe
- observe -> evaluate
- evaluate -> terminate
- terminate -> terminate

Invariants

State order is init, plan, act, observe, evaluate, terminate.
Each execution unit records its state.
Transitions align with Execution Model.

Failure Modes

Out-of-order transitions break traceability.
Missing states break evaluation artifact records.
Lifecycle drift breaks Architecture.

Extension Points

Lifecycle changes update Execution Model.
Lifecycle changes update Invariants.
Lifecycle changes update Core Concepts.

Exit Criteria

This doc becomes obsolete when execution is generated.
The replacement is Architecture.
Obsolete docs are removed.

Code refs: tests/integration/test_runtime_flow.py.