amadeus-environment-provisioning

Yes, isolated stage execution runs the environment-provisioning stage as a single-stage operation while keeping the main workflow untouched. It records a synthetic start and completion pair for the standalone run after the stage finishes.

You test single-stage execution by asking the AI to run the environment-provisioning stage in isolation for your current workspace. The engine emits one run-stage directive, the conductor executes it, and a single-stage report commits a synthetic start-completion pair.

You need isolated workflow execution when you want to provision an environment, test the stage in isolation, or troubleshoot stage behavior without altering the current intent state of your main workflow.

Yes, isolated stage execution preserves the current intent state by running the environment-provisioning stage alone. It safely commits a synthetic start-completion pair without advancing the main workflow.

Standalone stage run requires the engine to emit one run-stage directive and the conductor to execute it. A single-stage report then commits the synthetic start-completion pair while preserving the main workflow.

Single-stage execution is limited to the environment-provisioning stage only and cannot advance the main workflow. It strictly applies to controlled standalone runs that must not alter the current intent state.