One search. Connected ideas.

AI and LLM fundamentals

Long-term memory stores selected information beyond one task. Semantic memory contains facts or preferences; episodic memory records past events; user-profile memory contains explicit attributes such as preferred language. These categories overlap and should…

Context is what the model sees now. Short-term memory is task/session information retained across nearby steps. Conversation memory is selected dialogue history or a summary used to maintain continuity.

Beginner — Context versus memory?

vLLM is an inference-serving system designed for efficient model execution. Serving techniques such as batching and attention-memory management help multiple requests share expensive hardware. GPU optimization is matching workload, memory, scheduling, and…

Summarization compresses earlier interaction into a shorter record. Memory retrieval selects relevant stored entries, sometimes through vectors and metadata. Both reduce context volume but can lose or distort information.

State persistence stores task progress; checkpoints record recovery positions. Neither automatically means user preference memory. A durable claim workflow may need execution records even when conversational history is deleted under a different retention…

MongoDB collections can store conversation messages, task/run state, approved preferences, and memory records. A LangGraph checkpointer requires its expected integration contract rather than an arbitrary collection called memory. Business claims remain…

A checkpoint records execution progress and state at a recovery boundary. Persistence saves it outside the process. Memory is selected information reused by later turns or tasks; a checkpoint is not automatically good long-term user memory.

Tools are approved external capabilities. Planning breaks a goal into steps; state records current execution facts; memory carries selected information across turns or tasks. Autonomous action means the system can perform some actions without a new user…

Prompt injection is an attempt to make a model follow an attacker's instructions instead of the intended task. Indirect injection places those instructions in external content, such as a PDF, webpage, email, or tool result. Jailbreaking generally attempts to…

Map every trust boundary: UI, uploads, parser, retrieval, memory, provider, tools, business APIs, caches, and traces. Minimize information and authority, enforce tenant/object/action checks, constrain egress, validate schemas and rules, and test adversarial…

Context is what the model sees now. Short-term memory is task/session information retained across nearby steps. Conversation memory is selected dialogue history or a summary used to maintain continuity.

Long-term memory stores selected information beyond one task. Semantic memory contains facts or preferences; episodic memory records past events; user-profile memory contains explicit attributes such as preferred language. These categories overlap and should…

AI and LLM fundamentals

Summarization compresses earlier interaction into a shorter record. Memory retrieval selects relevant stored entries, sometimes through vectors and metadata. Both reduce context volume but can lose or distort information.

State persistence stores task progress; checkpoints record recovery positions. Neither automatically means user preference memory. A durable claim workflow may need execution records even when conversational history is deleted under a different retention…

It must resolve current policy applicability through the business service. Historical memory may explain past conversation but cannot decide the active version. I invalidate dependent caches and test stale-memory conflicts explicitly.

I define which sources may create memory, require provenance and verification for important facts, scope it by tenant/user, and provide expiry and correction/deletion. Retrieved memory remains lower authority than fresh canonical business data.

Checkpoints recover execution progress; long-term memory stores selected preferences or verified past events. I keep both separate from authoritative policy and claim records because their purposes and retention differ.

Beginner — Context versus memory?

Context is the information a model sees in the current call. Memory is stored application data that may be selected for later context. Persisting something does not make it accurate, current, relevant, or authorized for every task.

vLLM is an inference-serving system designed for efficient model execution. Serving techniques such as batching and attention-memory management help multiple requests share expensive hardware. GPU optimization is matching workload, memory, scheduling, and…

MongoDB collections can store conversation messages, task/run state, approved preferences, and memory records. A LangGraph checkpointer requires its expected integration contract rather than an arbitrary collection called memory. Business claims remain…

AI Engineering learning module

AI Engineering learning module

AI Engineering learning module

AI Engineering learning module

AI Engineering learning module

AI Engineering learning module

AI Engineering learning module

AI Engineering learning module

AI Engineering learning module