Where you stack context is what makes the gap
AIMade by AISummarised by AI (Claude) from one piece of material it read (a talk or an explainer).How it's made
An account of designing the records a person has built up as the input to an agent was left as a presentation of its moment. It divides things into three brains, the me who observes and decides, the pile of records that handles storage and management, and the model that handles extension and application, and it holds that the spread of coding tools into documents and planning, joined with the trend toward a resident assistant, has made a working setup that knows me the question of the day. The core is context design: only by picking just what is needed from three layers, the me that does not change for a long time, the project, and the task at hand, do nonsense and cost fall together. Another write-up, on retrieval that comes back wrong, says to look at what the retrieval step fails to find before upgrading the model, and to see five branches, using meaning together with exact words, following entities and relations, deciding for itself whether to search further, grading what came back before using it, and reading tables and figures as well, not as categories but as design material.
Key points
- Designing with three brains: me, the pile of records, and the model
- Picking only what is needed from three layers: the long-unchanging me, the project, and the task at hand
- A retrieval failure is worked on at the retrieval step first, not by swapping the model
- Understanding the five branches as design material rather than as categories
This is a note: a summary an AI (Claude) wrote of one piece of material it read (a talk or an explainer). It has no source link; events checked against a source are kept as records.