8.1.3. Maintenance Responsibilities Within the Established Scope
Maintenance Responsibilities Within the Established Scope¶
The principle is:¶
-
The decision to extend the managed correlation scope is distinct from the responsibility to maintain established correlations.¶
Once participants undertake responsibility for protocol-managed correlations, they are expected to keep those correlations sufficiently coherent for their intended purpose. This involves preserving or communicating relevant changes to affected correlations, rather than broadcasting every update or disclosing the complete upstream context. Intermediaries may retain private mappings or translate identifiers.¶
The distinction between scope extension and maintenance is particularly relevant in autonomous and decentralized agentic systems, where participants may independently decide whether to extend the managed correlation scope. In controlled administrative domains or orchestrated environments, scope extension may instead be governed by deployment policies or orchestration logic. Where all relationships contributing to an Activity are required to be managed through the dialog-management protocol, the protocol-managed correlation scope may coincide with the logical interaction scope of the Activity.¶
Maintenance responsibilities apply regardless of how scope extension is governed.¶
Consider a barge-in in D1 that changes requirements for Tasks in D2 and D3 in a manner that affects established managed correlations:¶
D1 D2 D3
AIE <----> FNE FNE <----> Agent A Agent A <----> Agent B
Task t_11 Task t_22 Task t_13
| | |
barge-in changes | |
requirement for t_11 | |
+-- relevant update -->+-- relevant update --->+
| |
correlate impact correlate impact
on t_22 on t_13
An unrelated Dialog D5 does not require the same update.
¶
If Agent A fails to communicate a change necessary to maintain an established correlation between D2 and D3, this constitutes a maintenance failure rather than a decision not to extend the managed scope. The dialog-management protocol should make detected maintenance failures observable without requiring disclosure of private metadata.¶
If Agent B establishes a further Dialog D6 with Agent C outside the protocol-managed correlation scope, the protocol cannot impose corresponding maintenance responsibilities on Agent C. Agent B remains responsible for its established managed correlations, even when dependencies outside that scope affect its ability to maintain them. Failures originating outside the managed scope may remain unobservable or their causes indeterminate.¶