The people and standards behind the new internet stack.

Pamela Norton / Dagny

Founder-architect of M5, TitleChain, M5Bank, and the human-rooted sovereign banking stack. Her work connects decades of infrastructure, commerce, payments, digital identity, blockchain, private AI, real-world asset title, and no-capture protocol design into one constitutional architecture. US Patents #11,720,888 and #12,518,273 — The Elemental Sovereignty Method.

Read the full founder story →

Dr. Justin "Goju" Gottschlich / Merly.ai

Machine-programming and code-integrity authority for the M5 private repository review path. His role brings outside technical review, machine-programming discipline, and controlled software-integrity validation into the stack via Merly Mentor™ before protocol-level standards are opened through the proper foundations.

merly.ai →

Jim Harding / Otonoma

Founder and CEO of Otonoma, bringing Paranet autonomous workflow infrastructure into the M5 stack. In the M5 architecture, Otonoma supports sovereign autonomous coordination across devices, agents, industrial systems, grid networks, and machine-to-machine economic activity.

Scott Thibault / Otonoma

Technical architect behind Otonoma's actor-based autonomous workflow engine. His work maps into M5's machine-to-machine coordination layer, where agents, devices, workflows, and real-world systems need to coordinate without becoming dependent on a single platform controller.

Rosario Cammarota, Ph.D. / CAMMAROTA Labs

Founder of CAMMAROTA Labs and former Principal Engineer at Intel Labs. M5 maps CAMMAROTA Labs to the Fully Homomorphic Encryption standards layer, Track 3 hardware certification, secure compute, and quantum-resistant hardware sovereignty. The CAMMAROTA Standard governs all FHE computation in the M5 stack.

Sir Tim Berners-Lee / Solid Protocol

Inventor of the World Wide Web and creator of the Solid Protocol. M5POD sovereign data containers extend the same human-first principle: the standard should serve everyone, and the data should remain under the control of the person or lawful entity that owns it.

Sir Nigel Shadbolt / Open Data Institute

Co-founder and Executive Chair of the Open Data Institute. M5 aligns with the ODI principle that data should benefit people and society, not simply platforms — carried into M5POD consent, data access, credentialing, and human-controlled vault design.

Tauri Programme / The Commons Conservancy

Secure, lightweight cross-platform application shell for M5Bank, M5POD, and sovereign banking interfaces across desktop and mobile surfaces. Tauri gives the M5 app layer a safer path than heavy web wrappers while preserving open-source governance and portability.

Signal Foundation / Signal Protocol

Encryption standard mapped to M5 sovereign communications. Inside M5, member-to-agent and member-to-member messaging is bound to TCID identity, M5Canon authorization, and privacy-preserving communication via libsignal — Double Ratchet, X3DH, forward secrecy, no message storage.

MEST / Dr. Mark Tehranipoor

Hardware-security standards corridor for ICSN and M5 secure compute. This layer supports hardware provenance, anti-tamper thinking, secure silicon, supply-chain integrity, and trusted hardware certification for sovereign infrastructure.

Dean Nelson / iMasons

Founder and CEO of iMasons, the Climate Accord infrastructure standard. M5 maps iMasons to hardware certification authority and green cloud — sovereign compute infrastructure that meets the M5Cloud credentialed node architecture standard.

Platforms that reached billions.

Leaders who architected and scaled the consumer internet — ride-sharing, payments, marketplace, social, and commerce platforms that operate at global scale. They understand identity, transaction integrity, fraud systems, and what happens when a platform loses sovereign control of its own rails.

• Payment platform architecture and settlement systems (Uber, PayPal, Stripe-scale)
• Consumer identity and trust frameworks at hundreds of millions of users
• Fraud detection and behavioral analytics at platform scale
• Marketplace economics and multi-sided network design
• Mobile-first and API-first consumer financial products

Systems that move billions daily.

Executives and architects from the institutions that operate the clearing, settlement, custody, and lending infrastructure of the global financial system. They know what it means when a system goes down — and what it will mean when autonomous agents gain access to rails that were never designed to authenticate them.

• Core banking systems and real-time settlement networks
• Institutional custody and clearinghouse operations
• Central bank and interbank messaging infrastructure
• Regulatory capital and compliance systems (Basel III/IV, DFAST)
• Treasury management and liquidity risk at institutional scale
• Cross-border payments and correspondent banking networks

The highest-stakes data systems on earth.

Leaders from the national health networks, hospital systems, payer platforms, and clinical informatics infrastructure that carry the most sensitive and consequential data a human being can generate. These systems face the sharpest edge of AI agent risk — and have the most to lose from unauthorized autonomous access.

• Electronic health record systems serving tens of millions of patients
• Clinical decision support and diagnostic AI infrastructure
• Health information exchange and interoperability (HL7 FHIR, TEFCA)
• Payer and claims processing at national scale
• Genomic data stewardship and precision medicine platforms
• Medical device connectivity and IoT security in clinical environments

The infrastructure of sovereign authority.

Former and current leaders from federal agencies, defense contractors, and national security infrastructure who have operated and secured the systems that underpin government function. They understand FedRAMP, ITAR, FISMA, and what sovereign-grade identity actually requires at the classification level.

• Federal agency IT modernization and zero-trust architecture
• Defense and intelligence-grade secure compute and communications
• National identity systems and credentialing infrastructure
• Critical infrastructure protection (energy, water, transport)
• FedRAMP authorization and FISMA compliance at scale
• Cross-agency interoperability and data-sharing frameworks

The systems at the center of the autonomy risk.

Engineers and executives from the grid operators, utility networks, and energy management platforms now facing the front line of autonomous agent exposure. These systems were built for reliability, not for sovereign identity verification — and that gap is exactly what ICSN Internet 3.0 closes.

• Grid management systems and SCADA infrastructure
• Distributed energy resource coordination at national scale
• Smart grid communications and device identity
• Energy trading and settlement infrastructure
• Critical infrastructure cybersecurity and resilience
• Green compute certification and sustainable infrastructure standards

The silicon layer of sovereignty.

Hardware architects, cryptographers, and secure compute leaders from the chip level through the data center. They are building the physical substrate that FHE, post-quantum cryptography, and sovereign compute require — and setting the certification standards the ICSN hardware working group will codify.

• Fully Homomorphic Encryption hardware design and certification (CAMMAROTA standard)
• Post-quantum cryptography migration and NIST PQC alignment
• Trusted Execution Environment (TEE) and secure enclave architecture
• Hardware supply-chain integrity and anti-tamper standards
• Silicon provenance and device identity at the chip level
• Green cloud certification and iMasons Climate Accord alignment

Reaching millions of developers worldwide.

Professors, educators, and platform leaders who have built the largest developer education programs in the world. Their role in ICSN is to design and deploy the SOPHIA certification tracks that will credential the global developer workforce — the people who maintain, extend, and secure every system listed on this page.

• Developer certification programs reaching millions of engineers globally
• University curriculum and academic standards bodies
• Open-source developer community governance and tooling
• Corporate technical training and workforce transition programs
• AI and machine learning curriculum for responsible deployment
• Legacy systems education — COBOL, FORTRAN, mainframe, RPG, NATURAL, JCL

The architects of the open internet.

Leaders from the standards bodies, foundations, and open-source governance organizations that define how the internet works — from hardware through identity through payment. They bring the institutional credibility, process discipline, and cross-industry trust that sovereign internet standards require.

• W3C, IETF, and ISO protocol standards governance
• Linux Foundation, AAIF, and open-source foundation leadership
• Open hardware and silicon certification (OpenHW Group)
• Data stewardship and open data governance (ODI framework)
• Sovereign data containers and M5POD/Solid protocol alignment
• ICANN, DNS, and global naming infrastructure governance

What this working group exists to prevent.

The systems above — financial rails, health networks, energy grids, federal infrastructure, consumer platforms — were built by humans for humans. None were designed to verify whether an instruction came from a credentialed human actor or an autonomous agent operating outside any accountability chain. That is the gap. ICSN Internet 3.0 closes it by making sovereign identity and credential verification the prerequisite for every protocol interaction — not a bolt-on, not a firewall rule, but a constitutional requirement baked into the protocol layer.

• Agentic AI systems operating on financial and payment rails without human approval gates
• Autonomous access to healthcare and clinical decision systems
• Grid and critical infrastructure exposure to unverified agent instructions
• Centralized platform capture and single-point-of-failure dependencies
• Legacy system vulnerability to automated exploitation at scale
• Developer workforce gaps in sovereign-aware and credential-verified systems design

TitleChain Foundation

The sovereign registry, certificate-authority, and title-verification root for M5 identities, credentials, contracts, assets, and provenance records. Wyoming 1,000-Year Sovereign Purpose Trust. IP holder for Patents #11,720,888 and #12,518,273.

titlechain.com →

ICSN Global / Internet 3.0

The DUNA standards body governing the World Sovereign Web, m5s:// protocol, ICSN IS-001 v3.0, and the M5IP improvement proposal framework. 170+ nation chains. Net3.eth resolves all in under 200ms.

Internet 3.0 Architecture →

M5Canon

The constitutional rules engine that governs authority, consent, provenance, due process, agent activation, and no-capture behavior across the M5 stack. Mythos 6-gate pre-execution enforcement. CYRUS© Binding Protocol for constitutional rights.

M5Canon Protocol →

M5x402

The registered M5 implementation of x402-style payment semantics, designed for audited, credentialed, and registered payment flows. Patent #11,720,888. Payment is the protocol — not an add-on. Every M5Pay atomic operation incorporates GREEN treasury intelligence and PAINE compliance.

M5-OpenAPI v2.7.0

The sovereign API standard. 109 total endpoints. All paths use /m5/ prefix. All require X-TCID-Header. 14 mandatory X-M5-* WSW response headers on every endpoint via NodeClassificationMiddleware. Auth: TCIDAuth. Five node classes: M5N-EDGE through M5N-GOVS.

API Reference →

SOPHIA Credentials

407 credentials · 29 categories. The sovereign professional credential framework built on ICSN IS-001. Credential class gates endpoint access. SOPHIA L3 minimum for Certified Integrator license. L4 for institutional M5-API conformance.

Browse All Credentials →

Solid / M5POD

The sovereign data-container model for human-controlled vaults, credentials, memory, documents, agents, and consent-managed data access. ESS/Inrupt/Solid-compatible. FHE-encrypted. Member-controlled. Cloud-Sovereign tier: M5Cloud OpenStack.

W3C DID / Verifiable Credentials

Reusable identity and attestation standards for TCID, M5HUM, member credentials, legal-entity authority, and proof-based access. did:m5 — canonical DID method per M5IP-0004.

FHE Dual Stack

Optalysys LightLocker (photonic, on-chain) + Belfort Labs HEonGPU (CUDA, CAMMAROTA standard). FHE runs first — computation on encrypted data, amounts never in plaintext. ZK circuits prove validity on-chain after. Sequential and complementary.

Cosmos SDK / IBC Protocol

The sovereign-chain architecture for TitleChain registry, jurisdiction-chain, and interoperable state-machine operations. Base Mainnet (Chain ID 8453) via Gnosis Safe. IBC for cross-chain interoperability.

Bitcoin Notary Anchoring / MILNER

Capture-resistant timestamp and provenance proof layer. Every settlement hashed to Bitcoin. MILNER anchors critical records, hashes, registry events, and legal-state transitions. Immutable proof that cannot be rewritten.

OpenInfra / OpenStack

Sovereign cloud substrate that reduces hyperscaler lock-in and supports portable infrastructure for M5Cloud and credentialed node environments. iMasons Climate Accord certification required for M5Cloud hardware.

Linux Foundation AAIF

Open AI and agentic infrastructure corridor for contributed standards such as M5-OpenAPI, agent accounting, and interoperable AI workflows. M5 is an AAIF contributor — M5-OpenAPI submitted through proper foundation governance.

OpenHW Group

Open hardware governance corridor relevant to secure compute, device provenance, and hardware certification pathways under the CAMMAROTA standard.

Eclipse Foundation

Open systems and standards governance corridor for future tooling, interoperability, and developer ecosystem contributions to the Internet 3.0 stack.

M5Valoris VSP

Real-time on-chain valuation replacing quarterly earnings. Merly Mentor™ engine — 1M+ lines of code per minute on single CPU, deterministic, no GPU. Credential-gated access for BOU/BOB/BOI. Verification: m5scan.io (public) · m5bank.cloud (credentialed).

M5 sovereign roots

M5Canon, TitleChain, TCID, M5POD, M5Ledger, M5x402, the sovereign registry, the native agent stack, and the human-rooted authority path remain M5-controlled sovereign infrastructure. The constitutional root does not move.

Partner and contributor layers

Technical contributors, standards bodies, open-source projects, custodians, identity systems, cloud providers, payment rails, and app frameworks may support the stack without owning or controlling the protocol core.

Public language rule

Public materials describe the relationship accurately: aligned with, integrated with, mapped to, licensed from, or reviewed by — not as ownership or formal partnership unless that relationship is documented.