Objectives, Not Instructions: How Gemini's Four-Layer Memory Changes the Agent Contract
Google frames the Gemini agent as a shift in the unit of delegation: instead of issuing step-by-step prompts, a user hands it an objective and returns to finished work. Kurian put it directly: 'You give it objectives, not instructions. You delegate an outcome and come back to finished work' [1]. What makes that possible is a four-layer memory system - session memory for the task at hand even if it runs for days, semantic memory built from documents and conversations, procedural memory for skills the agent writes for itself, and episodic memory of everything it has done before [1]. To handle genuinely multi-step work, Gemini does not operate as a single thread - it spins up temporary, job-specific sub-agents, each with its own identity, and a manager can even spawn a named agent with its own Workspace account, Gmail address, calendar, and Drive storage [2]. That is a meaningful departure from a chatbot-style assistant: the agent is architected to behave like a small, disposable team rather than one responder.



