Carnac™ · two packages
Every AI answer should come with proof.
There are two places proof can live: inside the request where it begins, and at the door where it arrives. We built both.
Most teams use both. Start with where your AI lives.
I ship AI-powered products
apps, copilots, agents, voice, devices
I operate AI infrastructure
model APIs, inference endpoints, clouds, data centers
CarnacPrompt™ · Proof Inside
Your product has a request surface: a chat box, a voice command, a "book it for me" button. CarnacPrompt™ puts a signed, third-party receipt on every answer, believable precisely because it is not yours.
Carnac.init({ key: "int_9f2a...", origin: "booking-app" }) // one line, onceCarnac Gateway™ · Proof at the Door
Everything is heading to your building: questions from desktops, cars, hospitals, and other machines. Today they all look identical, and you cannot tell them apart, price them apart, or prove any of it. The Gateway countersigns everything that walks in.
app.use(carnacGateway({ facility: "wy-dc-01" })) // fail-open · sub-ms countersignWhere the packages sit
What one receipt pair looks like
One answer, signed twice: once at birth, once on arrival. This is a labeled example so you can read the shape. The values are illustrative, not real signatures.
Origin label
- request
- "book the 9am flight to Denver"
- origin
- booking-app
- request_hash
- 0x7f3ac9d1e208
- alg
- ML-DSA-65 · FIPS 204
- origin_sig
- a91f4b...e772 (3309 bytes)
Arrival countersignature
- facility
- wy-dc-01
- covers request_hash
- 0x7f3ac9d1e208
- grade
- critical · cannot wait
- alg
- ML-DSA-65 · FIPS 204
- arrival_sig
- 6b02d8...1f4c (3309 bytes)
How they link. The pair is parallel: two independent signatures over the same answer, not one wrapped inside the other. The arrival countersignature names the same request_hash the origin label signed, so a verifier can confirm both marks describe one answer.
Why a verifier can trust it. Each signature is checked offline against a published ML-DSA-65 public key. No trust in Hive is required. If either mark were altered, the check fails.
What it settles. When the origin label and the arrival countersignature agree, the dispute about "what was sent vs. what was served" is over. When they disagree, the mismatch is visible and provable, never a silent verdict.