Development Environments, Compute, and Composable Infrastructure

4. Tradeoffs and alternatives

Prebuilt images reduce startup time and can become stale or oversized. Building from source improves transparency and consumes time. Persistent workers reduce cold starts and increase cross-run state risk. Remote environments improve central control and can complicate local debugging, high-bandwidth tools, device access, or internal-service connectivity.

Owning the environment usually creates more product leverage than owning raw compute because it captures organization-specific toolchains and services. Owning both may still be premature for a small workload. Start with the simplest operable arrangement, measure startup and failure, and preserve an exit contract before scaling.

5. Current Mission Control Implementation

At study commit d902fae, Mission Control defines Sandbox Profiles, provider identity, image and toolchain digests, resource ceilings, network and secret boundaries, qualification evidence, local and remote backends, worker capability attestations, leases, budgets, cancellation, teardown, and compatibility checks. The architecture correctly keeps sandbox capability separate from execution authority.

The studied production admission packet remained blocked by operator configuration. The evidence does not establish a fleet-scale development environment service with reproducible multi-repository bootstrap, shared service connectivity, authenticated previews, warm-pool policy, autoscaling, cross-tenant load tests, or cost allocation. Remote backend contracts and local qualification are not equivalent to sustained production operation.