eve / RUNTIME AUDIT / 2026-09-11

One inbox. Resume first.

The path from a request to the first model call, with post-acceptance identity resolution and optional infrastructure shown separately. This is a source-derived map, not measured latency.

1 eve inbox + aliasesAlso 1 SDK cancellation hook per new turn. No eager authorization, workflow-reply, or anchor hook.
0 eve send preflightsThe SDK still looks up the token inside resumeHook. Known-session sends never hydrate hook metadata.
3 separate clocksFirst model request · dispatch response · visible turn settlement. These are not interchangeable.

Critical dependency chain

Rows are logical operations, not a single serial waterfall. Startup claims are concurrent; timer startup overlaps the first turn. Cold replay, retained-VM execution, SDK preloads, and stream-key caches change the physical requests. Expand a row for its justification and source.

Operation Network work / durable operations Why it exists

Identity and the remaining SDK boundary

sessionId = anchorRunId identifies the original stream-owning run. hook.runId = ownerRunId identifies the current executor. Hook metadata stores only { sessionId }. Reading metadata is explicit and lazy, after resume acceptance. A random named stream still needs its owning run ID.

What this map does not claim