CS-OBS-004 · OBS Operations, lineage, data readiness and consumption · 158 of 192
Assess whether a use case has its required data
Data Consumer Owner · Trigger: An intelligence or workflow use case is activated or loses an input.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
1 of 4 steps satisfiedA failed dependency will propagate to the affected use-case readiness view with its 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-005RGH Relational database E5 → canonical flow · run 20260904Flow run· OPTIMON-IND / Raigarh Melt Shop
executionsucceededadmissionpartialdeliverypartial
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-008Schema drift detected — 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.
not yet satisfiedOperates onINCI-015Delivery lag breach — Raigarh Melt ShopIncident· OPTIMON-IND / Halol Packaging Line
triagependingimpactdegradedremediationblocked
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: remediation = complete, triage = resolved
Step 4. Close the run with reconciliation evidence.
not yet satisfiedOperates onRUN-026NGD File drop B26 → canonical flow · run 20260925Flow run· OPTIMON-IND / Nagda Warehouse
executionfailedadmissionpartialdeliveryaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: execution = succeeded
Exception path
Data readiness will not independently authorize a physical action or certify a business decision as safe.
Alternate path. Remediation is not permitted at this level: escalate to the release manager.
not yet satisfiedtriageresolvedimpactdegradedremediationcomplete
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: impact = blocked
Workflow as specified
CoreSync will compare registered input contracts with availability, freshness, completeness, semantic binding and access evidence, reporting satisfied, degraded, missing and unknown inputs.
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