Documentation

CooL seals every change to an AI system — a prompt edit, a model swap, a permission grant — as a signed, tamper-evident record. This documentation covers producing those records and, more importantly, checking them.

Start with verification, not with capture

Most integration guides begin by telling you how to send them data. This one begins with how to check what comes back, because that is the only part that determines whether any of the rest is worth doing.

npm install -g cool-nwc
cool verify ./change-receipt.json --offline

If you do not have a receipt yet, produce one in your browser at /verify and download it. The verifier that runs on that page and the one you just installed are the same implementation.

What the verifier reports

Seven domains, each checked and reported separately.

| Domain | Proves | |---|---| | canonical | The record serialises deterministically | | binding | The digest matches the record | | signature | ML-DSA-65 and Ed25519 both verify | | inclusion | The record is in the log where it claims | | consistency | The log only ever grew | | attestation | Where the record was produced | | witnesses | An independent party saw the same log |

Where to go next

• Quickstart — from install to a sealed record in five minutes
• Verify it yourself — check a record without trusting us
• Receipt format — what a record contains, field by field
• Threat model — who you still have to trust