쉐도잉 연습: AI Agent Memory Architecture: Structured SQL, Semantic Vector Search & Memory Bank - 영상으로 영어 말하기 배우기

연습 모드 선택

각 모드는 전체 화면 연습실로 열립니다.

173 문장

문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.

Hi, I'm Annie.

If your agent can hear, see, and take action, the next question is, what should I remember after the session ends?

In this episode, I will show you the architecture for long -term memory in a multi -model agent,

facts in structure memory, understanding in semantic memory, and raw audio or video outside of memory.

Hi there.

Hey there.

Good for that customer dinner tomorrow

or just browsing oh i want

you suggest something for customer dinner tomorrow based on my wish list for sure you have those leather ankle boots

and a classic black pump on your list either would go great with

that red cocktail dress you bought but

if you want something a bit more relaxed for dinner maybe mix it up with the plaid button -up

and classic denim jeans all right let's start with the two types of the memory when you're talking to a multimodal agent.

It feels like the agent remembers everything.

It remembers what you said five minutes ago.

It can use what it just heard.

But most of that is short -term memory.

It is like RAM.

It is useful while the session is running, but it's gone when the session ends.

So the real design question is not, can we save everything?

The real question is, what is worth carrying into the next session?

And And that memory comes in two kinds.

The first kind is facts.

Facts are exact.

You have a dinner on Thursday.

You bought the blue jacket.

Those are things you can put in rows and columns.

They have IDs.

They have dates.

They can be created, updated, and deleted.

That is structured memory.

The second kind is understanding.

Understanding is not one clean role in a table.

It is an age in learning what something means about you.

You prefer simple over flashy, you run warm, you reach for dark colors when you want to feel confident.

That is not just a fact to look up.

That is a pattern.

It is a difference between knowing your calendar and knowing you.

So, here is the first takeaway.

Facts are exact.

You look them up.

Understanding is meaning.

You recall it.

Now let's talk about the decision that makes or breaks your memory system.

Those two kinds of memory should not live in the same place.

Facts belong in a structured database.

That usually means SQL, Postgres, MySQL, Cloud SQL, and Google Cloud whatever fits your stack.

Why SQL?

Because facts need exact answers.

If I ask what is on my calendar Thursday, I do not want a similar memory.

I want an exact event.

The database should return the actual roles.

That is what structured databases are good at.

Now, understanding belongs somewhere else.

Understanding stays in a vector store.

A vector store lets you search by meaning.

So instead of asking, find a role where preference equals dark colors,

the agent can ask, what do I know about any style preference for this kind of event?

And the memory system can bring back memories that are semantically related.

And that is the job of embeddings and vector search.

Here is an important detail.

VectorStore is a category.

It is not one specific product.

You could use PG Vector inside Postgres.

You could use AlloyDB.

On Google Cloud, one managed option is agent platform memory bank.

Memory bank is useful because it does more than store vectors.

You can read past sessions, extract useful memories, and update those memories over time so

if you use a plain vector store you usually build

that extraction logic yourself if you use memory bank

that part is managed for you

but the lesson is not you must use memory bank the lesson is understanding goes in a system

that can search by meaning now here's a mistake many people make they hear semantic memory

and they put everything into the vector store.

Facts, preferences, calendar events, everything.

That sounds simple, but it creates a real problem.

A vector store is designed for similarity.

Similarity is great when the question is fuzzy, but similarity is dangerous.

when the answer must be exact.

If the user asks, what did I buy?

The agent should not guess from a similar memory.

It should curate the database.

If the user asks, what do I usually like for dinners?

Then semantic memory makes sense.

That is a meaning -based question.

So the rule is, structured facts goes in database like Cloud SQL.

Unstructured understanding goes in a vector store.

And there is one more category people often forget, raw perception.

The camera frames, the audio waveform, the live stream itself, that does not usually belong in memory.

Your agent does not need to permanently remember every pixel or every sound wave.

It needs the meaning you extract from them.

For example, she is wearing that black hat again.

Or that you just said this dinner is formal.

Those meanings can become memory.

The raw video and audio are separate storage decisions.

You might keep them for replay, audit, debugging, or training data.

But that is not the same thing as agent memory.

Agent memory should keep what matters, not every raw signal that pass through the app.

So here is a second takeaway.

100

Facts go in structured memory, like classical.

101

Understanding goes in a vector store, like agent, platform, memory, bank.

102

Role perception usually stays out of memory, unless you have a separate reason to store the media itself.

103

Alright, let's make this concrete.

104

How does the agent actually remember?

105

There are two important moments, the start of a session and the end of a session.

106

At the start, the agent loads memory before the conversation really begins.

107

It reads structured facts from the database, for example, upcoming occasions, wishlist items, profile details.

108

Then it searches the vector store for a relevant understanding, for example, style preference, comfort constraints, favorite colors from past conversations.

109

Then the agent gets both kinds of context, so when the user starts talking, the agent is not starting from zero,

110

it already has the facts and it already has a meaning.

111

That is why the code open works.

112

The agent can say, you have that dinner on Thursday from the structure database

113

and I know you like to keep it simple from semantic memory.

114

One answer, two memory systems.

115

Now let's talk about saving memory.

116

Facts should usually be saved immediately.

117

If the user says I Add that Blazor to my wish list, the agent should write that to the database right away.

118

That is a tool call.

119

It is structured, it is exact, and the user expects it to be saved now.

120

Understanding is different.

121

You usually do not want to update someone's long -term identity from one random sentence.

122

If I say, maybe I like yellow today, that does not mean yellow is now my whole style.

123

Understanding needs judgment.

124

It should come from stronger signals.

125

Maybe the user explains why something matters.

126

Maybe the same pattern repeats across sessions.

127

That is how you keep memory from getting noisy.

128

So instead of treating every sentence as a permanent preference, you let the memory series review the conversation and extract what is actually worth keeping.

129

Now, when does the extraction happen?

130

You have a choice.

131

You can extract memory during the conversation, after each turn, or at interverse.

132

Agent Platform Memory Bank supports this directly.

133

You can trigger memory generation mid -session, not only at the end

134

and extracting as you go has real advantages shorter exchanges often produce cleaner memories

135

and if the user drops off early you have already saved what they said

136

but there's a catch in a live multi -modal agent extraction

137

is heavier than a database write a model has to read the conversation

138

and infer meaning that takes time and a live voice agent is latency -sensitive,

139

you cannot let a slow extraction step block the audio.

140

So the rule is not always wait until the session ends.

141

The rule is keep extraction off the live path.

142

Run it asynchronously, after the turn or after the session, wherever it will not stall the conversation.

143

And in this demo, the structured facts are written immediately during the conversation.

144

The understanding is extracted off the hot path after the session and stored as semantic memory.

145

That gives you two tracks, fast synchronous writes for facts, slower asynchronous extraction for understanding,

146

and the next time the user comes back and the agent loads both again.

147

That is the loop.

148

Read at the start, write what changes, bring it forward next time.

149

Here's the third takeaway.

150

So both memory systems, when the session starts, save facts as soon as it happens,

151

save understanding after you have enough context to know what is actually worth remembering.

152

All right, let's recap.

153

If you want your AI agent to remember users across sessions, do not start by dumping everything into one type of database.

154

Start by asking, what kind of memory is this?

155

There are two main kinds.

156

Facts are exact.

157

It looks them up.

158

Understanding is meaning.

159

You recall it.

160

Facts belong in a structural database like classical.

161

Understanding belongs in a vector store.

162

Agent Platform Memory Bank is one managed option because it can help extract and maintain that semantic memory for you.

163

But the architecture works beyond one product and raw camera frames or raw audio do not automatically become memory.

164

You usually store the meaning you extract from them, not the raw signal itself.

165

That is what turns a forgetful agent into an agent that can actually pick up where it left off.

166

It knows the facts of your life and it understands what patterns that makes those facts useful.

167

That's it.

168

So what is the first thing you would want your agent to remember about you?

169

Don't forget to leave that in the comments.

170

In the next episode, we will give the agent eyes with real -time vision.

171

All right, I will see you in the next episode.

172

Bye.

173

Thank you.

앱 다운로드

유창하게 말하는 데 필요한 모든 것

AI 발음 평가문장마다 점수 확인

IPA 발음 연습모든 소리 마스터

단어 학습나만의 단어장 만들기

단어 게임놀면서 외우기

QR 스캔

Download on theApp Store Get it onGoogle Play

같은 채널

FOR YOU

이 레슨의 어휘와 말하기 포인트

이 말하기 레슨은 영상 “AI Agent Memory Architecture: Structured SQL, Semantic Vector Search & Memory Bank”을(를) 바탕으로 합니다. 가장 자주 반복되는 단어는 다음과 같습니다: memory, agent, understanding, session, vector. 이 영상에는 섀도잉할 문장 173개와 단어 1681개가 있습니다. 말하는 구간의 길이는 12:17입니다. 화자는 분당 약 137단어의 일정한 속도로 말해서 섀도잉하기에 편한 속도입니다. 단어의 84%가 영어에서 가장 많이 쓰이는 3,000단어에 속합니다. 나머지는 연습 전에 미리 확인해 두세요.

이 영상의 핵심 어휘

영상에 나오는 익혀 둘 만한 단어 15개를 발음, 뜻과 함께 정리했습니다.

단어	발음	뜻
vector 명사	/ˈvɛktɚ/	벡터
database 명사	/ˈdeɪtəˌbeɪs/	데이터베이스
audio 형용사	/ˈɔ.di.oʊ/	오디오
belong 동사	/bɪˈlɒŋ/	속하다
preference 명사	/ˈpɹɛf(ə)ɹ(ə)ns/	선택
calendar 명사	/ˈkæl.ən.də/	역법, 력법
similarity 명사	/ˌsɪm.ɪˈlæɹ.ɪ.ti/	유사, 유사성
lesson 명사	/ˈlɛs.ən/	수업, 과
architecture 명사	/ˈɑː.kɪˌtɛk.t͡ʃə/	건축, 건축학
sensitive 형용사	/ˈsɛn.sɪt.ɪv/	민감하다
formal 형용사	/ˈfɔɹməl/	형식적
plain 명사	/pleɪn/	평지, 평야
occasion 명사	/əˈkeɪ̯ʒən/	기회, 경우
leather 명사	/ˈlɛðɚ/	가죽, 피혁
jacket 명사	/ˈd͡ʒæk.ɪt/	재킷

영상에 나오는 구동사

단어	뜻
come back 동사	돌아오다
drop off 동사	떨어지다
pick up 동사	줍다

따라 말해 볼 만한 문장

영상에 나오는 짧고 완결된 문장으로, 일상 대화에서 그대로 쓸 수 있습니다:

If the user asks, what did I buy?
If the user asks, what do I usually like for dinners?
Alright, let's make this concrete.

주의할 발음

화자는 don't, I'm, you're 같은 축약형과 약화된 형태를 3번 사용합니다. 들리는 대로 짧게 발음하세요.

“sh”와 “zh” 소리: extraction /ɪkˈstɹækʃən/, perception /pɚˈsɛpʃ(ə)n/, occasion /əˈkeɪ̯ʒən/, structural /ˈstɹʌk(t͡)ʃəɹəl/, flashy /ˈflæʃi/
긴 단어 — 강세 위치에 주의: similarity /ˌsɪm.ɪˈlæɹ.ɪ.ti/, architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, permanently /ˈpɜː.mə.nənt.li/, asynchronous /eɪˈsɪŋ.kɹə.nəs/

한국어 화자가 어려워하는 소리:

/f/ — ㅍ(/p/)으로 바꾸지 말고 윗니를 아랫입술에 대기: preference /ˈpɹɛf(ə)ɹ(ə)ns/, formal /ˈfɔɹməl/, comfort /ˈkʌm.fət/, fuzzy /ˈfʌzi/, flashy /ˈflæʃi/
/v/ — ㅂ(/b/)과 구별하기: vector /ˈvɛktɚ/, sensitive /ˈsɛn.sɪt.ɪv/, wherever /(h)wɛɹˈɛvɚ/
/z/ — ㅈ이 아니라 성대를 울리는 /s/: jeans /d͡ʒiːnz/, columns /ˈkɑləmz/, noisy /ˈnɔɪzi/, fuzzy /ˈfʌzi/, browse /bɹaʊz/

이 영상으로 연습하는 방법

먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
보통 속도로 한 문장씩 섀도잉하고, 화자의 리듬과 맞을 때까지 반복합니다.
자신의 목소리를 녹음해 원본과 비교하고, vector, database, audio 같은 단어에 특히 주의합니다.

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →

쉐도잉 연습: AI Agent Memory Architecture: Structured SQL, Semantic Vector Search & Memory Bank - 영상으로 영어 말하기 배우기

연습 모드 선택

앱 다운로드

같은 채널

The No-Code Roadmap: How I Approach Prototyping

What's new in Google Cloud in less than 1 minute

AI harness crash course

MCP vs API: The protocol every developer needs to know

추천 영상

When AIs act emotional

How to Remember Everything You Read

Configure storage accounts | AZ-104 | Episode 16

Why Memory Prices Are Crazy High

Master AI in 60 Minutes with Vector Databases!

Your AI Agent Starts Every Session Like a New Hire - Killian Carlsen-Phelan, Sonar

Core Knowledge (Stanford Psych 60)

Andrew Ng on Coding Agents and Deciding What to Build

LangChain in 5 Minutes (Explained Clearly)

[TALK 13] Structure Prediction and Design using AlphaFold – Sami Chaaban

Mixture of Experts Explained Visually: How Trillion-Parameter Models Actually Work

3-D Brain Scans | Pathways 2

이 레슨의 어휘와 말하기 포인트

이 영상의 핵심 어휘

영상에 나오는 구동사

따라 말해 볼 만한 문장

주의할 발음

이 영상으로 연습하는 방법

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법