CS-VAL-006 · VAL Simulation, qualification and acceptance evidence · 184 of 192
Compare shadow and operational acquisition before acceptance
Integration Lead · Trigger: A replacement or newly built flow is ready for field evaluation.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
2 of 3 steps satisfiedAcceptance will identify the tested use cases, site conditions, unresolved issues and evidence owner.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
Conformance is demonstrated on fixtures and accepted as release evidence.
Step 1. Re-run the conformance suite against its fixture.
not yet satisfiedOperates onLABR-002Historian adapter 2 · conformance run 2Laboratory run· OPTIMON-IND / Nagda Warehouse
executionfailedconformancepartialacceptancepending
Moves the record and writes evidence. Permission: test.
Acceptance for this step: execution = succeeded
Step 2. Accept the bundle as release evidence.
satisfiedOperates onLABR-009Vision adapter 9 · conformance run 9Laboratory run· OPTIMON-IND / Raigarh Melt Shop
executionsucceededconformanceconformantacceptanceaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: acceptance = accepted
Step 3. Record the qualification result for the adapter under test.
satisfiedOperates onADAP-016Line onboarding blueprint 16Adapter / blueprint· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
submissionacceptedqualificationqualifiedpublicationretired
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: qualification = qualified
Exception path
Demonstrated, installed, operational and accepted states will remain distinct.
Alternate path. Assertions fail: reject the evidence; the release does not proceed on hope.
not yet satisfiedOperates onLABR-002Historian adapter 2 · conformance run 2Laboratory run· OPTIMON-IND / Nagda Warehouse
executionfailedconformancepartialacceptancepending
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: acceptance = rejected
Workflow as specified
CoreSync will compare bounded shadow and authorized operational evidence, reconcile differences and record formal acceptance scope without allowing the shadow path to create production effects.
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.