🧬 PyAutoScientist → https://github.com/PyAutoLabs/PyAutoScientist — this repo is one organ of the PyAuto organism.
📖 Full documentation → https://pyautoscientist.readthedocs.io — the whole PyAutoScientist organism, including how to fork and run your own.
The Mind of the PyAuto organism: every piece of work in the ecosystem starts here, as a markdown file describing what you want in plain English. An AI agent (or a human) picks the file up and turns it into a tracked GitHub issue, a feature branch, and a merged pull request. No template, no special syntax — if you can describe the change in a GitHub issue, you can drive the workflow.
What lives here:
| File / folder | What it is |
|---|---|
ideas.md |
raw incubating ideas, no structure required |
draft/<work-type>/<target>/*.md |
scoped prompts, not started (feature/, bug/, docs/, …) |
active/<name>.md |
issued prompts — an open issue, in flight |
complete/<YYYY>/<MM>/<slug>.md |
shipped — the rich completion record (complete/AGENTS.md) |
active.md, planned.md, complete.md |
the task ledger: in flight, queued, done |
repos.yaml |
the body map — the single source of repo identity |
scripts/ |
registry sync + drift checks (repos_sync.py, lifecycle.py) |
A prompt flows through three file states that mirror the ledger: idea →
draft/… → /start_dev → GitHub issue + active/ + active.md entry →
worktree development → PR → merge → complete/<YYYY>/<MM>/ +
complete.md. scripts/lifecycle.py advances the file and drift-checks the
invariant. The registry is shared state, so any machine or session can pick up
an in-flight task.
The schemas and conventions — prompt taxonomy, prompt file format, the
active.md / complete.md schemas, epic trackers, bootstrap on a new
machine — are in REFERENCE.md. How agents should operate
this repo is in AGENTS.md.
The organism this repo is the Mind of (Mind, Brain, Heart, Hands, Memory) is described once in PyAutoBrain/ORGANISM.md and documented in full at https://pyautoscientist.readthedocs.io.