shiplooplisted

# shiploop — self-improving multi-agent harness ## What it is A workspace pattern where you do the specs and systems engineering and shiploop ships the code. A workspace root contains N independent git repositories as sub-folders — each with its own remote, PR queue, and CI — and the root is *also* its own git repo, holding workspace config, cross-cutting scripts, the ticket queue, the governor, and shared AI context. You operate N services as one product without sacrificing their independent deploy cadences or PR isolation. On top of the workspace substrate sits a self-improving multi-agent harness (worktrees + tickets + governor + hooks): the governor drives a ticket loop through fresh headless `claude -p` workers — one worker per ticket, right-sized to the ticket's difficulty — and every resolved ticket promotes a durable lesson into the git-tracked `CLAUDE.md` so the next run inherits it. Memory you can read, diff, and edit. Example shape: `your-workspace/{backend,console,website}/` — three sub-folders, each its own git repo, a script launcher at the root invoked via your chosen package manager. **The root uses ONE package manager — your choice of npm, pnpm, yarn, or bun** (`ROOT_PM` in `scripts/lib/workspace.sh`, default `npm`). The root is private and near-zero-dependency: its `package.json` holds only thin `bash scripts/<x>.sh` aliases, so `npm run dev`, `pnpm dev`, and `yarn dev` all execute the same PM-agnostic bash. `ROOT_PM` only governs which CLI you type and