Request lifecycle
How a request moves: verify, route, pin, execute, record. Chat and jobs are the same idea. Only how the path is chosen differs.
Autonomy modes
autonomy_mode 0-3 answers one question: who picks the next step. How this binary hydrates each mode.
Run data
goal, slots, and notes: the three channels the run graph uses to hand data between stages, and what HTTP actually receives.
Identifiers
Who mints request_id, session_id, and correlation_id, how they propagate across boxes, and how to query them in Grafana.
Claims and scopes
User claims entitle a route. Agent scopes permit a tool. They are different principals, different moments, and they do not share a string.
Identities
Three principals on every run: the user who asked, the agent acting as software, and the Runtime box. They never share a bearer.