Tasks

Add a minimal UI for the Narasim owner on top of the existing project and container management functionality.

Use the project's own Git as the primary source of history and environment state without platform lock-in.

Eliminate the need to re-download images and dependencies on every new DinD run.

Implement the transmission of runtime secrets separately from Git and the project image being built.

Ensure server-side isolation of operations with containers and project paths before multi-user usage.

Provide the API and agent with sufficient logs to diagnose a Docker Compose project within the runtime.

Separate the external container state from the actual readiness of the child application.

It is a non-priority to explore the future level of managing dozens and hundreds of projects through a common infrastructure loop.

Investigate which repetitive infrastructural operations prevent reducing the launch of a new website from a day to about an hour.

Investigate how to handle secrets, credentials, and external services to keep the project secure and reproducible.

Formulate a practical criterion for the absence of infrastructure lock-in: the project can be handed over to the owner or another team as a working system.

Understand the minimal observability required for an agent and a specialist to safely maintain a running project.

Explore the general approach to saving and restoring the operational state of different project types.

Understand the general infrastructural approach to publishing changes and returning to working condition upon failure.

Investigate a secure and verifiable cycle in which an agent modifies a real project from task formulation to verified result.

Determine what parts, other than Git, make up the portable and reproducible state of a real-world project.

Understand the minimal infrastructure model for multiple project environments and the safe promotion of changes between them.

Investigate the process of onboarding an existing project regardless of its initial stack.

Understand how to describe and reproduce the project's execution environment without binding the entire platform to a single stack.

Research the minimal infrastructure that allows creating, accepting, reproducing, modifying, deploying, maintaining, and transferring websites and applications using an agent.

Page 1 of 2