CS-OBS-002 · OBS Operations, lineage, data readiness and consumption · 156 of 192
Trace a record from source to consumer
Data Steward · Trigger: A user questions the origin or interpretation of a publication.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
3 of 4 steps satisfiedAn investigation will reproduce the record's admission path and identify any missing evidence.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
A failure is seen at the failing stage, owned, remediated and closed with evidence.
Step 1. Inspect the run and identify the failing stage.
satisfiedOperates onRUN-003HAL Application API C3 → canonical flow · run 20260902Flow run· OPTIMON-IND / Halol Packaging Line
executionsucceededadmissioncompletedeliveryaccepted
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: evidence entry written
Step 2. Assign the incident to an owner with its runbook.
not yet satisfiedOperates onINCI-004Quarantine spike — Halol Packaging LineIncident· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
triageresolvedimpactunknownremediationcomplete
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: triage = in review
Step 3. Execute the permitted remediation.
satisfiedOperates onINCI-004Quarantine spike — Halol Packaging LineIncident· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
triageresolvedimpactunknownremediationcomplete
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: remediation = complete, triage = resolved
Step 4. Close the run with reconciliation evidence.
satisfiedOperates onRUN-024SHF Event stream F24 → canonical flow · run 20260923Flow run· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
executionsucceededadmissioncompletedeliveryaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: execution = succeeded
Exception path
Restricted payloads will not leak through lineage views.
Alternate path. Remediation is not permitted at this level: escalate to the release manager.
not yet satisfiedOperates onINCI-004Quarantine spike — Halol Packaging LineIncident· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
triageresolvedimpactunknownremediationcomplete
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: impact = blocked
Workflow as specified
CoreSync will expose the authorized source reference, input evidence, binding and transformation versions, quality decisions, publication and per-consumer receipts.
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
Views where it lives
Acquisition Operations · Operational overviewAcquisition Operations · Incidents and runbooksAcquisition Operations · Lineage and evidence explorerAcquisition Operations · Use-case data readinessDesign · Policy and locality editorDelivery · Published data and subscription catalogueGovernance · Usage, entitlements and capacity