Cloud Development Environment Platform · View 09 of 21 · Structure
Decisions
- Browser editor, SSH, the agent API and the admin console are four transports over one authorisation model, so a permission means the same thing however the caller arrives.
- A workspace's only outbound route is the pull-through registry proxy. Everything else it might reach is reached by the platform on its behalf, with a brokered credential.
- Preview URLs are not an interface in this catalogue: they are a published port on one workspace, routed separately and private by default (view 20).
Assumptions
- Base images are pulled by digest from a registry mirrored per region; no workspace start depends on an upstream public registry being reachable.
- Usage events reach billing on the durable lifecycle stream rather than through a synchronous interface.
Risks
- Four client transports means four places a version floor can rot; an old client that cannot be cancelled is a cost problem as well as a compatibility one.
- The registry proxy is a single point of friction for every dependency install in the estate, and a single point of insight if it is ever read as a surveillance tool rather than a control.
