THE CONNECTED RECORD
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 “Context should be abundant.”
EDITORIAL DRAFT · OPEN · V0.1
An open notebook proposition: repeatedly reconstructing earlier state may be one reason context feels scarce. Indexing reusable state is a question to investigate, not an established saving.
READ THIS DRAFT ↗EDITORIAL DRAFT / STATEMENT · OPEN · V0.1
Context is treated as expensive because we repeatedly reconstruct it.
READ THIS DRAFT ↗EDITORIAL DRAFT / CONNECTION · OPEN · V0.1
Retirement turned out to be the mechanism rather than the optimisation, and addressing rather than traversal turned out to be the bottleneck. Both point at the same engineering question the software has been circling: which operations should a model be asked to perform, and which belong to an index outside it.. LARQL / querying learned systems. VINDEX3 / the representation. What has to survive?. Context should be abundant
READ THIS DRAFT ↗