Every industry pays for the representation it chooses
Representing a workload densely can require materializing and moving the full state. The applications below show where a different representation changes the cost of useful work.
Choosing a representation for each workload
Engineered physical systems
Hypersonics, propulsion and thermal systems, plasma and kinetic devices, nuclear and regulated aerospace. Coupled disciplines, expensive physics, and design campaigns where many high-value quantities are infeasible to represent densely.
The engine builds representation-aware response surfaces across topology changes and tested validity regions, propagates uncertainty natively, and records each result's validity decision under an explicit policy. HX-MDAO-TP distinguishes VALIDATED, NOT_VALIDATED and ABSTAIN; model-domain failure or an unconverged solve produces NO_RESULT. Signed evidence retains the decision and supporting policy.
AI infrastructure
Two workloads, one buildout. Thermal-fluid simulation of AI factories and high-density datacenters, so cooling strategy, layout changes, and failure scenarios are evaluated before capital commits. And the inference data plane as one signed runtime on GPU infrastructure the customer already operates.
High-consequence records
Compliance evidence, discovery productions, cyber incident artifacts, public-sector case files, financial model outputs, healthcare documentation and utility inspection records may be challenged after creation. HX-Provenance binds each registered artifact to an ML-DSA-signed receipt with tamper-evident integrity records. Reviewers can verify the exported bundle offline with the matching verifier and independently established expected issuer key.
Agent-evaluation incident evidence
HX-AEIR validates and preserves the supplied evidence used to reconstruct an agent-evaluation incident. Its required inputs include signed authorization and preflight documents, with consistent links between the source evidence, incident record and any prior revision.
HX-Provenance supplies receipts and evidence bundles for registered artifacts across applications. HX-AEIR applies a specific incident-evidence contract, checking document syntax, cross-document semantics and authorization linkage before signing and exporting a reviewer package.
The private appliance runs in the customer's Google Cloud project. Reviewers verify an exported package with the matching tooling and independently pinned issuer key. The package preserves the supplied record; it does not establish that telemetry is complete or that an incident conclusion is correct. HX-AEIR does not execute, monitor or contain evaluated agents.
Cryptography is distributed across code, libraries, TLS endpoints, certificates, keys, databases, and vendor products, and most estates have no authoritative inventory of what is quantum-vulnerable. The transition runs Discover to Quote to Migrate to Protect to Assure, each stage emitting signed artifacts: CycloneDX CBOM, deterministic signed quotes, ledgered migration events, posture snapshots.
OMB M-26-15 requires covered federal agencies to submit a PQC Migration Plan to OMB and ONCD within 120 days of June 24, 2026, identifying cryptographic-inventory methods and automated tools. National security systems are excluded.
Workload comparisons
Smooth, coupled, high-dimensional physics. The structure measurement says fold: fidelity-governed QTT, with dense and sparse retained where they measure better.
Pooled final-output embeddings where folding does not pay. The same measurement says do not force it: structure-governed latent-factor plus SQ8 instead.
The pair is the point. The substrate measures the structure and chooses the representation; it does not force one answer onto every workload. Their difference is the doctrine, demonstrated.
Federal is a mission environment
Every workload above operates inside it: design campaigns, AI infrastructure, records, and the cryptographic transition. What changes is the boundary, the procurement path, and the authorization state.