USE CASES · CORTEX
Intelligence software for law enforcement
Build intelligence assessments with traceable sources, reviewed analysis and controlled sharing.
CORTEX helps law-enforcement intelligence teams manage requirements, authorised collection, source evaluation and intelligence reporting. Original material stays connected to cited analysis, while review and release controls record who approved the assessment and its audience. The workflow supports intelligence-led policing tasks such as threat assessment, gap identification and follow-on tasking, without replacing investigative case management or legal decision-making.
Threat assessment and intelligence-led tasking
Example workflow: an intelligence unit assesses a pattern of reported activity before a tasking decision. Record the question, deadline and handling restrictions, check existing holdings, and review source authority before additional collection. Preserve original material, compare explanations and distinguish reported claims from analytical judgements. Submit the assessment for independent review, release it to authorised recipients and use corrections or new reporting to guide reassessment.
01 · Intelligence requirements for policing decisions
Define the intelligence question, decision point, deadline, priority and gaps before collection starts. Assign an accountable owner and retain scope changes. An internal RFI lets the team check holdings and record cited answers, nil returns, refusals or referrals.
This supports the requirements and tasking work behind intelligence-led policing. Decisions to collect, close or retask remain explicit, with reasons recorded for later review. Application priority and permissions do not create investigative powers.
02 · Source authority and permitted collection
Record permitted methods, intended use, authority references, restrictions and validity for each source. Collection tasks connect the reviewed source revision and requirement to an eligible collector and time window.
Review expiry, withdrawal and amendments before new use. The organisation remains responsible for lawful powers, necessity, proportionality and approvals; CORTEX records the reviewed authority and enforces the permitted workflow.
03 · Original material, provenance and integrity
Retain original TXT, PDF, DOCX, CSV and JSON material with acquisition context and an integrity hash. Keep originals separate from processing derivatives, giving analysts a stable reference for the material behind an assessment.
Where an approved scanner is adopted, exact-byte verdicts are linked to the original hash, engine and policy. Failed or unavailable outcomes remain quarantined. Preservation supports intelligence provenance, while evidential admissibility requires separate legal procedures.
04 · Source evaluation and analyst interpretation
Use structured extraction segments and locators to cite exact passages. Analysts can accept, reject or correct extraction suggestions with reasons. Reprocessing creates a new derivative while earlier citations remain attached to the version originally used.
Keep source reliability separate from information credibility and analytical confidence. Preserve original observations and grades during reassessment, and record unknown reporting origins as limitations when evaluating corroboration.
05 · Entity and relationship analysis
Analyse cited entities and relationships with Draft, Proposed, Accepted and Rejected states. Retain supporting and contradictory evidence, and use bounded graph traversal that respects handling restrictions and visibility.
Record alternative explanations and uncertainty before drawing conclusions from associations. A relationship remains an analytical record supported by citations, with independent review of the submitted assessment rather than an assumption that every link proves intent.
06 · Intelligence reports and authorised sharing
Prepare a versioned intelligence assessment with exact citations, an information-as-of date and stated limitations. Release review and independent approval apply to the content and its intended audience, separate from PDF, DOCX or JSON draft exports.
Where adopted and authorised, reviewed UK domestic sharing records agreements, recipient purpose, originator conditions, approved projections, transfer and receipt. External sharing arrangements remain subject to the organisation’s disclosure authority.
07 · Corrections, feedback and follow-on tasking
Connect feedback to the exact package received and acknowledged. Record usefulness, timeliness, corrections and outstanding needs, giving requirement owners a clear basis for follow-on collection or a revised assessment.
Preserve earlier reporting and acknowledgement when corrections arrive. The owner decides whether to close, reopen or retask the requirement, or commission a new product and release, retaining the reason for each decision.
08 · Post-quantum security for sensitive police intelligence
ML-KEM key establishment, ML-DSA signatures and independently keyed double AES-256 (dAES) support confidentiality and integrity for sensitive intelligence. Current-authority access checks and retained workflow records complement the cryptographic protection.
Agree identity, key custody, revocation, retention, correction and recovery arrangements for the deployment. Security assessment should cover external data flows and organisational obligations; the platform is not a statutory compliance or accreditation certificate.
Example workflows illustrate the documented capabilities. Deployment acceptance, lawful use and accreditation are assessed for each organisation and environment.