When Routine Operations Break Architectural Pattern Relationships in LLM Agent Harnesses
Organizations: Responsible AI Research Centre · Adelaide University · CSIRO · UNSW
Abstract
LLM agent harnesses distribute tool mediation, state management and safety guardrails across native services, independently written plugins and configuration. Routine operations can change the runtime order or retained state that architectural pattern relationships require, without any code change. We study five relationships associated with the Guardrail Enforcement Point, Autonomy Controller and Blackboard patterns across five released harnesses, analysing a main sample of fourteen independently written plugins. Using PatternOps, our assessment procedure, we trace requirements from pattern descriptions, provider documentation and deployment profiles to the providers that realise them and the records that decide them. We then compare alternative allocations under supported operations. Such operations broke relationships silently: after a plugin was reapplied or an allow rule saved, policy stopped evaluating edits while every plugin stayed active, and a prohibited edit executed. Which alternatives qualified depended on the requirement. Allocations that kept the required order, or kept or rebuilt the needed state, held on their tested paths and operation sequences, while others prevented prohibited effects but missed edits rejected elsewhere. In these harnesses, a pattern relationship is a property of the running system and its history, so architects should evaluate it against the decision paths, state lifetimes and operation sequences their deployments use.
Figures & tables
| Relationship | Authority of assessed requirement |
|---|---|
| GEP: policy participation | Pattern duty: The inline enforcement point “must return before execution proceeds” and enforces prohibitions returned by policy (§3.2.1). Provider promise: Governance “intercepts every tool call”. Deployment requirement: A study policy service decides; approval does not override a prohibition; every admitted edit call is evaluated, including rejected ones (the every-edit requirement). |
| GEP: decision information | Pattern duty: The decision receives the candidate action and its boundary context. Provider promise: Airlock: untrusted content cannot direct an egress-capable tool, and compaction cannot launder (remove) a label. Deployment requirement: An untrusted source restricts edits, or under Airlock’s built-in rules egress-capable tools, while it is in the model’s input or a summary’s sources. RiskProof: an observe-mode read restricts the first enforce decision. |
| AC: response applied | Pattern duty: The operator’s response is applied before progression (§3.2.2). Study reading: the response to the pending action. |
| AC: completed work | Deployment requirement (task): Resumption repeats no completed work. |
| Blackboard: membership | Pattern duty: Knowledge is “accessible to all agents”. Study reading: participating members. Provider promise: Ensemble: its lookup returns only members that have not shut down. Deployment requirement: A shut-down member stays excluded until it re-enrols. |
| Host | Carrier: operations or routes |
LLM Agent Harnesses
LLM agent harnesses are the software and runtime systems that organize an agent’s tools, context, state, execution, and safeguards.
See all 419 papers