Controller Package Generator

Built the workflow that turns the source plan into the documents controllers use to run CADE, while keeping every turn tied to the same facts and trainer review.

Key Design Decisions

Generate the Controller Package from the OPORD, not from freestanding scenario notes

Reasoning

Freestanding scenario notes drift. An OPORD-quality source layer forces internal consistency and gives reviewers a fixed reference for checking each turn against source intent. Downstream products that contradict the OPORD can be identified and corrected before execution.

Alternatives considered
  • Draft turn content from a loose scenario summary
  • Let each phase document evolve independently

Keep trainers in the review loop before any document reaches execution

Reasoning

AI generation produces operationally plausible content, but only trainers can confirm that the exercise logic is sound for this unit in this context. Review is not a formality — trainer changes fed directly into subsequent runs.

Alternatives considered
  • Deliver documents directly to controllers and collect feedback after execution
  • Run a single design review at the end of production rather than per-document
Back to overview