Workers And Control Plane
Worker services own API behavior, service boundaries, auth forwarding, and runtime entry points.
Architecture Role
- Keep public browser and API behavior aligned.
- Use service boundaries to separate billing, auth, MCP, operations, callbacks, tools, and public edge responsibilities.
- Verify user-visible routes after worker changes.
Review Questions
- What workspace, artifact, API, runtime, or operations behavior does this area affect?
- What user-visible route or developer-facing API proves the behavior?
- What event, artifact, blob, link, or operation should a reviewer inspect afterward?
Media To Add
- Diagram: public edge worker and internal service workers with request routing. It helps operators understand service ownership. Source: deploy topology.