ClusterOS Diagnostic Profile
Toulouse Space Technology
Toulouse Space Technology exhibits 8 observable stalls with Extracting without reinvesting and Stabilizing around incumbents as primary behavioural patterns. 5 stabilisation stacks identified.
Re-proving infrastructure (Re-proving: support programs, events) creates venues requiring coordination (Coordinating: coordination entities); coordination entities provide legitimacy for continued re-proving activity; mediation infrastructure (Mediating: intermediaries) enables coordination without forcing exclusionary decisions. Each stall's X-side provides substrate for others.
Narrating (Narrating: designations, multi-domain stories) justifies scaling activity (Scaling activity: program expansion, entity proliferation); scaling activity provides material for narrative construction (company counts, program diversity); neither requires demonstrating throughput or market validation.
Stabilizing around incumbents (Stabilising: large manufacturers/agencies in network roles) aligns with waiting for permission (Waiting: seeking official designations, institutional partnerships); incumbents provide legitimacy for permission-granting; permission structures protect incumbent positions by gating access.
Re-proving (Re-proving: multiple support programs, recurring events) generates material for narrating (Narrating: ecosystem vitality, strategic priority); narrating justifies continued investment in re-proving infrastructure; neither requires demonstrating market conversion or strategic commitment.
Extracting without reinvesting (Extracting: startup capital exits) reduces pressure on incumbents to adapt (Stabilising: incumbents maintain specialization boundaries, network positions); incumbent stability enables continued public funding substitution for private reinvestment; neither requires demonstrating startup displacement of incumbents or capital recycling.
"If outcomes from support programs (: 6 programs) were made comparable through standardized reporting, it might reduce the system's ability to absorb uncertainty about which programs generate strategic narrowing without requiring coordination entities to make exclusionary...
Leverage hypotheses are testable perturbations, not prescriptions. Where demand-side behaviour is weakly visible, the correct move is observation — improving visibility before attempting change.
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.