Quality & Provenance

Data is more valuable when you can trace it.

DModify treats provenance, schema validation, deduplication and delivery metadata as first-class parts of the data product.

Authoritative sources

Records are derived from official public systems such as SEC EDGAR and government sources.

Schema validation

Production records are checked against explicit dataset contracts before export.

QA states

PASS and WARNING states are retained where appropriate; invalid records can be rejected.

Deduplication

Stable identities and persistent state help prevent previously delivered records from being emitted again.

Run metadata

Runs record processed, accepted, duplicate, exported, rejected, warning and failure counts.

Batch integrity

Delivery manifests can include file size, timestamps and SHA-256 checksums for exported files.

Provenance example

Trigger filing and financial source are distinct.

When an 8-K triggers a financial record, DModify can preserve the 8-K accession and archive URL while separately identifying the 10-Q or 10-K used for the metrics.

form_type: 8-K
accession_number: 0001104659-26-105905
source_filing_url: sec.gov/.../000110465926105905/
financial_source_form_type: 10-Q
financial_source_accession_number: 0001628280-26-035067
financial_source_filing_url: sec.gov/.../000162828026035067/
Preview service levels: The SEC feeds are still undergoing controlled production validation. DModify is not publishing a guaranteed ingestion-latency SLA until operational measurements are complete. This avoids promising a latency target before it has been validated.
Important: DModify provides structured data and data services. We do not provide investment recommendations, trading signals or financial advice.