Source coverage
12 / 12
Every source in the synthetic scope produced an observation.
WebTruffle
Menu
Public proof asset · Synthetic specimen
What a feed should provebefore you use it.
This specimen shows the shape of an acceptance report for a managed data feed: agreed rules, measured results, quarantined exceptions, and delivery evidence. It contains synthetic records only—no customer data and no invented client outcome.
Run verdict
Pass with quarantine.
12,475 synthetic records passed the agreed rules and 11 were held out for review. Nothing questionable was silently dropped into the delivered file.
Required fields
99.92%
Ten missing required values were detected before delivery.
Schema validity
99.97%
Four records failed a structural or field-level validation rule.
Delivery freshness
6m 48s
The synthetic output arrived inside its 60-minute acceptance window.
What the artifact separates
Four different kinds of confidence.
Pipeline health
Did the scheduled run complete, retry correctly, and process every expected source?
Data health
Did the output meet its schema, completeness, identity, range, and anomaly rules?
Source fidelity
Did reviewed outputs reflect the source and the agreed interpretation of each field?
Delivery integrity
Did the accepted records reach the agreed destination with a manifest and checksum?
Define the report around your decision.
The fields, thresholds, sample size, and failure actions shown here are illustrative. A real report follows the schema and acceptance rules agreed for your project.