From Doctrine to Software: Encoding Mission Command in Opspex

Doctrine sits on shelves. Opspex puts it in soldiers’ hands.

The gap between Mission Command philosophy and practical execution is where operations fail. Teams understand the principles intellectually but struggle to operationalize them in contested environments. How do you:

Encode commander’s intent so it travels across echelons without degradation?
Validate that tactical actions actually align with operational objectives?
Rehearse decentralized decision-making before communications are jammed?
Build the shared understanding that makes trust possible?

Opspex was built to answer these questions.

This post explains how we transformed Canadian Armed Forces doctrine into software that enables Mission Command at the tactical edge.

The Opspex Architecture: A Doctrinally-Aware Layer

Opspex is not a replacement for existing command-and-control systems. It’s a doctrinally-aware situational awareness layer that sits between raw observations and actionable intelligence.

The Core Pipeline

Raw Observations (drones, sensors, reports)
    ↓
Doctrinal Processing (ATP-112 + ACP-125)
    ↓
NATO-Recognizable Claims
    ↓
Actionable Soldier Interface

The Doctrinal Layer: Our Differentiator

Most situational awareness tools aggregate data. Opspex interprets it through doctrine.

ATP-112: Tactical Formations

ATP-112 (Allied Tactical Publication 112) defines how NATO forces organize, deploy, and maneuver. Opspex encodes this doctrine to:

Auto-rollup formations: When individual unit positions are reported, Opspex identifies formation patterns (wedge, column, line, circle) and represents them as cohesive entities
Validate disposition: Alert commanders when unit positioning violates doctrinal standards
Predict capabilities: Estimate formation strength, mobility, and vulnerability based on doctrinal norms

ACP-125: SALUTE Reporting

ACP-125 (Allied Communications Publication 125) standardizes intelligence reporting through the SALUTE format:

Size: How many?
Activity: What are they doing?
Location: Where?
Unit: Who?
Time: When?
Equipment: What do they have?

Opspex structures all observations into SALUTE format, ensuring:

Consistency: Every report contains the same critical elements
Interoperability: Reports are recognizable across NATO forces
Completeness: Missing elements are flagged for clarification

Threat-Tier Classification

Not all contacts are equal. Opspex classifies threats into tiers based on:

Capability: What can they do?
Intent: What are they likely to do?
Proximity: How close are they?
Context: What does this mean for our mission?

This classification drives prioritization in the user interface — high-tier threats demand immediate attention, low-tier threats are monitored.

The Three Opspex Modes

Opspex operates in three distinct modes, each serving different operational needs.

Mode 1: Training Simulator

Status: Sellable today, demo-able end-to-end on laptop

The training simulator is Opspex’s first use case and market entry point. It provides a safe environment where teams can:

Explore multiple scenarios: Test “what-if” analysis with discrete event simulation, agent-based modeling, and physics-based wargaming
Rehearse intent-driven decision-making: Practice operating within commander’s intent before it matters
Conduct after-action reviews: See how decisions cascaded, where alignment broke down, and what to improve
Build shared understanding: Reveal misalignment in mental models through collaborative scenario exploration

Technical capabilities:

Terrain databases (One World Terrain integration)
Force laydowns and entity modeling (friendly, enemy, civilian)
Environmental modeling (weather, EM spectrum effects)
Stochastic and deterministic outcome simulation
Monte Carlo simulations for probability distributions under uncertainty

Mode 2: ATAK/TAK Integration

Status: Phase 3 development, critical for deployment

The ATAK (Android Team Awareness Kit) integration brings Opspex’s doctrinal layer to deployed units’ existing tactical systems.

Key features:

CoT (Common Operational Picture) bridge: Opspex processes ATAK’s CoT XML feeds through doctrinal filters
Enhanced situational awareness: Raw contacts become doctrinally-classified threats
Intent validation: Tactical actions are scored against higher-echelon objectives
Offline capability: Full functionality when comms are degraded

Deployment model:

Runs on tactical tablets and laptops
Integrates with existing ATAK plugins and data sources
Synchronizes with higher systems when connected, functions fully offline when disconnected

Mode 3: Deployed-Unit Watch View

Status: Working prototype, Watch UI v2 completed May 2026

The watch view is Opspex’s deployed interface for monitoring operations in real-time.

Watch UI v2 features:

Last contact time: Shows when each unit was last heard from (critical in degraded comms)
Speed/stationary indicator: Visual cues for unit movement status
Larger contacts count: Improved visibility of force disposition
Doctrinal formation display: Units shown in ATP-112 formation patterns
Threat-tier coloring: Visual prioritization based on threat classification

Figure description: [Screenshot of Watch UI v2 showing a tactical map with friendly units displayed in formation patterns (wedge, column), enemy contacts color-coded by threat tier (red=high, yellow=medium, green=low), last contact timestamps in the corner of each unit icon, and a sidebar showing SALUTE-formatted intelligence summaries]

Intent-Driven Experimentation

Opspex doesn’t just simulate scenarios — it enables intent-driven experimentation.

The Multi-Objective Scoring System

Traditional simulators optimize for tactical victory. Opspex optimizes for alignment with higher-level intent.

How it works:

Input higher-echelon intent: Commander specifies purpose, end-state, and key tasks
Define measures of effectiveness (MOEs): What outcomes matter? (e.g., enemy degraded, collateral damage minimized, information environment shaped)
Define measures of performance (MOPs): How efficiently are we executing? (e.g., time to objective, resource consumption, casualty rates)
Weight the objectives: Not all MOEs/MOPs are equal — some reflect operational art priorities
Score courses of action: Each tactical decision is evaluated against the weighted objectives

Example scenario: A platoon executing a raid might test variants that also support broader objectives like:

Shaping the information environment (media-friendly conduct)
Preserving escalation control (avoiding actions that trigger broader conflict)
Maintaining alliance cohesion (coordinating with partner forces)

The scoring system reveals which variants best balance tactical success with operational alignment.

Constraint-Based Optimization

Opspex allows teams to layer in strategic or operational goals from higher headquarters’ campaign plans into tactical-level play.

Practical application:

Company commander: Inputs intent from battalion (“secure the valley while minimizing civilian casualties”)
Platoon leaders: Test tactical variants (assault routes, timing, force composition)
Opspex: Scores each variant against both tactical success (mission accomplished) and operational alignment (civilian casualties minimized)
Result: The team chooses the variant that best balances both objectives

Shared Understanding and Rehearsal

Mission Command requires mutual trust and shared understanding. Opspex builds these through collaborative rehearsal.

Integrated Visualization

2D/3D maps: Terrain-aware displays that show unit positions, threat locations, and environmental factors

Augmented reality overlays: (Future capability) Project tactical information onto the real world through AR headsets

Collaborative interfaces: Multiple users can explore the same scenario simultaneously, seeing each other’s decisions and reasoning

After-Action Review (AAR) Capabilities

Opspex’s AAR system goes beyond “what happened” to reveal “why it happened”:

Decision timeline: See when key decisions were made and what information was available
Intent alignment trace: Track how each decision supported or conflicted with commander’s intent
Cascade analysis: Understand how local decisions affected broader outcomes
Counterfactual exploration: Test “what if we had done X instead?”

Building the Common Operating Picture

The AAR process creates shared understanding by:

Revealing assumptions: Different team members often operate with different mental models
Validating intent comprehension: Did everyone understand the purpose the same way?
Identifying communication gaps: Where did information fail to travel?
Calibrating for next time: Teams leave with aligned expectations

Integration with Broader Systems

Opspex doesn’t operate in isolation. It’s designed to interface with existing command-and-control ecosystems.

C2 System Integration

Opspex can integrate with:

NATO-standard C2 systems: Using standard data formats and protocols
National C2 architectures: Customizable integration for country-specific systems
Commercial tactical systems: ATAK, FBCB2, and equivalent platforms

Digital Twins of Operational Networks

(Future capability) Opspex can create digital twins of operational networks to:

Simulate network effects: How does jamming one node affect the whole system?
Test resilience: What happens when communications are degraded?
Optimize topology: Where should nodes be placed for maximum robustness?

Live-Virtual-Constructive (LVC) Training

Opspex supports LVC architectures that bridge simulation to real-world execution:

Live: Real operators and equipment
Virtual: Simulated operators in realistic environments
Constructive: Algorithmic forces that behave according to doctrine

This enables training that scales from individual skill development to large-scale force-on-force exercises.

The Standalone Deployment Model

Opspex can be deployed in a self-contained configuration for company or platoon-sized units — critical for austere environments where enterprise networks are unavailable.

Technical Architecture

Ruggedized, portable hardware: Laptop-class servers, tactical edge computing nodes, or vehicle-mounted systems
Offline-capable software: Full functionality without network connectivity
Lightweight, containerized modules: Docker/Kubernetes containers that require minimal infrastructure
DIL operations support: Disconnected, Intermittent, Limited bandwidth operations

Core Components

Scenario engines: Discrete event simulation, agent-based modeling, physics-based wargaming
Terrain databases: One World Terrain and custom terrain data
Entity modeling: Friendly, enemy, civilian force representations
Effects simulators: Kinetic, cyber, electronic warfare, and logistical outcomes

Standalone Features

Local data stores: Classified/unclassified scenarios stored locally
Exportable plans/orders: Generate standard operational orders for distribution
Map overlay compatibility: ATAK, FBCB2, and equivalent tactical tools
Low-footprint resource usage: CPU/GPU optimized for field laptops
Sync-when-connected: Synchronizes with higher systems when available, functions fully offline otherwise

Validation by Subject Matter Experts

All doctrine in Opspex is validated by Drago Banovic, a 20+ year Canadian Armed Forces intelligence subject matter expert.

This ensures:

Doctrinal accuracy: ATP-112, ACP-125, and other NATO standards are implemented correctly
Operational relevance: Features address real tactical problems, not theoretical ones
NATO interoperability: Outputs are recognizable and usable by partner forces

The Bottom Line

Opspex bridges the gap between doctrinal Mission Command principles and practical execution at the tactical edge.

What we’ve built:

A doctrinally-aware situational awareness layer that interprets data through NATO standards
A training simulator that enables safe-to-fail experimentation
An ATAK integration that brings doctrine to deployed units
A watch view that provides real-time operational monitoring

What this enables:

Teams that understand intent and can act within it
Decisions that align tactical actions with operational objectives
Trust built through shared rehearsal and validated competence
Adaptability in contested environments where centralized control fails

In our next post, we’ll dive into Base Defense — our first use case and the perfect scenario for training Mission Command at the tactical edge.

References

Canadian Armed Forces. B-GJ-005-300/FP-001: Operational Art and Command.
NATO. ATP-112: Tactical Employment of Forces.
NATO. ACP-125: Intelligence Reporting.
U.S. Army. ADP 6-0: Mission Command.
Drago Banovic. Personal communication. Opspex doctrine validation, 2026.

← Previous: Why Mission Command Fails
Next: Base Defense — The Perfect Mission Command Training Scenario →