Description: I describe a solution that helps collaboratively model, understand, operate and improve systems using local-first graph analysis.
Example domain paragraphs
~🌱~ Meaning Communication Maps Collaboration Streams 🌊 🌳 🧠 ☎️ 🗺️ 🌊 ☎️ 👥 facilitates 🌳 👥 🧠 🗺️ 📛 🧩 🔩 📅 ❓️ 🧭 Who is participating? How do we get there? When will we arrive? Why are we doing this? Where are we going? Where are the interactions? What are the pieces? ⏪ 🎦 🤖 ⚛️ 🗄️ 🥤 👁️ ✏️ 💡 🎼 Existing event streams for insight Replay streams over time periods BI, AI/ML stream and store Validate changes Accountable for changes Contribute to changes Agreed meaning atoms Filter for crucial knowledge Standard format (o
There is an assumption in this paper that collaborative system inquiry, leveraging existing tools like BI and AI/ML when prudent , is the most effective route to resilience ( Anderson and Burney 1999 ) . There is another assumption that fulfilling the feature requirements for resilience leads to better telemetry against documented goals. I admit this is a form of optimism, and does have some technological bias; however, my analysis likely yields many features that are familiar and useful to the reader. (🤪)
(💎) Fig. 2 lists system quality requirements. A cloud vendor might promise only three nines of availability. (💯) Coupled with external infrastructure availability, like office power or network connectivity, many organizations are running at two nines of availability. If the system is down, slow, locks up, or the user loses data, quality requirements all of a sudden become the most important aspects. For the analyst, there is a bit of crystal ball reading involved with them. What kinds of things can happen t
Xfig