{
  "workflow": "shipping_resolution",
  "environment": "production",
  "issue_type": "shipping",
  "customer_tier": "self-serve",
  "prompt_name": "shipping-delay-triage",
  "prompt_version": 7,
  "release_version": "2026.04.13",
  "model_provider": "openai",
  "model_name": "gpt-4o",
  "ticket_id": "ticket_fallback_shipping_path_recovered_after_timeout_cluster_session_shipping_timeout_cluster",
  "language": "en",
  "user_id": "customer_shipping",
  "agent_profile_id": "shipping-delay-resolution",
  "agent_team": "Logistics Support",
  "agent_owner": "Logistics ops",
  "agent_mission": "Explains delivery delays, damaged shipments, and replacement paths using logistics knowledge.",
  "story_label": "Fallback shipping path recovered after timeout cluster",
  "story_summary": "The revised fallback sequence kept quality high enough even while the logistics knowledge system remained unstable.",
  "scenario_id": "scn_kb_timeout_recovered",
  "customer_intent": "Customer needed a grounded answer on a delayed replacement shipment after a carrier scan gap.",
  "expected_resolution": "Explain the fallback status honestly and give a clear next checkpoint.",
  "policy_result": "recovered_after_fallback",
  "quality_score": 0.88,
  "severity_tag": "healthy",
  "status_label": "Recovered fallback path",
  "replay_label": "Shipping Delay Resolution · Fallback shipping path recovered after timeout cluster",
  "operator_notes": "Case: Fallback shipping path recovered after timeout cluster\nIntent: Customer needed a grounded answer on a delayed replacement shipment after a carrier scan gap.\nExpected resolution: Explain the fallback status honestly and give a clear next checkpoint.\nObserved policy result: recovered_after_fallback\nStory summary: The revised fallback sequence kept quality high enough even while the logistics knowledge system remained unstable.\nAgent role: Shipping Delay Resolution\nOwner team: Logistics Support"
}