USE CASES · CORTEX
Military intelligence software for intelligence units
Support commander-led intelligence requirements, collection planning and staff assessments.
CORTEX supports military intelligence staffs from the commander’s information need to a reviewed intelligence product. JDP 2-00-informed terminology connects PIRs, SIRs and EEIs to collection tasks, retained evidence and analytical judgements. Joint intelligence estimate and JIPOE draft starters help staff prepare products, with source evaluation, independent review and controlled dissemination built into the production workflow.
From commander’s requirement to staff assessment
Example workflow: a commander needs an assessment of a change in the operational environment before a planning decision. Staff record the PIR and supporting SIRs and EEIs, review holdings, and plan authorised collection against available capacity. Analysts compare explanations and record uncertainty. A selected analysis revision forms the basis of a Joint intelligence estimate or JIPOE draft, followed by independent review, authorised release and feedback on remaining gaps.
01 · JDP 2-00-informed PIR, SIR and EEI management
Record the commander’s decision need, deadline and information gaps as linked intelligence requirements. Use priority intelligence requirements, specific intelligence requirements and essential elements of information to organise the work, with an owner and retained revision for each requirement.
The workflow reflects the terminology reviewed from JDP 2-00, Fourth Edition, August 2023. Requirement changes remain visible to the staff, connecting the current question to its collection and analysis history without replacing command authority.
02 · Collection planning and resource deconfliction
Build collection plans around the objective, handling restrictions, reviewed source revision, eligible collector and task window. Resource availability and reservations help staff identify capacity conflicts before tasking proceeds.
Record priority and deconfliction decisions, responsible owners and revised windows for displaced tasks. CORTEX manages the collection workflow; sensor control and external military-system tasking require separately established interfaces and authority.
03 · Source evaluation and collection results
Capture the observation, acquisition time, credibility assessment and remaining gaps for each collection attempt. Retask work with a new attempt and result, preserving the original reporting rather than overwriting it.
Keep source reliability, information credibility and analytical confidence distinct. Shared reporting origins remain visible when assessing corroboration, giving analysts a more reliable basis for comparing reports from different channels.
04 · Structured analysis of the operational environment
Record competing hypotheses, assumptions, discriminating checks and significant disagreement. Separate PHIA probability from analytical confidence, and use time-bounded judgements to make reassessment practical when the operational environment changes.
Defence lenses and futures methods extend the retained evidence workflow. Independent challenge examines the submitted revision, giving staff a record of the reasoning, alternatives and uncertainty behind the assessment.
05 · Joint intelligence estimate and JIPOE drafts
Prepare an editable Joint intelligence estimate / JIPOE draft from a selected analysis revision. Other starters include Brief, Assessment, Intelligence Assessment and Intelligence and security directive (draft), with retained judgements, assumptions, gaps and citations.
Draft templates organise staff reporting and support JDP-informed production practice. Staff retain responsibility for the assessment, its review and its use; a draft directive is not an issued operational order.
06 · Staff review and controlled dissemination
Give reviewers the exact product revision, information-as-of date, processing declarations and limitations. Independent review and approval precede publication to the selected internal audience, with a separate publisher decision.
Keep draft export, approved release, publication and receipt as separate states. Audience or content changes receive renewed review where required. Foreign disclosure and cross-domain transfer need their own authorised arrangements.
07 · Feedback, indicators and retasking
Record recipient acknowledgement and feedback against the released package. Staff can assess relevance, timeliness, corrections and gaps, then decide whether the originating requirement needs closure, reopening or further collection.
Indicators and observations provide a basis for deliberate reassessment. Preserve the earlier judgement and record why it changed, so follow-on tasking addresses the current intelligence gap rather than repeating completed work.
08 · Post-quantum protection for military intelligence
ML-KEM, ML-DSA and independently keyed double AES-256 (dAES) support the protection of sensitive military intelligence and data integrity against evolving threats. Assess these controls alongside local operation, handling restrictions and access management.
Agree identity, key custody, recovery and disconnected-operation dependencies for the proposed deployment. Classified-network accreditation, operational integration and acceptance must be assessed for the actual environment.
Example workflows illustrate the documented capabilities. Deployment acceptance, lawful use and accreditation are assessed for each organisation and environment.