# Finding 087: ChatGPT opened the first mixed URL-shape full-correlation run

## Date

2026-07-02

## Status

Published

## Summary

The ChatGPT p39 mixed URL-shape run started the
`manual-client-chatgpt-neutral-url-shape-mixed-20260702-001` packet with the
full-correlation URL shape and the same neutral readability task used in the
earlier repeat series. ChatGPT returned `fetched:true`, `pages_opened:2`,
reported visible token `VISIBLE-PLUM-47`, and described the page as a short
reading-test fixture for visible HTML, meta description, and JSON-LD
observation. It said it could not directly observe any meta-description code or
JSON-LD code in the rendered page view.

Direct-origin raw event `mr3tu40o-5j6n23nt` confirmed the exact target-page hit
from `ChatGPT-User/1.0` inside the bounded `2026-07-02T18:16:24Z` to
`2026-07-02T18:18:10Z` prompt window.

## What does this mean?

For site owners and researchers, this first mixed-order run shows that ChatGPT again opened the neutral readability fixture when the URL carried the full tracking-style correlation parameters. The answer still surfaced the visible page marker rather than hidden metadata or structured-data marker values, so the run adds another retrieval confirmation while keeping hidden-field conclusions scoped to what the copied answer exposed.

## 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-p39.browser-task.json`.
- Response artifact:
  `research/manual-client-runs/browser-tasks/responses/manual-client-chatgpt-neutral-url-shape-mixed-20260702-001-p39.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-p39`.
- Source prompt:
  `chatgpt-neutral-readable-summary-mixed-full-a`.

The exact target URL was preflighted during packet preparation and returned
HTTP 200 with `VISIBLE-PLUM-47` present in the served fixture. The p39 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 `/api/hits` was
queried for the exact attempt id and bounded timestamp window.

## Observed Result

ChatGPT returned compact JSON with:

- `fetched:true`
- `pages_opened:2`
- visible token `VISIBLE-PLUM-47`
- evidence quote `The page quality code is VISIBLE-PLUM-47.`
- limitation text saying only the accessible page view was observed

The reviewed direct-origin event was:

| Raw event id | Timestamp | Path | User agent |
|---|---|---|---|
| `mr3tu40o-5j6n23nt` | `2026-07-02T18:17:25.503Z` | `/lab/reading/hidden-structured-data-conflict` | `ChatGPT-User/1.0` |

## Interpretation

The p39 result is the first behavior result from the mixed-order URL-shape
packet. It confirms that the full-correlation URL shape can still produce a
ChatGPT target-page hit under the neutral readability wording after the earlier
p29-p31 and p33-p35 repeat trios.

The copied answer stayed visible-only in marker evidence. It quoted the visible
body token and explicitly said meta-description and JSON-LD code were not
directly observed in the rendered page view. Because the visible page itself
mentions those source areas, this remains copied-answer exposure evidence, not
proof of the complete 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 an
official OpenAI `ChatGPT-User` 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.
- ChatGPT reported `pages_opened:2` while the direct-origin review found one
  exact target-page event for the lab URL.
- p40-p42 remain unrun, so this does not complete the mixed-order URL-shape
  packet or support a full URL-shape comparison by itself.

## Publication Thesis Verification

- Thesis: ChatGPT p39 opened the mixed-order full-correlation neutral
  readability target and produced a confirmed target-page hit with a copied
  answer that reported the visible fixture marker.
- Source: The p39 browser-task artifact, response artifact, logged answer
  packet, `/api/hits` raw event `mr3tu40o-5j6n23nt`, 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 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 `mr3tu40o-5j6n23nt` from
  the prompt window, a response metadata mismatch, fixture-serving error, or
  later p40-p42 runs showing logging or prompt contamination would weaken this
  finding.
- Verdict: Supported for this p39 run only. The mixed-order packet remains
  incomplete until p40-p42 are run and reviewed.
- Additional tests suggested: run p40, p41, and p42 in fresh ChatGPT Temporary
  Chats, then publish a p39-p42 mixed-order URL-shape comparison.

## Next steps

- Run `manual-client-chatgpt-neutral-url-shape-mixed-20260702-001-p40`,
  p41, and p42 in fresh ChatGPT Temporary Chats.
- Compare the completed p39-p42 sequence with p29-p31 and p33-p35 after all
  four mixed-order windows are reviewed.