Google’s AI Mode appears to rely on a proprietary content store rather than fetching live web content during searches. A recent test revealed a significant inconsistency: a page that had been deleted and re-indexed still returned a 404 error when accessed through AI Mode, even though it was listed in Google’s search results. This contradicts the common assumption that indexed pages should be accessible via AI Mode. The testing process involved deleting a specific page and confirming its absence with a 404 error. After restoring the page, a second fetch still resulted in a 404, despite the page being indexed. This unexpected outcome raises questions about how Google’s AI Mode interacts with the search index and what criteria are used to pull content. The author is inviting others to replicate this test to gather more data on the issue. The article also touches on technical aspects related to Linux container configurations, memory limits, and CPU quotas. It includes code snippets that illustrate the use of system files and directories, emphasizing the intricacies of managing resources in a controlled environment. The mention of potential errors in AI responses serves as a caution for users relying on automated outputs.