Agent Architecture in Partially Observable Stochastic Environments (POMDPs)

Agent Architecture in Partially Observable Stochastic Environments (POMDPs)

Verified Sources
Nov 7, 2026

An agent’s architecture determines (i) what internal information it keeps, (ii) how it updates that information from observations, and (iii) how it uses the internal state to choose actions under uncertainty. In partially observable and stochastic environments, the key architectural distinction is whether the agent represents uncertainty explicitly and maintains memory across time.

A standard formalization is the POMDP model. In a POMDP, the agent does not observe the true environment state sts_t directly; it receives observations oto_t that are generated stochastically from sts_t, and the environment transitions stochastically from one state to the next. Therefore, optimal decision-making depends on the agent maintaining a distribution over possible states—typically called a belief state.

Architectural implications:

  • Memory & state estimation: Architectures with no memory (purely reactive) cannot, in general, recover hidden state information; they act from oto_t only, which is typically insufficient in POMDPs. Architectures with explicit belief estimation (e.g., Bayes filter / particle filter) can.
  • Inference module: An “inference” component (filtering) computes/upgrades the belief state using the observation model and transition dynamics.
  • Decision module: A policy can be conditioned on belief state rather than on raw observations.
  • Planning horizon & computation: Some architectures approximate the belief-state optimal control problem with limited lookahead, while others compute exact/near-exact solutions.

Below is a compact view of the information flow that architecture choices control.

Architectural rule of thumb

If your agent must act optimally under partial observability, its architecture must include some form of memory/inference (explicit belief or implicit recurrent state), otherwise it will collapse uncertainty too early.

Reactive agents often fail in POMDPs

A purely reactive policy that maps only ot↦ato_t \mapsto a_t ignores how observations combine over time. In many stochastic environments, this leads to systematically suboptimal (or unstable) behavior.

How architecture components map to POMDP operation

Observation acquisition

Sensing

Agent receives oto_t from a hidden state sts_t through a stochastic observation process."

Belief/memory update

Inference

Agent updates internal representation btb_t from history (actions + observations)."

Action selection

Decision

Agent selects ata_t using a policy conditioned on belief (or recurrent memory)."

Closed-loop interaction

Control

Action influences next hidden state via stochastic dynamics, closing the loop."

1) What “architecture” changes, formally

In a POMDP, an agent’s quality depends on replacing the unobservable sts_t with an internal representation that is computable from history. Architecture controls:

  1. Belief update mechanism

    • If the agent has access to P(otmidst)P(o_t\\mid s_t) and P(stmidst−1,at−1)P(s_t\\mid s_{t-1}, a_{t-1}), it can perform a Bayes filter: bt(s)proptoP(otmids)sums′P(smids′,at−1),bt−1(s′)b_t(s) \\propto P(o_t\\mid s)\\sum_{s'} P(s\\mid s', a_{t-1})\\,b_{t-1}(s')
    • If it does not have models, it must learn approximate updates or use a learned memory module.
  2. State representation

    • Explicit belief state: architecture maintains btb_t as a distribution (tabular, factorized, particle-based).
    • Implicit belief: architecture uses recurrence (e.g., RNN/LSTM) so internal hidden state acts as a learned summary of the history.
  3. Policy conditioning

    • Belief-conditioned policy: ,pi(atmidbt)\\,\\pi(a_t\\mid b_t)
    • Observation-conditioned policy (reactive): ,pi(atmidot)\\,\\pi(a_t\\mid o_t)

The critical limitation: ,pi(atmidot)\\,\\pi(a_t\\mid o_t) generally cannot represent the information lost by not tracking uncertainty over hidden states. In contrast, belief-conditioned policies can act differently depending on how likely each hidden state is under the same observation.

Key terms: POMDP, belief state, Bayes filter, observation model.

2) Common architectural patterns and their consequences

A. Purely reactive architecture (no memory)

A typical reactive agent does:

  • perception: otrightarrowo_t \\rightarrow
  • decision: at=pi(ot)a_t = \\pi(o_t)

Effect in POMDPs: two different hidden states may produce the same observation distribution, and the reactive policy cannot disambiguate them over time. Stochasticity worsens this because the same observation may correspond to different histories.

B. Reactive-with-memory (implicit belief via recurrence)

Modern agents often use recurrent networks:

  • update internal state: ht=f(ht−1,ot,at−1)h_t = f(h_{t-1}, o_t, a_{t-1})
  • act: at=pi(ht)a_t = \\pi(h_t)

Effect: the architecture can learn to approximate a belief state (or useful statistics) even without explicit transition/observation models. Performance depends heavily on capacity, training signal, and whether the recurrence captures sufficient history.

C. Deliberative architecture (explicit inference + planning)

A classic structured approach:

  • belief update (Bayes filter / particle filter)
  • planner/policy uses btb_t (sometimes with lookahead)

Effect: can be theoretically aligned with POMDP optimal control when models are available and computation is adequate. When models are approximate or planning is truncated, it becomes an informed approximation.

From architecture to behavior: belief-based operation loop

  1. 1
    Step 1

    Read oto_t from the sensors at time tt.

  2. 2
    Step 2

    Compute/approximate updated belief btb_t using the previous belief bt−1b_{t-1}, last action at−1a_{t-1}, and observation oto_t (e.g., Bayes filter or particle filter).

  3. 3
    Step 3

    Choose ata_t according to a policy conditioned on belief: at∼π(⋅∣bt)a_t \sim \pi(\cdot\mid b_t).

  4. 4
    Step 4

    Execute ata_t; stochastic dynamics transition the hidden state and the next observation follows.

  5. 5
    Step 5

    If multiple hypotheses remain plausible, the policy can choose information-gathering actions (exploration) rather than committing early.

Practical Example: Robot navigation with localization uncertainty

Scenario: A robot moves in a 1D corridor with walls (hidden exact position). It moves stochastically (motor noise) and senses obstacles with uncertainty (sensor noise). The robot only receives noisy distance/observation readings, not the true position.

Architectural choices

  1. Reactive controller (no memory):

    • Input: current noisy reading oto_t
    • Output: action ata_t
    • Failure mode: the same reading can occur at multiple positions; because movement is stochastic, the robot can “oscillate” or systematically drift.
  2. Belief-based architecture (explicit inference):

    • Maintains belief bt(x)b_t(x) over positions xx
    • Uses a transition model for motion noise and an observation model for sensor noise
    • Chooses actions based on btb_t
    • Often can recover by accumulating evidence across time

Mini-model (conceptual)

  • Hidden state: st=xts_t = x_t (true position)
  • Actions: atintextleft,textrighta_t \\in \\{\\text{left},\\text{right}\\}
  • Transition: P(xt+1midxt,at)P(x_{t+1}\\mid x_t, a_t) due to motion noise
  • Observation: P(otmidxt)P(o_t\\mid x_t) due to sensor noise
  • Belief update: bt(x)proptoP(otmidx)sumx′P(xmidx′,at−1),bt−1(x′)b_{t}(x) \\propto P(o_t\\mid x)\\sum_{x'} P(x\\mid x', a_{t-1})\\,b_{t-1}(x')

What changes due to architecture?

  • Reactive: cannot represent “I might be at location A with probability 0.6 or B with probability 0.4.” It makes the same choice whenever oto_t looks similar.
  • Belief-based: can decide “move right if right is more likely” and can also take actions that reduce uncertainty when needed (e.g., move to a region where observations disambiguate positions).

Key terms: particle filter, motion model, sensor noise, localization.

Qualitative impact of architecture on handling partial observability

Higher is better for robustness under hidden-state uncertainty.

Common edge cases and design implications

POMDPs for Beginners (conceptual overview)

Knowledge Check

Question 1 of 4
Q1Single choice

In a partially observable stochastic environment, what is the most important architectural capability for optimal decision-making?