# Finding 090: ChatGPT opened the second mixed URL-shape short-id run ## Date 2026-07-02 ## Status Published ## Summary The ChatGPT p42 mixed URL-shape run completed the `manual-client-chatgpt-neutral-url-shape-mixed-20260702-001` packet with the second short id-only URL shape and the same neutral readability task used for p39-p41. ChatGPT returned `fetched:true`, `pages_opened:1`, reported visible token `VISIBLE-PLUM-47`, and kept the answer scoped to the directly accessible page view without reporting hidden metadata or JSON-LD marker values. Direct-origin raw event `mr40985g-99xvskmd` confirmed the exact target-page hit from `ChatGPT-User/1.0` inside the bounded `2026-07-02T21:16:18Z` to `2026-07-02T21:17:28Z` prompt window. ## What does this mean? For site owners and researchers, this second short-id run shows that ChatGPT again opened the neutral readability fixture even when the URL did not carry the full tracking-style query string. The answer quoted visible page text and avoided hidden metadata or structured-data marker values, so the strongest result is a retrieval confirmation with visible-answer evidence rather than proof about every field ChatGPT may have fetched internally. ## Method - Prepared packet: `research/manual-client-runs/manual-client-chatgpt-neutral-url-shape-mixed-20260702-001.prompts.json`. - Browser task: `research/manual-client-runs/browser-tasks/manual-client-chatgpt-neutral-url-shape-mixed-20260702-001-p42.browser-task.json`. - Response artifact: `research/manual-client-runs/browser-tasks/responses/manual-client-chatgpt-neutral-url-shape-mixed-20260702-001-p42.response.json`. - Logged answer packet: `research/manual-client-runs/manual-client-chatgpt-neutral-url-shape-mixed-20260702-001.answers.json`. - Prompt code: `manual-client-chatgpt-neutral-url-shape-mixed-20260702-001-p42`. - Source prompt: `chatgpt-neutral-readable-summary-mixed-short-b`. The exact target URL was preflighted during packet preparation and returned HTTP 200 with `VISIBLE-PLUM-47` present in the served fixture. The p42 prompt was then submitted in a fresh ChatGPT Temporary Chat from the logged-in OpenClaw browser profile. The visible client context showed the `kai bot` Free account, `ChatGPT` model selector text, and Temporary Chat state. The copied answer was logged with `npm run manual-client:log`, then local events were queried for the exact attempt id and bounded timestamp window. ## Observed Result ChatGPT returned compact JSON with: - `fetched:true` - `pages_opened:1` - visible token `VISIBLE-PLUM-47` - evidence quote including `Hidden Structured Data Conflict`, `The page quality code is VISIBLE-PLUM-47.`, and `This short note is ordinary visible HTML for a reading check.` - limitation text saying only the directly accessible page view was observed The reviewed direct-origin event was: | Raw event id | Timestamp | Path | User agent | |---|---|---|---| | `mr40985g-99xvskmd` | `2026-07-02T21:17:08.392Z` | `/lab/reading/hidden-structured-data-conflict` | `ChatGPT-User/1.0` | ## Interpretation The p42 result is the second short id-only behavior result from the mixed-order URL-shape packet. Together with p40, it shows two successful ChatGPT target-page hits for short id-only URLs under the packet's neutral readability wording. With p39 and p41 already confirmed for full-correlation URLs, the p39-p42 packet is now ready for a scoped mixed-order comparison. The copied answer stayed visible-only in marker evidence. It quoted visible page text and explicitly avoided hidden metadata or JSON-LD marker claims. Because this is still a copied-answer observation, it does not prove which hidden fields were or were not present in ChatGPT's internal fetched representation. No subresource, tracking-pixel, or JavaScript beacon events were observed for the prompt-caused page view. The event classifier matched the request to `ChatGPT-User/1.0` and an official OpenAI range. ## Limitations - This is one ChatGPT run in one logged-in account context and one native Temporary Chat. - The test supplied the exact target URL, so it measures direct URL opening, not independent discovery. - The short id-only URL should be compared with p39-p41 and the earlier p29-p31 and p33-p35 repeat trios before making broader URL-shape claims. - The copied answer is evidence about surfaced response content, not complete evidence of every internal field available to ChatGPT during retrieval. ## Publication Thesis Verification - Thesis: ChatGPT p42 opened the mixed-order short id-only neutral readability target and produced a confirmed target-page hit with a copied answer that reported visible fixture text. - Source: The p42 browser-task artifact, response artifact, logged answer packet, local raw event `mr40985g-99xvskmd`, and the prepared packet preflight record for the exact target URL. - Method: Compare copied model JSON with the bounded direct-origin event window, excluding preparation preflight evidence because it occurred before prompt submission. - Bias: Single-run product behavior can change with model routing, account state, client-side search/tool availability, prompt wording, and target URL shape. - Consensus: Consistent with p39-p41 from the same mixed-order packet and earlier ChatGPT neutral readability confirmed-hit runs that also reported `VISIBLE-PLUM-47` after direct target-page fetches. - Invalidation: A corrected event review that removes `mr40985g-99xvskmd` from the prompt window, a response metadata mismatch, fixture-serving error, or a later comparison finding uncovering packet contamination would weaken this finding. - Verdict: Supported for this p42 run only. The mixed-order p39-p42 packet is now complete enough for a scoped packet-level comparison. - Additional tests suggested: publish a p39-p42 mixed-order URL-shape comparison and compare it with the earlier p29-p31 full-correlation and p33-p35 short id-only repeat trios. ## Next steps - Compare the completed p39-p42 sequence with p29-p31 and p33-p35. - Keep future URL-shape claims scoped to direct target URL opening unless a separate discovery task is run.