Scraps from various sources and my own writings on Generative AI, AGI, Digital, Disruption, Agile, Scrum, Kanban, Scaled Agile, XP, TDD, FDD, DevOps, Design Thinking, etc.
Page Hits
Wednesday, September 17, 2025
Friday, August 29, 2025
Friday, August 22, 2025
Friday, August 08, 2025
AI Agents Memory
𝗔𝗜 𝗔𝗴𝗲𝗻𝘁’𝘀 𝗠𝗲𝗺𝗼𝗿𝘆 is the most important piece of 𝗖𝗼𝗻𝘁𝗲𝘅𝘁 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴, this is how we define it 
In general, the memory for an agent is something that we provide via context in the prompt passed to LLM that helps the agent to better plan and react given past interactions or data not immediately available.
It is useful to group the memory into four types:
𝟭. 𝗘𝗽𝗶𝘀𝗼𝗱𝗶𝗰 - This type of memory contains past interactions and actions performed by the agent. After an action is taken, the application controlling the agent would store the action in some kind of persistent storage so that it can be retrieved later if needed. A good example would be using a vector Database to store semantic meaning of the interactions.
𝟮. 𝗦𝗲𝗺𝗮𝗻𝘁𝗶𝗰 - Any external information that is available to the agent and any knowledge the agent should have about itself. You can think of this as a context similar to one used in RAG applications. It can be internal knowledge only available to the agent or a grounding context to isolate part of the internet scale data for more accurate answers.
𝟯. 𝗣𝗿𝗼𝗰𝗲𝗱𝘂𝗿𝗮𝗹 - This is systemic information like the structure of the System Prompt, available tools, guardrails etc. It will usually be stored in Git, Prompt and Tool Registries.
𝟰. Occasionally, the agent application would pull information from long-term memory and store it locally if it is needed for the task at hand.
𝟱. All of the information pulled together from the long-term or stored in local memory is called short-term or working memory. Compiling all of it into a prompt will produce the prompt to be passed to the LLM and it will provide further actions to be taken by the system.
We usually label 1. - 3. as Long-Term memory and 5. as Short-Term memory.
#LLM #AI #ContextEngineering
Thursday, August 07, 2025
Google Genie 3 & where's it leading us to
1. Advancing “world models” for AI
AI agents need realistic, interactive environments to learn decision-making (e.g., how to navigate, manipulate objects, or plan actions).
Traditional simulators (like game engines) are hand-coded and slow to build. Genie 3 generates new, physics-aware environments instantly from text prompts.
This makes it useful for training AI at scale without needing human-designed levels.
---
2. Democratizing content creation
Currently, building a game or simulation requires coding, asset design, and engines.
Genie 3 removes that barrier by letting anyone type a prompt (“a forest at sunset with floating islands”) and get an explorable world in seconds.
This could lead to personalized games, educational tools, or VR simulations without technical skills.
---
3. Testing AI memory and reasoning
Genie 3 introduces visual memory (the AI remembers object placement for ~1 minute).
This allows researchers to study how AI handles continuity—a step toward agents that can remember and interact in more complex ways.
---
4. Faster experimentation for researchers and developers
Instead of waiting weeks for artists and engineers to design levels, researchers can spin up thousands of unique worlds for experiments, robotics planning, or reinforcement learning.
Potential applications: autonomous driving, robotics training, creative prototyping.
---
5. Laying groundwork for AI-generated entertainment
While not a finished product, Genie 3 hints at a future where games “write themselves” based on what you imagine.
Think: a Minecraft-like game that reshapes itself dynamically rather than relying on blocks or mods.
---
In short: Genie 3 solves the problem of rapidly generating rich, interactive worlds without manual effort, which is crucial for AI development and creative prototyping, not just gaming
Subscribe to:
Comments (Atom)
If we already have automation, what's the need for Agents?
“Automation” and “agent” sound similar — but they solve very different classes of problems. Automation = Fixed Instruction → Fixed Outcome ...
- 
Requirements Analysis -- Business requirements document or business requirements specification System Design -- Systems requireme...
 
 
 
