Two Independent CCS Implementations Achieve 14/14 Interoperability
The Correctover Conformance Shape (CCS) specification — IETF Internet-Draft draft-correctover-ccs-06 , Experimental status — defines a runtime verification framework for AI agent tool calls across seven dimensions: Structure, Schema, Latency, Cost, Identity, Integrity, and Security. As of August 2026, two independent implementations from separate codebases now pass all 14 conformance checks. This…
Two independent implementations of the Correctover Conformance Shape (CCS) specification have achieved full interoperability, passing all 14 conformance checks. This development was documented on August 21, 2026, in an IETF Internet-Draft draft-correctover-ccs-06. The two implementations, created from separate codebases, serve as the reference implementation accompanying the draft and an independent implementation of the EMILIA Protocol.
The conformance suite encompasses seven dimensions: Structure, Schema, Latency, Cost, Identity, Integrity, and Security. The developments include several normative changes in the -06 revision, such as promoting AEB (Admission Enforcement Boundary) and CAID (Correctover Action ID) to normative references, specifying detached Ed25519 signature construction normatively, correcting JCS (JSON Canonicalization Scheme) serialization, clarifying receipt lifecycle as two-phase, and specifying Ed25519-only signature for version 1.3.
Despite the IETF's focus on "rough consensus and running code," the interoperability evidence demonstrates that the specification is sufficient for building an interoperable implementation without reference to the author's code. However, this does not automatically validate production readiness, security at scale, or real-world deployment.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
