Every AI answer should come with proof. Proof can live in only two places. One is inside the window, where a request is built. The other is at the door, where the request arrives to be answered. Tell us what you do and what you are looking for. This tool reads the canon and returns the primitives that fit your words, and it shows you what you would need to deploy each one. A primitive is one small tool that does one proof job. Carnac™ makes the call and routes each request. The primitives prove what happened.
CarnacPrompt™ sits where requests are built. It labels each request as it forms.
Born labeled.Carnac Gateway™ sits at the door you run, where requests arrive. It countersigns each one. To countersign is to sign again to confirm.
Arrived countersigned.Both ends work together. Each proof is a receipt, which is a signed record you can check later. The start receipt and the arrival receipt link into one pair for each answer.
Born labeled · Arrived countersigned.Reading the canon data.
Every result above ends in the same three doors. Pick the one you need.
Nothing in the canon scored high enough on what you typed, so we are not going to hand you a filler result. Try naming your industry, the duty you have to meet, or a company that looks like yours. If you would rather just tell us, go to contact and we will read it ourselves.
Carnac looks at the stakes and sends each request to the proof it needs. The Hive Canon primitives under it make the proof. Anyone can check that proof on their own. Proof Inside labels a request where it starts. Proof at the Door countersigns it where it arrives. Paired Provenance links both records into one pair for each answer. So arguments about what was sent versus what was served just end.
Honesty note. When we name a field or an example company, we only show where a setup could fit. It is not a claim of any customer, partner, or deal. Carnac runs next to a request, not in its way, so it does not slow the request down. Most work gets a small signed note. Work with higher stakes gets more proof. We never block traffic that has no label. A mismatch is a flag, not a route. We never read what you type at the window or the door. And we never fake a receipt.
The first link is the entry this page is about. The rest are the entries the registry names as related, in the order it names them. Each link opens that entry in the canon implementation explorer, where its schema, mint route, open verify route, auth requirement and implementation state are stated. The state shown here is read from the same registry file the explorer renders from, so the two cannot drift apart. Nothing here implies a customer, a deployment or an endorsement.
Search the explorer for Carnac Director