Financial Services Illustrative engagement Factory run complete

From £2.3M/month in declined mortgages to a deployed AI re-scoring platform — through five human gates.

NorthBridge Bank is a fictional UK retail mortgage lender, built to give the pipeline a realistic brief. The engagement, the pipeline run, and the artefacts are real. The client is not. Every figure shown is from the factory run itself.

Engagement IDTKA-NB-20260702-001
Readiness score84 / 100 · Conditional
WAF readiness76% · Conditional handover
Gates passed5 of 5
Critical findings0
Compliance frameworksFCA SYSC · ISO 27001 · ISO 42001 · UK GDPR · NCSC CAF

The problem

NorthBridge Bank was losing approximately £2.3 million per month in revenue from mortgage applications that its legacy credit scoring model was automatically declining — applications that senior underwriters believed were creditworthy when reviewed manually.

The root cause: the legacy model ingested only internal credit history. It could not consume open banking feeds, affordability signals, or behavioural data. Edge-case applicants — self-employed, recently relocated, thin credit file — were declined with no secondary review pathway.

A board directive set a 90-day window. Challenger banks already had this capability. The requirements were non-negotiable: Azure-native, UK sovereign data residency, FCA-regulated with a full audit trail on every AI decision, and explainability under FCA Consumer Duty.

£2.3M
revenue lost per month
90
days to MVP — board mandate
0
secondary review pathways available

The constraints the factory had to honour

🏴󠁧󠁢󠁥󠁮󠁧󠁿
UK Sovereign
All data — applicant PII, open banking feeds, model outputs, audit logs — UK South only. No cross-border replication.
⚖️
FCA Consumer Duty
Every AI decision must produce a human-readable rationale under FCA SYSC 6.3 and Consumer Duty. No black-box model.
🔐
Zero Trust
Partners access over the internet — no corporate network assumption. Internal underwriters on Entra ID-joined devices. Zero Trust throughout.
🏦
Open Banking Integration
Third-party FCA-regulated AISP delivering via REST API with OAuth 2.0. Existing data in Azure SQL and Microsoft Dataverse.

How the factory ran it

Four agents. Five human gates. Nine video chapters. Every step is in the evidence pack below.

01
Minerva · Discovery & Requirements
Gate 1 · Specification sign-off

Minerva captured the NorthBridge requirement through four Logic Gates, asking exactly three clarifying questions. Data residency, regulatory classification, and connectivity were all ambiguous in the initial brief — Minerva refused to proceed until each was resolved.

The requirement locked: UK sovereign, Zero Trust, FCA Consumer Duty explainability, PII and contracts under UK GDPR. A Readiness Passport was issued at 84/100, Conditional — the conditional flag attached to the open banking OAuth flow, requiring the AISP's token handling to be confirmed before architecture was finalised.

02
Vitruvius · Architecture & Blueprint
Gate 2 · Well-Architected sign-off

Vitruvius designed the cloud topology against WAF and CAF 2026 frameworks. The Sovereign Gate applied: any pillar scoring below 7 in Security or Reliability would auto-reject the design. The architecture passed.

Key decisions: Azure Machine Learning (UK South, private endpoint) for the re-scoring engine; Azure OpenAI (Sweden Central, Standard regional — not Global) for the Consumer Duty explainability layer; Azure API Management in internal mode for the open banking OAuth gateway; Azure SQL with TDE and customer-managed keys; Entra ID B2B for partner access. All Bicep-first, Azure Verified Modules.

03
Themis · Compliance Audit
Gate 3 · Artifact and code sign-off

Themis cross-referenced the architecture against six control frameworks: ISO 27001, ISO 42001, FCA SYSC 6.3, FCA Consumer Duty, NCSC CAF, and UK GDPR. The pre-flight compliance report surfaced 3 blocked items that had to be resolved before IaC generation could begin.

  • BLOCKED: Azure OpenAI Global SKU proposed — replaced with Standard regional (UK + Sweden Central) to enforce data residency.
  • BLOCKED: Public network access enabled on AML workspace — private endpoint enforced.
  • BLOCKED: OAuth token storage proposed in app config — moved to Key Vault reference.

All three resolved before Gate 3. Zero blocked items at handover.

04
Vulcan · IaC Build
Gate 4 · Deployment authorisation

Vulcan generated AVM-first, born-compliant Bicep from Fabricius's approved implementation plan. Seven modules: Key Vault with customer-managed keys, Azure ML workspace, Azure OpenAI, API Management (internal mode, OAuth policy), Azure SQL (TDE, private endpoint), main orchestration, and production parameters. Zero hardcoded secrets. Tagging lock on every resource.

A pre-build assessment was issued before a single line of Bicep was written, confirming implementation feasibility against the approved design. The Azure DevOps backlog — 138 work items across infrastructure, model training, API integration, FCA audit trail, and QA sign-off — was generated and imported to the client's board in a single operation.

05
Themis · Final Adversarial Review
Gate 5 · Final acceptance

Themis executed the final adversarial review of the deployed system — not the design, the live deployment. Runtime misconfigurations, credential leakage in Application Insights logs, and Consumer Duty explainability output were all checked against the as-built state.

WAF composite: 76%. Two high findings and four medium findings flagged for operator sign-off. Zero critical findings. Gate 5 status: Conditional — the two high findings were documented, accepted, and tracked in the as-built report. IP transferred. Factory disconnected.

What the factory produced

84/100
Readiness Passport — conditional approval to proceed
3
Blocked compliance items surfaced and resolved before build
7
Bicep modules generated — AVM-first, zero hardcoded secrets
138
Azure DevOps work items generated and imported to client board
76%
WAF composite readiness at handover
0
Critical findings at Gate 5
5/5
Human gates passed — nothing advanced unreviewed
100%
IP transferred to client at Gate 5 — code, docs, model lineage

Watch the factory run

Nine chapters. Eight minutes. Every step of this engagement — Minerva's intake, Vitruvius's architecture, Themis's compliance audit, Vulcan's Bicep generation, and the Gate 5 handover — is in the evidence pack. Open and ungated.

Open the evidence pack → Book the live demonstration

NorthBridge Bank is a fictional UK retail bank created to demonstrate the Talastron Kinetic AI pipeline against a realistic, regulated brief. The pipeline run, artefacts, scores, and findings shown are from the actual factory session. NorthBridge Bank is not a real client, system, or dataset. All figures are from this illustrative engagement only.