{
  "acceptance": "A reviewer can trace each displayed count to the saved window, identify the responsible layer only when evidence supports it, and distinguish a successful recheck from continued monitored recovery.",
  "automated_checks": true,
  "built_at": "2026-11-01T18:10:07.393025+00:00",
  "description": "A dated own-site case of gateway response failed, with affected public paths, retained request counts and a bounded investigation handoff.",
  "diagram": [
    "Locate saved response window",
    "Inspect matching service evidence",
    "Make a scoped verified change",
    "Record later 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 investigation workflow with real counts from the dated window. This is not a screenshot or a measured AI platform result.",
  "figure_title": "Saved HTTP 502 access evidence",
  "group": "Observed access cases",
  "human_review_claim": false,
  "intent": "own-site-case-http-502",
  "interpretation": "Correlate the affected interval with proxy upstream errors and application availability. The case establishes the response condition in the saved source, not a verified root cause or measured impact on AI recommendations.",
  "keyword_volume": "Not obtained",
  "limits": "The response does not establish whether the proxy, upstream application or a deployment caused the failure. Original AI answers, citations, customer losses and search effects were not measured.",
  "path": "/ai-analytics/guides/future-intech-502-access-evidence/",
  "policy": "analytics-evidence-v1",
  "problem": "A retained response condition needs an evidence-based investigation.",
  "product": "/ai-analytics",
  "published_at": "2026-11-02T09:50:01.500630+00:00",
  "reader": "Site operators reviewing the documented incident",
  "related": [
    "/ai-analytics/guides/ai-crawler-502-investigation/"
  ],
  "required_status": 502,
  "slug": "future-intech-502-access-evidence",
  "source_signature": "d48ad588b81411b536926980dca258d7998adf5c246a0f77b66115e2ce759c0e",
  "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": [
    "Preserve this edition, the affected paths and the first and last observed timestamps before investigating.",
    "Correlate the affected interval with proxy upstream errors and application availability.",
    "Record whether matching operational evidence supports a cause. If not, leave the cause unresolved and identify the missing record.",
    "After an authorized change, retain a dated public response and a later complete observation window. Keep the original failure evidence intact."
  ],
  "title": "A saved HTTP 502 window on Future InTech: evidence and next checks",
  "worked_example": "The table lists only the HTTP 502 windows that qualified this case. These are requests, not affected people. Some requests can be our own checks. Use the exact intervals to locate supporting operational records rather than treating the aggregate as a complete incident trace."
}