THE CONNECTED RECORD
Ask
the work.
Find the question. Follow the work. Return to the source.
4 THREAD · 4 SYSTEMS · 31 NOTEBOOK ENTRIES · 2 QUESTIONS · 242 FILMS · 239 CHAPTERS
Search the authored text, its questions and refusals, and the films around it. Drafts keep their status. Chapters identify a topic and a time; only the 2 indexed transcripts provide spoken passages, and their automatic captions are unreviewed. This edition retrieves sources rather than generating an answer. Explore what is connected ↗
3 RESULTS FOR “The site was there. The agent never saw it.”
PUBLISHED RECORD · SUPPORTED · V1.1
The site was there. The agent never saw it. ↗
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.
ORIGINAL SOURCE ↗PUBLISHED RECORD · SUPPORTED · V1.1
The site was there. The agent never saw it. / observation ↗
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.
ORIGINAL SOURCE ↗PUBLISHED RECORD · PARTIALLY SUPPORTED · V1.0
It wrote the right address. Only the link was opened. / observation ↗
THE PAGE WAS GIVEN THIS TIME. In the discovery experiment, the agents never saw the site. This time ChatGPT was given the page. The question was smaller: once a page tells an agent where to go next, does it get there? Each trial used a fresh, unguessable path prefix on one host. The index page said the access code was not there and to open code/heron/, relative to the page. The server computed the code for each prefix at request time, so the exact code required a request for that trial's code page.
ORIGINAL SOURCE ↗