Hi! Another member of the ossia crew here: so, no, there's no connection between both projects (so far).
However, even if both projects seem pretty similar at first sight, they might be quite different (I say "might", because I didn't find any way to download or try hyperproduction).
ossia score is initially oriented towards managing temporal behaviors and evolutions (aka "interactive scenarios") whereas hyperproduction seems more oriented towards creating and managing conditioning and mapping of control data and signal. ossia score can also do (some of) this, but so far hyperproduction seems to have a larger base of data-processing modules. Maybe we should try and see if both can be connected/made interoperable ?
Hello! Hyperproduction was my MS thesis. I can answer questions if you'd like. It's a fairly simple platform based on Node/Electron and focuses only on control automation rather than any type of "renderer" such as audio or video outputs. Furthermore, it was primarily developed in rehearsals for various productions, so it's quite rough around the edges and serves as a working toolkit for a few of us who find ourselves doing a lot of interactive performance design. Looking at Ossia, I think a fundamental philosophical difference is that Hyperproduction focuses less on being a "score" and more on mapping and completely flexible interconnection. It's a simple forward propagation network. Although there are many processing blocks, there isn't currently any enforced typing along "noodles," which means that it's a somewhat difficult environment to train new users on. You need to have a basic understanding of what all the blocks do and what types of input and output they take before really getting going.
If you would like to see some of the productions we put together, you can check out my dissertation here: https://ben.ai/research
Well, yes, ossia is initially based on a score paradigm, but our main dev @jcelerier added a node-base system recently, which kind of turns it to a node/patching system for mapping and interconnection.
However, as I said, we don't nearly have such a variety of processing blocks yet - there is a clear API to make new ones, though.
For those interested in such mappings systems, there is also http://libmapper.github.io/ that might be of some interest...