Conversation the graph answers, when it came from a conversational channel.
How many continuation hops preceded this one, so a re-submitted graph can carry depth + 1.
OptionalSecurityWhat a reinvoke turn runs under: the graph's stored security envelope (the submitting run's
scope, audience, bound parameters and tenant), with IsRunTainted set when the submitting run was
tainted or any step's output the outcome carries is. Absent when the graph carries neither.
The agent run that emitted the graph — the target of a reinvoke.
The person who submitted the graph. Its outcome is posted as them, so it lands only where they may write.
One-line human-readable roll-up.
Per-task outcome. Deliberately carries a summary and an outputRef, not inline payloads —
a ten-task graph's full outputs would swamp the continuation turn's context window, and the
agent can pull what it actually needs by task ID.
Everything a continuation needs to say what happened.