Having worked on hard realtime systems for years, the definition is quite clear. Everything you describe falls into the soft realtime bucket because missing a d

Having worked on hard realtime systems for years, the definition is quite clear. Everything you describe falls into the soft realtime bucket because missing a deadline isn't a system fault, it's just undesirable, not to mention that system load can and does affect hitting deadlines. "Soft realtime" is fairly broad term that gets abbreviated and thrown around in domains in which it is not appropriate. What this article describes is really just a UI and architecture that enables live updates. There's no deadline, there's not even a concept of wall clock time baked into the system. We understand despite the muddling of terms, but let's not pretend that precise language isn't desirable to the best extent possible.