Untitled design (57).jpg
CIN white circle.png

COLLABORATIVE INTELLIGENCE NETWORK (CIN)

The Collaborative Intelligence Network (CIN) is the flagship initiative of the Data Collaboration Alliance.

Taking inspiration from the principles of
Collaborative Intelligence we're defining an infrastructure composed of self-hosted nodes that introduce a level of control, collaboration, and efficiency to the design of new digital solutions that is incomparable to today's approach .

Repreesentation of the nodes within the Collaboratvie Intelligence Network

The end of datase silos and copy-based data integration

The CIN Blueprint is defining a global network of interconnected nodes and datasets where people and systems collaborate in a Zero-Copy environment.

 

Intelligent digital solutions (apps, automations) are not stand-alone entities but incoporated into the fabric of the network itself.

DRAFTING THE BLUEPRINT 

Currently a Google Doc, the CIN Blueprint is a collaboration between experts from a diverse spectrum of sectors, technologies, and roles.

KEY ELEMENTS

Node Roles
Node Operations
Node Governance
Standards & Protocols
Interoperability
Scaling and Expansion
Capacity Building

POWERED BY ZERO-COPY INTEGRATION

Zero-Copy Integration is an emerging standard that provides the framework for the activation of Collaborative Intelligence

Zero-Copy Integration is an emerging standard that provides the framework for the activation of Collaborative Intelligence using Autonomous Data. 

STARTING WITH NODE ZERO

Node Zero is the data-centric community that supports the Collaborative Intelligence Network initiative at the Data Collaboration Alliance

The human brain starts with a single neuron.

The internet started with a single computer.

The worldwide web started with a single server.


The CIN starts with Node Zero.

EXPANDING WITH NODE X

Node X is the free software program of the Data Collaboration Alliance in support of advanced research teams

The Node X program provides free and subsidized resources for the establishment of self-hosted nodes at universities, research nonprofits, public sector agencies, and Corporate For Good programs.

CONTRIBUTE TO BLUEPRINT

Established leaders with a passion for collaborative innovation to contribute to the CIN Blueprint initiative.

BLUEPRINT APPLICATION

Thanks. Please check your inbox (including Spam folder).

We'll be in touch soon!

 

FREQUENTLY ASKED QUESTIONS

General

What technology is CIN based on?


The CIN Blueprint is currently defining its foundational concepts and the basic operations for a network-based architecture rather than specifying technologies.

That said, there are certain combinations of technology that exist today than can support many of the intended outcomes of the CIN initiative, include Linked Data, Data Encryption, Active Metadata, and Data Mesh technologies.

Over time, the Blueprint contributors are likely to develop "compatibility tests" for applicable technologies, for example:

Does it eliminate copies of data from new digital service design?

Does it necessitate the creation of new data silos indepedent of the network?

However, no technology lives in isolation, and every effort will be made to define ways to enable the CIN to interoperate and coexist with other approaches to data management and solutions delivery e.g. graph database, blockchain.




How does this relate to Web 3.0?


Web 3.0 is a concept that aims to create a decentralized version of the virtual world, where users can interact and collaborate intelligently without worrying about the central, data-specific repositories. Overall, it will be more of a peer-to-peer internet with no single authority.

In this way, the CIN is very much aligned to the core principles of most interpreations of Web 3.0 but it extends the concept into the realm of solution delivery.




How does this relate to Self-Sovereign Identity?


Self-sovereign identity (SSI) is an approach to digital identity that gives individuals control of their digital identities. SSI addresses the difficulty of establishing trust in an interaction. In order to be trusted, one party in an interaction will present credentials to the other parties, and those relying parties can verify that the credentials came from an issuer that they trust.

In this way, the verifier's trust in the issuer is transferred to the credential holder. This basic structure of SSI with three participants is sometimes called "the trust triangle".

It is generally recognized that for an identity system to be self-sovereign, users control the verifiable credentials that they hold and their consent is required to use those credentials.This reduces the unintended sharing of users' personal data. This is contrasted with the centralized identity paradigm where identity is provided by some outside entity.

The CIN initiative defines self-managed nodes for multiple types of data stakeholders, from commercial and nonprofit organizations and government agencies down to individual citizens and their custodians e.g. parents for children.

The bottom line is that identity and credentials, while incredible important, are just data that stand to benefit from the Zero-Copy approach that is outlined in the CIN Blueprint. There's much to be worked out, but CIN is broadly aligned with the core tenets of SSI.




How does this relate to No-Code delivery?


No-code is a software development approach that requires few, if any, programming skills to quickly build an application. This allows people who have the necessary organizatonal and governance knowledge and understand the business requirements for a digital solution, but lack knowledge of programming languages, to create digital solutions such as a form, workflow, or website, or add functionality to an existing solution.

A core element of the Collaborative Intelligence Network (and the Zero-Copy Integration framwork which it leverages) is the "data-centric" approach which replaces complex code with Active Metadata and "Transient Data Models" which can be build via drag and drop using familiar query building interaces. As a result, the CIN architecture can be said to support a No Code approach.

That said, a major part of the CIN Blueprint will be to define how individual data nodes can interoperate with Low Code and Pro Code approaches by replacing solution-specific databases by providing data persistence and access controls.




What is Zero-Copy Integration?


Zero-Copy Integration is an emerging national and international standard that advocates the following core tenets:

Decouple data from applications
Access-based collaboration over copy-based integration Govern and manage data as a product (Data Mesh) Enforce controls at the data layer Create metadata-driven experiences Design for solution modularity / composability




Is this a graph database?


No. The CIN is defining an architecture for a network of nodes which are each comprised of a network of Autonomous Datsets which are governed within data domains (aka Data Mesh approach).

Each node combines the best capabilities of relational and graph representations but exceeds the performance of either.

A Graph Database is still a DATABASE silo, not part of a network of datasets, which is ironic, given that its purpose is to reveal network patterns.

That said, the CIN initiative will be working with graph leaders to explore compatibilities between the Graph Databases and the networked/linked data architecture.




Is this a Data Fabric or Data Virtualization?


No. The CIN is defining an infrastructure for the hosting, control, and operationalization of physical (but un-copied) data. Each node supports a data persistence layer.

The CIN Blueprint does however include elements of what might be described as an "Operational Data Fabric" whereby each node uses connectors to facilitate a "last copy integration" from pre-existing data silos (e.g. spreadhseets, Data Lakes, Data Warehouses, app-specific databases) onto the network.
Node connectors are intended to be bi-directional to facilitate a migration from data silos to nodes/CIN over time. A greenfield organization or project team should be able to avoid such migration patterns entirely.