Some contextual knowledge has little to do with the agent's current problem-solving activities and goals, but rather concerns other aspects of the agent's behavior in the current context that indirectly may impact problem solving. We call this information ``standing orders'', and there are two kinds: behavioral parameters and initiation/termination actions.
Behavioral parameters modulate many aspects of an agent's behavior. Examples for an AUV include: operational envelopes (i.e., minimum and maximum values) for depth, velocity, etc.; control of obstacle-avoidance behavior (on/off, acceptable distances to obstacles); and type of communication channel (e.g., laser vs. radio vs. acoustic link). When entering or leaving a particular context, an agent should not have to reason deeply, if at all, about these sorts of parameters. Instead, the current c-schema should provide the required parameter settings automatically, thus ensuring that the agent's behavior is always appropriate for its context.
Initiation/termination actions are those actions an agent should automatically do when entering or exiting a particular context. In a schema-based reasoner, this is equivalent to goal activation or deactivation. For example, if an AUV realizes that it is in the context of ``incipient power failure'', the goal ``obtain help'' may be activated; in the context resulting from receiving a distress call, the goal ``help other agent'' should be automatically activated.