Concept icon
Concept

Null Directive Protocol Consistency

In a four-module modular harness protocol h=(M,P,A,F)h = (M, P, A, F), harnesses that lack an explicit planning mechanism maintain type consistency through a canonical null directive d∅∈Ddird_\emptyset \in \mathcal{D}_{\text{dir}}. The planning module is instantiated as a null planner P_emptyset, which unconditionally emits d_emptyset at every time step tt. This ensures that downstream capability orchestration (FF) and action (AA) modules retain identical functional signatures and interface semantics across both purely reactive architectures (such as ReAct) and complex planned workflows without requiring branching protocol logic.

0

1

Concept icon
Updated 2026-09-25

Tags

Prep Sessions

Adaptive Agent Runtimes: Architecture, Synthesis, and State Control @ University of Michigan - Ann Arbor

Ch.1 Agent Harness Principles and Architecture - Adaptive Agent Runtimes: Architecture, Synthesis, and State Control @ University of Michigan - Ann Arbor

Four-Module Modular Harness Protocol - Adaptive Agent Runtimes: Architecture, Synthesis, and State Control @ University of Michigan - Ann Arbor