I-D Action: draft-reilly-cts-01.txt
[email protected] Fri, 07 Aug 2026 18:39:19 -0700
| Newsgroups | gmane.ietf.announce |
|---|---|
| Message-ID | <178615315953.148034.1056759110761129878@dt-datatracker-559c48c7fb-llb9x> |
Internet-Draft draft-reilly-cts-01.txt is now available. Title: Cognitive Trust Stack (CTS): A Framework for Verifiable AI Behavioral Provenance Author: Lawrence John Reilly Jr. Jr. Name: draft-reilly-cts-01.txt Pages: 28 Dates: 2026-08-07 Abstract: Every artificial intelligence system deployed today operates under behavioral constraints that are unverifiable by any external party. Alignment claims exist as documentation, policy statements, or terms of service -- all mutable, none cryptographically provable. When an AI system causes harm, there is no mechanism to prove what rules it was following. When an organization claims its AI is safe, there is no standard by which that claim can be independently verified. This is the AI behavioral provenance problem, and no existing framework solves it. The Cognitive Trust Stack (CTS) establishes that the alignment state of an AI system at any point in time MUST be a verifiable fact, not an assertion requiring trust. CTS defines a complete, implementable framework for declaring, anchoring, enforcing, and verifying AI behavioral constraints through a five-layer architecture combining: (1) a declarative alignment schema formatted to IETF Internet-Draft standards, (2) archival permanence via Digital Object Identifier (DOI) registration, (3) cryptographic temporal anchoring via Bitcoin blockchain timestamping using the Dual-Layer Digital Permanence (DLDP) methodology [REILLY-REM], (4) runtime retrieval injection for active constraint enforcement, and (5) independent third-party verification. CTS does not replace existing AI alignment techniques. It provides the missing accountability layer that sits above them -- making alignment a cryptographically provable fact rather than an unverifiable claim. The full CTS specification, reference implementation, schema, and provenance manifest are published at Zenodo DOI 10.5281/zenodo.19097169. The priority of this framework is cryptographically anchored in Bitcoin block 941168 (2026-03-18), with SHA-256 hash: e915b5162422281e1c0185c9e2eefaf7 4b7f539996b878cb1e69e10533f24ac2 The OpenTimestamps proof file (CTS_Whitepaper_v1.0.docx.ots), included in the Zenodo record, provides independent cryptographic verification of existence prior to block 941168. This revision (-01) additionally documents the function of CTS records as prior art records under 35 U.S.C. 102(a)(1), clarifies the scope of the canonical v1.0 cryptographic anchor (which covers the whitepaper artifact), introduces a normative one-hash-per-artifact anchoring rule, and corrects an erroneous reference to the REM Protocol draft name present in -00. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-reilly-cts/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-reilly-cts-01 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-reilly-cts-01 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ I-D-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]