🏗️ Build Server
The fleet's build queue, as a package. Every push and pull request lands in the queue as a node; a Job on our own pool runs it; the GitHub App posts the stages as check runs. Under governed activities the build server proposes what should follow a verdict and executes what a signed activity asks for — a deploy, a bake, a re-run — never reviewing, never signing.
Where to start
- Build activities — the build server as a proposer and as a substrate.
- Examples — set up a build queue; a governed deployment process, end to end.
- Build service — the instance, the queue, the Job, the stages (moves here in slice 2).
/build-activities— how an agent reads and follows a build-backed activity.