The team member agent architecture is suitable for PTS domains. Individual agents can capture locker-room agreements and respond to the environment, while acting autonomously. Based on a standard agent paradigm, our team member agent architecture allows agents to sense the environment, to reason about and select their actions, and to act in the real world. At team synchronization opportunities, the team also makes a locker-room agreement for use by all agents during periods of limited communication. Figure 1 shows the functional input/output model of the architecture.
Figure 1: A functional input/output model of the team member agent architecture for PTS domains.
The agent keeps track of three different types of state: the world state, the locker-room agreement, and the internal state. The agent also has two different types of behaviors: internal behaviors and external behaviors.
Internal and external behaviors are similar in structure, as they are both sets of condition/action pairs where conditions are logical expressions over the inputs and actions are themselves behaviors as illustrated in Figure 2. In both cases, a behavior is a directed acyclic graph (DAG) of arbitrary depth. The leaves of the DAGs are the behavior types' respective outputs: internal state changes for internal behaviors and action primitives for external behaviors. One leaf is illustrated in Figure 2.
Figure 2: Behaviors in the team member agent architecture. Both internal and external behaviors are organized in a directed acyclic graph.
This notion of behavior is consistent with that laid out in . In particular, behaviors can be nested at different levels: selection among lower-level behaviors can be considered a higher-level behavior, with the overall agent behavior considered a single ``do-the-task'' behavior. There is one such top-level internal behavior and one top-level external behavior; they are called when it is time to update the internal state or act in the world, respectively.
The following section introduces the teamwork structure that builds upon this team member agent architecture. The teamwork structure is designed for use in PTS domains. It exploits the locker-room agreement and the behavior definitions of the team member agent architecture.