What problem does it solve?
Use when QA-ing a dataset or an analysis before it is shared, published, or fed downstream —
the last gate before a number leaves your laptop. Covers two entry points: (1) dataset QA
(schema/dtype contracts, unexpected nulls, key uniqueness, duplicate rows, cardinality and
value-range sanity, parquet round-trip integrity) and (2) analysis QA (re-run determinism,
benchmark reconciliation, units/scale/sign, whether the conclusions are actually supported by
the data, and coverage/selection/survivorship/revision bias). Polars-first; tuned to BLS
pipelines (QCEW/CES/JOLTS), NumPyro/PyMC nowcasts, and as-of/vintage correctness. Trigger on:
"is this ready to publish", "sanity-check this dataset/parquet", "review my analysis", "do the
numbers reconcile", "why doesn't this match the official total", validating an ETL output,
pre-publish review, reproducibility / "I can't reproduce yesterday's run", silent cache or
fallback masking a failure, a coverage ratio that looks too clean, a decomposition whose
components don't add up, future leakage past a data's knowability boundary, or a claim that a
result is "fine" without an independent check. Always consult before signing off on data or an
analysis — these checks are the ones agents skip unprompted.
Core Features & Use Cases
- Dataset QA — Validate schema contracts, detect nulls, ensure key uniqueness, and guard against duplicates; supports parquet round-trip checks.
- Analysis QA — Evaluate reproducibility, bias, and methodology to ensure conclusions are data-supported.
- Pre-publish Guardrails — Emit a structured validation report summarizing schema, integrity, and bias checks.
Quick Start
Run a one-time validation pass on your dataset or analysis and emit a structured validation report.