Verifiable Convergence Protocol (VCP) v0.1

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 21 January 2027.¶

Copyright Notice

Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

As AI transitions to autonomous agents, lack of verifiable trust is a bottleneck. VCP provides minimal protocol for claims, actions, and traces.¶

2. Conformance

A system is VCP-Compatible iff it implements 4 Core Endpoints, confidence via MWU plus Gossip as per GQRVP, Actions reference Claim as basis, and Trace is immutable and content-addressed.¶

3. Core Types

Claim is atomic unit: claim_id, content, provenance, confidence 0.0-1.0, trace.¶

Attestation is signature over Claim by DID.¶

Action is state change grounded in Claims. Gateway MUST reject if basis empty or confidence less than 0.731.¶

Trace is immutable record with final_confidence and merkle_root.¶

Formal-to-epistemic threshold theta_critical equals 0.731. Empirical sybil-10x-g1.5 trace shows 30 scores above threshold.¶

4. Core Endpoints

POST /v1/claim, GET /v1/claim/{id}, POST /v1/action/verify, GET /v1/trace/{id} over HTTPS, application/json.¶

5. GQRVP Security Parameters

MUST use eta equals 0.2, gamma equals 1.5, eps equals 0.1. Provides 67 percent Byzantine resilience.¶

6. IANA Considerations

No actions.¶

7. Security Considerations

VCP guarantees cost of manipulation exceeds cost of validation given honest supermajority.¶

Author's Address