Execution records and inspectable artifacts support the product claims collected here. Published results identify their measured configuration; release-specific proof packs are available during evaluation.
| Product | Availability | Access |
|---|---|---|
| HX-SDP | Private Appliance · Scoped pilot | Request HX-SDP access |
| HX-Provenance | Google Cloud · AWS · Private Appliance · Scoped pilot | Deployment options |
| HX-PQC | Private Appliance · Scoped pilot | Contact HX-PQC sales |
| HX-AIFactoryTwin | Private Appliance · Scoped pilot | Discuss a thermal analysis |
| HX-MDAO-TP | Scoped pilot | Request an MDAO pilot |
| HX-AEIR | Google Cloud Marketplace · Private Appliance · Scoped pilot | View on Google Cloud Marketplace |
| HX-Fusion | Local runtime release candidate · Scoped integration | Discuss HX-Fusion integration |
The register covers product benchmarks and qualification records. Each record identifies its workload, hardware, precision, baseline, methodology and limitations. Public summaries and evaluation records are identified below.
Serving-path consolidation and exact-recall performance. Public engineering documentation reports measured configurations and their retrieval, latency and resource scope; release-specific benchmark records are available during evaluation.
Read performance evidenceRead operational boundariesThe co-branded Google Cloud solution brief reports 214.8 signed receipts per second across 1,000 requests with zero errors on a documented 2-vCPU deployment.
Workload: receipt issuance. Precision: not applicable. Baseline: none published. Scope: single-node throughput.
Read the source brief · PDFInventory coverage and migration throughput. Benchmark records are available during evaluation for the agreed discovery or migration scope.
Request the benchmark recordThe public 64³ development card and native 512³ A100 records describe the Developer Edition reference path. The later qualified QTT-native runtime has separate July 2026 qualification records bound to the documented exclusive H100 80 GB profile. They establish numerical equivalence, failure-boundary preservation and memory-safe execution within that profile.
Review the qualified runtimeReview the reference benchmark scopeRequest Twin qualification materialCoupled-campaign evaluation and acceptance rate. Evaluation records carry the discipline models, solver settings and validity boundary for the campaign under review.
Request the campaign recordThe published v1.0.0-rc1 local CPU runtime records 4,252 assertions across 89 groups, canonical parity and exact recovery. A bounded Bat Cave public-data exercise retained an UNKNOWN conclusion and returned ACQUIRE.
Review runtime qualificationRead the capability statement (PDF)Request qualification recordsEvidence-package export and offline-verification throughput. Benchmark records are available during evaluation for the applicable package and verifier release.
Request the benchmark recordEvaluate whether another team can check a critical record after handoff, even when its originating system is unavailable. Use the published execution records and synthetic verification exercise to define an evaluation with your own representative records.
The Google Cloud brief reports 214.8 receipts per second across 1,000 requests with zero errors on 2 vCPUs.
The downloadable verification demo contains a fictional record, signed receipt, bundle and matching standalone verifiers. Its seven cases cover valid artifacts, altered content and an unexpected issuer key. After dependency installation, it runs offline without an appliance or account.
Record how your current process collects, hands off and verifies evidence: staff time, elapsed review time, integration effort and retention cost. Measure your required record sizes, issuance rate, error rate and verification time. Agree thresholds before comparing the appliance with that baseline.
The Google Cloud throughput result has no published comparison baseline. The figures above are source-reported; the synthetic demo is a mechanism demonstration. Customer outcomes, cost savings and independent replication require separate evidence.
| Exercise | Expected result |
|---|---|
| Verify the original receipt and complete bundle | The matching verifier accepts the material under the independently established expected issuer key. |
| Alter the record, receipt or bundle | The relevant integrity checks reject each altered specimen. Retain the verdict and failed check. |
| Check against a different issuer key | Verification rejects the material under the unexpected key. |
| Verify without access to the originating system | Verification succeeds using the retained evidence, required original artifact or linked material, matching verifier, dependencies and expected issuer key, with network access disabled. |
For a deployment decision, repeat the exercise on representative records and compare the measured review effort and performance with the agreed baseline. Include software, infrastructure, integration and ongoing operation in the total cost. A valid signature establishes integrity within its scope; it does not establish that the record's statement is correct.
3 December 2025 · HX-Provenance substrate · Company-reported execution
HolonomiX reports end-to-end execution of a quantum circuit on a Rigetti Ankaa-3 QPU (84 qubits) through AWS Braket in us-west-1. The circuit was submitted, results returned, and the execution record signed and independently verified using ML-DSA-65.
The dated company record describes the completed execution. Its signed execution bundle and documented verification chain are available during evaluation.
Request the signed execution bundle| Record | Recorded scope | Access |
|---|---|---|
| HX-Provenance on Google Cloud | Live from 1 July 2026 in the company registry. In-tenant deployment with a free trial; current eligibility and terms appear in the listing. | Public listing |
| HX-Provenance for Vertex AI | Recorded live on 19 August 2026. A separate Google Cloud SKU with deployment and operations documentation. | Public listing |
| HX-Provenance on AWS | In-tenant deployment through AWS Marketplace. Purchase options and current trial terms appear in the listing. | Public listing |
| Google Cloud solution brief | Co-branded solution overview and the scoped receipt-throughput result reported above. | Public PDF |
| Canonical receipt schema | hx.provenance.receipt/v1.1, documented as stable and fixture-tested, with compatibility for hx.exact.receipt/v1.1 exact-recall verification. | Public schema description |
| Evidence bundle format | Portable archive containing receipts, an artifact manifest, a verification record, issuer-key material, signature metadata and timestamp metadata. | Public format description |
| HX-SDP performance documentation | Reported engineering results and configuration scope. | Public summary |
| Customer-control deployment architecture | The in-tenant and Private Appliance boundaries for records, key custody and verification. | Public product description |
| Product proof packs | Release-specific artifacts, validation results, expected checks and limitations. | Available during evaluation |
Dates identify entries in the HolonomiX company registry. Marketplace terms apply at purchase; the linked technical records identify the scope of each result.
The following field sets and structures show what the product evidence records contain. They are documentation excerpts with placeholder values; complete release-specific specimens are available during evaluation. The public synthetic demo provides an additional runnable example.
| Product | Evidence to review |
|---|---|
| HX-SDP | Exact-result and operation receipts, with workload-specific runtime and retrieval results |
| HX-Provenance | Signed receipts and portable evidence bundles |
| HX-PQC | CBOM, signed deterministic quotes, migration events, runtime evidence and posture snapshots |
| HX-AIFactoryTwin | Signed execution evidence binds runtime profile, release, inputs and recorded outcome; Developer Edition benchmark cards identify requested and effective grids. |
| HX-MDAO-TP | Validity status, convergence, acceptance results, provenance and formal certificates for specified invariants |
| HX-AEIR | Signed receipts, deterministic evidence exports and offline verification records |
| HX-Fusion | Runtime validation and a bounded public-data exercise, with canonical result and packet recovery checks |
Canonical fields from the documented hx.provenance.receipt/v1.1 schema.
{
"schema": "hx.provenance.receipt/v1.1",
"receipt_id": "…",
"artifact_id": "…",
"artifact_hash": "sha256:…",
"issuer": { "key_fingerprint": "…" },
"signature": {
"alg": "ML-DSA-65", "value": "…"
}
}The documented portable archive brings together the receipt, referenced-artifact hashes and verification material.
evidence-bundle/
receipt.json
artifact_manifest.json
verification_result.json
public_key.json
signature_metadata.json
timestamp_metadata.jsonA CycloneDX cryptographic bill of materials records discovery-scan findings. A sample CBOM is available during evaluation.
{
"bomFormat": "CycloneDX",
"specVersion": "…",
"components": [
{ "type": "cryptographic-asset",
"cryptoProperties": { … } }
]
}A checksum-addressed thermal-scenario record includes configuration, validation results and quantities of interest. The structure below describes the Ed25519 signing mode; the documented HMAC fallback has different verification requirements.
run-bundle/
run_config.json
validation_results.json
quantities_of_interest.json
benchmark_card.json
signature (Ed25519)The validity-gated result carries the model and solver record alongside convergence and acceptance outcomes. Formal certificates apply to specified invariants where included.
validity-receipt/
model_hashes
discipline_contracts
solver_settings
convergence_status
acceptance_results
validity_policy
signature
lean4_certificate (where applicable)The documented operation receipt supports exact-recall verification through the Provenance verification standard.
{
"schema": "hx.exact.receipt/v1.1",
"operation": "…",
"result_hash": "sha256:…",
"signature": { … }
}HX-AEIR's package and offline-verification documentation describes incident-evidence checks and required linked material. Use the schema and verifier supplied with each product release.
HX-Provenance receipts and bundles can be checked offline with a matching verifier and the expected issuer public key. Product-specific procedures also cover SDP exact-result records and AEIR incident-evidence packages.
The public synthetic HX-Provenance demo lets you run valid, altered and wrong-key cases with actual signatures. It supplements the company records and release-specific proof packs above. Production verification uses its own release-matched tools and an issuer fingerprint established through a trusted channel.
The demo uses fictional data and a dedicated demo key. A hosted upload verifier is not yet available.
The product control matrix documents signing algorithms, key initialization and offline evidence checks. The security page also describes HX-Provenance appliance manifest verification, its customer-runnable validation harness and release dossier.
Algorithm standardization and FIPS architectural alignment are distinct from module certification. The security page states the applicable qualification.
Explore the representation thesis and published research records.