> Typically, "monolith" implies services - ie, the "backing services"

I don't know if that's a common interpretation - in the monolith-loving companies I've worked with it very much meant a single ball of code (e.g. huge Rails app), not separate services.