A completed agent turn can leave a live change.

Video caption

Each child has state, deadline and recovery owner.

Late effects can reverse the apparent result.

My rule: All required child outcomes must be known.

#EricFieldNotes

Full written post / accessibility read

In a fleet operation, the orchestrator may return while host groups still apply, fail or roll back. An agent that calls the top-level response success can hide the most consequential work.

Define the expected group set and an effect identity for every branch. Record accepted, pending, converged or diverged separately, with a readback timestamp and an escalation owner.

A coordinator continues observing target groups after the model turn ends. A late completion updates the original case; a failed or missing branch follows its forward-fix or owner route.

Permit whole-fleet complete only when every required resource satisfies its terminal contract. Do that because the agent's task boundary is not the distributed system's effect boundary.

#EricFieldNotes

Four-beat scene transcript

1. A completed agent turn can leave a live change.

In a fleet operation, the orchestrator may return while host groups still apply, fail or roll back. An agent that calls the top-level response success can hide the most consequential work.

Visual: Asynchronous effects need their own lifecycle.

2. Track resources, not just tasks.

Define the expected group set and an effect identity for every branch. Record accepted, pending, converged or diverged separately, with a readback timestamp and an escalation owner.

Visual: Each child has state, deadline and recovery owner.

3. Sample after the return.

A coordinator continues observing target groups after the model turn ends. A late completion updates the original case; a failed or missing branch follows its forward-fix or owner route.

Visual: Late effects can reverse the apparent result.

4. Make a fleet pass compositional.

Permit whole-fleet complete only when every required resource satisfies its terminal contract. Do that because the agent's task boundary is not the distributed system's effect boundary.

Visual: All required child outcomes must be known.

Research and claim limits

AWS Step Functions redrive (S214)
Temporal Child Workflows (S216)

The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.