BLOG
Insight, not filler.
Notes on contract consolidation, deterministic extraction, and what changes once a business can prove what it signed.
UK CTP Regime: Why Hyperscaler Oversight Doesn't Cover Your Contract Obligations.
CTP designation gives regulators a direct line to four hyperscalers. It does nothing for your obligation to know what you signed with them.
On 13 July 2026, the Bank of England, PRA, and FCA started overseeing Amazon Web Services, Microsoft, Google Cloud, and Oracle directly. HM Treasury has said the list will grow. What hasn't changed: firms still have to produce a specific answer on exit clauses, notice periods, and data portability the moment a regulator, auditor, or board asks. If that answer sits scattered across a master agreement and a hundred-plus order schedules, someone is reading documents from scratch to construct it. CTP designation didn't create that problem. It just made it visible.
The amendment you don't know is missing
You cannot check for a document you don't know should exist. A checklist only works when someone already knows what's missing. The fix isn't a better checklist. It's reading the contract chain itself: a master agreement that references Appendix 4 tells you Appendix 4 should be there, whether or not it's in the file. Read the whole estate as one chain and the gaps announce themselves.
Why we didn't build this on a large language model
A contract's current position isn't something to guess at, however well. Most of what looks like an AI problem is actually a structural one: matching an amendment to the clause it changes, tracing a defined term back to its source. Rules-based logic handles that reliably, the same way every time. A small language model (SLM) only earns its place where genuine language understanding is required, and even then, its output gets checked against the source document before it's presented as an answer.
