CS-OBS-006 · OBS Operations, lineage, data readiness and consumption · 160 of 192
Evaluate service objectives with defensible time measures
Platform Operator · Trigger: A flow has freshness, latency or completeness objectives.
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 satisfiedObjective reports will show their denominators, time basis, exceptions and supporting runtime 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-014NGD Event stream B14 → canonical flow · run 20260913Flow run· OPTIMON-IND / Nagda Warehouse
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.
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: remediation = complete, triage = resolved
Step 4. Close the run with reconciliation evidence.
satisfiedOperates onRUN-014NGD Event stream B14 → canonical flow · run 20260913Flow run· OPTIMON-IND / Nagda Warehouse
executionsucceededadmissionpartialdeliverypartial
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: execution = succeeded
Exception path
Negative clock-skew latency will not be displayed as excellent performance.
Alternate path. Remediation is not permitted at this level: escalate to the release manager.
not yet satisfiedOperates onINCI-008Schema drift detected — 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 compute objectives using declared observation boundaries, clock-quality rules and exclusion policies, distinguishing measured values from unknown or estimated metrics.
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.
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