Why should an agent see handover events as well as current record state?

A current-state export can hide an important interval. A service request may show its latest owner without revealing that the transfer waited in another team's inbox while the source team continued editing it. Agents acting during that interval need a different view from agents reading the final record.

A generated event stream can use fields such as `event_id`, `handover_id`, `event_type`, `occurred_at`, `record_version` and `supersedes_event_id`. Events such as `submitted`, `withdrawn`, `revised` and `accepted` preserve how the transfer developed. The associated record snapshot provides the content at each relevant version.

JSONL suits a chronological stream that an agent consumes through a polling tool. A separate snapshot table can support direct record retrieval. Keeping event time distinct from retrieval time lets the environment represent delayed delivery without rewriting business history.

A training task could stop the stream after submission and ask what remains unresolved. An evaluation hook could then inspect whether the agent acts on a withdrawn transfer. This representation makes the period of uncertainty available for reasoning instead of compressing it into a final owner field.