{
  "acceptance": "Another operator can locate the source and execute the check without guessing its location or success condition.",
  "automated_checks": true,
  "built_at": "2026-11-01T17:32:50.400276+00:00",
  "description": "A report should tell the next operator what to inspect and how to verify the result without inventing a root cause.",
  "diagram": [
    "Locate observation",
    "Bound the inference",
    "Assign a specific action",
    "Define acceptance"
  ],
  "evidence": {
    "observed_at": "2026-11-01T16:09:23+00:00",
    "period": {
      "end": "2026-11-01T16:09:23+00:00",
      "start": "2026-10-31T15:00:00+00:00",
      "timezone": "UTC"
    },
    "rows": [
      {
        "detail": "2026-11-01T04:57:29+00:00 to 2026-11-01T14:29:05+00:00",
        "label": "/ · HTTP 502",
        "unit": "requests",
        "value": 28
      },
      {
        "detail": "2026-10-31T15:20:32+00:00 to 2026-11-01T02:15:59+00:00",
        "label": "/ai-analytics · HTTP 502",
        "unit": "requests",
        "value": 6
      }
    ],
    "scope": "own_site_selected_public_paths",
    "self_tests_excluded": false
  },
  "figure_caption": "Original explanatory workflow. Numeric callouts reproduce dated own-site evidence; they are not an AI platform test.",
  "figure_title": "Turn crawler analytics into an investigation handoff",
  "group": "Practical delivery",
  "human_review_claim": false,
  "intent": "analytics-action-handoff",
  "interpretation": "Keep observation, interpretation, proposed action and acceptance separate. The owner can confirm or reject the diagnosis without losing evidence. Priority should reflect both consequence and uncertainty.",
  "keyword_volume": "Not obtained",
  "limits": "A handoff is not proof of deployment or traffic improvement. Record those outcomes separately.",
  "path": "/ai-analytics/guides/analytics-action-handoff/",
  "policy": "analytics-evidence-v1",
  "problem": "A report should tell the next operator what to inspect and how to verify the result without inventing a root cause.",
  "product": "/ai-analytics",
  "published_at": "2026-11-01T17:33:16.659688+00:00",
  "reader": "Website owners, SEO analysts and site operators",
  "related": [
    "/learn/ai-crawler-logs-vs-ai-visibility/",
    "/research/ai-crawler-analytics/"
  ],
  "slug": "analytics-action-handoff",
  "source_signature": "eb280c89f8d015584757f83c33e50b77f34fe413e3ccfd8e5d3c3b4ce74e42a4",
  "sources": [
    {
      "hash": "54a7b1645b80ae3466689f04be544208ae7cba23239d2b80199317616123f92a",
      "locator": "paths",
      "observed_at": "2026-11-01T16:09:23+00:00",
      "title": "Saved own-site monitoring evidence",
      "url": "https://future-intech.com/research/ai-crawler-analytics/"
    }
  ],
  "sources_required": [],
  "steps": [
    "Record one condition with source, time, location and scope.",
    "State the supported inference and the missing evidence for a stronger conclusion.",
    "Assign a responsible role and a bounded action that role can perform.",
    "Define success, failure and unreproduced-history outcomes before implementation."
  ],
  "title": "Turn crawler analytics into an investigation handoff",
  "worked_example": "The public monitoring case links path errors to an investigation, not a claimed fix. Matching operational records are required before naming the cause."
}