Aerospace & Defense

Mission Planning Knowledge Assistant

Designed for Mission planner

Support the mission planner in building a course of action that is grounded only in approved intelligence products, current doctrine and verified resource availability, with classification handling and human authority enforced at every step of the planning cycle.

Contract AER-02 · primary aggregate MissionPlanningFolder · mode loading

Decision brief

Wargaming and comparison: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Planning staff

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

2 approval gates

Approval gates prevent the copilot from making consequential decisions.

Business problem

A planner builds a personnel-recovery mission across a 6-hour execution window.

Decision to make

Support the mission planner in building a course of action that is grounded only in approved intelligence products, current doctrine and verified resource availability, with classification handling and human authority enforced at every step of the planning cycle.

Outcome to show

approvedCourseOfAction gives Approving authority the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Mission analysis and constraint framing
  2. 2Approved intelligence retrieval
  3. 3Doctrine-bounded COA development
  4. 4Wargaming and comparison
  5. 5Commander approval of selected COA

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Planning staff verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved MissionPlanningFolder evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Support the mission planner in building a course of action that is grounded only in approved intelligence products, current doctrine and verified resource availability, with classification handling and human authority enforced at every step of the planning cycle.
Primary aggregate
MissionPlanningFolder
Primary container
missionPlanningFolders
Hierarchical key
/tenantId + /missionId
Schema version
1

Sample scenario

A planner builds a personnel-recovery mission across a 6-hour execution window. The assistant retrieves only released intelligence within the planner's clearance and caveats, excluding two products whose validity expired the prior day and flagging the assumption they supported. It surfaces the doctrine constraint limiting a proposed ingress route below a specified altitude band and the resource picture showing only one of two rotary platforms at ready readiness across the full window. Two courses of action are developed with explicit assumption registers, wargamed by the staff, and the approving authority selects COA B, with the decision, the authority level and the frozen intelligence and doctrine citations written to the record.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
missionPlanningFolders Primary /tenantId + /missionId Mission, ResourceAvailability, CourseOfAction, PlanningDecisionRecord
intelligenceProductArchive Reference /tenantId + /productId IntelligenceProductChunk
doctrineLibrary Reference /tenantId + /echelonApplicability DoctrineChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
Mission missionPlanningFolders /tenantId + /missionId mission::{missionId} None
IntelligenceProductChunk intelligenceProductArchive /tenantId + /productId intel::{productId}::{chunkOrdinal} chunkVector
DoctrineChunk doctrineLibrary /tenantId + /echelonApplicability echelon::{echelonApplicability}::doctrine::{doctrineDocId}::{chunkOrdinal} chunkVector
ResourceAvailability missionPlanningFolders /tenantId + /missionId mission::{missionId}::resource::{resourceId} None
CourseOfAction missionPlanningFolders /tenantId + /missionId mission::{missionId}::coa::{coaLabel} coaVector
PlanningDecisionRecord missionPlanningFolders /tenantId + /missionId mission::{missionId}::decision::{decisionTimestampUtc}::{decisionId} None

Query patterns