Interesting, I do wonder about FIPA performative acts. On the one hand they have a clear function in terms of tagging steps in the protocols, and the protocols have a very clear function in terms of co-ordination and resource management. On the other hand this doesn't seem to have been the driver for the development of the performative act library - rather they developed them from the perspective of "let's classify the intent of all messages".
I did a paper for AAMAS 20 years ago where I reviewed the use of performative acts by real developers. No one in my project would co-author it with me (bad sign) and it got rejected (doh) but I do believe that it was useful and it's a shame that it didn't get into the literature. Anyway, the punch line was that when devs actually tried to use FIPA they just used the performative acts in the protocols that they implemented, and those protocols were almost always Fipa-Request and Fipa-Query.
I've created some mirrors as well.
FIPA mirror : https://github.com/sgt101/FIPA-Mirror-/tree/main
and
Zeus: https://github.com/sgt101/zeus
Zeus has a FIPA transport as well as its native transport, it's got reasoning engines that it uses to act as approximately a BDI agent. The problem is that its STRIPS style planner can't reason so much... and also the RETE engine has sharp limits around rule chaining explosions and so on. The other big problem is that I haven't actually run it successfully for about 10 years due to Java versioning challenges (it works on 1.4 very well... however...)