Map Every Gate a Build or Change Must Pass
The Gate Map
Companion to You Are Not the Warfighter · Updated 2026-09-29
Use this when a Warwright team has a build or a change in hand. The map shows every gate that applies, its owner, its clock, and whether the latest change sends the build back through it. Worked in “Pass Every Legal, Safety, and Cyber Gate Without Rebuilding the Old Chain.”
At the top, write the system and configuration, its Integrator Sort consequence answer, and the latest change. Size every gate to that consequence answer. Check consequences beyond the threat that started the project.
The Gate Map for one build.
| Gate | Applies? | Owner | Clock | Evidence it needs | Latest change re-enters it? |
|---|---|---|---|---|---|
| Weapons legal review (and a new review for a significant change) | |||||
| Weapons board arming request (30 days under the July 10, 2025 memo) | |||||
| Autonomy review under DoDD 3000.09 (being rewritten under NSPM-11; check the current version) | |||||
| Airworthiness (Group 1 and 2 drones exempt “with few exceptions” under the memo; Group 3 and above back inside) | |||||
| Battery certification (a week under the memo) | |||||
| Cyber authorization (O-6 ATO for closed-loop drones only; otherwise the Risk Management Framework or a platform’s continuous ATO) | |||||
| Spectrum | |||||
| Explosives safety | |||||
| Component origin | |||||
| Purpose statute (the right money for the thing bought) | |||||
| Inherently governmental line (no contractor decides what the government buys) |
Each gate owner decides whether that gate applies. The team and its tools never make that decision. Fill in the last column for every gate. A new release mechanism, a network connection, or more copies can send a build back through a gate it passed.