<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.correctover-ccs" target="https://datatracker.ietf.org/doc/html/draft-correctover-ccs-02">
   <front>
      <title>Correctover Conformance Shape (CCS): A Receipt and Binding Specification for Agent Runtime Verification</title>
      <author initials="" surname="Correctover" fullname="Correctover">
         <organization>Correctover</organization>
      </author>
      <date month="August" day="9" year="2026" />
      <abstract>
	 <t>   The Correctover Conformance Shape (CCS) defines a tamper-evident
   receipt schema and a set of cryptographic bindings that together
   constitute a verifiable conformance record for an agent runtime&#x27;s
   decision to permit, deny, or escalate a tool invocation.  CCS is
   designed as a one-receipt-per-invocation object that can be consumed
   by an executor-side Action Evidence Boundary (AEB), providing the
   request_hash, response_hash, runtime_context_hash, action binding,
   params_hash binding, issuer, audience, nonce/sequence, freshness, and
   config_hash fields that the AEB processing model requires as native
   inputs.
   This document specifies the CCS Receipt Schema, the Canonical
   Configuration model, the nine binding mechanisms, key management,
   transport requirements, verifier source classification, conformance
   levels, and negative test cases.  It is intended to enable a reader
   such as the author of the Action Evidence Boundary specification to
   evaluate whether and how a CCS receipt can be mapped into an
   Authorization Evidence Chain (AEC) component.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-correctover-ccs-02" />
   
</reference>
