Overview#
Planning a multi-phase intelligence operation from scratch takes hours of manual effort. The Mission Plan domain cuts that down sharply: an analyst describes the objective in plain language, and the system generates a structured plan complete with steps, resource requirements, timelines, and risk assessments. Plans adapt as the operation evolves, and step-level tracking keeps the team aligned throughout.
Key Features#
- AI-driven generation of structured mission plans from natural language prompts
- Plan refinement and optimisation for evolving operational needs
- Step-level status tracking and progress monitoring
- Resource allocation and timeline management
- Risk assessment integration for each plan
Use Cases#
Relevant sectors include intelligence agencies, defence, and law enforcement.
- Generating structured operational plans for intelligence missions
- Refining and optimising existing mission plans based on new information
- Tracking step-by-step progress through complex multi-phase operations
- Assessing resource requirements and risks for planned activities
Integration#
The Mission Plan domain integrates with Investigation for case context, Operational Step for step management, and Target for entity tracking within plans.
Open Standards#
- GraphQL (June 2018 specification): the entire Mission Plan API is exposed as a typed GraphQL schema, with strongly-typed queries and mutations for plan generation, refinement, phase management, and simulation.
- GeoJSON (RFC 7946): the
location_geojsonfield accepts and stores an RFC 7946 GeoJSON geometry string to define the geographic area of operations for a plan. - ISO 8601: all temporal fields, plan time windows, creation, update, and refinement timestamps, are stored and serialised as timezone-aware UTC datetime values in ISO 8601 format.
- RFC 4122 (UUID): every mission plan, phase, and step is assigned a version 4 UUID as its primary identifier, ensuring globally unique, collision-resistant references.
- JSON (RFC 8259): structured plan data including steps, phases, risk factors, resource allocations, and AI feedback are persisted as JSON (PostgreSQL JSONB), with RFC 8259-compliant serialisation throughout the API.
- JWT (RFC 7519) with RS256: all GraphQL resolvers require a valid RS256-signed JSON Web Token verified against a JWKS endpoint; access is denied when token verification fails.
- OAuth 2.0 Bearer Token (RFC 6750): the platform carries authenticated identity via the standard
Authorization: BearerHTTP header pattern, consistent with RFC 6750 token usage.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14