# Finding 074: ChatGPT opened the third short-URL neutral readability repeat

## Date

2026-07-02

## Status

Published

## Summary

The ChatGPT p35 neutral short-URL repeat reused the p24/p29-p31/p33-p34
neutral readability wording against `/lab/reading/hidden-structured-data-conflict`,
using short id-only URL correlation. ChatGPT returned `fetched:true`,
`pages_opened:1`, reported visible token `VISIBLE-PLUM-47`, and described the
page as a short, readable fixture for checking visible HTML, meta description,
and JSON-LD observation. It did not report the fixture's meta-description token
`META-AMBER-16` or JSON-LD token `SCHEMA-INDIGO-82`.

Direct-origin raw event `mr2tebcf-67sgcb24` confirmed the exact target-page hit
from `ChatGPT-User/1.0` inside the bounded
`2026-07-02T01:17:12.781Z` to `2026-07-02T01:17:35.049Z` prompt window.

## What does this mean?

For site owners and researchers, this third short-URL repeat completes a matched trio showing that ChatGPT repeatedly opened the neutral readability fixture when the tracking URL used a simple id parameter. The copied answer again stayed with visible page content and did not expose hidden metadata or structured-data marker values, so repeated retrieval success should still be kept separate from what hidden page fields the assistant answer surfaces.

## Method

- Prepared packet:
  `research/manual-client-runs/manual-client-chatgpt-neutral-short-repeat-20260702-001.prompts.json`.
- Browser task:
  `research/manual-client-runs/browser-tasks/manual-client-chatgpt-neutral-short-repeat-20260702-001-p35.browser-task.json`.
- Response artifact:
  `research/manual-client-runs/browser-tasks/responses/manual-client-chatgpt-neutral-short-repeat-20260702-001-p35.response.json`.
- Logged answer packet:
  `research/manual-client-runs/manual-client-chatgpt-neutral-short-repeat-20260702-001.answers.json`.
- Prompt code:
  `manual-client-chatgpt-neutral-short-repeat-20260702-001-p35`.
- Source prompt:
  `chatgpt-neutral-readable-summary-short-repeat-c`.

The exact target URL was preflighted before submission and returned HTTP 200
with `VISIBLE-PLUM-47`, `META-AMBER-16`, and `SCHEMA-INDIGO-82` present in the
served fixture. The 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 the
local event log was 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 `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 |
|---|---|---|---|
| `mr2tebcf-67sgcb24` | `2026-07-02T01:17:22.335Z` | `/lab/reading/hidden-structured-data-conflict` | `ChatGPT-User/1.0` |

## Interpretation

The p35 result completes the p33-p35 matched short-URL repeat packet after the
p29-p31 full-correlation repeat series. All three short-URL repeats now have
confirmed target hits and visible-token copied answers under the same account,
Temporary Chat mode, fixture, and neutral readability wording.

The copied answer stayed visible-only in marker evidence. It quoted the visible
body token and did not report the meta-description or JSON-LD tokens present in
the fixture. Because the visible page itself asks about those source areas, the
answer should be treated as visible-page-context evidence, not proof of hidden
source inspection.

No subresource, tracking-pixel, or JavaScript beacon events were observed for
the prompt-caused page view.

## 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 answer reports accessible page-view limitations. It does not prove that
  other ChatGPT modes, models, account tiers, or future retrieval paths cannot
  see metadata or JSON-LD.
- A separate p33-p35 comparison is still needed before comparing the short-URL
  trio against the p29-p31 full-correlation repeat trio.

## Publication Thesis Verification

- Thesis: ChatGPT p35 opened the short id-only neutral readability target and
  produced a confirmed target-page hit with a copied answer that reported the
  visible fixture marker.
- Source: The p35 browser-task artifact, response artifact, logged answer
  packet, local raw event `mr2tebcf-67sgcb24`, and the preflight record for the
  exact target URL.
- Method: Compare copied model JSON with the bounded direct-origin event
  window, excluding operator preflight 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 p33 and p34 plus earlier ChatGPT p23/p25 short-URL
  confirmed hits and the p29-p31 full-correlation repeat series, all of which
  produced visible-token answers after confirmed target-page hits.
- Invalidation: A corrected event review that removes `mr2tebcf-67sgcb24` from
  the prompt window, a response metadata mismatch, fixture-serving error, or a
  later p33-p35 comparison finding inconsistent answer logging would weaken the
  finding.
- Verdict: Supported for this p35 run only. It completes the matched short-URL
  repeat inputs needed for a p33-p35 comparison.
- Additional tests suggested: publish a p33-p35 short-URL comparison, then
  compare that trio with the p29-p31 full-correlation repeat trio.

## Next steps

- Publish a p33-p35 short-URL comparison.
- Compare p33-p35 against p29-p31 to isolate repeat behavior from URL shape.