You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 790fa3e
Browse filesBrowse the repository at this point in the historyBrowse files
James Nightingale
authored
Merge pull request #15 from PyAutoLabs/feature/cortex-checkin-stamp-prominent
chore(dashboard): regenerate for the prominent check-in stamp
<headerclass="hero"><spanclass="orb"><svgclass="mark" viewBox="0 0 48 48" fill="none" stroke="currentColor" stroke-width="1.3" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circlecx="24" cy="24" r="20.4"/><pathd="M11.8,18.6 C14.4,14.8 17.8,14.4 20.1,17.1 C22.4,19.8 25.8,20.2 28.5,17.9 C31.2,15.6 34.4,16.2 36.1,19.1"/><pathd="M11.6,24.6 C14.2,20.8 17.6,20.4 19.9,23.1 C22.2,25.8 25.6,26.2 28.3,23.9 C31.0,21.6 34.2,22.2 35.9,25.1"/><pathd="M12.8,30.6 C15.3,27.2 18.4,26.8 20.5,29.4 C22.6,32.0 25.7,32.4 28.2,30.2"/><circlecx="32.6" cy="33.0" r="3.8"/><gfill="currentColor" stroke="none"><circlecx="32.6" cy="33.0" r="1.5"/><circlecx="11.7" cy="18.6" r="1.2"/><circlecx="11.5" cy="24.6" r="1.2"/></g></svg></span><h1>PyAuto<b>Cortex</b><spanclass="kind">Dashboard</span></h1><divclass="rule"></div><pclass="tag">Question. Run. Rule.</p></header><pclass="lede">Every science phase the Cortex is holding. Tap a phase's 📋 and its next command is on your clipboard. The verdict is always yours — this page hands you the command, never the ruling.</p>
<divclass="fresh"><p><b>Last updated 2026-09-04.</b> This page is generated from <code>phases/</code>, <code>rulings/</code> and <code>projects.yaml</code>, so it is only as current as they are. <code>dashboard_refresh.yml</code> re-renders it on every push to <code>main</code>.</p></div>
<divclass="task"><buttonclass="copy" data-cmd="/cortex — check in on every active science project since the last check-in (2026-09-04T17:18Z): pull each project through its sync CLI, score every live run against its pre-registered witness, move what came back, re-render and push the board, then read me the by-project summary with the prompt each phase needs next." aria-label="Copy the Claude command">📋</button><p>check in since last time</p></div>
<aid="projects"></a><h2>Projects <aclass="mdsrc" href="https://github.com/PyAutoLabs/PyAutoCortex/blob/main/projects.yaml">markdown version</a></h2><pclass="muted">The science body map, active first: where each project lives, what it is holding, and the one phase of it to act on next. The plans and the issues are one click away — this page routes to them rather than reprinting them; <code>census --by-project</code> and the check-in printout keep the full per-phase tree.</p>
<li><ahref="https://github.com/PyAutoLabs/PyAutoCortex/blob/main/phases/euclid/sersic_index_recovery.md">Euclid — phase 6: do we recover Sersic indices? 10 simulated Euclid lenses vs the real prior-edge pile-up</a><spanclass="facets">— planned</span></li>
250
263
<li><ahref="https://github.com/PyAutoLabs/PyAutoCortex/blob/main/phases/euclid/magnification_robustness.md">Euclid — phase 7: how robust are magnification estimates? model-match vs mismatch across the 10 Euclid lenses</a><spanclass="facets">— planned</span></li>
<li><ahref="https://github.com/PyAutoLabs/PyAutoCortex/blob/main/phases/inference_programme/prodigy_mass_pix.md">Inference_programme — phase 22: MultiStartProdigy on mass_pix — does a gradient search beat Nautilus in a SLaM mass[1] shape?</a><spanclass="facets">— planned</span></li>
263
278
<li><ahref="https://github.com/PyAutoLabs/PyAutoCortex/blob/main/phases/inference_programme/likelihood_term_levers.md">Inference_programme — phase 23: likelihood-term levers on mass_pix — slogdet vs cholesky, relative jitter on reg.Adapt</a><spanclass="facets">— planned</span></li>
<li><ahref="https://github.com/PyAutoLabs/PyAutoCortex/blob/main/phases/subhalo_validation/delaunay_adapt_split_pl_eff_1_outer.md">Subhalo_validation — phase 3: delaunay_adapt_split on pl_eff_1_outer — the outer-component lens, plus the AdaptSplit fix rerun</a><spanclass="facets">— ready</span></li>
275
292
<li><ahref="https://github.com/PyAutoLabs/PyAutoCortex/blob/main/phases/subhalo_validation/rectangular_adapt_pl_sersic_0.md">Subhalo_validation — phase 4: rectangular_adapt on pl_sersic_0 — the RectangularBilinear comparison</a><spanclass="facets">— ready</span></li>
<aid="awaiting-ruling"></a><h2>Awaiting ruling <aclass="mdsrc" href="https://github.com/PyAutoLabs/PyAutoCortex/tree/main/phases/">markdown version</a></h2><pclass="muted">Results are in and nothing is running — the human's verdict is the only thing outstanding. Ordered failures first, then the phases a ruling is required for, then the clean ones.</p>
279
296
<pclass="muted">(nothing awaiting a ruling)</p>
280
297
<aid="running--submitted"></a><h2>Running / submitted <aclass="mdsrc" href="https://github.com/PyAutoLabs/PyAutoCortex/tree/main/phases/">markdown version</a></h2><pclass="muted">On the queue or on the machine. Wall is what the run lines record at the last refresh, against the phase's own budget.</p>
Copy file name to clipboardExpand all lines: dashboard.md
+16-9Lines changed: 16 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ This is the markdown version of the [PyAutoCortex Dashboard](https://pyautolabs.
6
6
7
7
Every science phase the Cortex is holding, on one page: what is waiting on your verdict, what is running, what could be launched next and what is still gated on development work. The verdict is always yours — this page hands you the command, never the ruling.
8
8
9
-
> **Last updated 2026-09-04.** This page is generated from `phases/`, `rulings/` and `projects.yaml`, so it is only as current as they are. `dashboard_refresh.yml` re-renders it on every push to `main`.
9
+
> **Last updated 2026-09-04.**
10
10
11
11
| Where | Count |
12
12
|-------|------:|
@@ -24,7 +24,7 @@ Every science phase the Cortex is holding, on one page: what is waiting on your
24
24
25
25
</details>
26
26
27
-
**Last check-in:** 2026-09-04T17:18Z
27
+
### Last check-in: 2026-09-04T17:18Z
28
28
29
29
## Summary
30
30
@@ -36,9 +36,22 @@ One row per active project — the next thing, what it is holding, and when it l
[markdown version](https://github.com/PyAutoLabs/PyAutoCortex/blob/main/projects.yaml) — The science body map, active first: where each project lives, what it is holding, and the one phase of it to act on next. The plans and the issues are one click away — this page routes to them rather than reprinting them; `census --by-project` and the check-in printout keep the full per-phase tree.
[markdown version](https://github.com/PyAutoLabs/PyAutoCortex/tree/main/phases/) — Results are in and nothing is running — the human's verdict is the only thing outstanding. Ordered failures first, then the phases a ruling is required for, then the clean ones.
0 commit comments