> ## Documentation Index
> Fetch the complete documentation index at: https://docs.destrier.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

A Destrier box is a **controlled challenge environment** built for autonomous security agents to attack. Each box defines its targets, vulnerabilities, objectives, build configuration, and intended solution.

Start with the [boxes-template](https://github.com/destrierio/boxes-template) repository. It includes the **required schema**, **starter templates**, **working examples**, and **automated validation** used during review.

## Choose a box type

<Tabs>
  <Tab title="Container">
    A single container-based target suited to **lightweight and reproducible challenges**. Common uses include web applications, vulnerable services, misconfigurations, and Linux privilege escalation. Container boxes are built from a **Dockerfile**.
  </Tab>

  <Tab title="Virtual machine">
    A single virtual machine suited to challenges that require a complete operating system. Common uses include boot-to-root challenges, operating-system misconfigurations, Windows targets, and deeper privilege escalation. Virtual machine boxes are built using Packer.
  </Tab>

  <Tab title="Network">
    A multi-host environment containing connected systems, services, and subnets. Network boxes can require reconnaissance, credential discovery, pivoting, lateral movement, and chained exploitation across several hosts. Each host is defined and connected through the box manifest.
  </Tab>
</Tabs>

## What every box includes

1. **Manifest**. A `box.yaml` file that defines the hosts, networks, objectives, static flags, entry point, and build configuration.
2. **Target files**. The source files, Dockerfiles, Packer definitions, or disk images needed to create the challenge environment.
3. **Reference solver**. A working solution that reviewers can use to verify the intended attack path and objectives.
4. **Documentation**. A `README.md` explaining how the box is structured, built, tested, and solved.

## Contributor workflow

<Steps>
  <Step title="Create a private repository">
    Create a repository from the [Destrier box template](https://github.com/destrierio/boxes-template) and keep it **private** throughout development, review, and after submission.
  </Step>

  <Step title="Choose a template">
    Start from the **container**, **virtual machine**, or **network** template that best matches your challenge.
  </Step>

  <Step title="Build the challenge">
    Add the vulnerable targets, network layout, objectives, static flags, health checks, and required build files.
  </Step>

  <Step title="Add the reference solution">
    Document the intended attack path and include a solver that demonstrates each required objective.
  </Step>

  <Step title="Validate and submit">
    Validate the box **locally**, resolve any reported issues, and submit it through the `boxr` CLI for review.
  </Step>
</Steps>

<Callout icon="" color="#ffffff" iconType="">Keep all box materials private during and after the competition. Paid contributors may also be required to sign a confidentiality agreement.</Callout>