CCS defines a 7-dimension runtime verification framework for AI agent tool calls: Structure, Schema, Latency, Cost, Identity, Integrity, Security. This is an IETF Internet-Draft (individual submission, not an RFC and not endorsed by the IETF), draft-correctover-ccs-10 (Submission #169924). Revision 10 restructures key management around two orthogonal trust levels: VERIFIED, the self-contained integrity and key/signature consistency verifiable fully offline from the receipt alone, and ACCEPTED, which adds out-of-band issuer pinning and is the only level that authenticates the signer. The embedded public_key, public_key_fingerprint, and signing_algorithm fields are required to be covered by the signature to prevent key substitution and algorithm downgrade. The framework provides Ed25519-signed, tamper-evident receipts for runtime allow/deny/escalate decisions, enabling independent offline verification and accountability. Files: draft-correctover-ccs-10.xml (authoritative RFCXML v3 source) and draft-correctover-ccs-10.txt (rendered text) are this revision; draft-correctover-ccs-00.md is retained from the prior version as the lineage starting artifact. Earlier intermediate revisions 01-09 are available in the IETF archive.
No takes yet. Share an insight, caveat, or question.
Guigui Wang (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: