Why is a good handover summary insufficient for an interactive environment?

**Isn't the task simply to write a useful summary?**

A summary is one artefact in a handover. An interactive environment also needs rules governing what the recipient can decide. Without those rules, an agent can sound competent while taking an action that its role cannot authorise.

**What does that distinction look like?**

In professional services, an engagement team passes a completed delivery assessment to the billing team. The assessment records an unresolved dispute about additional work. Billing can prepare an invoice draft, but the engagement lead retains authority to settle the disputed scope. Knowing the dispute exists does not transfer that authority.

**How should builders represent it?**

Keep the narrative, decision owner and permitted actions separate. A generated environment could allow the billing agent to request a scope decision while preventing it from converting an unresolved estimate into an approved charge. A reassignment should not silently expand permissions.

**What does this teach an agent?**

The agent must identify the decision it needs, route it to the authorised role and continue only when the resulting state permits progress. That tests operational judgement beyond summarisation quality.