Evidence profiles for regulated AI transactions.
Hive-PQ is a pilot profile for planning crypto-agile evidence: algorithm metadata, evidence references and verification requirements. It helps define what a future reviewer will need. The profile does not itself add an executed post-quantum signature, encryption or a tested long-term storage service.
When to consider Hive-PQ
Choose an evidence profile based on the workflow, applicable requirements and how long records must be retained. A RubricMesh recommendation is a declared selection, not regulatory approval or an automatic capacity increase. Confirm that the selected deployment implements the required cryptography and storage controls.
r1.0.0 PQ example carries Ed25519 plus future-algorithm metadata. Separately, retained afir.attestation / 1.0.0-typed-pq operator envelopes execute ML-DSA-65 verification locally. That is not hybrid verification of the commercial profile. ML-KEM establishes a shared secret for an encryption system; it is not a second signature. Endpoint capability evidence identifies the acceptance boundary.
Hive Standard. Hive Pro. Hive-PQ.
Three commercial scopes, with capabilities selected per endpoint. A larger profile is not automatically stronger evidence. Evaluate the signed claims, trusted issuer, required verification material and tested operational controls.
Fast, checkable agent commerce.
- Ed25519 signatures
- BLAKE3 supplied-root consistency checks
- HKTN provenance fields where supported
- Offline checks for documented receipt formats
- Dashboard / evidence room subject to deployment scope
- Spectral-ZK receipts (well-formedness; sample profiles)
- SHOD origin disclosure (sample envelopes)
- SMSH message-state hash (sample envelopes)
- x402 / USDC settlement references (quote endpoint pilot)
Enterprise evidence rooms and proof workflows.
- Customer dashboard
- Private evidence room
- Private verifier instance
- Richer policy and routing logs
- Curated proof artifacts (envelope, receipt, appendix)
- Embedded ROI worksheet
- Endpoint health and uptime view
- Enterprise onboarding
For regulated work you'll need to keep for years.
- Post-quantum-ready provenance profile
- Proposed dual-signature receipt structure
- ML-DSA / Dilithium-class signature posture
- ML-KEM / Kyber-class sealed envelope posture
- Rubric-bound evidence (RubricMesh)
- Long-retention crypto-agility metadata
- Regulator / auditor verifier mode
- Premium evidence-room posture
- Crypto-agility report
The Hive-PQ evidence profile
Hive-PQ groups evidence requirements across Spectral-ZK, SMSH, SHOD and HKTN. The following pilot profiles describe intended integration points, not automatically activated production controls.
Spectral-ZK
A Spectral-ZK proof applies to its specified statement and verification relation. Preserving it requires the proof, verifier and parameters, plus an approved retention and migration process. A profile label alone cannot preserve future verifiability.
SMSH-PQ: sealed evidence mode
The SMSH-PQ sealed-envelope profile proposes protected evidence access and ML-KEM integration. ML-KEM encapsulates a shared secret used by a separate encryption scheme. The smshPQ signature primitive does not encrypt receipt content. End-to-end sealing and access controls require separate acceptance.
SHOD-PQ: declaration and signature mode
The SHOD-PQ example combines an Ed25519 signature posture with ML-DSA metadata. Metadata is not a second signature. Hybrid acceptance requires executing both mandatory signature checks under trusted keys on the same bound statement; that acceptance is not established for this profile.
HKTN: clearance profiles
The HKTN pilot describes three clearance labels: standard, enterprise, and pq_regulated. They record a declared profile, not verified retention, regulatory clearance or continuity of historical evidence.
Rosetta: PQ recommendation
This illustrative Rosetta output recommends a profile from supplied workflow requirements. Confirm the selected endpoint and the authorized retention schedule; a recommendation is not a legal determination.
Prospector: PQ opportunity detection
The Prospector pilot describes candidate workflows for evidence integration. Validate the actual requirements and procurement scope before offering a retention or assurance package.
A profile recommendation, subject to acceptance.
RubricMesh can describe a recommended tier from supplied policy inputs. Verify the actual endpoint output and its signature before treating the recommendation as a signed declaration. A rubric fingerprint does not establish that controls ran or that a regulator approved the workflow.
Hive-PQ is a way to specify required evidence across these components. Test each binding, signature, encryption boundary and storage control separately. No single profile establishes complete capture or long-term recovery.
Include Hive-PQ in a scoped offering.
Scope Hive-PQ within your offering using an agreed integration, verification and storage plan. Pricing depends on the selected services and retention obligations. Keep those obligations visible in the customer agreement.
Compare expected review effort and evidence value against signing, verification, storage, recovery and integration costs. Revenue, margin, deal speed and compliance outcomes depend on the workflow and are not guaranteed.
Regulated work may need stronger evidence, but that does not automatically require this product or satisfy a legal obligation.
Implemented checks. Pilot profiles. Open acceptance.
Review boundary: 2026-09-05. Implemented code, a responding endpoint and a deployment that has passed acceptance are different states. The developer capability inventory records exact schemas and algorithms. NIST FIPS 204 defines ML-DSA, not Hive deployment certification.
Receipt verification
The browser verifier checks documented receipt formats and separates signature validity from issuer trust. Supplied-root consistency is not a trusted checkpoint. Hive-operated countersigning is not organizationally independent, and settlement references are not evidence of chain inclusion or finality.
Hive-PQ evidence profile
The commercial r1.0.0 example uses receipt_profile=pq and crypto-agility metadata. Selecting a profile does not execute ML-DSA or establish a hybrid signature.
The documented selector is profile=pq on receipts.thehiveryiq.com/v1/receipt/emit; the advertised $0.0012 rate requires current endpoint and commercial confirmation. No seven-year storage promise is established. Receipt, log, inspection, account, backup and processor-copy schedules, start events, legal holds, deletion and verification methods require deployment approval and testing.
Cryptography and operations
Production-bound hybrid acceptance, end-to-end ML-KEM sealing, external cryptography review, historical verification after key rotation, backup restoration and retention enforcement remain separate gates. Real ML-DSA implementation and retained local checks do not close them.
Tell us about your regulated workflow.
Tell us the workflow, the regulator, and how long you need to keep records. We'll figure out the right proof tier with you, share an ROI worksheet sized to your assurance package, and walk through everything with you in a working session.