An action is the smallest narrative-code unit: a low-level method that performs one small operation or event. It handles raw mechanics such as running a query, checking a condition, or sending a queue message, usually in one focused chunk and rarely more than two. section 2.3.4
A focused validation action
A method such as validateMandatoryField(fieldValue, fieldName) checks whether one value is blank and raises an appropriate exception. Email validation can then compose this action with uniqueness checking at the scene level, keeping each method readable at its own narrative level. section 2.3.4
Choose the action boundary for clarity rather than line count alone. Extract code when it performs a narrow responsibility or hides cognitively heavy logic, but avoid methods that merely wrap one simple line. If a method accumulates too many actions, split it into scenes or a higher-level chapter. section 2.3.5
Figure 2.2 Hierarchical structure of a story
Use the hierarchy to see how actions compose into scenes, chapters, and a table of contents. section 2.3.4
