To get a fully functional Beaker instance, you need to set up more than just Beaker itself. You at least need an appropriately configured DHCP server for the lab systems, as well as SMTP access from the systems under test, and you ideally want an archive server (for bulk log storage), a conserver (for console log access), and perhaps other components as well.

This kind of information doesn't fit well into any of the existing guides, so it makes sense to add a Beaker Architectural Guide that explains all of the components of Beaker, the key external interfaces, and some internal technical details that don't make sense in the other documents (such as how bare metal provisioning works and the scheduling algorithm used to assign recipes to idle systems).