This article is just describing Clojure. The SUPER principals are describing the native natural way of writing Clojure, no category theory needed.

My impression too. Most of what is in this post I've discovered almost entirely through clojure and I'm not even a clojure dev, just try to explore it in my free time. I did cmd + f in browser and searched for clojure pretty soon in to reading this.

OP here: thanks for chiming in.

I've explored Clojure after talking to Metabase about how it had benefited them. That said, it was years ago so I can't claim it influenced this work.

The framework was designed to be a language agnostic way of sharing best practices to bias agent behavior towards a more scalable end. I initially used it when I was working with a team to do some massive refactoring/clean up across the codebase. We didn't come to an acronym but similar principles and it was "testable" and easy to push back on PRs that weren't aligned with the principles.

That said, it may be interesting to see if I could replace all that context and just say -- "code it like you would with Clojure"

Have you tried that?