# Attack path

**Required explanatory design prose.** Describe the intended route(s) from the
participant start state to each objective or flag, the pivots, and how the assets
chain together. This document is not machine-readable scenario state and must
not define a pack-side behavior schema. The hydrated ACES SDL is the
specification: declare attacker behavior there with ACES participant semantics,
and keep this explanation aligned with that SDL, `flags/placement.yaml`, the
reference tests, and the walkthroughs.
