Separate the workspace from its credentials
AWS Operations is an independently deployable category extracted from a larger local service. The hosted factory creates an empty configuration store and constructs the operations interface, but does not copy desktop AWS or SSH credentials.
The adapter rejects infrastructure mutations and most live inventory endpoints with an explicit unavailable response. It directs those operations to the existing authenticated production controller. That boundary is visible in code rather than left to an informal promise.
Preserve reviewable source
The package contains editable source modules and a source manifest with hashes. It can evolve independently of unrelated tools while retaining a path back to the extracted implementation. Shared hosting supplies revision, origin, verified identity, and scoped storage.
A compare-and-set manifest publishes mutable files and binary chunks. Concurrent writes conflict instead of silently replacing each other. The application does not start an embedded Redis server or obtain unrestricted subprocess authority.
Even the empty profile configuration is created through the runtime abstraction, preserving a consistent storage boundary from the service's first request.
Keep the operating authority clear
The isolated interface can preserve configuration and explain its workflow without claiming access to live infrastructure. The existing production controller remains the authority for those actions. Making unavailable capabilities explicit is part of the migration: a familiar page should never imply that desktop credentials or permissions quietly traveled with its source.