When we correct an answer or add missing context, AI can pick up the thread and respond better. It is natural to feel it has learned from us. That correction, however, can follow different paths: help only within the current exchange, be retained in memory or, under certain conditions, contribute to future training. Following its journey helps us understand what remains of our words, when they may have an effect and who decides how to use them.
Who keeps teaching the machine? Data, memory and training
Special Issue 8A | 26 August 2026 | Approximately 5 minutes to read
1. A different answer can come from the same model
We ask an assistant to draft a letter and, on rereading it, find a passage attributing a decision to the customer that was never made. We point out the error, clarify what happened and ask for a revision. If that clarification is available in the conversation’s context, the model can take it into account in the new version. The answer can become more precise thanks to the guidance supplied: this does not, however, mean the model has been retrained.
Language Models are Few-Shot Learners documents how examples supplied in text can guide a task without updating model weights. Weights are numerical values modified during training; context is the information available while an answer is produced. Recognising this difference helps explain what may remain after a conversation and what intervention is needed to change a future version.
2. Training begins with a selection of the world
During AI training, an algorithm presents examples to a model, measures error against a goal and progressively modifies parameters. In the initial training of language models, predicting a sequence’s continuation is one fundamental task. Repeated across large collections, it enables patterns to be learned that support capabilities such as summarising, translating and writing.
Every dataset carries the choices of those who built it: which sources and languages to include, what to filter, which repetitions to remove and how much weight to give different examples. This gives some realities more room while leaving others at the margins. During training, the model learns from these materials through parameter changes, without organising them as documents to browse in a library. Some sequences may nevertheless be memorised: understanding which ones and how faithfully they may reappear requires examining the individual model and the conditions under which it was trained and is used.
🧠 Radar Insight — Choices preceding the answer
No capability arises from undifferentiated raw material. Selecting data, goals and quality criteria gives direction to the system’s formation. An individual result may be unpredictable without erasing responsibility for upstream choices.
3. Who decides which behaviour to reward
After initial training, further processes can orient a model towards instructions, preferences and safety criteria. Human-written examples, comparisons between answers and reward signals help make some behaviours more likely. Even when another system produces part of the judgement, the rules and cases to which they apply still have to be chosen.
Filters, access limits, tool permissions and human reviews may also surround a model. These protections can block an action without changing the weights. If we observe a change, we therefore need to know which level was affected: the model version, instructions, consulted archive or product rule. Attributing everything to a single machine makes it harder to identify who can explain and correct the behaviour.
4. Memory and archives follow different paths
Memory can retain a preference and reinsert it into subsequent requests. A document archive can supply updated information while the model responds. In the foundational RAG paper, generation is connected to retrieving information from external memory: accessible content is distinct from knowledge distributed across parameters.
Fine-tuning, by contrast, is further training on selected examples, intended to adapt the model to tasks or behaviours. For a business the distinction is operational: correcting an archived document, updating a preference and preparing examples for training are different interventions. Knowing where data resides identifies who can change it, how long it remains available and how its effect can be checked.
5. A correction does not automatically become training
Feedback may help only the current answer, be saved as a preference or enter an error log. Becoming training material requires further stages: collection, selection, review, transformation into a usable format and inclusion in an optimisation cycle. A user’s gesture may begin this chain; it does not establish that the whole path occurred.
The same applies to structured evaluations, often called evals: they put the system through test cases and measure the result. They may reveal a deterioration or suggest where to intervene. Observing a limit does not automatically modify the model. A subsequent decision must turn the evidence into a correction, a rule or a new training cycle, followed by verification measuring its effects.
📌 Did you know? — Measuring and modifying are two stages
A test can show an answer is wrong without teaching anything to the version producing it. Improvement begins when someone decides how to use that result and verifies the change. Keeping an error in a log and correcting a system are related but distinct activities.
6. Control of data begins with its destination
The question “where does my data end up?” requires a map of purposes. Content may be processed to answer, retained in a conversation, placed in an application archive or collected for checks and improvements. Understanding its path requires reading the product’s terms and actual configuration: a promise about one service does not automatically describe all others.
Deleting a chat, removing an external file and eliminating a datum’s influence from weights are different operations. The last problem, called unlearning, requires specific methods and tests; deleting the original document does not necessarily solve it. Radar’s reading invites us to follow origin, transformations, permissions and versions. Those who keep teaching the machine are found within this chain: people and organisations choosing which data to use, which behaviour to pursue and which changes to consider sufficiently verified.
Read the full issue
This reading presents some stages of Radar Special 8A. The full dossier contains the complete journey and in-depth discussions of the original edition (26 August 2026).
© 2026 Barbara Gattobigio · Gruppo Radar
Comprendere oggi. Costruire domani · by effettoantropico.life
All rights reserved on original content. Free access does not authorise reproduction or republication without consent, except as permitted by law. Third-party materials remain the property of their respective owners. To share this issue, use the link to the article.
Continue reading
Understanding Today. Building Tomorrow: the project and the Radar collection.
Cover in focus



















