gsd-orchestrator Wiki
Role in the CAS portfolio
gsd-orchestrator is the Control plane of the Coding-Autopilot-System three-plane model
(Control / Execution / Governance — see the root docs/VISION.md
architecture diagram). Its job: admit goals as typed, bounded, budgeted work items and drive
dependency-aware scheduling through a durable state machine — issue in, PR out, with every
step checkpointed so a crashed or interrupted run can be resumed rather than restarted.
| Plane | This repo's responsibility |
|---|---|
| Control | Goal admission, state-machine scheduling, checkpoint/resume, PR lifecycle |
| Execution | (not this repo — see autogen) |
| Governance | (not this repo — see Promptimprover, cas-contracts, cas-evals) |
Quickstart
- README.md — setup,
.envconfiguration, running the orchestrator against a real issue - docs/portfolio-proof.md — concise reviewer-oriented summary
- Architecture — state machine, component topology, typed-failure path
- Operations — build, test, and CI commands (verified against the live tree)
- Decisions — index of phase summaries and the ADR convention
Ecosystem links
Part of the Coding-Autopilot-System org: autogen (execution plane) · Promptimprover (prompt governance) · cas-contracts (shared schemas) · cas-evals (evidence gate)