Execution Model
Talon separates an agent’s declared behavior from its durable interaction state and live execution.
Relationship map
An Agent supplies runtime behavior. A Session supplies durable interaction state. A Submission records requested work, and a worker claims it, writes a journal, and commits canonical session state while clients observe live parts.
Read in order
Start with Sessions and Submissions when you need to distinguish a session from a channel, workflow run, or task.