Make the Controller Package the runtime center of gravity
It records how the NextGen Wargame system is governed.
This decision is part of the operating model behind CADE and its supporting workflows. It explains not just what was chosen, but how judgment, source truth, and execution pressure shaped the choice.
Context
A CADE event succeeds or fails in execution. Controllers need to find prompts, role guidance, adjudication aids, timing cues, and review structure under pressure without relying on the original designer.
Decision
Move from fragmented runtime artifacts toward a unified Controller Package as the primary execution artifact.
Alternatives Considered
Keep a runbook-centered model
- Familiar structure for long-form exercise planning
- Useful as reference material
- Higher context switching during execution
- More designer dependency
- Harder for controllers to locate specific runtime guidance quickly
Use separate products for each controller function
- Each product can be optimized for a specific role
- Simpler individual documents
- Increases fragmentation
- Creates risk that controllers use different references
- Makes portability harder
Reasoning
Good AI-generated content is not enough if humans cannot use it under time pressure. The Controller Package makes CADE more portable by consolidating execution logic, quick references, role aids, decision prompts, and review tools.
AI Operator Skill Demonstrated
Designing AI-produced artifacts for runtime human usability
The Controller Package is the product-design move that turns CADE from a designer-supported event into a framework designed for independent facilitation.