Where does an AI request go?

The source has three stages, Request, Secure hardware and Protected result. One stage is displayed at a time. Bars count three conceptual stages against zero actual service requests made by these controls, using one hundred fifty pixels per item. The protection language is attributed to the supplied post, not independently verified encryption, attestation or data handling. This page has no prompt submission, secure hardware connection or inference result service. The current stage is index zero, one or two. Clicking Next computes current plus one modulo three, so index two wraps to zero and the visible Stage three becomes Stage one. Bars use one hundred fifty pixels per index to compare index two and wrapped zero. This is a navigation cycle through fixed text, not the lifecycle of an actual AI request. The numeric index is saved locally; no data is protected by choosing a stage. One stage is visible but every downloaded text brief includes all three stage descriptions and the explicit not a live secure hardware integration boundary. Bars compare one displayed stage with three exported stages at one hundred fifty pixels per item. Reload restores the stored selection and Reset returns to the first stage. No private prompt, returned model answer, service logs or hardware evidence is retrieved. Downloading the brief verifies only the pages fixed text.