Skip to content

DATA CONTRACT AND COVERAGE SANDBOX / V126

Validate structure before analysis.

Exercise nine public synthetic fixtures across schema drift, grain, cardinality, duplicate keys, table hashes, missingness, and explicit coverage denominators.

Synthetic fixtures
9
Declared schemas
9
Grain contracts
4
Remote writes
0
01Declare.

Name schemas, native keys, grains, and expected multiplicity.

02Refuse.

Block incompatible structure before any ratio is shown.

03Count.

Build Common and Union sets from unique declared join keys.

04Denominate.

Keep left, right, and union coverage meanings separate.

STRUCTURE-FIRST WORKSPACE

Inspect one contract failure at a time.

Every fixture is synthetic, immutable, and bundled with the public release.

Current-tab only. Bundled synthetic data has not been uploaded, transmitted, or stored.

01 / Fixture

Choose a bundled structural case.

A declared schema, equal grain, and one-to-one keys permit coverage calculation.

02 / Validation

VALID

All declared structural contracts pass.

Declared
one-to-one
Observed
one-to-one
Coverage
Available
  1. Schema
  2. Leak
  3. Hash
  4. Native keys
  5. Grain
  6. Cardinality
Declared inputs

Schema, grain, and join contract

clean-site-one-to-one
Left table

context-site-v1

FieldTypeRequiredKey
site_aliasstringYesNative
context_classenumYes-
Right table

metric-site-v1

FieldTypeRequiredKey
site_aliasstringYesNative
metric_idstringYes-
metric_valuenumber|nullYes-
Left grain
site.v1site_alias
Right grain
site.v1site_alias
Join keys
site_aliassame-grain
Cardinality
one-to-onedeclared before join

SYNTHETIC STRUCTURE BOUNDARY

A valid join is not proof of scientific validity.

Every displayed identifier and value is synthetic. Structural validation does not establish measurement quality, causality, statistical adequacy, model validity, process fitness, or production readiness.