PyAutoScientist

PyAutoScientist is a working, opinionated reference implementation of an AI-agent development organism for human-led, natural-language software development: a set of ten git repositories — Brain, Mind, Cortex, Memory, Eyes, Ears, Heart, Hands, Pulse, Insight, Nerves, Gut — through which you lead a multi-repo project in plain English. You describe what you want; AI agents plan, implement, test, gate and release it; you make every judgment call.

It is not a framework you install. It is the live system that develops the PyAuto astronomy stack every day — tens of repositories, nightly releases, hundreds of tasks — documented so that you can fork it and lead your own, driving projects that have nothing to do with astronomy.

The idea in five lines

• Every piece of work starts as a plain-English markdown file you write in the Mind.

• The Brain classifies it, plans it, and routes it through specialist agents.

• Work happens on task worktrees and ships as pull requests, gated by the Heart’s health verdict.

• The Hands package and release what merges.

• The Memory holds the long-term domain knowledge the agents consult.

What adopting it means

You fork the three framework organs (Brain, Heart, Hands), replace a small set of declared config surfaces with your own repositories, write your own Mind and Memory from the documented shapes, and git pull upstream improvements cleanly from then on. One upstream, N private organisms — never a shared deployment. The adoption guide is the walkthrough; The declared config surfaces is the exact contract.

Be aware of what this is before investing: PyAutoScientist assumes Claude Code (skills and commands installed under ~/.claude), the GitHub CLI, a trunk-based single-maintainer flow with task worktrees, and GitHub Actions + PyPI for releases. Those assumptions are the product, not incidental debt — they are stated plainly in the adoption guide.

Reading order

• The organism
  • Responsibility roles and repository categories
  • The call chain
  • Framework vs instance
• Conductors and faculties
  • The consult graph is a DAG
  • The growth rule
  • The command surface
• The development workflow
  • The autonomy contract
  • Model tiers

The organs

• Brain — PyAutoBrain
• Mind — PyAutoMind
• Cortex — PyAutoCortex
• Memory — PyAutoMemory
• Eyes — PyAutoEyes
• Ears — PyAutoEars
• Heart — PyAutoHeart
• Hands — PyAutoHands
• Pulse — PyAutoPulse
• Insight — PyAutoInsight
• Gut — PyAutoGut

Adopting it

• The category contract
• Adopting PyAutoScientist
• The declared config surfaces
• Shared organism standards
• Responsive board sizing
• Shared board navigation
• Dashboard orchestration panel
• The worked example: the live lensing instance