Conduit OS

Overview

The Conduit OS (Operating System) is a purpose built suite of software that implements protocol driven commerce on a temporal, rights-based, graph of graph DLT. This produces a left to right solution for governance and commerce that models reality presenting a low-friction path for existing paper-based contracts and agreements to migrate to digital on the Conduit Network. It is designed from the ground up to be composable, auditable, scalable and secure.

Protocol Engine (Computable Contracting Platform)

The core of the Conduit Network technology stack is the Computable Contracting Platform. The Computable Contracting Platform is a protocol engine which is to say that it is an engine that produces protocols. For Conduit, protocols are the codification of agreements, which in many cases contain one or more transactions. With this foundation established we will call protocols implemented in the Conduit Network "Computable Contracts".

Computable Contracts are a combination of composable State Machines and Workflows that leverage data from Core Services in thier execution. Computable Contracts have a number of advantages over Smart Contracts designed to work with blockchains:

• State Machines are notoriously fast and can even be written to a chip level expanding Computable Contracts execution environment possibilities.
• Core Services presents a Graph of Graph DLT system that provides much more flexiblilty than traditional blockchain concerning data structures.
• State Machines and workflows are inspectable during execution which allows Parties engaged in a Computable Contract to see where all data aspects of a Computable Contract are, at any given time.
• This also presents the opportunity for Computable Contracts to adapt to emergent reality, allowing parties to make multilateral decisions on the fly (just like real world non-digital contracts today).
• Computable Contracts were also designed to be auditable from the ground up (State Machines produce a fixed number of outcomes by design) making them easy to interpret by jurisdictional law.

The power of a protocol: Protocls often become the standard or cannonized way of doing things, a foundation upon which other things can be built. For instance TCP/IP is a set of protocols that nearly all of the Internet is built upon.

Core Services

The key challenge in any form of contracting, digital or not, is modeling reality. Contracts exisit to put parameters on what "should" happen in agreements and the contingency behaviors. The problem with modeling reality is that it is emergent or non-deterministic. Petri net theory is an approach to mitigate this problem which in TLDR; form says: I will consider something is true (a part of reality) if there is sufficient evidence to support that claim. So to implement Computable Contracting we needed to build a "net" for evidence. For this digital evidence to be useful we need to establish a taxonomy. This implemented taxonomy is what Conduit Network calls Core Services. The Core Services represent a way to collect, store, and recall evidence needed for Computable Contracts, in other words Composable Proof.

ESSL

Much of the Core Services layer is built upon a custom event store which implements a persistent hash chain (a form of Merkle tree used to make records tamper proof). ESSL stands for Event Store Specification Language. ESSL is Conduit Network domain specific language (DSL) that is used to articulate models as well as automatically generate functional code around those models. This affords Conduit Network the opportunity to be language agnostic at many levels as moving to a new lower level language like Golang, Rust, or Java is just a new code generation specification rather than a full re-implementation of a code base. The other benefit of this approach (creating a DSL) is that multiple levels of APIs design for consumption by clients can be code generated from ESSL.

Protocol API

Conduit Network produces a protocol level API, that is generally a reflection of the information in a Computable Contract. This API primarily only useful in interfaces between Core Services or Computable Contracts as data being passed is more reflective of how it is stored than how it might be used in a business use case. Therefore this API is typically used only for low level communication and to create higher level APIs that service use cases of a Computable Contract.

API interpretation by Use Case

Conduit Network generates a use case based taxonomy to interpret the Protocol API in order to effectively bridge the gap between the data models used for system architecture and the data models used for user interaction. Use cases are also then symbolically linked together to support higher level use cases which then start to inform endpoints for APIs to be used by application developers.

Back-end for Front-End APIs

One of the goals of the Conduit Network technology stack is to provide a set of tools that allow application developers (Web 2.0 app and Web 3 dApps) to build business models. This means they will need both consistency and flexibility from an API. Many current fixed endpoint API structures limit business models inherently by thier structure. For example, some applications (and application execution environments) benefit from making many request with small payloads, while others need to be very efficient with the number of requests, most would benefit from being able to optimize this for thier specific use cases and business model. This dual layer API architecure allows Conduit Network and those building on Conduit Network to build robust tooling to implement back-end for front-end APIs and with a well defined Protocol API even engage AI to support in this process. This offers an optimization option to third-party application developers that is typically only available to first-party application developers.

Business Models

The ultimate goal of the Conduit Network technology Stack is to increase the velocity of business model execution. Business is based on contracts and agreements, Conduit Network has assembled a package of cutting edge technologies purpose built to bring ideas to life faster, safer, and more transparently than any platform today. The Computable Contracting Platform is the bridge between Web 2.0 and Web 3.0, bringing access to technologies like Distributed Ledger Technology (blockchain), Distributed Identity, Syncronized Accounting and more. A bridge that delivers composable protocols, based on composable state machines, that leverage composable proofs which gives the application developer an uncompromized platform of flexibility and data integrity to build upon.