Verifiable Enterprise Search builds attested answers whose authority, policy, pipeline, corpus, model, evidence, citation, and replayability can all be independently verified — without contacting H33.
Apache 2.0 open-source verifier · Reproducible builds · Federal-profile available (CNSA 2.0 aligned)
When your verifier produces a verdict on a VES bundle, no H33 endpoint participates. The verifier binary is open source. The conformance vectors are published. The cryptographic primitives are standard. The bundle's portability is the product.
What happens if H33 disappears? Verification still succeeds. → Read the answer.
A buyer, regulator, auditor, or carrier never asks for "EC-3 verdict" or "EC-8 verdict." They ask the six questions on the card. The card answers them. The substrate underneath is the engine; the card is the product.
Loading trust card…
Download the bundle · Print this page (court-admissible) · Verify it yourself · What happens if H33 disappears?
Same bundle. Two independent verification paths. Same result.
Decision Insurance verticals require provenance for every claim evaluation. The bundle is the underwriting record.
Acquirers need to verify that the target's documented decisions actually executed per the target's documented pipeline.
Submit attested evidence to regulators without giving them a vendor-lock-in dependency. The bundle survives outside the originating system.
Audit-grade evidence chains for AI-driven decisions. Auditor questionnaire answers with cryptographic evidence references.
Customer-held cryptographic keys. FIPS 140-3 Level 3+ HSM custody. No vendor-side key escrow.
When the EU AI Act's traceability requirements become operational, ship today against tomorrow's regulatory bar.
Existing AI search and retrieval-augmented generation (RAG) stacks help your team find documents. They produce citations as references — pointers to source documents.
H33 builds the layer above. Citations as cryptographic bindings: proofs that the cited bytes in the source document support the claimed answer-span bytes, verifiable offline by anyone with the bundle and the verifier binary.
| OpenAI retrieval | H33 Verifiable Enterprise Search | |
|---|---|---|
| Citation type | Reference to a document | Byte-range cryptographic binding |
| Replay six years later | "See document X" | Same query × same corpus state × same model = byte-identical answer |
| Independent verification | Trust the vendor | Run h33-verify offline |
| Vendor dependency at verification time | Yes | None |
| Regulator-admissible evidence | Narrative | Court-admissible bundle |
H33 wraps your existing RAG stack — Tantivy, Qdrant, FST, OpenAI, Anthropic, your own embeddings. The retrieval mechanics stay unchanged. The trust posture is fundamentally different.
Apache 2.0. Reproducible build. Anyone audits it, anyone compiles it, anyone runs it.
Input → expected canonical output → SHA3 digest. Independent implementations are conformant if and only if they produce byte-equal outputs.
NIST FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA), RFC 8785 (JSON canonicalization). No proprietary cryptographic primitives.
FIPS 140-3 Level 3+ HSM custody. Customer-side ceremony. H33 holds no Federal-customer signing keys.
Click the trust card section above. The trust card renders client-side against the claim_84711 demo bundle. No signup.
Open the demoApache 2.0. Reproducible build. Single Rust binary. Verify any VES bundle offline.
Get the binaryThe claim_84711 demo bundle as JSON. Use it with the verifier or any independent implementation.
claim_84711.jsonThe deepest procurement question. Five-minute read. Honest structural answer.
Read the answer