Overview
Release-readiness documentation polish across the PyAutoLens stack. Three
independent pieces: (i) audit the docs/api/*.rst reference pages of PyAutoFit,
PyAutoGalaxy and PyAutoLens so they are clean and current; (ii) drop the "in
development / beta" framing from cluster examples now that cluster (and weak)
lensing are mature, user-facing features; (iii) document the three ways to learn
PyAutoLens (manual workspace navigation, an llms.txt-driven chat assistant, and
fully agentic AI) in the overview guide and both READMEs.
Filed from PyAutoMind/docs/autolens/release_docs_polish_and_learn_paths.md.
Run autonomously under --auto at effective level supervised (docs cap at
too-large) — plan written here, ship sign-off parks per the autonomy contract.
Plan
- Phase A — API docs audit (
audit_docs): check docs/api/*.rst in
PyAutoGalaxy and PyAutoLens for broken module paths, missing classes and stale
autosummary entries; fix in place. PyAutoFit's audit is parked — its
worktree is claimed by ep-graphical-docs (a PyAutoFit docs task) — to avoid a
collision; it resumes once that ships.
- Phase B — cluster maturity de-flagging (autolens_workspace): remove the
"IN DEVELOPMENT" / "Beta Feature" language from scripts/cluster/README.md and
scripts/cluster/start_here.py, rewriting it as a mature, usable feature;
regenerate the paired notebook. Weak lensing carries no dev flags — verified,
no change needed there.
- Phase C — three ways to learn: after the sentence "The autolens_workspace
contains a suite of example Jupyter Notebooks, organised by lens scale and
dataset type", add a subsection presenting three learning paths —
(1) manual navigation (read the workspace guides; flags the two questions
that follow), (2) AI chat assistant via the llms.txt interface with a
concrete ChatGPT-style example, (3) fully agentic AI via Claude / Codex —
pointing to autolens_assistant for both. Applied to
PyAutoLens/docs/overview/overview_2_new_user_guide.md,
autolens_workspace/start_here.py (§418, + notebook), and the README.md of
both PyAutoLens and autolens_workspace. Also soften the "experimental / not
recommended" assistant note in PyAutoLens/docs/index.md to match the new
third-way framing.
Resolves to 3 PRs (PyAutoLens, autolens_workspace, PyAutoGalaxy) plus a
parked PyAutoFit API-docs sub-phase.
Detailed implementation plan
Affected Repositories
- PyAutoLens (primary) — Phase A + Phase C
- autolens_workspace — Phase B + Phase C
- PyAutoGalaxy — Phase A
- PyAutoFit — Phase A (parked: worktree conflict with
ep-graphical-docs)
Branch Survey
| Repository |
Current Branch |
Dirty? |
Worktree claim |
| ./PyAutoLens |
main |
overview_2 reflow (WIP, trivial) |
free |
| ./autolens_workspace |
main |
stray dataset.fits (untracked) |
free |
| ./PyAutoGalaxy |
main |
clean |
free |
| ./PyAutoFit |
main |
clean |
claimed by ep-diagnostics, ep-graphical-docs |
Suggested branch: feature/release-docs-polish-learn-paths
Worktree root: ~/Code/PyAutoLabs-wt/release-docs-polish-learn-paths/
Work Classification: Both (library + workspace)
Implementation Steps
Phase C — three learning paths (highest-specified, do first)
PyAutoLens/docs/overview/overview_2_new_user_guide.md — insert the
"Three ways to learn" subsection immediately after the "suite of example
Jupyter Notebooks…" sentence; option 1 = manual navigation, flagging the two
questions below.
autolens_workspace/start_here.py (line ~418) — same subsection, in-comment
prose matching the script's markdown-in-docstring style; regenerate
start_here.ipynb.
PyAutoLens/README.md and autolens_workspace/README.md — add a concise
"Three ways to learn PyAutoLens" section (link autolens_assistant:
https://github.com/PyAutoLabs/autolens_assistant).
PyAutoLens/docs/index.md:12 — reword the assistant note from
"experimental / not the recommended starting point" to present agentic AI as a
legitimate third path.
- llms.txt example source:
autolens_assistant/README.md:51–54; llms.txt
files live at PyAutoLens/llms.txt, autolens_workspace/llms-full.txt.
Phase B — cluster de-flagging (autolens_workspace)
5. scripts/cluster/README.md — remove the "# IN DEVELOPMENT" header + prose;
reframe as a supported feature.
6. scripts/cluster/start_here.py:29,61–73 — remove the "Beta Feature" bullet
and "Beta Feature" block; keep any genuine caveats as ordinary notes.
Regenerate notebooks/cluster/start_here.ipynb.
Phase A — API docs audit (audit_docs skill)
7. PyAutoGalaxy docs/api/*.rst (8 files) — audit + fix.
8. PyAutoLens docs/api/*.rst (10 files) — audit + fix.
9. PyAutoFit docs/api/*.rst (8 files) — parked; comment on this issue when
ep-graphical-docs ships, then resume.
Key Files
PyAutoLens/docs/overview/overview_2_new_user_guide.md — Phase C anchor sentence
autolens_workspace/start_here.py — §418 anchor sentence (+ notebook)
PyAutoLens/README.md, autolens_workspace/README.md — Phase C sections
PyAutoLens/docs/index.md — assistant framing
autolens_workspace/scripts/cluster/{README.md,start_here.py} — Phase B
{PyAutoGalaxy,PyAutoLens,PyAutoFit}/docs/api/*.rst — Phase A
Testing / validation
- Docs-only: no library unit tests affected. Validate rst via the
audit_docs
checks; validate regenerated notebooks parse. Ship each repo's changes as its
own pending-release PR behind the four-leg autonomous-ship gate; supervised →
park at ship sign-off with a question on this issue.
Original Prompt
Click to expand starting prompt
I am readying for a PyAuto release and want to do the following on PyAutoLens docs:
(i) make sure API docs are clean and up to date (do this also for PyAutoGalaxy and PyAutoFit);
(ii) clusters and weak lensing are now working and mature and thus can be explained to users as things they can go and use (e.g. no "in development" flags); make sure this is also reflected on autolens_workspace;
(iii) in overview_2_new_user_guide.md, the equivalent location in autolens_workspace, and the README.md files of PyAutoLens and autolens_workspace, explain that there are 3 ways to learn to use PyAutoLens:
(i) reading workspace guides;
(ii) asking questions to an AI assistant like ChatGPT, which uses the llms.txt interface, giving an example of how a user does that (there is an example somewhere in the source code; the user points to the URL for the autolens_assistant);
(iii) fully agentic AI use via Claude, Codex, pointing to autolens_assistant for more information.
Put these 3 options as a subsection after this sentence: "The autolens_workspace contains a suite of example Jupyter Notebooks, organised by lens scale and dataset type", with the first option being "manual navigation" flagging the questions below that are about to follow.
Overview
Release-readiness documentation polish across the PyAutoLens stack. Three
independent pieces: (i) audit the
docs/api/*.rstreference pages of PyAutoFit,PyAutoGalaxy and PyAutoLens so they are clean and current; (ii) drop the "in
development / beta" framing from cluster examples now that cluster (and weak)
lensing are mature, user-facing features; (iii) document the three ways to learn
PyAutoLens (manual workspace navigation, an llms.txt-driven chat assistant, and
fully agentic AI) in the overview guide and both READMEs.
Filed from
PyAutoMind/docs/autolens/release_docs_polish_and_learn_paths.md.Run autonomously under
--autoat effective level supervised (docs cap attoo-large) — plan written here, ship sign-off parks per the autonomy contract.
Plan
audit_docs): checkdocs/api/*.rstinPyAutoGalaxy and PyAutoLens for broken module paths, missing classes and stale
autosummary entries; fix in place. PyAutoFit's audit is parked — its
worktree is claimed by
ep-graphical-docs(a PyAutoFit docs task) — to avoid acollision; it resumes once that ships.
"IN DEVELOPMENT" / "Beta Feature" language from
scripts/cluster/README.mdandscripts/cluster/start_here.py, rewriting it as a mature, usable feature;regenerate the paired notebook. Weak lensing carries no dev flags — verified,
no change needed there.
contains a suite of example Jupyter Notebooks, organised by lens scale and
dataset type", add a subsection presenting three learning paths —
(1) manual navigation (read the workspace guides; flags the two questions
that follow), (2) AI chat assistant via the
llms.txtinterface with aconcrete ChatGPT-style example, (3) fully agentic AI via Claude / Codex —
pointing to
autolens_assistantfor both. Applied toPyAutoLens/docs/overview/overview_2_new_user_guide.md,autolens_workspace/start_here.py(§418, + notebook), and theREADME.mdofboth PyAutoLens and autolens_workspace. Also soften the "experimental / not
recommended" assistant note in
PyAutoLens/docs/index.mdto match the newthird-way framing.
Resolves to 3 PRs (PyAutoLens, autolens_workspace, PyAutoGalaxy) plus a
parked PyAutoFit API-docs sub-phase.
Detailed implementation plan
Affected Repositories
ep-graphical-docs)Branch Survey
dataset.fits(untracked)Suggested branch:
feature/release-docs-polish-learn-pathsWorktree root:
~/Code/PyAutoLabs-wt/release-docs-polish-learn-paths/Work Classification: Both (library + workspace)
Implementation Steps
Phase C — three learning paths (highest-specified, do first)
PyAutoLens/docs/overview/overview_2_new_user_guide.md— insert the"Three ways to learn" subsection immediately after the "suite of example
Jupyter Notebooks…" sentence; option 1 = manual navigation, flagging the two
questions below.
autolens_workspace/start_here.py(line ~418) — same subsection, in-commentprose matching the script's markdown-in-docstring style; regenerate
start_here.ipynb.PyAutoLens/README.mdandautolens_workspace/README.md— add a concise"Three ways to learn PyAutoLens" section (link
autolens_assistant:https://github.com/PyAutoLabs/autolens_assistant).
PyAutoLens/docs/index.md:12— reword the assistant note from"experimental / not the recommended starting point" to present agentic AI as a
legitimate third path.
autolens_assistant/README.md:51–54; llms.txtfiles live at
PyAutoLens/llms.txt,autolens_workspace/llms-full.txt.Phase B — cluster de-flagging (autolens_workspace)
5.
scripts/cluster/README.md— remove the "# IN DEVELOPMENT" header + prose;reframe as a supported feature.
6.
scripts/cluster/start_here.py:29,61–73— remove the "Beta Feature" bulletand "Beta Feature" block; keep any genuine caveats as ordinary notes.
Regenerate
notebooks/cluster/start_here.ipynb.Phase A — API docs audit (
audit_docsskill)7. PyAutoGalaxy
docs/api/*.rst(8 files) — audit + fix.8. PyAutoLens
docs/api/*.rst(10 files) — audit + fix.9. PyAutoFit
docs/api/*.rst(8 files) — parked; comment on this issue whenep-graphical-docsships, then resume.Key Files
PyAutoLens/docs/overview/overview_2_new_user_guide.md— Phase C anchor sentenceautolens_workspace/start_here.py— §418 anchor sentence (+ notebook)PyAutoLens/README.md,autolens_workspace/README.md— Phase C sectionsPyAutoLens/docs/index.md— assistant framingautolens_workspace/scripts/cluster/{README.md,start_here.py}— Phase B{PyAutoGalaxy,PyAutoLens,PyAutoFit}/docs/api/*.rst— Phase ATesting / validation
audit_docschecks; validate regenerated notebooks parse. Ship each repo's changes as its
own pending-release PR behind the four-leg autonomous-ship gate; supervised →
park at ship sign-off with a question on this issue.
Original Prompt
Click to expand starting prompt
I am readying for a PyAuto release and want to do the following on PyAutoLens docs:
(i) make sure API docs are clean and up to date (do this also for PyAutoGalaxy and PyAutoFit);
(ii) clusters and weak lensing are now working and mature and thus can be explained to users as things they can go and use (e.g. no "in development" flags); make sure this is also reflected on autolens_workspace;
(iii) in overview_2_new_user_guide.md, the equivalent location in autolens_workspace, and the README.md files of PyAutoLens and autolens_workspace, explain that there are 3 ways to learn to use PyAutoLens:
(i) reading workspace guides;
(ii) asking questions to an AI assistant like ChatGPT, which uses the llms.txt interface, giving an example of how a user does that (there is an example somewhere in the source code; the user points to the URL for the autolens_assistant);
(iii) fully agentic AI use via Claude, Codex, pointing to autolens_assistant for more information.
Put these 3 options as a subsection after this sentence: "The autolens_workspace contains a suite of example Jupyter Notebooks, organised by lens scale and dataset type", with the first option being "manual navigation" flagging the questions below that are about to follow.