top of page

Principle 5:
Action Is Active

Action represents intentional effort that actively changes the state of a system.


If something is deliberately done, executed, interpreted, or adjusted by an agent, it must be modeled as an Action — distinct from sensing, waiting, or passive processing.

Plain-English Summary

An Action is an intentional act that actively changes the state of a system. If something is being done, interpreted, adjusted, or executed by an agent, it must be modeled as an Action.

 

What this Principle Means

​Action represents direct intervention. It is the only operator where effort is intentionally applied to cause change. Action is not sensing, waiting, or passive processing—it is active execution.

​​​

Why This Distinction Matters

When Action is confused with sensing or processing, execution becomes unclear and automation breaks. This principle ensures that all intentional effort is explicitly visible and accountable.

 

​​What Counts as an Action

An Action exists when:

  • A person, system, or agent deliberately intervenes

  • A choice or interpretation is applied to information

  • The state of the system is changed through effort

​

Concrete Examples

Human process: Enter data, send a message, approve a request, adjust settings.

​​

Observed reality: A worker manually reconciles two reports rather than letting the system process them.


Natural interaction: External force applied to a system (e.g., heating applied to water).

​

What Is Not an Action

  • Passive system transformation (Process)

  • Passive sensing or monitoring (Observe)

  • Time passing without intervention (Wait)

  • Readiness without activity (Standby)

​​

Mini Case: Misclassified Action

A step labeled “review data” causes confusion. When examined, the step actually includes Observe (view metrics), Decision (determine issue), and Action (update configuration). Separating these clarifies responsibility and timing.

 

How to Apply This Principle

  1. Ask whether effort is being intentionally applied.

  2. If yes, label the step as Action.

  3. Remove sensing, waiting, or processing from the step.

  4. Split the step if multiple behaviors exist.

​

Common Misunderstandings

  • Treating interpretation as observation

  • Treating automation as action when it is passive

  • Hiding multiple actions inside one step

​

Quick Diagnostic Questions

  • Is effort being intentionally applied here?

  • Does this step change system state directly?

  • Could this step be paused without change if no agent acted?

​

If You Only Remember One Thing

If something is intentionally done, it is an Action.

​

Canonical Statement

Action is the operator for intentional intervention that changes state.

© SolveBoard 2026

bottom of page