Dynamic Automaton Refinement

Context

Alinejad2026 - Dynamic Automaton Refinement and Planning for Non-Markovian RL uses learned automata to represent history-dependent rewards. The key technical pattern is to refine a DFA online when new trajectories contradict or under-support the current automaton, while keeping the induced product MDP usable for planning.

Formal Statement

An NMRDP is represented as

where R:(2^{AP})^* -> {0,1} maps proposition-label traces to binary outcomes.

The reward structure is encoded by a DFA

For automaton state q, DARP defines confidence

where P_q and N_q count positive and negative traces through q, lambda weights negative evidence, and beta delays confidence saturation.

After an episode with trace w_t and observed outcome y_t=R(w_t), refinement is triggered when either the current automaton prediction disagrees with the observation or the trace visits a state with confidence below a threshold:

When refinement is triggered, the next automaton is synthesized by RPNI over the updated positive and negative trace sets:

Derivation / Construction

  • Use the learned DFA to form the product MDP M x A_t with state space S x Q_t.
  • During action selection, add an exploration bonus that prefers rarely visited and low-confidence automaton regions:

where q_delta is the automaton state reached by the candidate transition.

  • When A_t changes to A_{t+1}, identify affected automaton states by transition differences:
  • Preserve Q-values for unaffected product states, average predecessor values for new-but-related regions, and initialize genuinely new regions conservatively.

Implications

  • Confidence is doing two jobs: deciding when the automaton model is unreliable enough to revise, and deciding where exploration should search for missing temporal patterns.
  • Product-MDP maintenance keeps the learned temporal abstraction coupled to planning, but it inherits state-space growth from both environment states and automaton states.
  • The method is attractive for implicit task rules, but safety-critical use would need a clear policy for whether low-confidence regions should be explored, avoided, or shielded.