Result

AIHackers has five known legacy routes in this recovery cluster:

  • four have concrete captures with recoverable bodies;
  • one has no located archived body and remains unresolved / memory-only.

The four concrete snapshots below replayed as 200 text/html on July 25, 2026. A fresh CDX query returned an intermittent 503 for one protocol variant and a timeout for another; successful variant results and direct replay preserve the validated status.

Authoritative ledger

Legacy routeConcrete capture in UTCReplayPreservation statusWhat the artifact provesFinal canonical
/2023/04/04/the-20-minute-blog/2023-07-22 18:52:54 UTC200 text/htmlvalidatedBody and metadata record ChatGPT prompts, Midjourney images, ZimmWriter with text-davinci-003, about 2,499 words, a 20-minute target, “18 minutes left,” and a 33-minute result/posts/20-minute-blog-archaeological-update/
/2023/04/04/the-fortune-telling-cyborg-how-ai-is-revolutionizing-divination/2023-04-11 17:45:50 UTC200 text/htmlvalidatedBody and media metadata for the April 4 divination article/posts/vibe-coding-trenches-2023-2026-retrospective/
/2023/04/04/the-top-10-ai-technologies-to-watch-in-2023/2023-04-11 09:57:08 UTC200 text/htmlvalidatedBody and media metadata for the dated technology list/posts/vibe-coding-trenches-2023-2026-retrospective/
/2023/04/05/10-game-changing-ai-chatbot-plugins-that-will-change-your-life-forever/2023-05-15 02:48:35 UTC200 text/htmlvalidatedBody, tool metadata, and media metadata for the plugin-era article/posts/vibe-coding-trenches-2023-2026-retrospective/
/building-an-ai-empire-from-scratch-a-conversation-with-chatgpt/No concrete capture foundNo body to replayunresolved / memory-only bodyThe archive proves nothing about the body; route continuity comes from the site’s redirect/remediation record/posts/vibe-coding-trenches-2023-2026-retrospective/

The earlier 2023-04-11 10:50:07 UTC capture of the 20-minute page also replayed as 200 text/html on July 25, 2026.

Method

The July 25 validation used this bounded order:

  1. exact HTTPS CDX lookup;
  2. exact HTTP protocol variant;
  3. parent-path wildcard fallback filtered to the target slug when exact results had no 200 text/html;
  4. direct id_ replay of every cited concrete capture.

The query window was 2023–2026. Direct snapshots, not wildcard lookup screens, are the public evidence.

For the “AI Empire” route, exact HTTPS, protocol variant, and bounded fallback produced no 200 text/html capture. Its body remains unresolved. This ledger will not infer contents from the title or redirect destination.

Confidence and preservation are separate

The ledger is high confidence for capture timestamps and replay results. Overall preservation is partial because the fifth body is unresolved.

Those labels do not endorse every statement inside an archived article. The artifacts prove what the site published and what its metadata recorded; they do not convert historical claims into verified facts.

Redirect and SEO boundary

The five known legacy routes have exact one-hop redirect mappings. Two redundant 2026 recovery pages also redirect to the surviving retrospective. Unknown year paths are intentionally not redirected to a generic essay.

Search rankings, traffic, backlinks, authority, and recovered SEO equity are unmeasured. IndexNow or sitemap submission records delivery requests, not crawling or indexing.