Skip to main content

Plans and actions

Overview​

Governed actions separate intent from mutation. A dry run creates a signed plan; inspection and verification establish what will change; apply executes only the verified plan.

Lifecycle​

  1. Discover and describe the action.
  2. Run it in dry-run mode with an input file.
  3. Inspect the plan and preserve its identifier and hash.
  4. Verify with the required confirmations.
  5. Apply the same plan with an idempotency key.
  6. Read the target again to verify the final state.

If verification returns PLAN_CONTEXT_MISMATCH or PLAN_SCHEMA_VERSION_MISMATCH, discard the stale plan and repeat the full dry-run, inspect, verify, and apply sequence.

Available actions and execution modes depend on the active schema and workspace modules. Never infer availability from an example alone.

See Error codes and Use cases.