Review a command plan before approval

Read the whole plan

The plan should match the business request and stay within the assigned workspace. Review what it proposes to observe or change, the evidence it relies on and the dependencies it leaves unresolved.

1. Compare the proposed steps with the original request.
2. Check the environment, system responsibilities and required permissions.
3. Identify assumptions, missing evidence and points that need a person to decide.

• Only a workspace owner can approve a command in this release.
• A prompt engineer can prepare work within assigned capabilities; that role does not grant owner approval rights.

Check what approval means today

Approval records the owner’s decision about the plan. The current external execution environment is not provisioned. An approved command can therefore be awaiting the environment rather than having changed an external system.

• Read the command status and environment notice together.
• Do not report a proposed action as completed work.
• Use source evidence to confirm a result when execution becomes part of an agreed provisioned environment.

When a plan needs revision

Explain the incorrect assumption or missing requirement in business terms. Include the command reference through an authorized private channel so the team can find the same plan.

• The command reference and relevant plan step.
• The expected behavior and evidence that changes the decision.
• The owner responsible for the revised scope or approval.