-   Terms of Use and Privacy
Analysis | Collaboration | Documentation | Meta
  -   Terms of Use and Privacy
Analysis | Collaboration | Documentation | Meta


Understanding graph models and their application to live, operational systems, is key to preventing, mitigating, and recovering from disaster. This site explains how to do this in a simple yet extensible way.

21st Century Challenges

We have much to learn and do. We have challenges that are known generally, but how we respond to the challenges and the many crises associated with them are not known. Our systems are complicated and overwhelming to deal with for most. We decompose our work streams down to easily manageable tasks, and outsource the details to cloud companies to address this problem.

But, decomposing our work streams and outsourcing knowledge of our systems, makes us reliant on others for how we run organizations and our civilization. The global supply chain is our civilization at this point in history. We know that much will change, but we are so busy working our tiny components, fed more and more slop of control by those we have outsourced knowledge to, that we are powerless to react quickly.

Graph Kit

Graphs have been part of math and computer science education for centuries. One kind of graph is a tree, which looks like a taxonomy, and has been used to organize knowledge for thousands of years. When Tim Berners-Lee invented the World Wide Web, his background bled into his work. While on the surface he was simply porting hypertext to utilize internet communication protocols, he knew about domains of knowledge and broader kinds of graphs.

Most current successful knowledge stores utilize graphs. We have built sophisticated ontologies as graphs, some even laid down on top of the World Wide Web. The flexibility and power of graphs to capture quickly changing and varied information is undeniable. The same organizations that we turned to when our systems became too complicated to manage internally, all leverage graphs for their products.


Buckminster Fuller wrote about The Great Pirates in his book Operating Manual For Spaceship Earth. From a certain perspective, the current leaders, with a couple glaring exceptions, were The Great Pirates of the Information Age, the age where knowledge at velocity was a requirement to survive at the current complexity of the global supply chain. My thought is that all participants have become ensnared, from the organizations that rely on large cloud parties, to the cloud parties themselves.

I want us to break out of thinking along those lines. I want the velocity of knowledge facilitated by graphs to be dynamic, elastic, and flexible. By definition this excludes relying on a handful of companies with massive, centrally controlled compute. I see a new form of knowledge pirate, one that is able to utilize all of the open, free tools that have been built up for the good (and used by a handful of companies to ensnare us, with our blessing at first).

Who am I to make such a bold statement? I have worked in some of the nastiest snarls of IT in my career. I also know what velocity means during many tours running IT in start-ups. As most everybody I worked with moved away from understanding systems end-to-end and ceding to cloud, I took the opposite approach, trying to fix what existed, model it, and own it again, rather than the typical fix of tossing the old and buying brand new cloud solutions. In the process, I realized that these methods were universally useful for many kinds of challenges. Further, it offered a tool kit worthy of Fuller's Great Pirates during the future opportunity of broad legacy collapse.


Bob Dylan was called an anarchist because he didn't offer any solutions. This site does not offer a tangible solution. There is no product. What it offers is more of a pirate tool kit for the next batch of Great Pirates that navigate the troubled waters ahead. What is the basic element of this tool kit? It is the lowly triple, an atom of knowledge that can model systems in orchestration with other triples, just a notch above a key-value pair.

2021-08-07: Triple Specification
2021-06-03: Fill In Between
2021-04-15: Placeholder
2021-04-13: Placeholder
2021-04-13: Placeholder
2021-04-11: Placeholder
2021-03-24: Maps vs. Values
2021-03-20: Autonomy and System Resilience
2021-03-16: Progress on Live Visualization
2021-03-16: The Trouble with Triples
2021-03-10: Edges and Labels
2021-02-15: Dot on the Fly With Xdot
2021-02-15: Dot-ish to Triple Filter
2021-02-14: Level Zero