ClusterOS Diagnostic Profile

London AI Data Software

London, United Kingdom Extraction-Permission (Triple) 116 evidence items

London AI Data Software runs on 116 evidence items (London AI Data Software UKRI grants: 2044 grants, £2106m total, 445 distinct). The diagnostic resolves a Extraction-Permission (Triple) configuration at HIGH confidence.

9
Active stalls
5
Stacks identified
116
Evidence items
6
Leverage timeline (mo)
S1
Re-proving Instead of Narrowing
low
S2
Coordinating Instead of Deciding
low
S3
Forgiving Instead of Redesigning
indeterminate
S4
Extracting Without Reinvesting
medium
S5
Mediating Instead of Coupling
low
Stabilising Around Incumbents
high
S7
Narrating Instead of Testing
low
S8
Scaling Activity Instead of Throughput
medium
S9
Waiting for Permission
low
Stack 01 S4 · S6 · S9

Incumbents extract value while functioning as permission gatekeepers; waiting for permission delays autonomous actor formation; incumbent centrality reinforces the permission architecture that sustains extraction.

Stack 02 S2 · S6 · S9

Coordination routes through incumbents as primary nodes; waiting for incumbent-sanctioned decisions sustains the coordination requirement; incumbent authority reinforced by being the node through which coordination and permission flow.

Stack 03 S2 · S4 · S9

Coordination delays structural response to extraction by converting it into a process task; waiting delays autonomous actor formation; extraction continues while coordination and permission-seeking absorb both response capacity and opportunity signals.

Stack 04 S4 · S7

Value extraction events generate narrative about ecosystem success; narrative legitimises continued extraction by framing it as ecosystem contribution; uncertainty about whether extraction is harmful absorbed by the success narrative.

Stack 05 S8 · S9

Activity scaling absorbs immediate pressure while waiting for permission; the waiting period provides time for further activity to accumulate; both pressure and opportunity absorbed without requiring conversion or autonomous action.

"If UKRI launched a 2-year pilot programme (£10m, 50 grants) restricted to non-anchor institutions (excluding the 18 configured anchors per P019), it might reduce the system's ability to absorb opportunity signals without adaptation by demonstrating that permission architecture can operate through alternative...

6-12 months

Leverage hypotheses are testable perturbations, not prescriptions. Where demand-side behaviour is weakly visible, the correct move is observation — improving visibility before attempting change.

What happens next
This is a structural profile, not a full diagnostic.

A full ClusterOS diagnostic adds actor questionnaire data, working sessions, and anchor interviews — producing higher-confidence stall identification, board-ready stack analysis, and leverage hypotheses calibrated to your specific context.

London AI Data Software
Free Pulse Check → Request a Diagnostic →