Responsibility before execution

Map the action.
Name who approves it.

Separate a suggested step from one that sends, changes or publishes something. Use a paper approval map before connecting any systems.

For a workflow idea that needs explicit control.

This is a method you can read and use independently. Begin with the question, follow the prompts, and keep uncertainty visible.

Name the exact initiating event, exclusions, rate limits and who owns the source.

List each field, sensitivity, source, recipient and retention question.

Mark which steps only suggest and which could send, update, spend or publish.

Test wrong category, duplicate event, timeout, unavailable integration and reviewer absence.

Describe versioned prompts or rules, logs, rollback, deletion and who can disable the workflow.

A useful next step can be a decision to wait. The purpose is to make the reasoning available for inspection.

Your output

An approval map with trigger boundaries, data questions, side effects, failure handling and stop ownership.

A reason to pause

Pause when an action has no authorised decision owner or a failure has no safe manual fallback.