Skip to content

How-to guide

Prepare and verify a controlled action

Prepare and verify a controlled action

2 min

Goal: distinguish a proposal, preparation and actual execution. Access: reading capabilities and, for application, an available authorized operation. Use a test workspace and demonstration resource.

This journey does not publish internal write routes. Choose a method and path from the published catalogue or an action explicitly available in your interface. Without a compatible operation, stop at a documented proposal.

1. Read initial state

Choose the resource and record its identifier, workspace, values and version when exposed by the contract. For Client–Commande, target CMD-001 rather than “ACME's latest order”.

Describe expected final state and associated effects. An action may affect several resources; understand its scope before applying it.

2. Prepare inputs

In the agent, inspect Capability profile, Tools and API, then Verification. Preparation produces a proposal or plan; it does not prove that records changed.

Review the target, changed fields, dependencies and validation errors. Use preview when the contract provides it. Do not assume every operation has a preview button.

3. Check applicable authorization

Distinguish permission to read, prepare and apply. A prompt instruction or skill grants none of these. If approval is required, use the defined approval stage and check its state before execution.

Consult the SDK and the chosen operation's contract for action plans and stages. Conversational approval does not replace recorded approval when required by the contract.

4. Apply once, then reread

Apply through the authorized capability only. Retain the execution identifier and response. Read the resource again and compare actual with expected final state.

After a timeout, check whether the operation occurred before repeating a write. After a version conflict, read current state and prepare a new proposal. Use idempotency guarantees only when documented for that operation.

Outcome and limits

Expect either a verified proposal without changes or an authorized execution with checked effects. A completed agent session does not prove successful action execution. Stopping a session does not automatically undo operations already performed.

Keep initial state, reviewed inputs and evidence from rereading. Continue with Test and evaluate.

Did this page help you achieve your goal?