> For the complete documentation index, see [llms.txt](https://docs.voting.works/vxsuite-tdp-v4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voting.works/vxsuite-tdp-v4/software-installation/trusted-build/build-machine-configuration.md).

# Build Machine Configuration

## Build Machine Requirements <a href="#build-machine-requirements" id="build-machine-requirements"></a>

* Operating system: Debian 12
* RAM: 8GB minimum
* Chip: x86-64 / amd64 CPU architecture, Intel i5 or higher
* Storage: 250GB minimum

## Build Machine Configuration <a href="#build-machine-configuration" id="build-machine-configuration"></a>

Debian 12 will need to be installed on the build machine. You can find detailed instructions for that process under [Installing Debian 12 on VxBuild](https://docs.voting.works/vxsuite-tdp-v4/software-installation/trusted-build/build-machine-configuration/installing-debian-12-on-vxbuild.md). Once that is complete, we can install the VotingWorks build system, [vxsuite-build-system](https://github.com/votingworks/vxsuite-build-system/tree/v4.0.7).

Throughout the rest of this document, substitute `<inventory-name>` with the inventory provided by VotingWorks.

```
sudo apt install -y git
mkdir ~/code && cd ~/code
git clone https://github.com/votingworks/vxsuite-build-system

cd ~/code/vxsuite-build-system
git checkout main
git pull
git checkout <inventory-name>
./scripts/tb-initialize-build-machine.sh <inventory-name>
./scripts/tb-clone-images.sh <inventory-name>
```

At this point, you should have two separate VMs: `debian-<inventory-name>-<apt-snapshot-date>-<debian-release-name>` and `online`. You can confirm this by running:

```
sudo virsh list --all
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.voting.works/vxsuite-tdp-v4/software-installation/trusted-build/build-machine-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
