What is software delivery machinery?
In RACE Programming, software delivery machinery is software that writes software: the agents, workflows, guardrails, evals and pipelines that the Forward Deployed Engineer and the RACE Engineer build so that the backlog of an engagement gets done by software. It is built per project, not a universal factory. It works when it takes an ever larger share of the backlog tasks, so the Pit Crew needs fewer people.
Software that writes the software
The word can suggest a button you press to get software out. In practice the machinery is engineering work. People design it, build it, and keep tuning it as models, tools and the team change. It has five kinds of parts:
- Agents. AI agents, each with one job, and their integrations with the systems the project uses.
- Workflows. The path a task takes from the Executable User Story to running code, as the team agreed it.
- Guardrails. The rules and checks that keep agent output inside what the team accepts.
- Evals. Tests of the agents themselves, so a change of model or prompt can be judged by its results.
- Pipelines. CI/CD and observability that take the result to production and show what happened there.
Each engagement gets its own
Every engagement has its own systems, its own agreed workflow and its own client. The machinery has to fit them, and above all it has to fit the workflow that actually works on that project. So the Forward Deployed Engineer builds it inside the engagement, from the project environment up.
RACE does not count on one factory that takes any backlog and returns software for any client. What carries over between engagements is experience. The RACE Engineer works across engagements, part-time and on request, rolls proven parts of the machinery into new projects, and collects telemetry on what worked for the next iteration.
The Forward Deployed Engineer and the RACE Engineer
- Forward Deployed Engineer. Builds and keeps evolving the machinery of their own engagement. The Pit Wall answers for it, with the FDE as its main engineering member.
- RACE Engineer. The most senior form of the FDE. Develops the machinery across engagements, rolls it out into projects, and helps each Pit Wall adopt, tune and improve it.
After the frame
Machinery comes after the frame. First the Pit Wall works on the client's problem, shows ways to solve it through prototypes and sets the frame of the solution; nobody has to build machinery before that. The frame is the rails, and the machinery is the locomotive that comes next. The Forward Deployed Engineer decides when to start and how much to build. While it is still unclear where the project is heading, the answer can be to wait.
The share of the backlog it takes
The measure is the share of backlog tasks the machinery takes on and gets done. The rest is done by hand: the FDE pulls it onto themselves, or passes it to the people in the Pit Crew.
When the machinery works, that share keeps growing, and the same backlog needs fewer people in the Pit Crew. This is how RACE scales: through the machinery, with the team staying small. How far the share can go on a given engagement depends on how mature the models are and how ready the project is.
The machinery is built and owned on the Pit Wall of a RACE Programming team. See who builds it and how the role grows across engagements.
What is a Forward Deployed Engineer? → · The RACE Engineer → · What is the Pit Wall? →