Understand the workspace.
Follow one action.

Check access and connector state.

1. Sign in through your organization’s configured identity provider.
2. Confirm the role assigned by your administrator. Requester and approver accounts are separate.
3. Read the connector status in the console before attempting an external-write scenario.

Six views, one action lifecycle.

• Guided demo: follow a shared-budget scenario step by step.
• Execution: create workflow authority, delegate agents and propose requests.
• Receipts: inspect recorded receipts and their integrity checks.
• Test lab: run isolated enforcement scenarios.
• Behavioral audit: compare declared intent and recorded behavior.
• Evidence: inspect and export the action’s event history.

Read states as evidence, not guarantees.

Unknown: the external outcome is unproven. Keep the hold and reconcile; do not blindly dispatch again.

Conflict: evidence exists but does not match the intended action. Keep dispatch blocked for review.

Committed: the recorded target outcome matched the action under the connector’s scoped checks. Inspect the receipt and target binding.

Cancelled: inspect the cancellation receipt. Compensation support depends on the target system and may not undo an existing effect.

Share a redacted report.

1. Export evidence from the Evidence view.
2. Remove credentials, tokens, personal identifiers, private instance URLs and customer payloads.
3. Preserve consistent pseudonyms for action, attempt and receipt IDs so the sequence remains comparable.
4. Include runtime versions, the failure boundary and observed target effect count. Label untested conditions explicitly.

Review the report before sharing. The console export is not an automatic guarantee that every field is safe to publish.