I very much align with that notion as described on the website. I also think it is the way forward for a more powerful task-oriented fediverse that breaks out of its application silo’s. I see such services as building blocks that might result from a domain-driven design exercise and define a single concept of bounded context well. For that a dedicated 'micro-'ontology/vocab can be created, and standardized on, together with some description of ‘domain logic’ that you’d need to adhere to in order to interoperate.
The only thing maybe unfortunate thing in your choice of title / domain name, is that ‘microservices’ are already so much tied to a very specific architecture in the minds of many people, i.e. of fully decoupled individually deployed services that you invoke over the network through (oftentimes ‘REST’) API’s. But they could just as well be defined in a monorepo or monolith app.