OptimonCoreSync Studio
IE
CS-DQ-001 · DQ Quality validation, drift and remediation · 121 of 192

Validate structural and semantic contracts separately

Data Steward · Trigger: A source record reaches admission.

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 satisfied

Fixtures will show independent structural and semantic pass/fail outcomes.

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 satisfied
Operates onQUAR-003Out-of-range value · lot 3Quarantine item· OPTIMON-IND / Halol Packaging Line
holdingreleasedcorrectionpendingreleaseAuthoritypending
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 satisfied
Operates onQUAR-010Missing mandatory field · lot 10Quarantine item· OPTIMON-IND / Nagda Warehouse
holdingheldcorrectionacceptedreleaseAuthoritygranted
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 satisfied
Operates onREAD-017OEE — input 17Readiness item· OPTIMON-IND / Raigarh Melt Shop
conditiondegradedevidencepartialtrenddegraded
Moves the record and writes evidence. Permission: test.
Acceptance for this step: condition = satisfied, evidence = complete

Exception path

A structurally valid payload will not automatically be semantically admissible.
Alternate path. The correction is not defensible: reject it and retain the evidence.
not yet satisfied
Operates onQUAR-003Out-of-range value · lot 3Quarantine item· OPTIMON-IND / Halol Packaging Line
holdingreleasedcorrectionpendingreleaseAuthoritypending
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: correction = rejected, holding = held

Workflow as specified

CoreSync will distinguish parse/schema checks from canonical identity, unit, reference and context checks, recording exact failure causes and contract versions.

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.