Abstract

In this episode, we dive into the concept of ssotme://, a universal protocol for business rules that builds upon the Business Rule Completeness Conjecture (BRCC) and the Conceptual Model Completeness Conjecture (CMCC). We explore how these ideas allow companies to capture and transfer rules from one technology stack to another without losing fidelity—much like Git for text files, but specifically aimed at preserving semantics.

Zero-to-Sixty Podcast summary webpage for the episode page.

ssotme, BRCC, and the Future of Semantics

Chapter List

• Introducing ssotme://

• A quick overview of the ssotme:// protocol and how it compares to Git, focusing on capturing semantics rather than merely storing syntax-based diffs.

• What Are BRCC and CMCC?

• Explaining the Business Rule Completeness Conjecture and the Conceptual Model Completeness Conjecture in simple terms, emphasizing how they support universal rule portability.

• Practical Demonstrations

• Walking through real-world scenarios—such as exporting an Airtable schema and data into Baserow or a Django project—to illustrate how the same core business rules can be re-expressed in different platforms.

• The Future of Semantic Sharing

• Speculating on how this approach might evolve into a new standard for cross-system interoperability, empowering teams to develop multi-stack solutions while preserving a single source of truth.

Executive Summary

In this episode, we focus on how capturing and sharing declarative business rules—independently of any single programming language—can dramatically streamline cross-platform development. By leveraging the Business Rule Completeness Conjecture (BRCC), we see that virtually any complex logic (time-based, multi-step, etc.) can be broken down into static facts, lookups, aggregations, and calculated fields. Coupled with the Conceptual Model Completeness Conjecture (CMCC), it becomes clear that these abstractly defined rules (the “hole and water” analogy) can be transported, versioned, and reconstructed in entirely different environments with zero loss of fidelity.

Key Takeaways

• Declarative Over Imperative: By focusing on what a rule says rather than how it’s executed, teams can unify their logic in a BRCC-compliant rulebook.

• Universal Portability: A schema-plus-data approach allows for easy transfer to and from systems like Airtable, Baserow, SQL-based platforms, or even full-stack frameworks in Django, Node.js, and more.

• ssotme:// Protocol: Envisioned as a universal transport for semantic data, ssotme:// stands to become the standard for sharing business rules across the industry, similar to how Git revolutionized text-based collaboration.

By embracing these notions, organizations can future-proof their logic and avoid the fragmentation commonly seen when business rules scatter across various microservices, databases, and code repositories. The approach offers a unified lens through which to view and manipulate critical enterprise semantics, creating a single source of truth that’s both robust and flexible.