How can a pilot expose an authority limit without expanding into a larger workflow?

A professional services coordinator is waiting for approval on deliverable DEL-1468. Approval task TSK-0923 is late, and the agent is authorised to request a decision and record the response. The pilot brief excludes changing the agreed work.

The client procurement role replies that approval will be given only if an additional service is included. The environment records that response and opens a commercial exception linked to the approval task. The original approval remains outstanding because the requested change has not been accepted.

The correct next step is to transfer the exception to the role authorised to discuss scope. The agent can provide the relevant record links and explain the dependency, but it cannot promise the additional service. The pilot ends when the transfer contains enough context for that role to act.

A buyer can request this generated branch in a sample to test authority recognition. It adds a consequential boundary case without requiring pricing, contract amendment or negotiation outcomes. Expansion into those activities can then be a separate scoping decision based on what the initial environment needs to measure.