Use cases
What people use CHP for.
Concrete jobs the protocol does. Software is live today; the same primitives — declared authority, governed invocation, evidence — carry into every domain, built with design partners.
See what an AI agent did
LiveThe boundary that is real today. One command hooks your agent CLI and records every tool call as replayable, tamper-evident evidence — the answer to a security review.
See how it works →Prove why an automated decision happened
LiveDenial is a first-class outcome in CHP, so an automated approve/deny carries an explicit reason, the deciding subject, and an evidence id you can replay.
See how it works →Put a human approval in the record
LiveA sign-off, consent, or authorization becomes the same kind of governed, provable event as an agent action — not a side note in a log.
See how it works →Replay a process across hosts
LiveOne correlation id flows across machines, services, and partners, so a process spanning many hosts replays as a single ordered trace.
See how it works →Gate a high-risk action
LiveA capability can require entitlement, approval, or a safety check; when one fails, the action is denied at the boundary and the denial is recorded.
See how it works →Expose a product capability safely
LivePublish what your product can do as a governed, discoverable capability with a stable contract and per-invocation evidence.
See how it works →Have a job that needs a provable record?
If your work needs to show what people, agents, and systems did, the protocol fits. Tell us the workflow and we'll map it with you.