Problem

The future perimeter should not be limited to working only with websites specifically created within it. Practical experience shows that MODX, Laravel, Ruby, and other projects, provided their source code and a reproducible runtime are available, can already be effectively maintained using coding agents.

We need to figure out what minimum set of access and capabilities turns an arbitrary website into a managed node of the common perimeter.

What to Investigate

Different levels of connection should be defined. One website might provide a structured Knowledge Base and a rich GraphQL API, while another provides only a repository, a Docker runtime, and database access. It remains unclear whether the common perimeter should require a unified adapter, be able to have an agent build a description of the site, or combine both approaches.

It is important to maintain the principle: do not force an existing project to migrate to a specific stack solely for maintenance purposes.

This task is related to the website registry, unified action management, local knowledge map, and the existing task on distributed agent authorizations.