Problem

Local project modifications are not enough for real-world operations. As a website matures, it develops a working environment, staging/preview, production, and the need to understand where a specific state is located at any given time.

The existing minimal project management task already assumes dev/stage/prod, but this part has not yet been elaborated as a standalone infrastructure problem.

What to Investigate

We need to understand which environments are actually needed for different classes of projects, how code, data, configuration, and external services are connected between them, and what the safe path for changes to production should be.

We should not assume that three identical environments are mandatory for every website. A small informational site and a production service handling user data may require different levels of strictness.

Related to the agentic change cycle, deploy/rollback, and the existing project management task.