Forem: Anthony Johnson II

From Theory to Evidence: Validating Shannon Entropy for Data Quality at Scale

Anthony Johnson II — Tue, 14 Apr 2026 18:22:24 +0000

This article was originally published on EthereaLogic.ai.

In a previous article, I laid out the case for why Shannon entropy — Claude Shannon's 1948 measure of information content — catches data quality failures that schema validation, row counts, and null checks structurally cannot. The theory is clean: entropy measures whether a distribution still carries the signal your downstream logic depends on, not just whether the data arrived in the expected shape.

Theory is a starting point. Evidence is what earns trust.

Over the past several weeks, we ran a structured sequence of experiments to answer a harder question: does entropy-based monitoring actually outperform traditional tools on real data, at real scale, under conditions that matter to production Databricks environments?

The answer, across three independent real-world datasets and nearly 6.6 million rows, is yes — and the margin is not small.

The Research Program

We designed and executed three preregistered experiments with a single governing constraint: every claim must be backed by reproducible, append-only evidence. No retroactive adjustments. No cherry-picked datasets. Every run produces a provenance manifest with configuration hashes, dataset fingerprints, and gate verdicts that can be independently verified.

The experiments tested two capabilities against traditional baselines:

Distribution drift detection — using Shannon entropy stability scores to detect when a column's information content has shifted, compared against a KS-test adapter modeled after the statistical drift detection approach used in Evidently, one of the most widely adopted drift monitoring frameworks.

Data quality validation — using distribution-aware semantic validation to detect source contract violations, compared against a rule-based constraint adapter modeled after the validation patterns in Deequ, the standard quality library for Spark environments. Where the rule-based adapter validates individual values against predefined constraints, the challenger evaluates the full distributional profile of each column — an approach informed by the same information-theoretic principles that underpin entropy-based drift detection.

In both cases, the baselines are simplified adapters designed to isolate the comparison against a specific detection mechanism — not full replicas of the Evidently or Deequ product surfaces.

The benchmark harness injected known faults into real data — schema violations, range violations, volume anomalies, gradual distribution shifts, and abrupt distributional breaks — then measured whether each approach caught them, how quickly, and with what precision.

Three Datasets, Three Domains, One Conclusion

We selected three real-world public datasets that span materially different territory. The row counts below are the specific benchmark samples used in the experiment; the full upstream datasets may be larger.

OpenML Adult Income (UCI) — 32,561 rows of socioeconomic tabular data with categorical features like education level, occupation, and marital status.

NYC TLC Yellow Taxi (January 2023) — 3,066,766 rows of transactional trip data with timestamps, geospatial coordinates, fare amounts, and payment types.

U.S. Census ACS PUMS (2022) — 3,500,000 rows of public demographic and earnings microdata from the American Community Survey.

Combined: nearly 6.6 million rows across three independent data domains.

What the Benchmarks Showed

Drift Detection: Perfect Sensitivity, Zero False Positives

The entropy-based drift detector achieved a sensitivity of 1.0 (caught every injected drift event) with a false positive rate of 0.0 (never raised a false alarm) — across all three datasets. Detection latency matched the baseline at 1 batch.

The KS-test baseline also achieved high marks on detection sensitivity. But the entropy approach matched it on every detection metric while providing something a KS-based approach does not naturally offer: a normalized measure of proportional information capacity that is intuitively comparable across columns with different cardinalities, including unordered categorical data where KS is not natively applicable. A stability score of 0.87 on a column with 4 categories carries the same operational meaning as 0.87 on a column with 100 categories — entropy is at 87% of the theoretical maximum for the observed support.

The throughput advantage was also notable: the entropy-based approach processed data at 1.29x to 2.12x the baseline's throughput across the three datasets.

Quality Validation: Where the Gap Becomes Measurable

On quality validation, the distribution-aware approach achieved precision and recall of 1.0 on all three datasets. The rule-based baseline matched on two of the three — but on the Census ACS dataset, the baseline's precision dropped to 0.6 and its F1 to 0.75, while the challenger maintained perfect scores.

Why did Census ACS expose the gap? The Census dataset has distributional characteristics that make rule-based boundary checks less reliable: overlapping value ranges across demographic categories, high-cardinality categorical fields with skewed distributions, and subtle schema interactions that look normal in isolation but carry measurable information loss when evaluated as a distribution.

A rule-based engine asks "is this value within the allowed range?" A distributional approach asks "does the distribution of values still carry the same information it carried in the trusted baseline?" When the answer to the first question is yes but the answer to the second is no, you have the kind of silent data quality failure that erodes downstream model performance without triggering a single alert.

The latency comparison reinforced this: the distribution-aware approach ran at 37–65% of the baseline's wall-clock time across datasets.

Cross-Machine Reproducibility

Every benchmark was re-run on a second machine — a Mac mini with a fresh dataset download, independent Python environment, and no shared state. The result: 60 out of 60 gate verdicts matched across both machines. Non-latency metrics were bitwise identical.

From Benchmark to Live Execution

In a follow-on experiment, we took the validated controls and executed them against a live, non-production Databricks workspace. Two consecutive replayable runs passed all charter-scoped gates, with a fidelity ratio of 1.0 (every source record accounted for in the output), inline cost measurement, and zero audit violations. This does not constitute production-scale proof — the experiment was explicitly scoped to Bronze-layer validation in a sandbox workspace — but it closes the gap between "this works in a benchmark harness" and "this works on Databricks."

Two consecutive replayable runs in a live, non-production Databricks workspace. All four FAIL-tier gates passed; WARN-tier latency sat at 6.4-6.6% of threshold and cost at 11.2% in both runs. Source: E62 closeout (2026-04-01).

Natural Fault Validation

The third experiment carried a validated_with_caveat evidence tier from the outset, reflecting a deliberately narrow scope. The question was whether the governed pipeline infrastructure could execute end-to-end against a corpus of naturally occurring faults rather than synthetic injections.

We curated a corpus of six naturally occurring Bronze-layer data quality incidents. The full pipeline passed all six preregistered KPI gates. Each lane's held-out set contained one true fault and one clean case; both lanes detected the fault and correctly identified the clean case, yielding held-out recall of 1.0 and false positive rate of 0.0 on each lane independently. The detection adapters used deterministic scoring against pre-adjudicated labels — validating the governed infrastructure, not independent model generalization. Proving that entropy-based detectors catch novel natural faults without prior labeling remains the objective of a planned successor experiment.

What We Learned About Entropy in Practice

Three experiments, hundreds of benchmark run artifacts, and millions of rows later, a few practical lessons emerged:

Normalization is non-negotiable. The stability score — entropy divided by the maximum possible entropy for the observed number of distinct values — is what makes entropy operationally useful. A normalized score of 0.75 means entropy is at 75% of the theoretical maximum for the column's current distinct-value count. DriftSentinel catches category disappearance by comparing the normalized score against the baselined snapshot, so a column that silently drops from 12 categories to 8 will trigger a drift classification even if the surviving 8 remain uniformly distributed.

Layer-aware thresholds match how lakehouses actually work. AetheriaForge ships with default coherence thresholds aligned to Medallion architecture layers: Bronze ≥ 0.5, Silver ≥ 0.75, Gold ≥ 0.95. These are operating defaults, not Databricks-prescribed standards. The thresholds are configurable per data contract, and the right values depend on what each layer is doing to the data.

Entropy and schema validation are complementary, not competitive. Schema validation catches structural defects. Entropy catches distributional defects. You need both. The mistake is assuming that passing schema checks means the data is trustworthy.

Evidence discipline changes the conversation. Every run produced append-only evidence artifacts: JSON bundles with configuration hashes, measured gate values, thresholds, and verdicts. When a downstream consumer asks "how do you know the data is good?", the answer is a specific artifact ID, a specific health score, and a specific gate verdict — queryable, auditable, and immutable.

Applying This in Your Pipeline

Both tools are open source and available on PyPI. The benchmark results reported in this article were produced on DriftSentinel 0.4.2+ and AetheriaForge 0.1.4+, after the defects described in each product's customer impact advisory were resolved.

DriftSentinel uses Shannon entropy as its primary distribution stability signal.

pip install etherealogic-driftsentinel

Org-EthereaLogic / DriftSentinel

Databricks-native data trust pipeline — intake certification, drift gating, and control benchmarking in a single deployable product.

Three Control Patterns. Multiple Datasets. One Platform That Proves All of Them Are Working.

Enterprise Data Trust — Chapter 4: DriftSentinel

Built by Anthony Johnson | EthereaLogic LLC

If this platform is useful to your team, consider starring the repo — it helps others in the Databricks community find it.

The first three chapters of Enterprise Data Trust prove three things: data can be certified at intake, distribution drift can be gated before publication, and control effectiveness can be measured against known failure scenarios. Each chapter solves one problem in isolation.

DriftSentinel solves the next one: running all three control patterns together, across multiple registered datasets, in a production Databricks environment — with append-only evidence for every run and an operator dashboard the platform team can actually use.

Three modules. One registry. Queryable evidence. No assumption that any run passed unless the artifact says so.

Important: If you used DriftSentinel…

View on GitHub

AetheriaForge uses Shannon entropy to score information preservation across transformations.

pip install etherealogic-aetheriaforge

Org-EthereaLogic / AetheriaForge

EthereaLogic Databricks Suite — Intelligent Data Transformation Engine

Intelligent Data Transformation. Coherence-Scored. Evidence-Backed.

EthereaLogic Databricks Suite — AetheriaForge

Built by Anthony Johnson | EthereaLogic LLC

If this tool is useful to your team, consider starring the repo — it helps others in the Databricks community find it.

Every Medallion transformation introduces information loss. Most pipelines ignore it. AetheriaForge measures it by transforming source records through schema contracts, scoring the result for coherence, applying optional exact-match entity resolution and latest-wins temporal reconciliation, and recording append-only evidence. Nothing is assumed to have passed unless the artifact says so.

Executive Summary

Leadership question	Answer
What business risk does this address?	Enterprises transforming data through Bronze to Silver to Gold layers have no mathematical model governing how much information loss is acceptable at each stage, no governed entity resolution across source systems, and no auditable evidence trail for transformation decisions.
What does this application prove?	A Databricks-deployable transformation engine that scores every

…

View on GitHub

Both deploy as Databricks Apps with four-tab operator dashboards, Asset Bundle definitions for governed deployment, and notebook-based onboarding workflows.

What Comes Next

The validated experimental surface covers Bronze-layer quality validation and drift detection. The next research priorities are operational readiness validation (unattended execution with service-principal authentication), expanded natural-fault coverage with independent model evaluation and multi-reviewer adjudication, and Silver/Gold layer escalation — each following the same discipline of preregistered charters, independent datasets, and reproducible evidence.

Shannon entropy is not a silver bullet. It does not replace schema validation, freshness monitoring, or volume checks. But it measures something those tools structurally cannot — whether the data still carries the information it carried yesterday. The experiments demonstrate that this measurement is accurate, fast, and operationally useful at scale.

The tools are open source. The gap between validating structure and validating signal is closable — and now there is evidence to back it up.

Anthony Johnson II is a Databricks Solutions Architect and the creator of the Enterprise Data Trust portfolio. He writes about data quality, distribution drift, and the engineering patterns that make data trustworthy at scale.

Why Shannon Entropy Catches What Schema Validation Misses

Anthony Johnson II — Sat, 11 Apr 2026 03:39:59 +0000

This article was originally published on EthereaLogic.ai.

Your pipeline passed every check. Schema valid. Row count matched. Null percentage within threshold. Freshness on time. Dashboard green.

But this morning the downstream segmentation model lost a third of its signal. Marketing is asking why the "Premium" and "Enterprise" tiers collapsed into a single bucket. Finance wants to know why revenue forecasting diverged from actuals by 12%. The Customer 360 that was supposed to unify 40,000 accounts is quietly deduplicating to 24,000.

Everything validated. Nothing was correct.

If this sounds familiar, you have a monitoring blind spot — and it is not a tooling gap you can solve with more schema checks.

The Monitoring Blind Spot

Most data quality tools validate shape: Is the schema right? Are the types correct? Are nulls within threshold? Did the expected number of rows arrive on time?

These are necessary checks. They are not sufficient.

Here is what none of them measure: information content. A column can go from 12 distinct categories to 8 and every traditional check passes. A distribution can shift from uniform to heavily skewed and row counts will not flinch. Two source tables can silently converge to identical values during a merge, destroying the differentiation your downstream model depends on — and your freshness monitor will report on time.

The problem is not that these tools are wrong. The problem is that they are answering the wrong question. They tell you whether data arrived in the expected shape. They do not tell you whether it still carries the information it carried yesterday.

This is the difference between validating structure and validating signal.

What Is Shannon Entropy and Why Does It Matter for Data?

Shannon entropy, introduced by Claude Shannon in 1948, is a measure of information content — specifically, the average amount of uncertainty (or surprise) in a distribution. The formula is straightforward:

H = -Σ p(x) log2(p(x))

Where p(x) is the probability of each distinct value in the distribution.

The intuition: a column where every row is "Active" carries zero information — entropy is 0.0. A column evenly split across 8 categories carries maximum information for that cardinality — entropy is 3.0 bits (log2(8)). The more uniform the distribution, the higher the entropy. The more collapsed or skewed, the lower.

A concrete example

Consider a customer_tier column with 10,000 rows across four values:

Baseline (Monday):

Value	Count	Probability	-p log2(p)
Free	2,500	0.25	0.500
Basic	2,500	0.25	0.500
Premium	2,500	0.25	0.500
Enterprise	2,500	0.25	0.500

H = 2.000 bits. Maximum entropy for 4 values. Stability score: 1.0.

Friday's load:

Value	Count	Probability	-p log2(p)
Free	7,000	0.70	0.361
Basic	2,800	0.28	0.514
Premium	200	0.02	0.113
Enterprise	0	0.00	0.000

H = 0.988 bits. Stability score: 0.494. A category has disappeared entirely. Your schema check? Still green. Your row count? 10,000 as expected.

That is what entropy catches: not whether data arrived, but whether the information content of that data is still intact.

Four Failure Modes Entropy Catches

1. Distribution Collapse

What it looks like: A categorical column gradually loses diversity. A region field that once had 12 values starts arriving with 8. An order_type column concentrates from evenly distributed to 90% dominated by a single value.

Why traditional monitoring misses it: Schema is unchanged. Row count is stable. The remaining values are all valid enum members.

How entropy catches it: The stability score drops proportionally to information loss. DriftSentinel classifies this as collapsed when the score drops below the baseline by more than the configured threshold, and it will gate the load before it reaches downstream consumers.

2. Coherence Loss Across Medallion Layers

What it looks like: Your Bronze-to-Silver transformation is supposed to clean, standardize, and enrich. But somewhere in the pipeline, a join condition is too aggressive, a filter is too broad, or a coalesce is silently flattening variation.

Why traditional monitoring misses it: The Silver schema matches the contract. Types are correct. Row count may even be similar.

How entropy catches it: AetheriaForge computes a coherence score — a ratio of preserved entropy to source entropy — and enforces layer-specific thresholds: Bronze must preserve at least 50% of information (score >= 0.5), Silver at least 75% (>= 0.75), and Gold at least 95% (>= 0.95).

3. Entity Resolution Drift

What it looks like: Your Customer 360 is supposed to resolve records from multiple source systems into unified entities. But matching logic drift causes over-matching. Your "Customer 360" is actually a Customer 240.

Why traditional monitoring misses it: The output schema is correct. The row count dropped, but entity resolution should reduce rows.

How entropy catches it: If the resolved output has significantly lower entropy than expected, you are over-merging — collapsing distinct entities into fewer buckets than the source data supports.

4. Temporal Conflict and Silent Overwrites

What it looks like: A latest_wins merge strategy is supposed to resolve temporal conflicts by keeping the most recent record per entity. But when timestamps are missing or malformed, the "winner" is arbitrary.

Why traditional monitoring misses it: The merge completed without errors. Row count is within expected range. Schema matches.

How entropy catches it: If a latest_wins strategy is silently falling back to arbitrary ordering, values from one source system will be systematically overrepresented, reducing entropy in source-identifying columns.

From Theory to Practice

Drift Gating with DriftSentinel

DriftSentinel uses Shannon entropy as its primary distribution stability signal. The drift policy configuration is declarative:

drift_policy:
  monitored_columns:
    - column_name: customer_tier
      method: shannon_entropy
    - column_name: transaction_amount
      method: shannon_entropy

  gates:
    health_score_threshold: 0.70
    max_columns_failed: 2

  verdict_on_fail: block

The entropy computation itself is compact:

def column_stability_score(series: pd.Series) -> float:
    counts = series.value_counts(dropna=False)
    n_unique = len(counts)
    if n_unique <= 1:
        return 0.0
    probs = (counts / counts.sum()).to_numpy()
    positive = probs[probs > 0]
    h = -float(np.sum(positive * np.log2(positive)))
    h_max = math.log2(n_unique)
    return round(min(h / h_max, 1.0), 4)

Coherence Scoring with AetheriaForge

Where DriftSentinel measures drift within a single dataset over time, AetheriaForge measures information preservation across a transformation:

coherence:
  engine: shannon
  thresholds:
    bronze_min: 0.5   # Raw ingestion — expect some loss
    silver_min: 0.75  # Cleaned and standardized — preserve most signal
    gold_min: 0.95   # Business-ready — near-perfect preservation

Getting Started

Both tools are open-source, available on PyPI, and designed to run on Databricks.

DriftSentinel — Databricks-native data trust platform for intake certification, drift gating, and control benchmarking.

pip install etherealogic-driftsentinel

Org-EthereaLogic / DriftSentinel

Databricks-native data trust pipeline — intake certification, drift gating, and control benchmarking in a single deployable product.

Three Control Patterns. Multiple Datasets. One Platform That Proves All of Them Are Working.

Enterprise Data Trust — Chapter 4: DriftSentinel

Built by Anthony Johnson | EthereaLogic LLC

If this platform is useful to your team, consider starring the repo — it helps others in the Databricks community find it.

Three modules. One registry. Queryable evidence. No assumption that any run passed unless the artifact says so.

Important: If you used DriftSentinel…

View on GitHub

AetheriaForge — Coherence-scored transformation engine for entity resolution, temporal reconciliation, and schema enforcement.

pip install etherealogic-aetheriaforge

Org-EthereaLogic / AetheriaForge

EthereaLogic Databricks Suite — Intelligent Data Transformation Engine

Intelligent Data Transformation. Coherence-Scored. Evidence-Backed.

EthereaLogic Databricks Suite — AetheriaForge

Built by Anthony Johnson | EthereaLogic LLC

If this tool is useful to your team, consider starring the repo — it helps others in the Databricks community find it.

Executive Summary

Leadership question	Answer
What business risk does this address?	Enterprises transforming data through Bronze to Silver to Gold layers have no mathematical model governing how much information loss is acceptable at each stage, no governed entity resolution across source systems, and no auditable evidence trail for transformation decisions.
What does this application prove?	A Databricks-deployable transformation engine that scores every

…

View on GitHub

Both projects publish customer impact advisories when defects are found that could affect operator decisions. If you are evaluating data quality tooling, look for that signal. The willingness to publicly disclose what went wrong, who was affected, and what to do about it tells you more about engineering culture than any feature list.