Mission-Frame Pre-fill
Extracts the decision owner, LTIOV, ALU, and threshold problem statement from scenario inputs for analyst review.
360iSR’s Integrated Decision-Driven ISR methodology reframes intelligence collection as a decision-enabling discipline. Every sensing task, every fusion product, and every intelligence requirement traces back to a named commander’s decision — not to platform availability or collection habit. AI augments that chain without replacing the human judgement at its heart.
An operating logic of Understand, Decide, Effect — governed by command intent, not machine tempo. Each cycle reshapes the others.
Traditional collection-led ISR begins with what sensors are available and works forward to what they can observe. IDDI inverts that logic. It begins with the commander’s decision — the specific threshold judgement that must be made, by whom, by when, and at what acceptable level of uncertainty — and works backward to determine what sensing, fusion, and staff action is required to support it.
In practice, decision-driven means that no ISR task is generated, no collection asset allocated, and no intelligence product commissioned without a traceable link to a named decision. IDDI’s operating logic — Understand, Decide, Effect — is not a linear sequence. Understanding shapes decisions; decisions reshape sensing priorities; effects generate new understanding. The cycle is governed by command intent, not machine tempo.
Problem-Centric Analysis (PCA) defines the threshold problem the commander must resolve. KASNIAN (Key actors, Alliances, Structures, Norms, Interests, Attitudes, Networks) maps the decision ecosystem inside that problem. Threshold-Evidence logic — testing Activity, Attribution, and Intent/Effect — provides the judgement mechanism. IDDI orchestrates all three, keeping every output anchored to decision relevance rather than collection capacity.
Define the threshold decision: what, who, by when, and at what acceptable uncertainty.
Translate the problem into a specific DSR — what clarity the commander needs, in which category.
Derive sensing, fusion, legal, and staff actions from the DSR — not from sensor availability.
Fuse outputs across domains; rate confidence using the Absent-to-Confirmed ladder.
Assess convergence of Activity, Attribution, and Intent/Effect; feed the verdict back to the decision.
“IDDI does not promise control of complex conflict. It offers something more realistic and more valuable: the ability to decide and act coherently, faster and with greater confidence, in an environment designed to defeat certainty.”
The demonstrator visualises a KASNIAN Decision Space Map for a notional operational scenario. Each node represents an actor, system, structure or condition that materially affects the commander’s decision. Colour, position and size encode group affiliation, polarity and decision-forcing weight — making the decision space legible at a glance.
Nodes above the dashed threshold line (Y ≥ 7) carry the highest decision-forcing potential and require a Priority DSR before mission start.
Nodes to the right are assets or enablers; nodes to the left are constraints, adversaries or friction. Swing actors near the centre warrant particular analytical attention.
The coloured outer ring denotes the primary DSR category — red for PIR/Kinetic, orange for ROE/Legal, purple for Fusion/COP, cyan for ISR Tasking, yellow for C2/Comms, green for OPSEC/EMCON.
This is a training scenario using a fictitious country (KASNIA) and an entirely fabricated order of battle. It contains no classified information and is marked UNCLASSIFIED // TRAINING USE ONLY throughout.
AI assistance within the 360iSR IDDI workflow is precise in its scope. It operates at the analytical preparation and pre-fill stages, and at fusion and convergence. It does not operate at the decision stages.
AI assistance within the 360iSR IDDI workflow is precise in its scope. It operates at the analytical preparation and pre-fill stages — reducing the time an analyst spends on structured but mechanical tasks — and at the fusion and convergence stages, where pattern-surfacing and gap detection add genuine analytical value. It does not operate at the decision stages.
In the end-to-end ISRT workflow, the process contains five operator interaction points: three doctrinal Human Gates and two checkpoints. Human Gate 1 fires after §2C — the commander’s threshold framework, risk-confidence linkage, and decision families must be confirmed by the commander before the workflow advances. Human Gate 2 fires after §6 — the convergence state per threshold and UK Probability Yardstick verdict must be confirmed before DSRs are generated. Human Gate 3 fires after §8 — the full DSR list, mandatory rule compliance, and priority ordering are confirmed before tasking. Checkpoint 1 fires after §10B asset declaration; Checkpoint 2 fires after the Stage 3 ISR Coordination Card is produced and reviewed.
AI pre-fills the mission frame and indicators between §0 and §2C; suggests convergence scores at §5 before the operator confirms or overrides at Human Gate 2; and generates draft DSRs at §8 for human review before Human Gate 3 closes. The operational posture throughout is: AI pre-fill, human approve. No gate may be bypassed. No analytical verdict is generated without the human operator’s confirmation at the relevant checkpoint.
Extracts the decision owner, LTIOV, ALU, and threshold problem statement from scenario inputs for analyst review.
Surfaces collection gaps, attribution weaknesses, and unresolved ambiguity drivers before the convergence gate fires.
Generates structured draft DSRs in the mandatory five-clause format — category, requirement, trigger, output — for human confirmation at Gate 3.
Flags spatial, temporal, signature, and thematic convergence across injects; presents a suggested convergence score per threshold for operator confirmation or override.
The AI does not issue collection tasking, authorise effects, or substitute for commander judgement. It does not operate without a confirmed human decision at each doctrinal gate. Autonomous sensor tasking is not a feature of 360iSR’s design. All AI-generated products carry full audit provenance. Pilot environments operate under UNCLASSIFIED // TRAINING USE ONLY classification. The human remains accountable for every verdict, DSR, and tasking action.
Request a structured briefing and we will walk through the methodology, the demonstrator, and the tooling against a scenario of your choosing.
Sessions typically run 90 minutes. We bring the demonstrator and a structured walk-through of how the IDDI chain maps onto your problem set. We respond to briefing requests within two working days.