Cleared to Build: AI Inside a Classified Programme
The situation
A defence prime wins a place on a multi-year framework requiring AI-enabled intelligence and surveillance capability. Models need to run across data at more than one classification, the accreditation route is unclear, and the delivery date is contractual. Engineering wants to start; security cannot yet say what "good" looks like.
What we would do
Map the real obligation set — Secure by Design, the departmental accreditation regime, NCSC CAF, and export control — into a single decision picture. Put the accreditor in the room in week one rather than month nine. Fix a cross-domain architecture pattern up front, and treat model provenance, evaluation records and human-oversight evidence as build artefacts produced continuously, not a document assembled before assurance.
Outcome: the accreditation route is agreed before code is written, months of anticipated re-architecture are avoided, and the pattern becomes reusable across subsequent bids — turning assurance from a programme risk into a competitive differentiator.