Runtime routing

For agents: Inspect current Account authority, exact revisions and native capabilities before acting.

The gateway first resolves an owned route and checks its current environment, exact deployment and admission state. Private previews additionally require a current exact-target grant. Unknown, stopped or unauthorized routes fail closed before app code runs.

Management credentials, internal headers and the preview proof are stripped before forwarding. The Worker then handles its own HTTP routes and native static assets according to its Wrangler configuration. There is no custom runtime fallback API to implement.

Shared Userland hosts use strict host-cookie and framing boundaries. Custom domains default to the same strict cookie policy. A separately proven exclusively owned browser site may opt into ordinary cookies, without a promise of sibling-host isolation within that site. See Security boundaries.

Gateway responses preserve application streams and supported WebSockets. Hosted verification currently supports HTTP browser flows only. Private previews use private/no-store caching; a cache hit or conditional response cannot bypass admission.