CS-DQ-008 · DQ Quality validation, drift and remediation · 128 of 192
Reconcile source truth with admitted data quality
Data Steward · Trigger: Persistent discrepancies suggest source or mapping problems.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
0 of 3 steps satisfiedThe investigation will identify its observation boundary, discrepancies and unresolved coverage limits.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
A quality failure is held, corrected under authority and reflected in consumer readiness.
Step 1. Propose the correction for the held payload.
not yet satisfiedholdingheldcorrectionacceptedreleaseAuthoritygranted
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: correction = proposed
Step 2. Release under authority; the original payload is retained.
not yet satisfiedholdingheldcorrectionproposedreleaseAuthoritypending
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: holding = released, releaseAuthority = granted
Step 3. Re-evaluate the readiness condition the failure affected.
not yet satisfiedOperates onREAD-024Maintenance risk — input 24Readiness item· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
conditionunknownevidencemissingtrendstable
Moves the record and writes evidence. Permission: test.
Acceptance for this step: condition = satisfied, evidence = complete
Exception path
An ingestion success rate will not be used as proof that the source captured every real-world event.
Alternate path. The correction is not defensible: reject it and retain the evidence.
not yet satisfiedholdingheldcorrectionacceptedreleaseAuthoritygranted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: correction = rejected, holding = held
Workflow as specified
CoreSync will compare bounded source extracts, admitted records and delivery outcomes to separate source absence, transformation error and delivery loss.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.
Journeys that include it
Not part of a composite journey; exercised through its family views.