28 Apr 2026

China blocking Meta's acquisition of Manus is not primarily a story about Meta. It's a story about where agentic AI capabilities are being built, who controls them, and how quickly geopolitical friction can collapse a deal that looked done.

For UK technology leaders, the interesting question is about dependency mapping. Most organisations building AI-powered products right now are stacking capabilities from a small number of US hyperscalers, with little visibility into where the underlying research talent or model architectures originated. Manus is a useful example because it was Chinese-founded, US-acquired, and globally deployed. That structure is common. The regulatory exposure it creates is not well understood.

The agentic AI space specifically carries more risk here than foundation models. Agents take actions, hold context, and increasingly operate with access to financial data and customer accounts. Regulators in multiple jurisdictions are paying attention to exactly that kind of capability. The FCA's ongoing work on AI accountability and the operational resilience requirements under PS21/3 both point toward a world where your AI supply chain is your problem, not your vendor's.

For consumer credit in particular, the operational and compliance stakes are high:

• An agent handling affordability assessments or collections interactions needs a clear, auditable governance trail
• If the underlying capability sits in a vendor whose ownership structure is contested or politically exposed, that trail gets complicated fast

Meta losing access to Manus is a setback for one company. The broader signal is that agentic AI development is fragmenting along geopolitical lines faster than most enterprise technology roadmaps have accounted for.

The organisations that will be best placed are those that treat AI capability sourcing as a strategic and regulatory question now, before a deal gets unwound and they're left explaining a dependency they didn't fully understand to a regulator who will absolutely ask.

The UiPath-Databricks integration looks like a product announcement. It's actually a control architecture problem dressed up as a feature release.

Most of our AI deployments in consumer finance are still in the insight business. A model flags a risk, a human decides, a system records the outcome. That loop keeps us comfortable because accountability sits with a person. What UiPath is describing collapses that loop. The agent sees live data and acts on it inside the same workflow, without a human checkpoint in the middle.

In a loan origination context, that could mean an agent repricing an offer, declining an application, or triggering a fraud flag based on real-time pipeline data. Fast, yes. But the FCA's Consumer Duty doesn't care how quickly you made a bad decision. It cares whether the outcome was fair and whether you can explain it.

This is where the tighter coupling the integration requires becomes the real story. When your data pipelines, orchestration layer, and access controls are all connected to an acting agent rather than a reporting one, your audit trail and your governance model have to evolve at the same pace. Most organisations haven't done that work yet.

Two things technology leaders should be thinking about now:

• What decisions in your current workflows are actually safe to automate to execution, versus decisions that only feel low-risk because a human has always been there to catch edge cases
• Whether your access controls were designed for systems that read data or for systems that act on it, because those are genuinely different threat models

The productivity case for agentic automation in consumer credit is obvious. Faster decisioning, less manual handling, cheaper operations. The governance case is less developed and that gap is where firms will get caught out.

The interesting question isn't whether to adopt this architecture. It's whether your change management and compliance functions can move fast enough to stay alongside it.