{
  "answer": "Post-deployment evidence includes TLS and redirect behavior, response headers, content types, caching, compression, error handling, protected-path denial, body hashes, route reachability, uptime windows, incidents, and repeated external observations. The release package alone cannot establish those live-host properties.",
  "canonicalUrl": "https://xn--mwe.com/questions/what-evidence-remains-after-deployment/",
  "claimStatus": "PROJECT TECHNICAL PROPOSAL",
  "correctionStatus": "CURRENT K05 RELEASE",
  "id": "K01-ANSWER-072",
  "lastReviewed": "2026-08-16",
  "question": "What evidence is still required after a static release is deployed?",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "shortAnswer": "Post-deployment evidence includes TLS and redirect behavior, response headers, content types, caching, compression, error handling, protected-path denial, body hashes, route reachability, uptime windows, incidents, and repeated external observations. The release package alone cannot establish those live-host properties.",
  "slug": "what-evidence-remains-after-deployment",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "status": "PROJECT TECHNICAL PROPOSAL",
  "topic": "evidence-provenance",
  "type": "Question"
}