Independent companies, developers, agents, and institutions should be able to build and transact on a shared fabric. Owning every application would make EXOCHAIN a portfolio. The strategic objective is a platform other organizations can adopt without permission to exist.
Open protocols, SDKs, and enterprise services. The platform earns its place by being useful to companies EXOCHAIN did not create, does not own, and does not control. Core software is Apache-2.0 and is in beta (v0.2.7), under normative specification v2.2.
The concrete result a buyer can evaluate: who authorized an AI-assisted decision, what evidence was used, which constraints applied, and what occurred afterward. The CrossChecked application in this repository is an adjacent prototype. It does not mint consent, authority, or governance outcomes, and this site does not claim it enforces the constitutional kernel.
Incubation, venture formation, and commercialization for companies built on the fabric. That venture role is separate from the protocol credential also called an AVC — the Autonomous Volition Credential documented at /avc.
Training and assessment for people building and governing AI systems. The institute’s value depends on staying independent of the products in the same commercial network. This page does not offer a certificate, a coverage product, or an attestation you can buy.
CyberMedica, LegalDyne, LiveSafe, Decision.Forum, and CrossChecked are not six equally urgent companies to launch. They are reference implementations and candidates for future independent businesses on the same infrastructure.
A clinical-research quality reference implementation. Adjacent to the trust fabric.
A legal-technology reference implementation. Adjacent to the trust fabric.
A safety-card reference implementation. Adjacent to the trust fabric, with its own proprietary boundary.
A deliberative decision-making reference. The Apache-licensed forum primitive in the repository is not a commercial product release.
Bring one constrained, cross-organizational workflow — a procurement decision or an executive approval, for example — where two parties need to verify legitimate authority without sharing an internal system. Developers can start from the SDK in the public repository.