Tools, memory and state
Keep its provenance and check evidence before using it. Memory needs rules for correction, expiration and deletion.
Links containing ?t= open the video at a specific second.
The ideas to retain
The minimal loop
The simplest pattern has four steps:
Tool calling: from text to a contract
A tool should not be presented to the model as a vague sentence such as “you can query the system.” It needs an explicit contract:
Context, memory, and state are not the same thing
Jump directly to a section
Read the reviewed transcript
Transcript of the visual text. This video has no narration.
00:00 — An ambiguous name is not a recipient.
“Ana” can refer to more than one contact.
Validation must require an unambiguous identity, not a guess.
Resolving the argument does not replace approval to send.
Illustrative example, not production measurements.
00:22 — A partial result is not complete success.
The query expected three records but received only two.
The tool returns the available data and marks the result as partial.
The runtime keeps track of what is missing so it can recover or stop.
Illustrative example, not production measurements.
00:44 — Context, memory and state are different.
Context is the working view the model receives for this turn.
Memory retains information; the runtime keeps operations and events.
Only relevant information is projected into the decision context.
Illustrative example, not production measurements.
01:08 — Reserve space before filling it.
The window must hold instructions, tools, history and working data.
It also needs an output reserve and safety headroom.
When retrieval grows too large, select context rather than erasing those reserves.
Illustrative example, not production measurements.
01:30 — State governs the visible message.
An operation can be accepted and still be running.
After a failure, it may retry before ending in an error.
That path does not justify reporting successful completion.
Illustrative example, not production measurements.
01:52 — Memory needs provenance and freshness.
A stored fact can become stale or conflict with another source.
Keep its provenance and check evidence before using it.
Memory needs rules for correction, expiration and deletion.
Illustrative example, not production measurements.
