Handoffs and planning

AgentPlat Handoff is a typed, attributable transfer of execution context and ownership between Room agent participants. It is not free-form message forwarding and it does not widen authority.

Handoff safeguards

A Handoff binds:

• source and target participants and runs;
• exact source and target agent revisions;
• Room-scoped context references with provenance;
• a non-expanding authority ceiling;
• predecessor identity for recovery.

The target must explicitly accept. Revision fencing rejects stale updates; depth and cycle guards bound delegation; terminal target runs reconcile the Handoff lifecycle. Tool output may propose a Handoff, but only the typed Handoff lifecycle and Room policy can authorize execution.

Progressive plans

The AgentPlat Planner materializes only dependency-complete steps. A plan can produce governed agent tasks, human contribution requests, approval requests and AgentPlat Handoffs. Materialized identities are stable so reconciliation and replay cannot duplicate logical work.

Room operational events update step progress and terminal plan state. A replanning operation is bound to its predecessor and trigger event, preserving lineage instead of mutating prior plan history.

The operational projector can enqueue accepted Handoffs and reconcile plan progress idempotently. It coordinates work; it does not replace Room or Handoff policy authority.