Clarify separate-repo-per-app model in docs

Update architecture, spec, and ecosystem docs to make explicit that
each application is a separate GitHub repository under the towlion org.
Split Docker Compose examples into platform-level (shared services)
and per-repo (app containers) layers.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: baijum

docs/architecture.md

@@ -213,28 +213,42 @@ Backups can be synced to remote storage using `rclone`.
 
 ## Docker Compose Services
 
-A typical deployment defines these services:
+Each application lives in its own GitHub repository under the `towlion` organization. The server runs two layers of Compose services:
+
+### Platform Services (server-level)
+
+Shared infrastructure managed at the server level, independent of any application repository:
 
 ```yaml
 services:
   caddy:
     image: caddy:2
-  app:
-    build: ./app
-    env_file: .env
-  frontend:
-    build: ./frontend
   postgres:
     image: postgres:16
     volumes:
       - /data/database:/var/lib/postgresql/data
   redis:
     image: redis
-  celery-worker:
-    build: ./app
-    command: celery -A app.tasks worker
   minio:
     image: minio/minio
     volumes:
       - /data/minio:/data
 ```
+
+### Application Services (per-repo)
+
+Each application repository defines its own containers. These connect to the shared platform services via Docker networking:
+
+```yaml
+services:
+  app:
+    build: ./app
+    env_file: .env
+  frontend:
+    build: ./frontend
+  celery-worker:
+    build: ./app
+    command: celery -A app.tasks worker
+```
+
+For single-app self-hosting (fork scenario), a repository may bundle platform services in its own Compose file so it can run standalone.

docs/ecosystem.md

@@ -43,11 +43,11 @@ New apps are created by:
 
 ### Application Repositories
 
-Individual deployable applications. Each one:
+Each application is a **separate GitHub repository** under the `towlion` organization. Each one:
 
-- Is a standalone web application
-- Contains its own deployment workflow
-- Can be forked and self-hosted
+- Is a standalone web application in its own repo
+- Contains its own Docker configuration and deployment workflow
+- Can be forked and self-hosted independently
 - Follows the [application specification](spec.md)
 
 ## Multi-Application Runtime

docs/spec.md

@@ -13,16 +13,17 @@ All applications must be:
 
 ## Repository Structure
 
-Every application repository should follow this structure:
+Each application lives in its own GitHub repository under the `towlion` organization. Every application repository should follow this structure:
 
 ```
 repo/
   app/                          # FastAPI backend
   frontend/                     # Next.js frontend
 
   deploy/
-    docker-compose.yml
-    Caddyfile
+    docker-compose.yml          # App-specific containers
+    docker-compose.standalone.yml  # Full stack for self-hosted forks
+    Caddyfile                   # Caddy site config for this app
     env.template
 
   .github/workflows/
@@ -34,6 +35,8 @@ repo/
   README.md
 ```
 
+In the multi-app setup, `docker-compose.yml` defines only the application containers (app, frontend, workers). Shared platform services (Caddy, PostgreSQL, Redis, MinIO) are managed at the server level. The `docker-compose.standalone.yml` file bundles everything for self-hosted fork deployments.
+
 ## Backend Requirements
 
 Applications must expose an HTTP server on **port 8000**.