ccs-runtime
Runtime verification for AI agents — 7 dimensions, sub-25μs P50, Ed25519 audit receipts
CCS (Correctover Conformance Shape) intercepts every tool call before execution and validates it across 7 dimensions: structure, schema, latency, cost, identity, integrity, and security. If something's wrong, it blocks — not after the damage, but before.
Why
The AutoGen community proved it: prompt-based guardrails don't work. 56 days of testing showed every safety rule being bypassed by the agent itself, resulting in $106K in losses.
The fix? Enforcement must be structurally separate from the agent's process. That's exactly what CCS does.
Install
npm install ccs-runtime
Quick Start
import { CCSVerifier } from 'ccs-runtime';
const ccs = new CCSVerifier({
block_on_failure: true,
latency_budget_us: 5000,
cost_budget_usd: 0.10,
});
const result = await ccs.verify({
tool_name: 'execute_sql',
tool_input: { query: "SELECT * FROM users; DROP TABLE users" },
});
As Middleware
Drop it into any agent framework as middleware:
import { CCSVerifier } from 'ccs-runtime';
const ccs = new CCSVerifier({ block_on_failure: true });
const safeResult = await ccs.middleware(
{ tool_name: 'http_request', tool_input: { url: 'http://169.254.169.254/latest/meta-data/' } },
() => executeHttpRequest(url)
);
7 Dimensions
| 1 | Structure | Tool call format validity |
| 2 | Schema | Input/output type conformance |
| 3 | Latency | Execution time budget enforcement |
| 4 | Cost | Token/USD budget per request |
| 5 | Identity | Caller identity verification |
| 6 | Integrity | Ed25519 payload signature |
| 7 | Security | Injection, RCE, SSRF, credential exfiltration |
Security Rules (Built-in)
| SEC-001 | Shell injection (;, ` | `, backticks) |
| SEC-002 | SSRF (internal IPs, cloud metadata) | BLOCK |
| SEC-003 | Cloud credential exfiltration (AWS/GCP/Azure keys) | BLOCK |
| SEC-004 | Path traversal (../, %2e%2e) | BLOCK |
| SEC-005 | SQL injection (SELECT/DROP/UNION patterns) | CRITICAL |
| SEC-006 | Command execution (eval/exec/system/spawn) | BLOCK |
Add your own:
ccs.addSecurityRule({
id: 'CUSTOM-001',
name: 'No crypto mining',
description: 'Block cryptocurrency mining patterns',
severity: 'block' as any,
dimension: 'security' as any,
pattern: /stratum\+tcp|xmrig|coinhive/i,
});
Schema Registration
ccs.registerSchema({
name: 'send_email',
input_schema: {
type: 'object',
properties: {
to: { type: 'string', required: true },
subject: { type: 'string', maxLength: 200 },
body: { type: 'string', maxLength: 10000 },
},
required: ['to'],
},
});
Licensing
| Free | 1,000 | $0 | 7-dimension verification, built-in security rules |
| Pro | 50,000 | $29/mo | + Custom security rules, priority support |
| Enterprise | Unlimited | Custom | + Ed25519 audit receipts, SLA, dedicated support |
Get your license key: correctover.com/license
import { CCSVerifier, LicenseManager } from 'ccs-runtime';
const lm = new LicenseManager();
const key = lm.generateKey('pro');
const ccs = new CCSVerifier({ license_key: key });
Standards
CCS is an open verification standard progressing through IETF (draft-correctover-ccs-05). The runtime SDK is the reference implementation.
Performance
| In-process | ~7.5μs | ~21μs |
| Out-of-process (API) | ~133μs | ~237μs |
Benchmarked on M2 MacBook Pro, Node.js 22, 7-dimension full verification.
MCP Live Demo
Try it: mcp.correctover.com/mcp
License
Proprietary — see LICENSE file. The CCS standard specification is open.