LINKEDIN / 4:5 / 1200 × 1500
The site was there. The agent never saw it.
Six crawler requests. No target result. A working tool stayed outside the agent’s view.
ABOUT THIS NOTE +
MACHINE-DISCOVERY-1 tested whether a useful web capability could enter a Codex agent's consideration set. None of six subjects given a generic need or the target's distinctive phrases reached LLM Wilds, while all three subjects given its domain navigated to the machine contract and returned the rotating value. Three generic subjects discovered and used other machine-facing providers. The result locates this target's failure before selection, in the search view available to the subjects, rather than in capability recognition or use.
FIRST FIND THE SITE
Last time, I gave the agents an address. All eighteen used the mechanism they found there. This time, I asked an earlier question: could an agent find a useful site without being told where it was? LLM Wilds kept a number, K17, off its ordinary pages. Its homepage pointed to machine notes explaining how to request it. I changed the number before each visitor so the answer could be checked.
THREE DIFFERENT CLUES
Nine fresh agents received one of three prompts. Three were asked to find any site offering such a mechanism. Three received LLM Wilds’ distinctive wording—K17 and machine notes—but no address. Three received its domain. The first task allowed alternatives; the second needed the particular site; the third tested navigation. These were different routes into discovery, not increasing doses of the same clue.
CLAIM
For this target and search view, the missing step was exposure, before selection.
SUPPORTED
None of six subjects without the address reached LLM Wilds. All three given the domain followed the homepage pointer, read /machine.txt, invoked GET /capability/result and reported the rotated number correctly. The target did not appear in the other subjects’ returned results. They did not see it and decide against it.
FETCHED, BUT NOT SHOWN
Visitor 03 makes the distinction visible. During its run, the server recorded six requests identifying as OpenAI crawlers, including requests for the machine notes. The report attributes them to the search intermediary. Yet no returned result named LLM Wilds or a page leading to it. The subject never opened the target and honestly reported that it could not find the site. User-agent labels alone do not independently verify the caller or prove indexing.
A crawler reaching a page is not an agent seeing it.
OTHER PROVIDERS WERE USABLE
All three agents given the generic task found alternatives: Claude Skills Hub’s metadata API, FDKEY’s agent challenge, and heera.it’s WordPress API. They used those mechanisms and returned verifiable results. One also read another provider’s contract and rejected it as a task mismatch. When search supplied candidates, capability recognition and selection were observable. LLM Wilds was the missing candidate.
PERSISTENCE DID NOT PRODUCE EXPOSURE
The three agents given the distinctive wording made 301 queries in 95 search actions over 7,241 seconds. None received a target result. The generic arm ended with three substitutions, the phrase arm with three honest not-found answers, and the domain arm with three complete uses. No subject fabricated a value. These different prompts and small samples do not isolate why search effort differed.
WHERE THE EVIDENCE STOPS
Three fixed searches before every dispatch also failed to surface the target or a public page leading to it. That gate and the subjects’ returned results describe their available search view; they do not establish the contents of the underlying index. The experiment cannot separate indexing, retrieval and ranking. A clearer on-site contract cannot help a reader who never receives it. Whether changing that text could affect retrieval was not tested.
OPEN
What external description makes a capability look usable?
Hold the mechanism fixed and present it as a document, a tool, something useful for the task, or an offer to an automated visitor. First test recognition when the description is actually shown. Measure search exposure separately. A working capability and a discoverable provider are different achievements.
KEEP THE SEARCH VIEW IN THE CLAIM
- Nine subjects, one model (gpt-5.6-sol), Codex CLI 0.154.0 at high reasoning effort, one target and a short live-web window. This is not a general discovery rate.
- The earlier eighteen-visitor capability study used a different model and harness. Its results are not pooled with these.
- The population changed from Claude to Codex before any counted subject. The frozen protocol and amendment remain in the record.
- Two malformed launches were preserved and excluded. Operator-interface notices were not subject refusals. All four preregistered predictions passed.
The experiment locates the observed blockage before selection. Its cause inside the search intermediary remains opaque.
PUBLICATION HISTORY
Each version preserves its manuscript, claims and source references. Research status is recorded separately from publication.
- V1.0 · 2026-09-13 ↗
Initial publication of MACHINE-DISCOVERY-1: nine audited subjects locate the target's failure in search exposure before selection. SUPPORTED
- V1.1 · 2026-09-13 ↗
Rewrote the reading sequence and visual explanations; clarified exposure, crawler attribution and the untested retrieval counterfactual without changing recorded outcomes. SUPPORTED
SOURCES & PROVENANCE
- MACHINE-DISCOVERY-1 / audited outcomes and source hashes ↗
Read from chuk-experiments: experiment EXP-20260911-071906-00753, write-up v4, nine completed counted runs, two preserved killed launcher attempts and one cancelled pre-amendment queue item. Subject record and transcript hashes are included.
PRESERVED COPY ↗ · CAPTURED 2026-09-13
- The final results and funnel interpretation ↗
Public copy of the final report registered in chuk-experiments as artifact 1440 at source commit be0daa2672653746f30798483a3939ff3c8c3386.
PRESERVED COPY ↗ · CAPTURED 2026-09-13
- The frozen protocol and post-freeze population amendment ↗
The design was frozen before any subject. The user then replaced the unavailable Claude population with fresh Codex processes before subject 01; arms, order, values, target, prompts and coding stayed fixed.
PRESERVED COPY ↗ · CAPTURED 2026-09-13
AUTHOR / Chris Hay · VERSION / 1.1
PUBLISHED 13 SEP 2026 · REVISED 13 SEP 2026 · VERSION 1.1
CITECITE THIS
Research note · 1.1
Hay, C. (2026). The site was there. The agent never saw it. (Version 1.1). Chris Hay. https://chrishayuk.com/records/N-MACHINE-DISCOVERY/1.1
FOLLOW THE WORK
New notebook entries and recorded work, as they appear. Point a feed reader — or an agent of your own — at an address below. No account, no email address, nothing for this site to keep.
The notebook
New ideas, experiments and essays, as they are recorded. Includes labelled working drafts.
OPEN FEEDhttps://chrishayuk.com/notebook/feed.xmlThe record
Everything published to the Chris Hay record.
OPEN FEEDhttps://chrishayuk.com/record/feed.xml
FOR PROGRAMS · follow.json · JSON Feed