Shipment stop is confirmed

Shipment confirmation is pending

Business outcomePending

The request

Shipment stop awaiting provider acknowledgment

Please stop the scheduled shipment for order ord_mvv9q7og67snbm75.

Referenced order ord_mvv9q7og67snbm75

Agent’s recorded message

The shipment-stop request is queued. Provider cancellation confirmation is still pending.

Expected

The provider confirms the referenced shipment is canceled

Actual

Shipment scheduled

What Veycera checked

The provider confirms the referenced shipment is canceled
Shipment status: scheduled · must equal canceled
Awaiting confirmation

View all checks · 1 →

Shipment stop is confirmed · business records read Oct 30, 2026, 17:56 UTCDue Oct 30, 2026, 17:57 UTC (business clock)

ExpectedCaptured contract v1 · due 10 s after resolution

Original agent message

The agent wrote, Oct 30, 2026, 17:56 UTC

The shipment-stop request is queued. Provider cancellation confirmation is still pending.

Predicate results · 0 satisfied, 1 violated, 0 unknown, 0 not applicable

Needs attention · 1 check

The provider confirms the referenced shipment is canceledShipment status: scheduled · must equal canceled

In this synthetic example, the provider must confirm an approved stop-shipment request within ten seconds after its support ticket is resolved.

ObservedSystems of record, read-only · retrieved Oct 30, 2026, 17:56 UTC

Tickettkt_mvv9q7pt6aoktptr

Status: Resolved
Agent approved: yes
Resolved at: Oct 30, 2026, 17:56 UTC
Order quoted: ord_mvv9q7og67snbm75
Source: Support

Orderord_mvv9q7og67snbm75

Status: Paid
Updated: Oct 30, 2026, 17:56 UTC
Total: $59.00
Source: Orders

Payment and refundsch_mvv9q7on68fhym4l

Payment: $59.00 Succeeded
Refunds: None
Refunded: $0.00 of $59.00
Source: Payments

Shipmentshp_mvv9q7pf69id254b

Status: Scheduled
Dispatch: Oct 30, 2026, 19:26 UTC
Updated: Oct 30, 2026, 17:56 UTC
Source: Fulfillment

Workflow and authorization

Immutable record

Workflow: Shipment stop is confirmed
Contract version used: v1approved Oct 30, 2026, 17:50 UTCOpen current configuration
Source of intent: Customer request in helpdesk ticket tkt_mvv9q7pt6aoktptr (shipping)
Authorization: Agent approved the request · required by the captured contract trigger
Trigger: A shipping ticket becomes resolved after agent approval
Obligation: 1 applicable condition must hold within 10 s of resolution; due Oct 30, 2026, 17:57 UTC
Instance created by: connector event · ticket.resolved via webhook (processed)
Checks run: 1

Correlated identifiers

Only explicit references are used

Ticket: tkt_mvv9q7pt6aoktptr
Order quoted in the ticket: ord_mvv9q7og67snbm75
Order resolved: ord_mvv9q7og67snbm75 · Orders
Payment: ch_mvv9q7on68fhym4l · Payments
Refunds on that payment: none
Shipment: shp_mvv9q7pf69id254b · Fulfillment
Customer: cus_mvv9q7nv6639b6dt
Other orders, same customer: none
Correlation rule: The order comes only from the ticket's order reference. When it is missing or unknown the verdict is indeterminate, never a guess by email or recency.

Missing or ambiguous evidence

0

Nothing was missing: every identifier resolved and every applicable condition could be read from Fulfillment.

Stored for this verdict: the business snapshot, predicate results and captured contract v1. No application logs, traces, runtime metrics or agent execution history were read or kept.

Contract as evaluated v11 conditions · deadline 10 s

This is the version the verdict was computed under. Editing the contract creates a new version and does not change this record.

{
  "trigger": {
    "object": "ticket",
    "categories": [
      "shipping"
    ],
    "status": "resolved",
    "requiresAgentApproval": true
  },
  "identifiers": {
    "order": {
      "source": "ticket.orderRef",
      "required": true
    }
  },
  "conditions": [
    {
      "path": "shipment.status",
      "op": "eq",
      "value": "canceled",
      "id": "fulfillment_canceled",
      "description": "The provider confirms the referenced shipment is canceled",
      "applicableWhen": []
    }
  ],
  "deadlineSeconds": 10,
  "instance": {
    "eventTypes": [
      "ticket.resolved"
    ],
    "initialRetrySeconds": 1,
    "maxRetrySeconds": 1,
    "maxAgeSeconds": 86400
  }
}

Timeline

UTC · clock domain labelled on every event

Ticket createdbusiness / scenarioDemo time · Oct 30, 17:56 UTC
Ticket resolvedbusiness / scenarioDemo time · Oct 30, 17:56 UTCthe clock for the deadline starts here
Event received (webhook)wall-clock ingestionOct 30, 2026, 17:50 UTC · 2 h agoticket.resolved · evt_mvv9q7s16bezhrnc
Event processedwall-clock ingestionOct 30, 2026, 17:50 UTC · 2 h agoprocessed
Instance createdwall-clock ingestionOct 30, 2026, 17:50 UTC · 2 h agoby connector event
Records retrievedbusiness / scenarioDemo time · Oct 30, 17:56 UTCSnapshot labelled by the source/simulation clock, not wall-clock ingestion
Evaluatedbusiness / scenarioDemo time · Oct 30, 17:56 UTCcheck 1 of this instance
Deadlinebusiness / scenarioDemo time · Oct 30, 17:57 UTC10 s after resolution
Next checkbusiness / scenarioDemo time · Oct 30, 17:57 UTC
Gives up (indeterminate)business / scenarioDemo time · Oct 31, 17:56 UTC1 day after resolution without a verdict

Record identifiers and retention

Execution out_mvv9q7v36dyzt2sh · ticket tkt_mvv9q7pt6aoktptr · 1 recorded checks.

Stored for this verdict: the business snapshot, predicate results and captured contract v1.

Simulated time · 6 min ahead

Business records and deadlines use scenario time. Ingestion, reviews, and investigation execution use wall time. Timeline events label their clock; both are shown in UTC. Demos advance business time instead of waiting.