HOLONOMIX

The HolonomiX Atlas

Data has structure. The Atlas measures it.

A signed measurement framework for understanding how data behaves before infrastructure decides how to move, compress, rerank, tensorize, or process it.

It is not a leaderboard. It is a deployment behavior map.

71
classified rows

text, vision, physics, scientific

5
QTT-native rows

3D tensor measurements

5
compressed-certified

physics rows only

Proof, not positioning

What the current Atlas measures.

Every row is classified under a locked calibration protocol. The Atlas tracks what was measured, what was certified, and what remains pending.

Evidence layerCount
Classified text, vision, physics, and scientific rows71
QTT-native 3D tensor measurements6
Text-corpus stability matrix7 models × 5 corpora
Physics compressed-path certified rows5
Signed rollup checkpointsML-DSA-65 / FIPS 204

Why the Atlas exists

Enterprise data infrastructure usually optimizes too late.

Data is copied, moved, embedded, transformed, indexed, compressed, and recomputed before the system understands what kind of data it is dealing with. That creates waste: unnecessary movement, duplicated compute, overused rerank paths, unsafe compression assumptions, expensive high-dimensional representations, and one-size-fits-all routing decisions. The Atlas changes the order of operations. First, measure the structure. Then choose the execution path.

What the Atlas measures

Six axes of structural intelligence.

Spectral governability

Can the data be reduced without destroying the structure that matters? The Atlas measures rank, retained-rank fraction, spectral decay, and compression ratio to determine whether a corpus is governable, compressible, conditional, or weak.

Retrieval recoverability

Does rerank actually help? The Atlas compares single-pass recall against reranked recall at K=10. Some rows recover strongly. Some are flat. Some get worse.

Rerank economics

Rerank is not a default feature. It is a measured policy. Each row is classified RERANK_RECOVERABLE, RERANK_LOW_LIFT, RERANK_FLAT, or RERANK_HARMFUL. A platform should not spend compute on rerank when the data shows it will not help.

Cross-corpus stability

Does the behavior survive domain drift? The Atlas measures model behavior across multiple text corpora to determine whether a model is stable, drifting, or insufficiently measured.

Compressed-path certification

Does compression preserve final recall under the actual serving path? The Atlas distinguishes fp32 calibration from compressed-path certification. A row can show strong fp32 rerank utility without being certified for TQ4 deployment.

Tensor-native structure

When is QTT the right tool? The Atlas measures QTT-native 3D tensor fields separately from flattened embedding rows. QTT is not treated as a universal embedding compressor. It is used where the data is natively tensor-structured.

Headline findings

What the measurements reveal.

Bigger embeddings ≠ better deployment

On C4, Qwen3-Embedding-4B at D=2560 lands A_ELITE with RR=0.9958 and G=+2.1 pp. Six of seven measured D=4096 7B-class rows land D_SENSITIVE.

Dimension is not a deployment strategy.

Rerank is not always helpful

Rerank policyCount
RERANK_RECOVERABLE43
RERANK_FLAT15
RERANK_LOW_LIFT6
RERANK_HARMFUL7

A uniform rerank policy is wrong. The Atlas tells the platform when rerank is worth paying for — and when it should stay off.

Some models are stable. Others drift.

Five models are STABLE_RECOVERABLE across all five measured text corpora:

  • · Gemini embed-v2
  • · BGE-M3
  • · Cohere v3 multilingual
  • · Voyage 3.5
  • · Qwen3-Embedding-4B

NV-Embed-v2 and OpenAI 3-large show drift. Customer data rarely looks exactly like a benchmark corpus.

Physics data is structurally different from text

RegimeResult
MACE-MP-0 largeρ=0.0007, CR=1365×
Smooth PDE fieldsCR=16–71×
Shock-dominated PDEsflatter spectra, stronger rerank dependence
QTT-native 3D fieldsup to 7571× compression

Different data structures need different execution paths.

QTT works where tensor structure is real

QTT underperforms when forced onto arbitrary flattened embeddings. But on native 3D tensor fields, the story changes. Taylor-Green vortex at 128³ reaches 7571× compression at rank 4, and 244× compression at rank 32 with 1.31e-5 relative L2 error.

QTT is not the default embedding path. QTT is the tensor-native path.

Classification coverage

DataVerdict × RetrievalClass.

The current Atlas covers only a portion of the verdict×class grid. The visual marks calibrated cells; empty cells are roadmap. fp32 calibration only — compressed deployment is a separate certification phase.

Atlas calibration coverageDataVerdict × RetrievalClass
DataVerdict ↓RetrievalClass →
A_ELITE
Native fp32 path
B_RECOVERABLE
fp32 with rerank
C_BORDERLINE
Calibration in flight
D_SENSITIVE
fp32 only, no compress
A_GOVERNABLE
Clean low-rank structure
B_COMPRESSIBLE
Structure with guard-rails
calibrated
C_CONDITIONAL
Slice-dependent structure
calibratedcalibrated
D_WEAK
No exploitable structure
calibratedcalibratedcalibrated
calibratedpartialroadmapfp32 calibration only · compressed deployment is a separate certification phase

Calibration scope

A_ELITE today is fp32 rerank utility, not TQ4 deployment.

Every text/vision row is fp32 calibration. Compressed certification measures ΔSP, ΔRR, and P before any text or vision row becomes COMPRESSED_CERTIFIED. Five physics rows are already compressed-certified under the locked protocol.

Atlas vs. leaderboard

A leaderboard ranks. The Atlas decides.

A leaderboard asks

Which model scored highest?

The Atlas asks

What should the system do with this data?

A model can score well and still be unstable across corpora. A high-dimensional embedding can still be deployment-sensitive. A compressed path can damage single-pass recall but remain safe after rerank. A tensor method can fail on flattened embeddings but excel on native fields. The Atlas is built to expose those distinctions.

HX-SDP integration

How the Atlas drives the platform.

HX-SDP uses the Atlas as a structural intelligence layer. The platform should not treat all data the same. It should classify the data first, then decide whether to:

  • ·reduce rank
  • ·rerank
  • ·avoid rerank
  • ·compress
  • ·certify compression
  • ·route differently
  • ·preserve exact recall
  • ·use QTT-native tensor storage

This is the core of structure-aware execution.

The Atlas decision stack

Measurement before policy.

01

Data stream

02

Structural measurement

03

Spectral governability

04

Retrieval recoverability

05

Rerank economics

06

Compression certification

07

Execution policy

The output is not just a score. The output is a decision.

Atlas assessment

What an assessment answers.

For a customer corpus, an Atlas assessment can answer:

  • ·Is this data spectrally governable?
  • ·Which embedding model behaves best on this corpus?
  • ·Does rerank help, hurt, or waste compute?
  • ·Is the model stable across similar corpora?
  • ·Is compression safe?
  • ·Should the data stay dense, reduce rank, quantize, or tensorize?
  • ·Which execution path should HX-SDP use?

Current coverage

What the Atlas covers today.

DomainCoverage
General text embeddingsmeasured
Vendor embedding APIsmeasured
Open-weight embedding modelsmeasured
Vision embeddingsmeasured
Scientific textmeasured
Physics PDE fieldsmeasured
Equivariant atomic representationsmeasured
QTT-native 3D fieldsmeasured
Text / vision compressed certificationpending
Protein language modelsplanned

Measurement integrity

The Atlas is built as an auditable measurement system.

Most rows are fp32 calibration rows. Only rows explicitly marked as compressed-certified should be treated as deployment-certified for compressed serving.

  • ·fixed calibration constants
  • ·fp64 brute-force ground truth
  • ·hardware-independent classification
  • ·signed rollup checkpoints
  • ·machine-readable row provenance
  • ·explicit class scope
  • ·explicit compression-certification status

Public assets

Three ways to engage with the Atlas.

Public Atlas Table

A cleaned, publishable table of measured rows, compressed-certified rows, stability results, and QTT-native tensor measurements.

Technical Report 001

A technical whitepaper explaining the Atlas method, measured results, and platform implications.

Atlas Assessment

A customer-specific measurement pass that classifies how a real corpus behaves under the HX-SDP structural data platform.

FAQ

Common questions about the Atlas.

Is the Atlas a model leaderboard?

No. The Atlas is a deployment behavior map. It measures what the system should do with a model/corpus/data pair, not just which model has the highest score.

Does A_ELITE mean TQ4-certified?

Not by default. In fp32 calibration, A_ELITE means native rerank utility is at least +1.0 pp. TQ4 readiness requires compressed-path certification.

Why does cross-corpus stability matter?

A model that behaves well on one corpus may drift on another. The Atlas measures whether model behavior survives domain shift.

Why does QTT appear in the Atlas?

QTT is evaluated where tensor structure is real. The Atlas distinguishes between flattened embeddings, where QTT may not be appropriate, and native tensor fields, where QTT can produce very high compression.

What does HolonomiX do with the Atlas?

HolonomiX uses the Atlas to guide HX-SDP execution policy: reduce, rerank, compress, tensorize, certify, or preserve the exact path based on measured structure.

Before optimization

Before data can be optimized, it has to be understood.

HolonomiX built the Atlas to measure the structure of data before the platform decides what to do with it. The result is a practical execution map: when to reduce, when to rerank, when to compress, when to tensorize, when to leave the data alone.

Data has structure. The Atlas measures it.