/pattern/agentic/foundational/

Functional group

Foundational · World Modeling & State

The Foundational phase stabilizes the agent's grip on reality. It ensures that every observation, memory access, and state transition entering the system is clean, salient, and durable. Without this integrity, downstream reasoning operates on hallucinated inputs, retrieval drift, or lost progress. The phase matters because the world model is the foundation every later decision depends on — if that foundation is sand, no amount of clever planning or execution repairs it. Its absence causes silent data corruption: schemas drift, tool responses mutate, and session state evaporates between steps, producing bugs that manifest three nodes later and require hours to trace back to a bad initial observation.

Integrator

Validates incoming observations before they enter the world model, ensuring downstream reasoning operates on clean signals rather than raw, potentially malformed inputs.

Addresses
Cognitive data quality — the systemic weakness of trusting raw observations.
When it stabilizes
When an agent must combine multiple noisy sensors, parse external APIs whose schemas drift, or admit user input that may misrepresent the world.
Example
A schema-validated JSON parser sits between a tool's raw response and the agent's state, rejecting malformed payloads before they poison the graph.
Full reference →

Retriever

Context-sensitive interface to long-term memory; selects what is salient to the current step rather than dumping the entire store into the prompt.

Addresses
Inefficient retrieval — the failure mode of either flooding the prompt or missing the relevant fragment.
When it stabilizes
When the knowledge base grows beyond a few pages and naive similarity search starts returning noise, or when different tasks need different retrieval strategies.
Example
A RAG retriever with a reranker selects top-k passages keyed to the current sub-goal, not the conversation history.

Recorder

Saves and restores Reasoning & World Model (RWM) states for durability, replay, and forward recovery across steps, sessions, and processes.

Addresses
Persistence — the loss of progress when runs span steps, sessions, or processes.
When it stabilizes
When a workflow must survive restarts, when HITL pause points need durable state, or when concurrent users must not bleed into each other.
Example
Checkpoint snapshots of agent state at every node boundary, persisted to Postgres with a composite thread key of UserID + SessionID.
Full reference →

Search

Search patterns, frameworks, and pages.