factory-bootstraplisted

Stand up a software factory from a bare Linux host — build the rig images, prepare project repositories, create rigs, bring up the shared console, and verify every step. Use when asked to install, set up, bootstrap, or create a factory, a rig, or run a new project through the factory for the first time. Docker (rootless) deployment only.
The-Zoop-Troop/software-factory-rs · ★ 1 · AI & Automation · score 72

Install: claude install-skill The-Zoop-Troop/software-factory-rs

# Factory bootstrap — from bare host to first landed task You are standing up an **autonomous software factory**: plan in → verified, merged code out. This skill takes a Linux host from nothing to running rigs with a console over them, with a verification gate after every step. Run it top to bottom for a new host; jump to a numbered step when only part is missing. **Sources of truth** (prefer them over memory when they disagree with this skill): `README.md` (quick start) · `docs/DEPLOYMENT.md` (runbook) · `docs/guides/first-project.md` (worked end-to-end example) · `docs/SECURITY.md` (threat model) · `docs/references/runtimes.md` (images) · `docs/generated/cli.md` (exact flags). ## The shape of what you are building | Piece | What it is | Where it lives | |---|---|---| | Rig | One project = one sandboxed compose project (`factory-<name>`) | volumes `ledger`, `repo`, `cache` | | Roles | `steward`, `verifier`, `integrator`, `worker`×N, `planner` — services sharing one runtime image | `compose.yaml` in this repo | | Ledger | The rig's Dolt SQL server over its bead database; first up, health-checked | `ledger` service, volume `/work/rig` | | Egress | The only route out: tinyproxy with a default-deny domain allowlist | `egress` service | | Console | The one externally reachable process: A2A API + embedded browser UI, over every rig's ledger | `factory rig console`, port 7700 | | Host files | Registry, per-rig env + secrets, console config | `~/.factory` (`FACTORY_ROOT`) | ##