diff --git a/.github/workflows/registry.yml b/.github/workflows/registry.yml
deleted file mode 100644
index a3b9ba8..0000000
--- a/.github/workflows/registry.yml
+++ /dev/null
@@ -1,12 +0,0 @@
-name: Registry
-
-on:
-  push:
-    branches: [main]
-    paths: [.graphite.yml]
-
-jobs:
-  sync:
-    name: Sync registry
-    uses: project-graphite/actions/.github/workflows/reusable-sync-registry.yml@main
-    secrets: inherit
diff --git a/.graphite.yml b/.graphite.yml
index 022a73d..27819b8 100644
--- a/.graphite.yml
+++ b/.graphite.yml
@@ -8,7 +8,7 @@ projects:
     tags: [django, postgresql, redis, celery, docker]
     owner: amrmscll
     authors: [AmrMsCLL]
-    status: live
+    status: archived
     listed: true
     showcase:
       problem: >
@@ -29,5 +29,4 @@ projects:
             Defined the test scenario and owns the deployment, infrastructure and acceptance
             criteria used to validate the Graphite hosting path.
     deploy:
-      kind: compose
-      host: message-lab.project-graphite.com
+      kind: none
diff --git a/README.md b/README.md
index d4cc880..c4efbf9 100644
--- a/README.md
+++ b/README.md
@@ -58,19 +58,20 @@ Messages are stored and read by the administrator. Do not enter private or sensi
 
 ## Deployment
 
-Production runs at https://message-lab.project-graphite.com from
-[`deploy/graphite-message-lab/values.yaml`](https://github.com/project-graphite/platform/blob/main/deploy/graphite-message-lab/values.yaml) in `platform`.
-A push to `main` publishes the `web` and `worker` images and records their tag there, which deploys
-them. PostgreSQL and Redis persist in named volumes, migrations run before Gunicorn starts, and the
-whole stack sleeps after 30 minutes without visitors and wakes on the next request.
-`SECRET_KEY` and `POSTGRES_PASSWORD` are in the organisation's secrets repository.
+Retired. Message Lab proved the Project Graphite deploy path end to end, and its one feature now
+lives in Graphite Hub as the messages wall at
+[project-graphite.com/messages](https://project-graphite.com/messages). Nothing runs at
+`message-lab.project-graphite.com`: the registry entry in `.graphite.yml` is `archived` with
+`deploy: none`, and `platform` has no `deploy/graphite-message-lab/` folder. The repository stays
+as the case study and runs locally as above.
 
-To create the first administrator, visit the site so it wakes, then open the `web` container's Terminal
-in the [Graphite Console](https://console.project-graphite.com) (or `docker exec` into it on the VPS)
-and run:
+A push to `main` still publishes the `web` and `worker` images to GHCR; the deploy job then finds
+no deploy folder in `platform` and records nothing, by design.
+
+To create an administrator locally:
 
 ```sh
-python manage.py createsuperuser
+./run manage createsuperuser
 ```
 
 ## Attribution