Approval is part of a consequential state transition. If it lives in a confirmation modal beside the application instead of inside the service-owned pipeline, the UI can ask a question without controlling the candidate that question is meant to protect. Chapter 15 puts an explicit approval boundary inside the FeatureCell™ pipeline, where a decision can continue or block a candidate before it reaches committed FeatureCell State.
The Stepwise behaviors let you inspect a candidate after Resolve, after Filter, or after Reducer processing. The Stepwise Controller coordinates those pauses, while the service owns the pending request and the one-use decision contract. The component can render a prompt, but it does not become a second state manager.
Key takeaway: Choose the smallest boundary that exposes enough information to answer the approval question, then guarantee that every pending request reaches a terminal decision.
Why Approval Belongs at a Pipeline Boundary
A modal is a presentation surface.…