Twelve Blank Field Tools, in the Order the Chapters Introduce Them
These pages give a blank version of every tool this fieldbook introduces, in the order the chapters introduce them.
Companion to You Are Not the Warfighter · Updated 2026-09-29
These pages give a blank version of every tool this fieldbook introduces, in the order the chapters introduce them. It also reproduces three forms from You Are Not the User unchanged (the Handoff Chain Trace, the Sensor Map, and the Simulated User Disclosure), each where this book first asks you to fill it in. Each tool starts with when to use it and the chapter that works it. Fill in one copy for each system, claim, or team. Keep the copy with the decision it informed. The AI prompts are in the chapters’ try-this boxes only. Use them only with unclassified, publicly releasable material, in an AI tool your organization has approved.
- Trace Where a Unit’s Need Changed Meaning on the Way
- Weigh What Each Office in the Chain Sees Well and Misses
- Record How Far a Test Was From the Fight
- Attach a Disclosure to Any Result Not From the Unit
- Send a Unit’s Need Forward With Its Strength, Distance, and Author
- Sort Each System by Who Should Integrate It
- Check That the Buy Delivers Components and Rights
- Write the Charter Before the Team Builds or Buys
- Map Every Gate a Build or Change Must Pass
- Test Whether the System Runs After the Builders Rotate Out
- Pick a Mode and Record What the AI Workforce Holds
- Check That Each Turn of the Loop Started and Ended in the Fight
In this section
- Trace Where a Unit’s Need Changed Meaning on the Way
Use this when a fielded system surprised the unit it was built for.
- Weigh What Each Office in the Chain Sees Well and Misses
Use this to weigh what each function in the acquisition chain tells you about the fight.
- Record How Far a Test Was From the Fight
Use this to record how far a test was from the fight the system will be used in.
- Attach a Disclosure to Any Result Not From the Unit
Use this when a test result came from anyone other than the unit that will fight with the system.
- Send a Unit’s Need Forward With Its Strength, Distance, and Author
Use this when a statement of what a unit needs is about to reach someone who decides.
- Sort Each System by Who Should Integrate It
Use this to decide who should integrate a class of system: industry, industry with warfighters judging, a Warwright team with reach-back, or a Warwright team at the unit.
- Check That the Buy Delivers Components and Rights
Use this before a Warwright team buys for a system the Integrator Sort put in lane III or IV.
- Write the Charter Before the Team Builds or Buys
Use this before a team starts to build, integrate, or buy for a class of system.
- Map Every Gate a Build or Change Must Pass
Use this when a Warwright team has a build or a change in hand.
- Test Whether the System Runs After the Builders Rotate Out
Use this before a team integrates a system.
- Pick a Mode and Record What the AI Workforce Holds
Use this when a Warwright effort starts or grows.
- Check That Each Turn of the Loop Started and Ended in the Fight
Use this to check one turn of the loop.