Datasets:
Task prompt ({op} is the case's operation)
You are the lead planner in a joint staff planning cell conducting Mission Analysis for Operation {op}, within the Joint Planning Process (JPP). Using ONLY the provided source documents, produce a single, complete Mission Analysis brief.
Cover all of the following, clearly delineated with headings:
1. Higher headquarters' mission, purpose, and commander's intent (two levels up), and how your effort nests within them.
2. Operational environment and threat: adversary composition, disposition, capabilities, most likely and most dangerous courses of action; terrain, maritime, air, and civil considerations.
3. Specified, implied, and essential tasks, each attributed to its source.
4. Constraints (required actions) and restraints (prohibited actions).
5. Commander's Critical Information Requirements: derived PIRs and FFIRs, each tied to the decision it supports.
6. Planning assumptions, sharply distinguished from facts, each necessary to continue planning and stated so it can later be confirmed or denied.
7. Risk to mission and risk to force, with recommended mitigations.
8. A restated mission statement (who, what, when, where, why).
9. Decision points and named areas of interest, including the decisive decision this operation turns on.
10. Known facts drawn from the source documents.
11. Force and resource analysis, including feasibility of the required flow and throughput.
12. Proposed military objectives and COA evaluation criteria.
Be thorough and specific: name commands, dates, units, authorities, and figures exactly as the sources state them, and cite the source document number for each determination. Do not introduce information not supported by the documents; where the source is silent, state the gap explicitly or record a clearly-labeled assumption.
The model input is this prompt, then a blank line, then # SOURCE DOCUMENTS, then the packet assembled from documents.jsonl.
Length cap (part of the reference protocol)
The reference protocol caps every brief at 3,000 words, and the system under test must be told: append the paragraph below verbatim to the task prompt (for an agent, to its task instruction), then discard text beyond the 3,000th word before grading. Applying the cut without showing the limit is not the protocol. The cap gives every model and harness the same length budget (about the length of a staff mission analysis brief) so scores measure what a system chooses to say, not how much it says. Uncapped runs are an ablation and must be labelled as such. Reasoning effort: medium where the provider exposes it, otherwise the provider default.
Length limit: the brief must not exceed 3,000 words. Text beyond 3,000 words is discarded before grading, so cover every required section before adding depth to any one.