diff --git a/dashboard.html b/dashboard.html
index b5d6b6d..461723b 100644
--- a/dashboard.html
+++ b/dashboard.html
@@ -237,6 +237,7 @@
 <table class="map">
 <tr><th>Project</th><th>Next task</th><th>Awaiting</th><th>Running</th><th>Last ruling</th></tr>
 <tr><td><b>euclid_dr1_prelim</b></td><td>Ten real DR1 lenses fitted from the pipeline repo alone</td><td>0</td><td>1</td><td>-</td></tr>
+<tr><td><b>slope_hierarchy_scale</b></td><td>Does hierarchical slope recovery hold at N=25 to 50</td><td>0</td><td>0</td><td>-</td></tr>
 <tr><td><b>subhalo_validation</b></td><td>Does rectangular_adapt false-detect a subhalo on the clumpy source</td><td>0</td><td>5</td><td>2026-09-07</td></tr>
 </table>
 <h3>Nothing open</h3>
@@ -248,11 +249,11 @@ <h3>Nothing open</h3>
 <tr><td>ic50_workspace</td><td>dormant</td><td>planned 1</td><td><button class="copy text" data-cmd="/cortex — retire the science project ic50_workspace: confirm it is holding nothing live, then in PyAutoCortex run `python3 scripts/cortex.py retire ic50_workspace --why &quot;&lt;one line on why&gt;&quot;`, `python3 scripts/cortex.py check`, `pyauto-brain cortex dashboard --apply`, and push the ledger. The row, its tasks and its rulings all stay — only the status and the note change." aria-label="Copy the retire prompt">📋 retire</button></td></tr>
 <tr><td>pj011646</td><td>dormant</td><td>none</td><td><button class="copy text" data-cmd="/cortex — retire the science project pj011646: confirm it is holding nothing live, then in PyAutoCortex run `python3 scripts/cortex.py retire pj011646 --why &quot;&lt;one line on why&gt;&quot;`, `python3 scripts/cortex.py check`, `pyauto-brain cortex dashboard --apply`, and push the ledger. The row, its tasks and its rulings all stay — only the status and the note change." aria-label="Copy the retire prompt">📋 retire</button></td></tr>
 <tr><td>profiling</td><td>dormant</td><td>none</td><td><button class="copy text" data-cmd="/cortex — retire the science project profiling: confirm it is holding nothing live, then in PyAutoCortex run `python3 scripts/cortex.py retire profiling --why &quot;&lt;one line on why&gt;&quot;`, `python3 scripts/cortex.py check`, `pyauto-brain cortex dashboard --apply`, and push the ledger. The row, its tasks and its rulings all stay — only the status and the note change." aria-label="Copy the retire prompt">📋 retire</button></td></tr>
-<tr><td>slope_hierarchy</td><td>dormant</td><td>planned 2</td><td><button class="copy text" data-cmd="/cortex — retire the science project slope_hierarchy: confirm it is holding nothing live, then in PyAutoCortex run `python3 scripts/cortex.py retire slope_hierarchy --why &quot;&lt;one line on why&gt;&quot;`, `python3 scripts/cortex.py check`, `pyauto-brain cortex dashboard --apply`, and push the ledger. The row, its tasks and its rulings all stay — only the status and the note change." aria-label="Copy the retire prompt">📋 retire</button></td></tr>
 <tr><td>subhalo_simulations</td><td>dormant</td><td>none</td><td><button class="copy text" data-cmd="/cortex — retire the science project subhalo_simulations: confirm it is holding nothing live, then in PyAutoCortex run `python3 scripts/cortex.py retire subhalo_simulations --why &quot;&lt;one line on why&gt;&quot;`, `python3 scripts/cortex.py check`, `pyauto-brain cortex dashboard --apply`, and push the ledger. The row, its tasks and its rulings all stay — only the status and the note change." aria-label="Copy the retire prompt">📋 retire</button></td></tr>
 </table>
-<details><summary>1 retired</summary><ul>
+<details><summary>2 retired</summary><ul>
 <li>inference_programme — retired 2026-09-07: restarting from scratch: the project setup was unsatisfactory and it informed how the Cortex manages projects; RAL outputs stashed at /mnt/ral/jnightin/inference_programme_retired_2026-09-07</li>
+<li>slope_hierarchy — retired 2026-09-08: wrapped up 2026-07-22 at N=5; succeeded by slope_hierarchy_scale; tree vaulted under z_projects_complete/</li>
 </ul></details>
 <a id="projects"></a><h2>Projects <a class="mdsrc" href="https://github.com/PyAutoLabs/PyAutoCortex/blob/main/projects.yaml">markdown version</a></h2>
 <section class="project">
@@ -264,6 +265,15 @@ <h3>euclid_dr1_prelim</h3>
 <p class="muted"><a href="https://github.com/PyAutoLabs/PyAutoCortex/tree/main/tasks/euclid_dr1_prelim/">tasks/euclid_dr1_prelim/</a></p>
 </section>
 <section class="project">
+<h3>slope_hierarchy_scale</h3>
+<p class="paths"><b>Local</b> <span class="pathchip">/mnt/c/Users/Jammy/Science/slope_hierarchy_scale</span></p>
+<p class="paths"><b>RAL</b> <span class="pathchip">/mnt/ral/jnightin/slope_hierarchy_scale</span></p>
+<p class="muted">active · both partition · tasks: gated 1</p>
+<div class="task"><button class="copy" data-cmd="python3 scripts/cortex.py gates   # then, once they have closed: move tasks/slope_hierarchy_scale/n25_scale_up.md ready
+# gates: PyAutoFit#1405, PyAutoFit#1558, PyAutoFit#1560, PyAutoFit#1562" aria-label="Copy the Claude command">📋</button><p><a href="https://github.com/PyAutoLabs/PyAutoCortex/blob/main/tasks/slope_hierarchy_scale/n25_scale_up.md">Does hierarchical slope recovery hold at N=25 to 50</a><span class="tags"><span class="pill n">gated</span></span><span class="facets"> — PyAutoFit#1405, PyAutoFit#1558, PyAutoFit#1560, PyAutoFit#1562</span></p></div>
+<p class="muted"><a href="https://github.com/PyAutoLabs/PyAutoCortex/tree/main/tasks/slope_hierarchy_scale/">tasks/slope_hierarchy_scale/</a> · <a href="https://github.com/PyAutoLabs/slope_hierarchy_scale/issues">issues</a></p>
+</section>
+<section class="project">
 <h3>subhalo_validation</h3>
 <p class="paths"><b>Local</b> <span class="pathchip">/mnt/c/Users/Jammy/Science/subhalo_validation</span></p>
 <p class="paths"><b>RAL</b> <span class="pathchip">/mnt/ral/jnightin/subhalo_validation</span></p>
diff --git a/dashboard.md b/dashboard.md
index 303e97e..fcef4db 100644
--- a/dashboard.md
+++ b/dashboard.md
@@ -30,6 +30,7 @@ One row per active project — the next thing, what it is holding, and when it l
 | Project | Next task | Awaiting | Running | Last ruling |
 |---|---|---:|---:|---|
 | euclid_dr1_prelim | Ten real DR1 lenses fitted from the pipeline repo alone | 0 | 1 | - |
+| slope_hierarchy_scale | Does hierarchical slope recovery hold at N=25 to 50 | 0 | 0 | - |
 | subhalo_validation | Does rectangular_adapt false-detect a subhalo on the clumpy source | 0 | 5 | 2026-09-07 |
 
 #### Nothing open
@@ -42,7 +43,6 @@ One row per active project — the next thing, what it is holding, and when it l
 | ic50_workspace | dormant | planned 1 | retire ↓ |
 | pj011646 | dormant | none | retire ↓ |
 | profiling | dormant | none | retire ↓ |
-| slope_hierarchy | dormant | planned 2 | retire ↓ |
 | subhalo_simulations | dormant | none | retire ↓ |
 
 <details><summary>📋 retire concr</summary>
@@ -93,14 +93,6 @@ One row per active project — the next thing, what it is holding, and when it l
 
 </details>
 
-<details><summary>📋 retire slope_hierarchy</summary>
-
-```
-/cortex — retire the science project slope_hierarchy: confirm it is holding nothing live, then in PyAutoCortex run `python3 scripts/cortex.py retire slope_hierarchy --why "<one line on why>"`, `python3 scripts/cortex.py check`, `pyauto-brain cortex dashboard --apply`, and push the ledger. The row, its tasks and its rulings all stay — only the status and the note change.
-```
-
-</details>
-
 <details><summary>📋 retire subhalo_simulations</summary>
 
 ```
@@ -109,9 +101,10 @@ One row per active project — the next thing, what it is holding, and when it l
 
 </details>
 
-<details><summary>1 retired</summary>
+<details><summary>2 retired</summary>
 
 - inference_programme — retired 2026-09-07: restarting from scratch: the project setup was unsatisfactory and it informed how the Cortex manages projects; RAL outputs stashed at /mnt/ral/jnightin/inference_programme_retired_2026-09-07
+- slope_hierarchy — retired 2026-09-08: wrapped up 2026-07-22 at N=5; succeeded by slope_hierarchy_scale; tree vaulted under z_projects_complete/
 
 </details>
 
@@ -137,6 +130,25 @@ Report where the runs of the PyAutoCortex task tasks/euclid_dr1_prelim/dr1_preli
 
 [tasks/euclid_dr1_prelim/](https://github.com/PyAutoLabs/PyAutoCortex/tree/main/tasks/euclid_dr1_prelim/)
 
+### slope_hierarchy_scale
+
+**Local** `/mnt/c/Users/Jammy/Science/slope_hierarchy_scale`
+
+**RAL** `/mnt/ral/jnightin/slope_hierarchy_scale`
+
+active · both partition · tasks: gated 1
+
+<details><summary>📋 <a href="tasks/slope_hierarchy_scale/n25_scale_up.md">Does hierarchical slope recovery hold at N=25 to 50</a> — <b>gated</b> — PyAutoFit#1405, PyAutoFit#1558, PyAutoFit#1560, PyAutoFit#1562</summary>
+
+```
+python3 scripts/cortex.py gates   # then, once they have closed: move tasks/slope_hierarchy_scale/n25_scale_up.md ready
+# gates: PyAutoFit#1405, PyAutoFit#1558, PyAutoFit#1560, PyAutoFit#1562
+```
+
+</details>
+
+[tasks/slope_hierarchy_scale/](https://github.com/PyAutoLabs/PyAutoCortex/tree/main/tasks/slope_hierarchy_scale/) · [issues](https://github.com/PyAutoLabs/slope_hierarchy_scale/issues)
+
 ### subhalo_validation
 
 **Local** `/mnt/c/Users/Jammy/Science/subhalo_validation`
diff --git a/projects.yaml b/projects.yaml
index d6891e0..332c74c 100644
--- a/projects.yaml
+++ b/projects.yaml
@@ -151,7 +151,7 @@ subhalo_simulations:
 
 slope_hierarchy:
   remote: Jammy2211/slope_hierarchy
-  local_path: /mnt/c/Users/Jammy/Science/slope_hierarchy
+  local_path: /mnt/c/Users/Jammy/Science/z_projects_complete/slope_hierarchy
   ral_root: /mnt/ral/jnightin/slope_hierarchy
   mirror: none
   sync_cli: hpc/sync
@@ -160,8 +160,22 @@ slope_hierarchy:
   assistant: none
   witness_file: results/**/*.json
   partition: both
-  status: dormant
-  note: "personal remote, recorded as a fact — not a PyAutoLabs repo; ral_root planned, sync_verbs unverified"
+  status: retired
+  note: "retired 2026-09-08: wrapped up 2026-07-22 at N=5; succeeded by slope_hierarchy_scale; tree vaulted under z_projects_complete/"
+
+slope_hierarchy_scale:
+  remote: PyAutoLabs/slope_hierarchy_scale
+  local_path: /mnt/c/Users/Jammy/Science/slope_hierarchy_scale
+  ral_root: /mnt/ral/jnightin/slope_hierarchy_scale
+  mirror: none
+  sync_cli: hpc/sync
+  sync_verbs: [push, pull, sync, status, submit, push-submit, jobs, tail, check]
+  ledger: wiki/project/state.md
+  assistant: autolens_assistant
+  witness_file: results/**/*.json
+  partition: both
+  status: active
+  note: "born 2026-09-08 as graphical-ep phase 3, code borrowed from slope_hierarchy (vaulted under z_projects_complete/); private remote created 2026-09-08"
 
 pj011646:
   remote: Jammy2211/PJ011646
diff --git a/tasks/slope_hierarchy/n25_scale_up.md b/tasks/slope_hierarchy_scale/n25_scale_up.md
similarity index 68%
rename from tasks/slope_hierarchy/n25_scale_up.md
rename to tasks/slope_hierarchy_scale/n25_scale_up.md
index 42266e8..d104ac8 100644
--- a/tasks/slope_hierarchy/n25_scale_up.md
+++ b/tasks/slope_hierarchy_scale/n25_scale_up.md
@@ -1,9 +1,9 @@
-# Slope_hierarchy — scale the hierarchical slope recovery to N=25–50
+# slope_hierarchy_scale — scale the hierarchical slope recovery to N=25–50
 
-Project: slope_hierarchy
+Project: slope_hierarchy_scale
 Summary: Does hierarchical slope recovery hold at N=25 to 50
-State: planned
-Gates:
+State: gated
+Gates: PyAutoFit#1405, PyAutoFit#1558, PyAutoFit#1560, PyAutoFit#1562
 Witness: an N=25–50 parity table in the same shape as the N=5 one, committed under `results/`, plus the scaling measurements (VRAM ceiling, JAX compile time vs model size, sampler ladder at 3N+1 dims, gradient-utilisation sanity)
 Budget: 48:00
 Runs:
@@ -15,7 +15,20 @@ Migrated-from: PyAutoMind/draft/research/graphical_ep/slope_hierarchy_n25_scale_
 
 ## Question
 
-Ready when: graphical-ep phase 2 (Mind) is issued — add its ref to `Gates:` and move to `gated`.
+Gate evidence (phase 2 of the `graphical-ep` epic is issued and shipped): the Mind record
+`PyAutoMind/complete/2026/09/ep-scale-collapse-basin-cure-or-caveat.md`, the phase-2 review
+bundle PyAutoFit#1572 / #1573 / #1574 / #1576, and the stale-mask fixed-point fix
+PyAutoFit#1580. `Gates:` carries PyAutoFit#1405 — the collapse-basin umbrella, deliberately
+still open pending the moment-matching cure decision — alongside PyAutoFit#1558, #1560 and
+#1562, the phase-2 EP defects this scale-up rests on, so `gates` surfaces all four for the
+human's `move … ready`.
+
+Borrowed from: this task's project was reborn 2026-09-08 as `slope_hierarchy_scale`
+(`/mnt/c/Users/Jammy/Science/slope_hierarchy_scale`), scaffolded fresh with the code borrowed
+from `slope_hierarchy`, which was wrapped up at N=5 on 2026-07-22 and vaulted intact at
+`/mnt/c/Users/Jammy/Science/z_projects_complete/slope_hierarchy`. The N=5 baseline of record
+is `results/ep_history_n5_maxsteps12/` inside that vault; the datasets are **re-simulated** at
+N=25 in the new tree, never copied.
 
 The `slope_hierarchy` project answered all four of its goals at N=5 and was wrapped up on
 2026-07-22. This is the *optional* scale-up that was left on the table, not a blocker or an open
@@ -51,8 +64,10 @@ CPU `ral` partition for the EP arm (finiteness, not throughput).
 
 ## Witness
 
-An N=25–50 parity table in the same shape as the N=5 one, committed under `results/`, plus an
-issue comment on slope_hierarchy#1.
+An N=25–50 parity table in the same shape as the N=5 one, committed under `results/` in
+`slope_hierarchy_scale`. (The old N=5 witness was commented on Jammy2211/slope_hierarchy#1;
+the new tree has no remote yet, so the committed table is the whole witness until a human
+runs `gh repo create`.)
 
 Scaling measurements to capture while the runs are up anyway (the EP campaign needs them):
 
@@ -70,7 +85,8 @@ Each number goes in the committed results table beside the parity numbers.
 
 ## Where to look
 
-- `slope_hierarchy` (project row): `results/ep_history_n5_maxsteps12/` — the N=5 baseline
+- `slope_hierarchy` (retired project row, vaulted at `/mnt/c/Users/Jammy/Science/z_projects_complete/slope_hierarchy`): `results/ep_history_n5_maxsteps12/` — the N=5 baseline
+- `slope_hierarchy_scale` (this project's row): `results/` — where the N=25 parity table and the scaling measurements land
 - Jammy2211/slope_hierarchy#1 — the project issue the parity table is commented on
 - Mind `research/graphical_ep/ep_campaign.md` phase 3 — the campaign rows this feeds
 - Mind `draft/research/graphical_ep/slope_hierarchy_methods_writeup.md` — the write-up it feeds