AIC
Intelligence
1.
Agree the question
One representative production case, handling scope, users and required outputs.
2.
See the real workflow
Synthetic requirement to approved release — including the negative cases.
3.
Validate your deployment
Disconnected, restart, restore and upgrade tests against your own criteria.
One connected workspace
Every product stays tied to the question that prompted it.
Requirements
/
Source authority
/
Retained evidence
/
Entity relationships
/
Structured analysis
/
Product revisions
/
Controlled release
/
Explicit receipt
/
Recorded feedback
/
Source protection
/
Records and disposition
/
AI lifecycle controls
/
Assurance evidence
/
Evidence, connected
Examine an assessment against the evidence behind it.
01
Original file
The acquired byte sequence, retained with its hash and acquisition context. Quarantine and processing state are real.
02
Retained extraction
A parser output derived from those exact bytes, retained separately so the original is never replaced.
03
Exact citation
A precise retained passage or data cell, with the version and integrity detail needed to find the same material later.
Reprocessing a source does not change an older citation. Amending a report does not reuse approval for different content.
Deployment
On-premise, private cloud or public cloud.
CORTEX ships as a signed five-service node: ingress, web application, database, isolated parser and an optional local model. Run it on your own hardware, in your private cloud, or in an AIC-operated Microsoft Azure environment in the UK. Same application, same controls, whichever route you choose.
Disconnected
On-premise or air-gapped
Browser
Local CORTEX node
Application, storage and parser. Optional local model.
External capabilities are blocked before transport. An air-gapped profile ships with the node; physical isolation and disconnected acceptance are confirmed per installation.
Connected
Private or public cloud
Browser
Local CORTEX node
Application, storage and parser. Optional local model.
Approved feeds, map tiles and hosted model endpoints only, under your organisation’s policy. Hosted in Azure UK South with independent environments, or on cloud infrastructure you operate.
TWELVE SPECIALIST WORKFLOWS
Built for the specialist work your teams already do.
Beyond the core lifecycle, CORTEX ships the governed workflows that intelligence, policing, records, privacy and assurance teams rely on. The relevant owner switches each one on for an approved profile and purpose, under current permissions, with every decision retained.
Adopt UK scope and guidance
Approved jurisdiction, applicability and catalogues, adopted explicitly for new work.
Commission, analyse and assure
Agreed question and design, recorded confidence, structured challenge and independent assurance.
Plan and protect collection
Permitted lineage, source protection, independence and reserved capacity before tasking.
Review evidence and reports
Quarantine and scanning, exact-span annotation, and approved projections of received reports.
Run police tasking
Force policy, control strategy, strategic and tactical assessments, subject and problem profiles.
Handle privacy and records
Bounded processing, rights requests, retention appraisal, holds and verified disposition.
Share to an approved recipient
Recorded agreements, identification-risk review, exact projections and transfer receipts.
Explore context and futures
Adopted lenses, intelligence-estimate sections, scenarios and unintended-effect sessions.
Govern people, risks and assurance
Asset and role risk, appointments, control baselines, incident correlation and custody receipts.
Use and review AI
Registered use cases, dataset rights, evaluation thresholds, approval, suspension and retirement.
Close the learning loop
Exact-version feedback, qualified outcome evidence, assigned lessons and verified completion.
Operate and extend the node
Approved data flows, signed bundles, recovery, workload sizing and justified optional capability.
Example operation · The intelligence lifecycle in action
Post-quantum security by design
Protect national interests. Prepare for quantum threats.
01
Fail-closed authority
Every content operation needs a current identity, an unexpired grant, workspace membership, a permitting role and the full handling scope, compartments and caveats included. Anything missing, malformed or expired fails closed.
02
Isolated processing
Uploaded files are treated as untrusted. Extraction runs in a separate non-root container with a read-only filesystem, capped memory and CPU, a hard deadline, and no access to database credentials or application keys.
03
Signed and recoverable
Release bundles are signed. Backups are encrypted without staging plaintext, carry a signed manifest, and restore into fresh storage only after signature, hash and image identity checks pass.
Protect national interests with post-quantum key establishment using ML-KEM, digital signatures using ML-DSA, and two independently keyed AES-256 encryption layers (dAES). Handling labels run from OFFICIAL to TOP SECRET, with versions, actors, timestamps, reasons and integrity hashes retained for documented changes.
AI, on your terms
Run a pinned local model on the node, or an approved endpoint you control.
01
Local model
A pinned, digest-verified model runs on your own hardware. No automatic download, no substitute model, no cloud fallback. Generation works in both Online and Offline modes.
02
Approved remote model
In Online mode, connect an OpenAI-compatible endpoint you have approved, with protected credentials and a handling ceiling. Tools, retrieval, remote storage and retries are switched off for this workflow.
03
Provenance you can inspect
Each assisted draft records the provider and model, prompt version, source and requirement versions, hashes and the first-draft fingerprint. The analyst reviews and edits before anything is saved.
Model assistance prepares an editable first draft from a bounded, authorised dataset. Review, approval and release stay with people.
Built to be trusted
Everything we say about CORTEX, we can show you running.
Every capability on this page is implemented, tested and demonstrable end to end, from the first requirement to an acknowledged release.
What CORTEX does
Connects requirements, retained evidence, analysis, products and feedback.
Supports local operation without requiring cloud AI.
Retains exact revisions, citations and audit history.
Requires independent approval for exact release content and audience.
Records explicit acknowledgement of a package by a named recipient.
What that means for you
Every assessment traces back to the evidence and the question behind it.
Sensitive material stays where you decide it runs: on-premise or in your cloud.
Reports, approvals and receipts stand up to scrutiny years later.
Analysts get AI assistance while keeping full control of provenance.
Your handling rules, compartments and caveats are enforced on every action.
Ask for a live walkthrough and watch the full chain run on a synthetic case, from requirement to acknowledged release.
Verified in build, browser and deployment.
2,506
Distinct standard-gate tests with passing evidence
105
Browser scenario executions across three configurations
175
User stories delivered across 32 feature groups
Zero
Browser errors or external requests in Offline runs
Every figure comes from named, dated runs across the application, browser suites and the release pipeline, recorded against an exact source revision. The full evidence register is available on request.
What buyers ask before they commit.
COMMON QUESTIONS