<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-agentproto-context-management-architecture-01" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="Context Management Architecture">Context and Correlation Management Architecture for Distributed Agentic Activities</title>
    <seriesInfo name="Internet-Draft" value="draft-agentproto-context-management-architecture-01"/>
    <author fullname="Hesham Moussa">
      <organization>Huawei Canada</organization>
      <address>
        <email>hesham.moussa@huawei.com</email>
      </address>
    </author>
    <author fullname="Arashmid Akhavain">
      <organization>Huawei Canada</organization>
      <address>
        <email>arashmid.akhavain@huawei.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Internet</area>
    <workgroup>agentproto</workgroup>
    <keyword>AI Network</keyword>
    <keyword>Agentic Networks</keyword>
    <keyword>AI inference</keyword>
    <keyword>AI training</keyword>
    <abstract>
      <?line 39?>

<t>Agentic applications increasingly distribute objectives across autonomous agents, tools, and services operating across different protocols and administrative domains. A single Activity may involve multiple independently maintained Dialogs, Tasks, Events, and Resources, spanning different modalities and extended periods of time.</t>
      <t>Existing protocols provide identifiers and context-management mechanisms for their own interactions, but these do not necessarily support correlation across Dialogs, protocols, and administrative boundaries, particularly as interactions evolve, branch, or resume over time.</t>
      <t>This document defines a context-and-correlation architecture based on Activities, Dialogs, Tasks, Resources, and typed Relationships. It describes how management and correlation metadata can be maintained and selectively propagated to preserve coherent context across distributed interactions, while allowing participants to determine the scope of correlations they share and manage.</t>
    </abstract>
  </front>
  <middle>
    <?line 47?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Distributed agentic systems are increasingly composed of multiple independently operated participants.</t>
      <t>A single Activity can involve:</t>
      <ul spacing="normal">
        <li>
          <t>Invocation by users, agents, or other invoking systems;</t>
        </li>
        <li>
          <t>One agent delegating work to another;</t>
        </li>
        <li>
          <t>Several independent agent-to-agent Dialogs;</t>
        </li>
        <li>
          <t>Agent-to-tool interactions;</t>
        </li>
        <li>
          <t>Resources produced in one branch and consumed in another;</t>
        </li>
        <li>
          <t>Downstream delegation hidden from upstream participants;</t>
        </li>
        <li>
          <t>Modality transformations, such as video to audio to text;</t>
        </li>
        <li>
          <t>Multiple vendors and administrative domains;</t>
        </li>
        <li>
          <t>Local protocol constructs that do not share identifiers or state; and</t>
        </li>
        <li>
          <t>Operation over different transport protocols.</t>
        </li>
      </ul>
      <t>Multiple Activities may proceed concurrently within the same distributed agentic system. Within each Activity, work may extend across independently maintained Dialogs, with participants having visibility into only parts of the overall interaction.</t>
      <t>This raises a practical challenge: as work is delegated, results are reused, or interactions resume after interruptions, how can the relevant Dialogs, Tasks, and Resources remain correctly associated? Existing protocols provide their own context-management mechanisms and identifiers, but these alone do not establish interoperable correlations across independently maintained interactions.</t>
      <t>This document introduces an information model for representing these correlations and examines how they can be maintained and selectively shared. An Activity may extend beyond the correlations managed through a dialog-management protocol, while those that undertake to maintain established correlations are responsible for preserving their coherence as interactions evolve.</t>
      <t>The remainder of this document is organized as follows. Section 2
states the core architectural principle, and Section 3 defines
terminology. Section 4 introduces the architectural model and
illustrates it through motivating examples that cross organizational
boundaries. Section 5 examines how independently maintained Dialogs
coexist within one Activity, and Section 6 addresses Tasks within a
Dialog. Section 7 describes binding to protocol-local context.
Section 8 develops correlation metadata propagation, including scope
and maintenance responsibilities, the propagation model, what is
propagated, context projection, identifier translation, freshness,
revocation, partial visibility, failure modes, related protocols,
architectural considerations, out-of-scope items, and open questions.</t>
      <t>This document distinguishes settled architectural principles from
open design questions. The open questions are deliberate: they
identify the decision space reserved for the dialog-management
protocol and for coordination with related work. They are
candidates for resolution in subsequent protocol documents, not
gaps in the architecture.</t>
    </section>
    <section anchor="core-architectural-principle">
      <name>Core Architectural Principle</name>
      <t>The architecture rests on a single central principle:</t>
      <ul empty="true">
        <li>
          <t>Identify the objects and relationships needed to keep independently
maintained Dialogs, Tasks, and Resources correlated across protocol
and administrative boundaries. Define their correlation semantics
without replacing protocol-local mechanisms, and distinguish
relationships maintained locally from information that needs to be
propagated for interoperability.</t>
        </li>
      </ul>
      <t>The architecture distinguishes application content from the management and correlation metadata associated with it. Application protocols carry the interactions and content that may contribute to an agent's conversational or LLM context, while dialog-management functions maintain and exchange the metadata needed to preserve coherent context across independently maintained Dialogs, Tasks, and Resources within an Activity.</t>
      <t>The model uses five primary objects:</t>
      <artwork><![CDATA[
Activity
Dialog
Task
Resource
Relationship
]]></artwork>
      <t>The model also introduces Dialog Management State (DMS), a management-state abstraction associated with each logical Dialog. DMS maintains the Dialog's management information and relevant correlations with other architectural objects.</t>
      <t>The model also identifies four Activity-relative participant roles:</t>
      <artwork><![CDATA[
Activity Initiating Entity (AIE)
First Next Entity (FNE)
Assistant Agent (AA)
Assistant Tool (AT)
]]></artwork>
      <t>Roles are relative to the invocation chain: the AIE initiates an Activity, its directly invoked entity is the FNE, and entities invoked downstream are Assistant Agents or Assistant Tools. Terminology follows below.</t>
      <t>The participant roles defined in this architecture refer to logical entities within an interaction wave, rather than prescribing their internal implementation. An AIE, FNE, or Assistant Entity may comprise multiple underlying participants. Such an entity may appear externally as a single Dialog endpoint, while its internal coordination and interactions remain hidden. Alternatively, constituent participants may be visible through separate Dialogs whose relationships are explicitly established. The architectural roles describe how entities participate in an interaction wave, independently of their internal organization.</t>
      <t>This information model complements protocol-local context
management mechanisms. A dialog-management protocol may use the
model's semantics and convey relevant Correlation Metadata through
bindings to existing protocols; this architecture does not define
those bindings.</t>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <ul spacing="normal">
        <li>
          <t>Activity: is the root of an interaction wave, initiated by one logical Activity Initiating Entity (AIE) to pursue an objective and reach an
outcome. An Activity is initiated when the AIE invokes one logical First Next Entity (FNE), establishing the Activity's initial Dialog. It
groups the Dialogs and their Tasks, together with the Resources
involved, for correlation purposes. This grouping does not imply a
shared conversational context or a shared participant set. An AIE
may initiate multiple Activities, and an Activity can involve
multiple tools and protocols.  </t>
          <ul spacing="normal">
            <li>
              <t>Examples:      </t>
              <artwork><![CDATA[
Analyze video V1
Plan a trip
Investigate a network fault
Prepare a financial report
]]></artwork>
            </li>
          </ul>
        </li>
        <li>
          <t>Dialog: is a logical container established among a set of two or
more participants that share a conversational context. It belongs to
exactly one Activity, and is created to pursue an objective that
contributes to that Activity. The Dialog may contain zero or more
Tasks, each pursuing a part of the Dialog's objective. A Dialog is
related to its Activity and to other Dialogs, Tasks, and Resources of
that Activity through correlation metadata. The metadata also records
the Dialog's lifecycle state. A Dialog is frequently pairwise, but may
involve more than two participants. The same set of participants may
maintain several concurrent Dialogs, within the same Activity or
across different Activities. Each Dialog is identified by its own
identity, not by its participant set. Every Dialog has its own
objective, conversational context, and lifecycle state. Its associated
DMS persists logically as its participant set changes.</t>
        </li>
        <li>
          <t>Dialog Management State (DMS): The logical management state associated with a Dialog, comprising its metadata such as identity, lifecycle state, applicable participant-membership information, and Correlation Metadata established within the Dialog's managed scope. Each Dialog is associated with one logical DMS, which may have multiple distributed representations maintained by its participants. These representations need not be identical.</t>
        </li>
        <li>
          <t>Task: is a bounded unit of work within a Dialog, created to pursue an
objective that contributes to the Dialog's objective. A Task
progresses through one or more Events, which advance that objective.
A Task has its own lifecycle state. A Task groups related Events under a common objective, allowing distinct strands of work within the same Dialog to be identified separately.  </t>
          <t>
Example: as part of the Activity "plan a trip", Agent A and Agent
B work together to generate a shortlist of suitable hotels in a
city within the trip's destination. Generating that shortlist is
the objective of the Dialog between Agent A and Agent B. Within
that Dialog, retrieving and evaluating each hotel is a bounded unit
of work, that is, a Task. Within each Task, Agent A and Agent B
carry out Events - for example, request hotel X's details, clarify
its breakfast arrangement, or check availability - and those Events
share the Task's identifier as they progress.</t>
        </li>
        <li>
          <t>Event: is a message, a job invocation, a tool call, or a similar
interaction carried out by the participants as they pursue a Task's
objective. An Event has no objective of its own. It is part of
carrying out the Task. An Event belongs to exactly one Task and
carries that Task's identifier as it progresses. Events are local
to their Task and are not correlation objects. An Event may carry or reference content in one or more modalities, including text, audio, images, and video. Events within the same Task or Dialog may use different modalities, concurrently or over time. A change in modality does not, by itself, require establishing a new Task or Dialog.</t>
        </li>
        <li>
          <t>Resource: is an identifiable object that participants consume,
produce, refer to, or transform during an Activity, such as video,
audio, text, documents, transcripts, tool outputs, and
agent-produced artifacts. The same Resource can be used in more than
one Activity. Each Activity may refer to it differently, and so may
its Dialogs, Tasks, and Events. The architecture does not prescribe a
particular method of referencing Resources. Inside an Activity, any
Dialog, Task, or Event can refer to the Resource, and the same
Resource can be referred to by several of them simultaneously.
Resources can also be physically carried within Events.</t>
        </li>
        <li>
          <t>Relationship: is a typed, directional association among
Activities, Dialogs, Tasks, or Resources. A relationship expresses
an association between its endpoints. Relationship types express the
meaning of those associations. Relationship types are Correlation
Metadata. A relationship may exist and be retained without its type being
disclosed (disclosure of relationship types is a decision for the endpoints to make). 
The relationship types presented below are illustrative. The companion
dialog-management protocol specification will determine which
relationship types require standardized semantics and interoperable
representation or exchange. Examples include:  </t>
          <artwork><![CDATA[
belongs-to
delegated-from
derived-from
input-to
output-of
]]></artwork>
        </li>
        <li>
          <t>Upstream and Downstream: are directional terms relative to a given
Dialog. Upstream refers to Dialogs from which work was delegated, in
the direction of the Activity Initiating Entity (AIE). Downstream
refers to Dialogs created by delegating work, in the direction away
from the AIE. Delegation proceeds downstream. Results, status, and
correlation updates proceed upstream.</t>
        </li>
        <li>
          <t>Context: in this document, refers to the set of relationships
(correlations) among Activities, Dialogs, Tasks, and Resources, and
to the Correlation Metadata that describes them. Context does not
refer to the internal state maintained by an AI agent (sometimes
called a "context window"). Agent-internal memory and its content is out of scope.
Implementations maintain the protocol state needed for correlation,
such as Dialog identities, asserted relationships, and protocol-managed
correlation scopes for which they accepted maintenance responsibilities,
independently of agent-internal memory or prompt context. This architecture does not prescribe how that state is stored
or deployed, whether in a library, sidecar, service, or equivalent form.
Context as defined here is also distinct from the application
conversation and Event content associated with a Dialog.  </t>
          <t>
The following should also be noted: Context, as defined in this document, represents an architectural correlation model and is broader than the Dialog context defined in the agentproto charter. The inclusion of an object or relationship in this model does not imply that it must be standardized or exchanged by the dialog-management protocol. A Dialog's DMS represents its own management state and selected shared correlations, not this broader architectural Context.</t>
        </li>
        <li>
          <t>Correlation Metadata: is the information that participants may
exchange to keep independently maintained Activities, Dialogs,
Tasks, and Resources correlated and to enable the establishment of a coherent context.
Correlation metadata consists of different kinds of assertions, examples include: relationships,
such as "D2 delegated-from D1" or "T1 derived-from V1", and
lifecycle state, such as "D5 revoked". It does not include
Resource content or an agent's internal state or memory.</t>
        </li>
        <li>
          <t>Protocol-Local Context: is the context establishment mechanism defined by the
application protocol used within a Dialog. For example, an A2A
<tt>contextId</tt> or <tt>taskId</tt>, etc are a Protocol-Local Context.</t>
        </li>
        <li>
          <t>Dialog Management: The correlation and lifecycle management of an
Activity's Dialogs and Tasks, including the correlation of the
Resources they use and the Activity that groups them. Although
named after the Dialog as the fundamental unit of interaction,
Dialog Management is not limited to Dialogs. A dialog-management
protocol supports these functions and enables participants to
exchange the information needed to maintain these correlations.
The protocol may represent and exchange the appropriate parts of a
Dialog's DMS without replacing application-protocol state.</t>
        </li>
        <li>
          <t>Resource Binding: describes a Resource's use or interpretation within
an Activity, Dialog, or Task.</t>
        </li>
        <li>
          <t>Interaction Wave: is the dynamically expanding set of Dialogs,
Tasks, and Resources within an Activity as work is delegated and
executed across participants. It is rooted at the AIE and begins
with the initial Dialog between the AIE and the FNE invoked for
that Activity. Subsequent invocations within the Activity extend
the wave through additional Dialogs.</t>
        </li>
        <li>
          <t>Activity Initiating Entity (AIE): is the entity that starts an
Activity and forms the root of the corresponding interaction wave.
The AIE is the originator of the Activity. An AIE can be a user, an
agent, or an invoking system. A tool cannot be an AIE.</t>
        </li>
        <li>
          <t>First Next Entity (FNE): A logical entity directly invoked by an Activity Initiating Entity (AIE) to pursue the objective of a newly initiated Activity. Each logical AIE-to-FNE invocation establishes a distinct Activity and its initial Dialog. An AIE may initiate multiple Activities by invoking the same or different FNEs. The FNE may be an application, agent, or tool. Its designation reflects its role in the Activity rather than its entity type or internal implementation. The FNE serves as the logical entry point for an Activity, through which the overall Activity objective and applicable policies or configuration may be conveyed. This role does not prescribe how the FNE internally processes, manages, or delegates the handling of such information. An FNE may invoke Assistant Entities through additional Dialogs within the Activity. However, an FNE acting as a tool is a terminal logical endpoint and does not establish downstream Dialogs within that Activity. This does not restrict its internal implementation.</t>
        </li>
        <li>
          <t>Assistant Entity: An entity invoked by an FNE or another Assistant
Entity as part of an Activity. The invoking entity and the Assistant
Entity interact through a Dialog associated with that Activity. An
Assistant Entity may be an Assistant Agent (AA) or an Assistant Tool
(AT). In this architecture, an application serving as an Activity entry point occupies the FNE role rather than an Assistant Entity role. This classification describes its role in the interaction wave and does not constrain its software implementation.</t>
        </li>
        <li>
          <t>Assistant Agent (AA): An Assistant Entity that is an AI agent. An
AA interacts with its invoking entity through a Dialog and may
invoke other Assistant Entities (AAs or ATs) to assist in completing
Tasks assigned to it within the Activity.</t>
        </li>
        <li>
          <t>Assistant Tool (AT): An Assistant Entity invoked to perform a bounded Task. An AT acts as a terminal logical endpoint within the Activity's interaction wave and does not establish downstream Dialogs within that Activity. Its internal implementation may involve multiple participants or interactions, which are not exposed as downstream Dialogs of the Activity. An AT may complete its Task through a single request-response exchange, but this architecture does not require a particular execution pattern.</t>
        </li>
        <li>
          <t>Invocation: is the logical act of an entity initiating an interaction with another entity to pursue an objective. An AIE-to-FNE invocation establishes an Activity and its initial logical Dialog. Where either entity comprises multiple participants, several underlying interactions or Dialogs may be associated with that invocation without constituting separate Activity initiations. Downstream invocations establish additional Dialogs within the Activity.</t>
        </li>
      </ul>
    </section>
    <section anchor="architectural-model">
      <name>Architectural Model</name>
      <section anchor="architecture-visualization">
        <name>Architecture Visualization</name>
        <t>An Activity begins when an Activity Initiating Entity (AIE) invokes
one First Next Entity (FNE) to pursue its objective. The invocation
establishes the Activity and its initial Dialog between the AIE
and the FNE:</t>
        <artwork><![CDATA[
          Activity
    +-----------------------------------+
    |                                   |
    | +-----+     Dialog D1   +-----+   |
    | | AIE |<-------+------->| FNE |   |
    | +-----+        |        +-----+   |
    |                |                  |
    |              DMS(D1)              |
    +-----------------------------------+
]]></artwork>
        <t>If the goal of the Activity can be fulfilled by the FNE itself, no
additional entities are invoked for that Activity. Alternatively, if
assistance from additional entities is required, the FNE, or any
downstream assistant entity, may invoke assistant entities. Dialogs
are created between the invoking entity and each invoked assistant
entity, and the respective Tasks are handled within their associated dialogs, all under the
umbrella of the Activity, and the interaction wave propagates.
Dialogs created in this way belong to the Activity but might not
directly involve the AIE; each is related to the Dialog that
created it through lineage relationships (see "Dialog Lineage"). The
interaction wave may then look like the following:</t>
        <artwork><![CDATA[
          Activity
+------------------------------------------------------------------+
|                                                                  |
| +-----+   Dialog   +-----+   Dialog   +-----+   Dialog   +-----+ |
| | AIE |<---------->| FNE |<---------->| AA1 |<---------->| AA3 | |
| +-----+   task(s)  +-----+   task(s)  +-----+   task(s)  +-----+ |
|                       +                  +                       |
|                Dialog |           Dialog |                       |
|                       | task(s)          | task(s)               |
|                       v                  v                       |
|                    +-----+            +-----+                    | 
|                    | AT1 |            | AT2 |                    |
|                    +-----+            +-----+                    |
|                                                                  |
+------------------------------------------------------------------+
]]></artwork>
        <t>An Activity groups multiple independently maintained Dialogs, each of
which may contain Tasks:</t>
        <t>Conceptually, the model looks like the following. Each Dialog has
its own logically associated DMS; the DMS maintains management state
and selected shared correlations rather than containing the Tasks,
Events, or Resources themselves:</t>
        <artwork><![CDATA[
                     Activity
                        |
            +-----------+-----------+
            |                       |
         Dialog D1               Dialog D2
            |    |                  |   |
            |    +-- DMS(D1)        |   +-- DMS(D2)
            |                       |
          Tasks                   Tasks
         (Events)                (Events)
            |                       |
            +-----------+-----------+
                        |
               +-------------------+
               |   Resource Layer  |
               +-------------------+
]]></artwork>
        <t>The figure above introduces the Resource Layer, a logical view of the
Resources associated with an Activity. It allows Dialogs and Tasks to
refer to the same Resource, including multimedia content that is
consumed, produced, or transformed across different Dialogs. A Resource
may be carried in an application exchange or accessed separately by
reference. The Resource Layer does not prescribe a storage service,
content-transfer protocol, or globally visible repository.</t>
        <t>Cross-Dialog lineage and shared Resource use are the architectural
focus. The interaction graph need not be globally stored or visible;
participants may retain only the correlations their operations require.
Neither the Activity nor the Resource Layer implies an Activity-wide
DMS, a shared repository for every Dialog, or disclosure of the full
correlation graph. An authorized view of an Activity may be assembled
from several Dialogs' DMS representations and locally maintained
correlations, without introducing a separate Activity-wide state object.</t>
      </section>
      <section anchor="motivating-multimedia-example">
        <name>Motivating Multimedia Example</name>
        <t>Consider a user requesting an analysis of video V1. The user acts as the Activity Initiating Entity (AIE) and invokes Agent A, the First Next Entity (FNE), establishing an Activity with the objective "analyze video V1" and its initial Dialog, D1. A Task within D1 pursues the requested analysis, with V1 serving as an initial Resource.</t>
        <t>Agent A determines that the analysis requires two capabilities: processing the visual content and transcribing the audio into text. Agent A therefore invokes Agent B, an Assistant Agent (AA) capable of analyzing video and text, and Tool X, an Assistant Tool (AT) responsible for audio transcription. These invocations establish two additional Dialogs within the Activity: D2 between Agent A and Agent B, and D3 between Agent A and Tool X.</t>
        <t>Within D2, Agent A provides V1 to Agent B and assigns the video-analysis Task. Within D3, Tool X receives a reference to V1, accesses the video through an authorized Resource-access mechanism, and produces transcript T1. Agent A subsequently provides T1 to Agent B within D2, where it is analyzed alongside the video.</t>
        <t>The participant roles are:</t>
        <artwork><![CDATA[
User     AIE
Agent A  FNE
Agent B  AA  (invoked by Agent A)
Tool X   AT  (invoked by Agent A)
]]></artwork>
        <t>These roles follow the invocation chain rather than the nature of the entity. For example, if the user directly invoked Tool X to transcribe V1, Tool X would be the FNE of that Activity rather than an AT.</t>
        <t>The scenario is depicted below:</t>
        <artwork><![CDATA[
                     User (AIE)
                          |
                          | Dialog D1:
                          | (Activity, V1)
                          v
                   Agent A (FNE)
              +-----------+-----------+
              |                       |
   Dialog D2: |                       | Dialog D3:
  (V1, Tasks) |                       | (Task, V1 ref.)
              v                       v
        Agent B (AA)            Tool X (AT)
       video analysis       audio transcription
              ^                       |
              |                       v
              |                      T1
              |                       | (back to agent A)
              |                       |
              |                       |
              +------ Dialog D2 ----Agent A (FNE)
              (T1 provided to Agent B)
]]></artwork>
        <t>The example illustrates two cross-Dialog Resource patterns: V1 is consumed in both D2 and D3, while T1 is produced in D3 and subsequently consumed in D2. Resources may be transferred through application protocols, as with V1 in D2, or accessed through references, as with V1 in D3. The Resource Layer provides a logical model for identifying and relating these Resources across Dialogs, independently of how they are physically stored or accessed. Retained Event content or records of application exchanges may also be represented as Resources and referenced later, including during context recovery.</t>
        <t>For Agent B to interpret T1 correctly, its application runtime needs to associate the transcript with V1 and the work being performed within the Activity. This becomes particularly important when Agent B is concurrently processing similar videos across different Activities. The relevant correlations include:</t>
        <artwork><![CDATA[
D2 delegated-from D1
D3 delegated-from D1
T1 derived-from V1
]]></artwork>
        <t>In this example, the application runtimes invoke DCMP through their local interfaces to establish and maintain these correlations as part of the Dialog-management state. DCMP exchanges the relevant management and correlation metadata among authorized endpoints, while the application protocols carry the video, transcript, and other application content. The runtime associated with Agent B can use the available correlation metadata and Resources to assemble the context supplied to Agent B.</t>
        <t>Protocol-local identifiers, such as an A2A <tt>contextId</tt> or a tool-specific request identifier, remain useful within their respective application interactions. However, these identifiers alone do not establish the cross-Dialog relationships or Resource provenance illustrated above. DCMP provides a common means of representing and maintaining these correlations across independently managed Dialogs, protocols, and administrative domains.</t>
      </section>
      <section anchor="cross-organization-operation">
        <name>Cross-Organization Operation</name>
        <t>The example of the previous section becomes architecturally more
interesting when its participants are operated by different
organizations:</t>
        <artwork><![CDATA[
User (AIE)      invokes Agent A (Organization 1)
Agent A (FNE)   Organization 1
Agent B (AA)    Organization 2
Tool X (AT)     Organization 3
]]></artwork>
        <t>Dialog D2, between Agent A and Agent B, and Dialog D3, between
Agent A and Tool X, cross organizational boundaries, while Dialog
D1 involves only the user and Organization 1.</t>
        <t>Each organization maintains its own local identifiers for the
portions of the Activity it can see as shown below:</t>
        <artwork><![CDATA[
Organization 1:
  activity_id = O1-17

Organization 2:
  A2A context = AB-92
  A2A task = TB-44

Organization 3:
  tool job = JOB-991
]]></artwork>
        <t>In architectural terms, O1-17 is Organization 1's local handle for
the Activity, AB-92 is the Protocol-Local Context of Dialog D2,
TB-44 is a protocol-local Task identifier within D2, and JOB-991 is
Tool X's local identifier for the transcription Task in D3.</t>
        <t>These local identifiers need not be globally shared, unique, or even
syntactically alike. Correlation must therefore work without replacing
or exposing protocol-local state. The architecture separates:</t>
        <artwork><![CDATA[
logical correlation
]]></artwork>
        <t>from:</t>
        <artwork><![CDATA[
local identifier representation
]]></artwork>
        <t>A domain may maintain private mappings between the two.</t>
        <t>The Resource Layer is logical, not administrative: V1 may be stored by
Organization 1 and accessed by Tool X subject to that organization's
access and privacy policies.</t>
      </section>
    </section>
    <section anchor="dialogs-within-an-activity">
      <name>Dialogs Within an Activity</name>
      <t>As described in the Architectural Model, a single Activity can
involve multiple Dialogs.</t>
      <t>An Activity does not imply a common conversational context, participant
set, protocol instance, or lifecycle for its Dialogs. In other words:</t>
      <ul empty="true">
        <li>
          <t>An Activity groups multiple independently maintained Dialogs
for correlation purposes.</t>
        </li>
      </ul>
      <t>Dialogs in different branches may have explicit relationships without
direct communication or shared conversation. Common Activity membership
alone does not imply a relationship.</t>
      <t>An AIE may initiate multiple Activities to pursue a broader objective.
The AIE may preserve associations between those Activities locally and
coordinate their results or Resources across Activity boundaries.
Consequently, Dialogs belonging to different Activities may be
correlated indirectly through the AIE, without requiring a direct
Dialog-to-Dialog relationship or disclosure of the other Activity to
its participants. Having the same AIE does not, by itself, imply that
those Activities are related.</t>
      <t>This distinction supports delegation, specialization, cross-domain work,
and recovery without collapsing independent interactions into one
Dialog.</t>
      <t>The motivating example illustrates this property: Dialogs D1, D2,
and D3 are established by separate invocations, are maintained
independently, and may use different application protocols, yet all
belong to the same Activity.</t>
      <t>Multiple participants may jointly constitute an AIE when pursuing a common objective with a shared fulfillment condition. Conversely, independently initiated requests with distinct fulfillment conditions constitute separate Activities, even when they involve the same FNE, reuse the same Resources, or share downstream work. The completion of one Activity does not imply the completion of another.</t>
      <t>It is worth re-iterating that a dialog here refers to the application level interaction as well as the correllation level interaction via the Dialog Context Management Protocol that feeds the logical Dialog Management State (DMS) assocaited with the dialog.</t>
      <section anchor="dialog-management-state">
        <name>Dialog Management State</name>
        <t>Each Dialog is associated with one logical instance of Dialog Management State (DMS). DMS comprises two main elements:</t>
        <ul spacing="normal">
          <li>
            <t>Management Metadata: Information associated with the management of the Dialog, including its identity, lifecycle state, participant information, and relevant management-operation metadata.</t>
          </li>
          <li>
            <t>Correlation Metadata: Information describing the Dialog's relationships with its Activity, other Dialogs, Tasks, and Resources.</t>
          </li>
        </ul>
        <t>The following illustrates the structure of DMS:</t>
        <t><tt>text
                  Dialog D1
                      |
                   DMS(D1)
                      |
           +----------+----------+
           |                     |
     Management Metadata   Correlation Metadata
</tt></t>
        <t>For example, the DMS associated with Dialog D1 may contain the following information:</t>
        <t>```yaml
DMS(D1):
  management:
    dialog_id: D1
    lifecycle: ACTIVE</t>
        <artwork><![CDATA[
participants:
  - id: AgentA
  - id: AgentB
  - id: AgentC
    authentication:
      method: method-X
      verification_ref: authn-12345
    admission:
      authorized_by: AgentA
      decision_ref: authz-67890
]]></artwork>
        <t>correlations:
    - D1 belongs-to A1
    - D2 delegated-from D1</t>
        <t>optional_references:
    tasks:
      - task_id: T1
        event_ids: [E1, E2]
      - task_id: T2
    resources: [R1]
    protocol_local_context: local-ctx-17
```</t>
        <t>Note: This representation is illustrative and does not prescribe a wire format or a mandatory set of fields.</t>
        <t>In addition to Dialog identity and lifecycle information, DMS may contain participant information, selected correlations, and references to Tasks, Events, Resources, or protocol-local identifiers. These references identify the corresponding objects without carrying their content. The inclusion of such information depends on the correlations established for management and the applicable disclosure policies.</t>
        <t>The management metadata may also include information associated with authentication and authorization. For example, when Agent C joins D1, its admission may involve authentication through an existing security mechanism and authorization by an entity with the appropriate authority. DMS may retain the authentication method, a reference to the verification process, and the corresponding authorization decision. Similarly, a lifecycle change may be associated with the identity of the participant that authorized it and a reference to the relevant authorization decision. Such information provides a record of the management operation without incorporating credentials or the underlying security exchanges into DMS.</t>
        <t>The dialog-context-management-protocol (DCMP) propagates the exchanges needed to
establish and maintain DMS. A successful operation may change Dialog
lifecycle state, participant membership, or managed correlations.
Requests, acknowledgments, rejections, and authentication or
authorization-related exchanges may also be needed, but do not
necessarily modify DMS. The protocol records or communicates the
relevant management outcome; it does not perform the application's work to enforce those management decisions. For example, a terminiation of a task is reflected as a task status and lifecycle change in the DMS. However, that does not mean that the agent handling the task has stopped working on that task.</t>
        <t>For example, consider D1, initially established between Agents A and B. During the interaction, a relationship with D2 is established, Agent C joins after successful admission, Agent B leaves, and D1 is eventually suspended:</t>
        <artwork><![CDATA[
  Establish D1
  Participants: A, B
  Lifecycle: ACTIVE
       |
       v
  Establish correlation
  D2 delegated-from D1
       |
       v
  Authenticate and authorize Agent C
  Agent C joins D1
  Participants: A, B, C
       |
       v
  Agent B leaves D1
  Participants: A, C
       |
       v
  Authorized lifecycle update
  D1 becomes SUSPENDED
]]></artwork>
        <t>Throughout these changes, D1 retains its identity and associated logical DMS. The protocol carries the exchanges needed to modify DMS, while DMS reflects the resulting management and correlation state. Implementations may maintain the current state, a history of management changes, or both.</t>
        <t>A DMS may have multiple distributed representations maintained by participating entities. These representations need not be identical, as correlation information and certain management metadata may be selectively disclosed. Correlations maintained privately by a participant do not automatically become part of the Dialog's shared DMS.</t>
        <t>DMS does not contain application message content, Resource content, or agent-internal memory. However, it may maintain identifiers and references to Tasks, Events, and Resources associated with the Dialog, allowing relevant portions of its interaction history to be identified. Where the corresponding content or interaction records are retained as Resources in the Resource Layer, these references may support their subsequent retrieval, subject to applicable access controls.</t>
        <t>Application protocols carry the interactions and content used to accomplish the Dialog's objective. Local bindings associate relevant application identifiers and state with the Dialog and its DMS; these bindings need not be stored in DMS or exchanged with other participants.</t>
        <t>The companion dialog-management protocol specifies the applicable information elements, operations, and mechanisms for maintaining and recovering DMS across participants.</t>
        <t>Note: In the rest of the document, saying Agent X or participant Y sees this aspect about the dialog context, we refer to the DMS instance associated with the logical dialog that participant is part of.</t>
      </section>
      <section anchor="reasons-for-creating-a-new-dialog">
        <name>Reasons for Creating a New Dialog</name>
        <t>New Dialogs routinely arise as an interaction wave expands through
delegation, specialization, tools, or recovery. For example:</t>
        <ul spacing="normal">
          <li>
            <t>Delegation: An agent may delegate part of its work to another
agent.</t>
          </li>
          <li>
            <t>Specialization: A participant may invoke a specialist because the
current participants lack a required capability. For example, if
Agent B cannot understand language L, it invokes an agent capable
of language L and creates a new Dialog with it.</t>
          </li>
          <li>
            <t>Tool invocation: Invoking a tool establishes a Dialog with a terminal logical endpoint in the Activity's interaction wave.</t>
          </li>
          <li>
            <t>Administrative Separation: A new Dialog may be created when
execution crosses into another organization, vendor, security
domain, or policy boundary.</t>
          </li>
          <li>
            <t>Failure Recovery: A replacement Dialog may be created after the
failure of a participant, route to a participant, the transport, or an intermediary entity. For
example, if Agent B fails mid-Activity, a replacement Agent B' is
started and opens a new Dialog with Agent A to continue from
where they stopped.</t>
          </li>
          <li>
            <t>Privacy Separation: A participant may intentionally create a
separate Dialog so that only a subset of Activity information is
visible to the downstream participant. The same two participants
may even run multiple Dialogs in parallel under the same Activity,
each exposing a different subset of Activity information.</t>
          </li>
        </ul>
        <t>The motivating example already exhibits several of these reasons:
D2 arises from delegating video analysis to a specialist, D3 from
tool invocation, and both Dialogs cross administrative boundaries.</t>
        <t>Applications decide when to establish Dialogs. The architectural concern
is correlating each Dialog with its Activity and relevant lineage, where
needed to capture causality.</t>
      </section>
      <section anchor="dialog-independence">
        <name>Dialog Independence</name>
        <t>Each Dialog is independently maintained, with its own logical DMS.
A shared Activity or participant set does not merge those states.</t>
        <t>In the motivating example, D2 and D3 both belong to the same
Activity:</t>
        <artwork><![CDATA[
Activity: analyze video V1

D2:
  Agent A <-> Agent B

D3:
  Agent A <-> Tool X
]]></artwork>
        <t>D2 and D3 may differ in:</t>
        <ul spacing="normal">
          <li>
            <t>Participants: Agent B versus Tool X;</t>
          </li>
          <li>
            <t>Protocol (e.g., HTTP vs MoQ) and transport (e.g., TCP  vs UDP);</t>
          </li>
          <li>
            <t>Protocol-local identifiers: A2A context AB-92 and Task TB-44 in
D2, tool job JOB-991 in D3;</t>
          </li>
          <li>
            <t>Resources referenced: V1 and T1 in D2, but V1 by reference in D3;</t>
          </li>
          <li>
            <t>Message history;</t>
          </li>
          <li>
            <t>Lifecycle state: D2 is long-running, D3 is one-shot;</t>
          </li>
          <li>
            <t>Privacy policy and authorization level;</t>
          </li>
          <li>
            <t>Administrative domain: Organization 2 versus Organization 3.</t>
          </li>
        </ul>
        <t>Therefore:</t>
        <artwork><![CDATA[
D2 != D3
]]></artwork>
        <t>even though both belong to the same Activity.</t>
        <t>Dialog independence extends to the same pair of participants. Two
entities may maintain multiple concurrent Dialogs with each other:
one per Activity on which they both work, or several within a
single Activity when privacy or task separation calls for it.
Suppose that, alongside D2, Agent A opens a clarification
dialog with Agent B:</t>
        <artwork><![CDATA[
Activity: analyze video V1

D2:
  Agent A <-> Agent B      (video-analysis Tasks)

D4:
  Agent A <-> Agent B      (clarification dialog)
]]></artwork>
        <t>Although D2 and D4 share participants, they have distinct local states
and potentially different disclosures:</t>
        <artwork><![CDATA[
D2 != D4
]]></artwork>
        <t>A Dialog is identified by its own identity and the Activity it
belongs to, never by its participant set.</t>
        <t>A participant MUST NOT assume that another Dialog participating in
the same Activity shares the same local state, and MUST NOT assume
that its Dialog with a given counterpart is the only one.</t>
      </section>
      <section anchor="multi-party-dialogs">
        <name>Multi-Party Dialogs</name>
        <t>A Dialog may involve more than two participants sharing a common logical Dialog context and lifecycle. This does not require every participant to communicate directly with every other participant or have visibility into all application exchanges. For example, Agent A, Agent B, and Agent C may participate in a single Dialog, D1, while their application runtimes exchange messages through Agent B acting as an orchestrator:</t>
        <artwork><![CDATA[
              Logical Dialog D1
  +------------------------------------+
  |                                    |
  |  Agent A <--> Agent B <--> Agent C |
  |                                    |
  |  Participants: {A, B, C}           |
  |         DMS(D1)                    |
  +------------------------------------+
]]></artwork>
        <t>The same application communication topology may also involve two distinct pairwise Dialogs:</t>
        <artwork><![CDATA[
  Agent A <--> Agent B <--> Agent C
             D2          D5

     DMS(D2)             DMS(D5)
]]></artwork>
        <t>In this case, D5 may have been established through delegation from D2:</t>
        <artwork><![CDATA[
D5 delegated-from D2
]]></artwork>
        <t>The distinction between these arrangements lies in their logical Dialog membership and management state, rather than the underlying application communication topology. A multi-party Dialog has one logical identity and associated DMS, whereas correlated pairwise Dialogs retain separate identities, management states, and lifecycles.</t>
        <t>This distinction also affects Dialog-management authority. In the multi-party arrangement, Agent C may join D1 and be granted authority to perform certain management operations, such as terminating the Dialog, according to an agreed authority policy. In the pairwise arrangement, Agent C participates in D5 but not D2. Its participation in D5 does not confer management authority over D2, regardless of the correlation between the two Dialogs. Any such authority would require separate authorization.</t>
        <t>A multi-party Dialog's participant set may change over time:</t>
        <artwork><![CDATA[
Initially:       {Agent A, Agent B}
Agent C joins:   {Agent A, Agent B, Agent C}
Agent B leaves:  {Agent A, Agent C}
]]></artwork>
        <t>The Dialog retains its identity and associated logical DMS as participants join or leave. Each participant's Dialog-Management Protocol Endpoint may maintain an authorized local representation of that DMS, and these representations need not be identical. Admission of a new participant may involve authentication and authorization, followed by propagation of the management and correlation metadata that the participant is authorized to access.</t>
        <t>Management authority may be assigned to the Dialog Originator or shared among authorized participants according to an agreed policy. Such authority may be scoped to particular operations and updated during the Dialog's lifetime. The DMS reflects applicable membership, lifecycle, and authorization information, while DCMP Endpoints process management operations according to the established authority policy. The application runtimes invoke these operations through local interfaces; their effects on application Task execution remain application-specific.</t>
        <t>A departing participant no longer receives future DMS updates by virtue of its former membership. Membership changes do not, by themselves, alter the Dialog's identity or invalidate its existing correlations, although associated permissions and correlation-maintenance responsibilities may need to be updated.</t>
        <t>This architecture supports both multi-party Dialogs and multiple correlated pairwise Dialogs without prescribing their underlying application communication topology. The companion dialog-management protocol defines the relevant membership, authority, propagation, and state-maintenance procedures.</t>
      </section>
      <section anchor="dialog-lineage">
        <name>Dialog Lineage</name>
        <t>Dialogs can be related through explicit lineage. For example:</t>
        <artwork><![CDATA[
D5 delegated-from D2
]]></artwork>
        <t>indicates that D5 exists because work from D2 was delegated into a
new Dialog. A new Dialog may carry forward work or correlation context from a
previous Dialog:</t>
        <artwork><![CDATA[
D2' continuation-of D2
]]></artwork>
        <t>Here D2 and D2' have distinct logical identities. This relationship
does not represent resuming D2 with its original identity. A new
Dialog may instead supersede an earlier Dialog:</t>
        <artwork><![CDATA[
D2' replaces D2
]]></artwork>
        <t>The two relationships describe different associations and may coexist.
Their semantics are further discussed under "Recovery and Continuation".</t>
        <t>This architecture distinguishes:</t>
        <artwork><![CDATA[
dialog identity
]]></artwork>
        <t>from:</t>
        <artwork><![CDATA[
dialog relationship
]]></artwork>
        <t>Two Dialogs remain independently identified even when one was
created from another.</t>
      </section>
      <section anchor="hidden-delegation-and-partial-visibility">
        <name>Hidden Delegation and Partial Visibility</name>
        <t>A downstream Dialog need not be disclosed upstream. Suppose Agent B
invokes Agent C:</t>
        <artwork><![CDATA[
Agent A <------> Agent B <------> Agent C
           D2               D5
             <------------->
                Delegation
]]></artwork>
        <t>Focusing on this delegation, the resulting visibility may be:</t>
        <artwork><![CDATA[
Local correlation view for Agent A:
  Agent B
  D2

Local correlation view for Agent B:
  Agent A
  Agent C
  D2
  D5
  D5 delegated-from D2

Local correlation view for Agent C:
  Agent B
  D5
]]></artwork>
        <t>In the above example, Agent A does not know that Agent C exists. Agent C does not know that Agent A exists. In other words, the visibility level is a decision that participants make.</t>
        <t>Such hidden delegation is common across organizational, vendor, trust,
and privacy boundaries. The architecture separates:</t>
        <artwork><![CDATA[
relationship exists
]]></artwork>
        <t>from:</t>
        <artwork><![CDATA[
relationship is disclosed
]]></artwork>
        <t>A relationship can be retained locally by an intermediary without
being propagated in full. For example, agents inside an
organization need to know only that edge agent Y can help achieve
objective X. Agent Y connects to agent Z in another organization;
agent Z needs to know only that agent Y exists and is asking for V, 
not who asked Y. Yet agent Y must know that responses from agent Z
relate to requests from internal agents.</t>
      </section>
      <section anchor="dialog-topologies">
        <name>Dialog Topologies</name>
        <t>An Activity's Dialogs may branch, chain, and converge.</t>
        <t>A participant may independently invoke another entity, so Activity
topology may emerge from decentralized decisions.</t>
        <t>The following scenarios are a few possible examples of how topologies of an Activity may extend.</t>
        <section anchor="branching">
          <name>Branching</name>
          <t>A participant in a Dialog can create several downstream Dialogs with other new participants as need arises. Agent B may invoke both Agent C and Agent E to pursue independent parts of its
work:</t>
          <artwork><![CDATA[
            
         Activity A1
              |
           D1 |
              v     D2, D4
           Agent A <------> Agent B
              |               /\
           D3 |           D5 /  \ D6
              v             /    \
            Tool Y         v       v
                        Agent C   Agent E
]]></artwork>
          <t>with the relationships:</t>
          <artwork><![CDATA[
D5 delegated-from D2
D6 delegated-from D2
]]></artwork>
          <t>D5 and D6 are independent: they may execute concurrently, use
different protocols, process different Resources, terminate
independently, and expose different subsets of upstream context.
Agent C and Agent E do not need to know of each other's existence.</t>
        </section>
        <section anchor="chaining">
          <name>Chaining</name>
          <t>A downstream participant can itself create further Dialogs. If
Agent C invokes Agent E, the Activity gains another level:</t>
          <artwork><![CDATA[
            
         Activity A1
              |
           D1 |
              v     D2, D4
           Agent A <------> Agent B
              |               /\
           D3 |           D5 /  \ D6
              v             /    \
            Tool Y         v      v
                        Agent C  Agent E
                           ^        ^
                           |   D7   |
                           +--------+
]]></artwork>
          <t>yielding:</t>
          <artwork><![CDATA[
D5 delegated-from D2
D7 delegated-from D5
]]></artwork>
          <t>The Activity therefore forms a delegation tree or, more generally,
a graph. No participant is required to maintain the complete
ancestry: Agent C may know that D5 has an opaque upstream origin
without knowing the identity of Agent A or of D2.</t>
        </section>
        <section anchor="converging-dialogs">
          <name>Converging Dialogs</name>
          <t>Separate branches can later contribute to another Dialog. If Agent
B invokes an aggregator, Agent F, to combine the results produced
independently in D5 and D6:</t>
          <artwork><![CDATA[
                D2
               /  \
              v    v
             D5    D6
              \    /
               \  /
                v
                D8
]]></artwork>
          <t>then D8 is correlated with more than one upstream Dialog:</t>
          <artwork><![CDATA[
D8 aggregated-from D5
D8 aggregated-from D6
]]></artwork>
          <t><tt>aggregated-from</tt> indicates that D8 was created to aggregate or
consume results produced independently in multiple upstream
Dialogs. It is a multi-parent Dialog relationship, distinct from
the single-parent <tt>delegated-from</tt>. Where only correlation is
asserted and no aggregation causality is intended, the weaker
<tt>related-to</tt> relationship may be used instead.</t>
        </section>
        <section anchor="the-dialog-graph">
          <name>The Dialog Graph</name>
          <t>The set of Dialogs participating in an Activity can therefore be
modeled as a directed graph:</t>
          <artwork><![CDATA[
G_D = (D, R_D)
]]></artwork>
          <t>where D is the set of Dialogs and R_D is the set of typed
relationships among them. Examples may include:</t>
          <artwork><![CDATA[
delegated-from
aggregated-from
continuation-of
related-to
replaces
]]></artwork>
          <t>The graph may branch, converge, and evolve over time, and no
participant is required to maintain it in full.</t>
        </section>
      </section>
      <section anchor="independent-dialog-lifecycle">
        <name>Independent Dialog Lifecycle</name>
        <t>Related Dialogs may hold different lifecycle states simultaneously. Each Dialog's lifecycle state is reflected in its own DMS, and a lifecycle transition in one Dialog does not, by itself, change the lifecycle state of another. The states below are illustrative; the dialog-management protocol defines the exhaustive list of lifecycle states of a Dialog.</t>
        <artwork><![CDATA[
D2 ACTIVE
D3 COMPLETED
D5 SUSPENDED
]]></artwork>
        <t>Termination of D5 does not imply termination of D2, and failure of
D5 does not necessarily invalidate D2 or D3.</t>
        <t>This distinction matters for failure recovery, long-running
activities, asynchronous delegation, partial completion, and retry
behavior.</t>
        <t>Related Dialogs can be correlated (they belong to the same Activity
and may be linked through lineage) yet maintain independent lifecycle
states. A transition in one Dialog does not inherently impose the same
transition on another Dialog or its Tasks. However, changes in
requirements, dependencies, or security and authorization conditions
may have consequences for related work. Where needed, sufficient
Correlation Metadata is preserved and selectively propagated to
identify affected Dialogs and Tasks and associate any resulting
changes with their causes.</t>
        <t>Lifecycle coupling, for example:</t>
        <artwork><![CDATA[
if D2 terminates, D5 should terminate
]]></artwork>
        <t>is not implied by this architecture. The actual consequences for
related work depend on the applicable protocols, policies, and
application requirements. This architecture concerns their correlation,
not the operational transitions themselves. A suspended Dialog may be
resumed, or a sub-dialog may be created as a child of it to resume
partial operations, independently of other Dialogs.</t>
      </section>
      <section anchor="recovery-and-continuation">
        <name>Recovery and Continuation</name>
        <t>Dialogs may be long-lived, spanning extended periods of activity and inactivity, multiple transport connections, or participant restarts. A temporary loss of connectivity, failure of a participant, or expiration of an underlying protocol session does not, by itself, terminate the logical Dialog. Recovery therefore requires distinguishing continuity of the Dialog's identity and management state from continuity of its communication sessions and application work.</t>
        <t>When the existing Dialog D2 is resumed, its logical identity remains
D2, even if its transport connection, protocol session, or
protocol-local identifiers change:</t>
        <artwork><![CDATA[
Before interruption:  D2
After resumption:     D2     (same logical Dialog)
]]></artwork>
        <t>No <tt>continuation-of</tt> relationship between distinct Dialogs is needed in this case, because no new logical Dialog has been established. D2 retains its identity and associated logical DMS, even if local representations of that state must be recovered or synchronized. Correlations needed to maintain coherent context must remain available or be recoverable within the applicable disclosure scope.</t>
        <t>Alternatively, recovery may involve establishing a new Dialog D2' with a distinct logical identity and its own DMS. D2' does not automatically inherit the management state or correlations of D2. Any relationships or metadata carried forward are established as part of the continuation or replacement process. Three situations are possible:</t>
        <ul spacing="normal">
          <li>
            <t>Continuation without replacement: D2' carries forward work or
correlation context associated with D2, but does not necessarily
supersede D2.  </t>
            <artwork><![CDATA[
D2' continuation-of D2
]]></artwork>
          </li>
          <li>
            <t>Replacement without continuation: D2' supersedes D2 as a Dialog,
for example when the original objective is attempted again without
carrying forward D2's previous execution context.  </t>
            <artwork><![CDATA[
D2' replaces D2
]]></artwork>
          </li>
          <li>
            <t>Continuation and replacement: D2' both carries forward work or
context associated with D2 and supersedes D2 as a Dialog.  </t>
            <artwork><![CDATA[
D2' continuation-of D2
D2' replaces D2
]]></artwork>
          </li>
        </ul>
        <t><tt>continuation-of</tt> expresses that a new Dialog carries forward work associated with an earlier Dialog, including work that has not yet started. Relevant context or correlations may also be carried forward. This relationship does not, by itself, imply taking over responsibility for the earlier Dialog's overall objective.</t>
        <t><tt>replaces</tt> expresses that a new Dialog supersedes an earlier Dialog as the primary Dialog through which the earlier Dialog's objective is pursued. The two relationships are not mutually exclusive.</t>
        <t>Neither relationship automatically triggers Task lifecycle transitions, terminates the original Dialog, or transfers all its correlations. Where only selected work is carried forward without assuming responsibility for the earlier Dialog's overall objective, <tt>continuation-of</tt>, together with relevant Task or Resource relationships, may express that narrower continuity.</t>
        <t>Historical associations remain meaningful following continuation or replacement. For example, if D3 was delegated from D2, that fact does not disappear when D2' replaces D2. If D2' also needs to correlate subsequent work with D3, the necessary associations must be preserved or established; they cannot be inferred solely from <tt>D2' replaces D2</tt>.</t>
        <t>Communication recovery and correlation recovery are distinct. A transport may reconnect while a participant has lost the mappings needed to correlate D2 with related Dialogs, Tasks, or Resources. Conversely, those mappings may remain available while a participant or its transport path is unreachable. Resuming the same Dialog identity also does not, by itself, guarantee recovery of its application Task state or of the outcome of an interrupted operation. An uncertain operation outcome is not itself a correlation failure if the operation remains correctly associated with its relevant Dialog and Task.</t>
        <t>Within an established protocol-managed correlation scope, a
participant remains responsible for the correlations it undertook to
maintain through an interruption or recovery. Where necessary
correlations cannot be preserved or recovered, that limitation must
be distinguishable from successful correlation maintenance, subject
to the detection and reporting capabilities of the relevant protocol.
This does not imply visibility into unregistered downstream Dialogs or
perfect attribution of a recovery failure.</t>
        <t>Recovery may involve several distinct layers:</t>
        <ul spacing="normal">
          <li>
            <t>Dialog-management and correlation state: preservation or
re-establishment of the Dialog's DMS representation and relevant
shared correlations, together with any participant-local mappings
needed for cross-Dialog Task and Resource association. Restoring a
DMS view does not imply recovering the full Activity Context.</t>
          </li>
          <li>
            <t>Application-protocol state: the sessions, Tasks, and operation
outcomes maintained by protocols such as A2A and MCP, which may
continue independently of a transport connection.</t>
          </li>
          <li>
            <t>Transport connectivity: re-establishment or migration of a
connection or path through the underlying transport mechanisms.</t>
          </li>
          <li>
            <t>Application-content recovery: retrieval of retained Event records,
messages, or Resources when the application needs them to reconstruct
interaction history or rehydrate its LLM context. DMS may supply
useful references and provenance through local bindings, but neither
DMS nor the Resource Layer guarantees that content was retained or
that an agent's previous internal state can be restored.</t>
          </li>
        </ul>
        <t>The architecture identifies these distinct concerns and their
correlation implications, without specifying recovery procedures.
Open protocol-design questions include how lost mappings are recovered
or rebuilt, how peers distinguish resumption from new Dialog creation,
how correlation is handled when an intermediary disappears, and how
unreachable participants or uncertain operation outcomes are reported.
These questions are to be addressed in the dialog-management protocol
draft, in coordination with relevant IETF working groups (for example,
SIP Core for Dialog semantics, QUIC for transport migration, and TLS,
WIMSE, and OAuth for session, identity, and delegated authority) and
with the application protocols to which the protocol binds, such as
A2A and MCP.</t>
        <t>The following matrix summarizes the recovery cases at the architecture
level; it is a set of questions to examine, not a failure taxonomy.
Propagation failure modes are described under "Propagation Failure
Modes" (§8.12).</t>
        <table>
          <thead>
            <tr>
              <th align="left">Case</th>
              <th align="left">Logical Dialog</th>
              <th align="left">Mapping state</th>
              <th align="left">What to examine</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Reconnect</td>
              <td align="left">Same Dialog D</td>
              <td align="left">Preserved</td>
              <td align="left">Whether participants can resume the existing correlation.</td>
            </tr>
            <tr>
              <td align="left">Reconnect with state loss</td>
              <td align="left">Same intended Dialog D</td>
              <td align="left">Lost</td>
              <td align="left">Whether they can detect or re-establish the association.</td>
            </tr>
            <tr>
              <td align="left">Continue</td>
              <td align="left">New Dialog D′ (continuation)</td>
              <td align="left">Reference to the earlier Dialog available</td>
              <td align="left">Whether D′ is clearly related but distinct.</td>
            </tr>
            <tr>
              <td align="left">Replace</td>
              <td align="left">New Dialog D″ (replacement)</td>
              <td align="left">Earlier state partly available</td>
              <td align="left">What remains related and what is explicitly superseded.</td>
            </tr>
            <tr>
              <td align="left">Continue and replace</td>
              <td align="left">New Dialog D′</td>
              <td align="left">Reference plus partial earlier state</td>
              <td align="left">Whether D′ both carries work forward and supersedes the earlier Dialog.</td>
            </tr>
            <tr>
              <td align="left">Peer unreachable</td>
              <td align="left">D or successor unknown</td>
              <td align="left">Possibly stale</td>
              <td align="left">What can be reported without inferring the root cause.</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="interruptions-and-barge-in">
        <name>Interruptions and Barge-in</name>
        <t>Work in progress can be interrupted. A barge-in is new input introduced while work is underway that may
modify, redirect, or interrupt it. It does not automatically determine
whether Tasks are modified, created, or replaced, or whether another
Dialog is established.</t>
        <t>The running Activity of "analyze the video" shows the pattern. The user asked Agent A to
analyze video V1; Agent A delegated the video-analysis Tasks to
Agent B and the transcription Task to Tool X, and work is in
progress. Ten minutes in, the user barges in and tells Agent A to
analyze only the last 50% of the video. In this example, no new
entity is invoked: the same Activity and Dialogs remain, while the
requirement governing the work changes.</t>
        <t>Two aspects of this barge-in are relevant to correlation:</t>
        <ul spacing="normal">
          <li>
            <t>First, the new requirement must be associated with the work it
affects. In this example, Agent B's Task is modified to analyze only
the last 50% of the video. Other barge-ins could instead result in
new or replacement Tasks, suspension, cancellation, or no change to
particular Tasks. Whether Tool X's transcription Task is also affected
is an application decision: the existing transcript may still cover
the full video, and Agent B may simply use its relevant part, or
Tool X's Task may be narrowed to match.</t>
          </li>
          <li>
            <t>Second, the input that carries the barge-in may arrive in a
different modality from the original requirement. The original
requirement reached Agent A as text; the barge-in reached it as
voice. In this example, the spoken correction is a Resource used as
input to the affected Task:</t>
          </li>
        </ul>
        <artwork><![CDATA[
AX1 input-to TB1
]]></artwork>
        <t>The correction is not a standalone requirement: "analyze only the
last 50%" is meaningful only relative to the original requirement it
narrows. Recording that the spoken correction modifies the original
requirement, rather than leaving the two statements unconnected, is
what lets any participant determine which requirement governs the
work after the interruption. How that association is encoded is left
to the dialog-management protocol.</t>
        <t>A barge-in may have several correlation-relevant aspects, which
are not mutually exclusive:</t>
        <ul spacing="normal">
          <li>
            <t>a lifecycle change in an affected Dialog, for example from active
to interrupted;</t>
          </li>
          <li>
            <t>the establishment of a related Dialog, such as a clarification
side-channel; and</t>
          </li>
          <li>
            <t>Resource provenance or binding information when the new input uses
a different modality or changes the requirement associated with a Task.</t>
          </li>
        </ul>
        <t>Which aspects arise is an application decision. The architectural
concern is that the initiating input, affected Dialogs, Tasks, and
Resources, and any resulting changes can be correctly associated;
it does not prescribe the operational response.</t>
        <t>The user interruption is therefore treated here as a correlation-relevant occurrence; the Task modifications, creations, replacements, suspensions, or cancellations discussed in this section are illustrative application responses. The minimal question is which Dialog, affected Task or requirement, input or derived Resource, and local identifier must remain associated across the interruption and, where applicable, the modality change.</t>
        <t>A barge-in can also affect in-flight or subsequent Events within an
affected Task. Events remain local to their Tasks and do not acquire
independent lifecycle states. Where necessary, their association with
the affected Task and relevant requirements must remain interpretable.</t>
        <t>A barge-in may affect several related Dialogs. Suppose Agent B has
created D5 with Agent C, Agent C has created D7, and D8 aggregates D5
and D6. In this example:</t>
        <ul spacing="normal">
          <li>
            <t>D5 is interrupted: its in-flight Task is modified, because the
requirement it was pursuing has changed.</t>
          </li>
          <li>
            <t>D7, which Agent C chained from D5, is suspended: the work it was
doing served the requirement that has just changed.</t>
          </li>
          <li>
            <t>D8, which aggregates results produced independently in D5 and D6,
is terminated: the Task that required D8 to aggregate from
upstream Dialogs was replaced by the barge-in, so D8's reason for
existence is gone and its awaiting Tasks are cancelled.</t>
          </li>
          <li>
            <t>D6, which runs independently of D5, is untouched.</t>
          </li>
        </ul>
        <t>One interruption readjusted work in four Dialogs: a lifecycle
transition and Task modification in D5, a suspension in D7, and a
termination in D8. Each is an explicit
fact of the model, tied back to the interruption through the lineage
relationships that link the four Dialogs.</t>
        <t>These questions are candidates for coordination with transport-
oriented work (for example, WebTransport, WebRTC, and MoQ) and with
the dialog-management protocol. Open questions include:</t>
        <ul spacing="normal">
          <li>
            <t>how lifecycle transitions behave when interruptions occur
mid-course;</t>
          </li>
          <li>
            <t>how changes resulting from a barge-in are associated with affected
Dialogs, Tasks, and Resources;</t>
          </li>
          <li>
            <t>how affected ongoing or subsequent Events remain interpretable
within the relevant Task;</t>
          </li>
          <li>
            <t>how the association between the barge-in input and the requirement
it affects is preserved across modality changes; and</t>
          </li>
          <li>
            <t>how far correlation information about the effects of a barge-in
needs to travel through the Activity graph.</t>
          </li>
          <li>
            <t>How to inforce a barge-in from an application prespective or is it an out-of-scope item.</t>
          </li>
        </ul>
      </section>
      <section anchor="reuse-across-dialogs">
        <name>Reuse Across Dialogs</name>
        <t>The same Resource can appear in several Dialogs. In the running
example, V1 is used by both D2 and D3, and T1, produced in D3, is
consumed in D2 and later referenced in D5 as provenance:</t>
        <artwork><![CDATA[
Resource V1                 Resource T1
  |                           |
  +--> D2                     +--> D2
  |                           |
  +--> D3                     +--> D5
]]></artwork>
        <t>Sharing a Resource does not imply identical local interpretation:</t>
        <artwork><![CDATA[
D2:
  T1 analyzed as primary text input

D5:
  T1 retained only as provenance
]]></artwork>
        <t>Resource identity remain stable while interpretation is local.
These Dialog-local interpretations are Resource Bindings, and roles can change as the Activity
executes and delegations happen.</t>
        <t>Sharing also does not imply the same Dialog. For example, that D2 and D5 both
reference V1 does not imply:</t>
        <artwork><![CDATA[
D2 == D5
]]></artwork>
        <t>or that Agent A, Agent B, and Agent C share one conversation.
Resource correlation and Dialog correlation are separate concerns:
a reference identifies the same Resource across Dialogs, while the
interpretation of that Resource remains local to each Dialog in
which it is used.</t>
      </section>
      <section anchor="the-running-example-assembled">
        <name>The Running Example, Assembled</name>
        <t>The concepts introduced in this section can be assembled into a
single picture of the running example. The figure below unifies the
two views of the Architectural Model: the invocation view of the
interaction wave, instantiated with the example's participants and
roles, framed by the Activity root above and the Resource Layer
below, as in the containment view.</t>
        <artwork><![CDATA[
                   Activity: analyze video V1
                                |
                           User (AIE)
                                |
                                | Dialog D1 (Activity, V1)
                                v
                          Agent A (FNE)
                       + -----------------+
         Dialog D2     |                  |   Dialog D3
      delegated-from D1|                  | delegated-from D1
           task(s)     v                  v  task (one-shot)
                 Agent B (AA)        Tool X (AT)
                       +
      Dialog D5        |
      delegated-from D2|
      task(s)          |
                        v
                  Agent C (AA)
               (invisible to Agent A)

      +----------------------------------------------+
      |               Resource Layer                 |
      |  V1:  transferred to D2; referenced by D3    |
      |  T1:  produced in D3; consumed in D2;        |
      |       referenced as provenance in D5         |
      |  AX1: barge-in input (voice); input-to TB1   |
      +----------------------------------------------+
]]></artwork>
        <t>The figure exhibits, in one place, most of the properties
established in this section:</t>
        <ul spacing="normal">
          <li>
            <t>Branching: D2 and D3 are both delegated from D1.</t>
          </li>
          <li>
            <t>Chaining: D5 is delegated from D2, extending the wave below
Agent B.</t>
          </li>
          <li>
            <t>Hidden delegation: D5 and Agent C are invisible to Agent A.</t>
          </li>
          <li>
            <t>Independent lifecycle: the Dialogs need not share state; D3
completes with its one-shot Task while D2 remains active and D5
may be suspended.</t>
          </li>
          <li>
            <t>Resource reuse: V1 is shared by D2 and D3, and T1, produced in
D3, is consumed in D2 and referenced as provenance in D5.</t>
          </li>
          <li>
            <t>Interruption: a barge-in (AX1, voice) narrows the objective of
TB1 mid-course; its effects travel through lineage to the Dialogs
that depend on it.</t>
          </li>
        </ul>
        <t>Every edge is an invocation, every Dialog is independently
maintained, and every correlation is an explicit relationship. Thus
D1, D2, D3, and D5 each have distinct logical DMSs, while the
participant retaining the D5--D2 delegation may keep that assertion
private rather than adding it to either Dialog's shared DMS.
This is the structure that the later discussion of context
propagation must preserve.</t>
      </section>
    </section>
    <section anchor="tasks-within-a-dialog">
      <name>Tasks Within a Dialog</name>
      <t>Tasks are bounded units of work within Dialogs. An invocation
establishes a Dialog but does not necessarily create a Task. A Dialog
may contain zero or more Tasks, performed sequentially, in parallel, or
through Assistant Tool interactions.</t>
      <t>The previous section zoomed in from Activities to Dialogs. This
section zooms in one more level, to the Tasks inside each Dialog.
It examines Task identity, states, cross-Dialog relationships,
and the effects of failures and privacy boundaries.</t>
      <t>The model defines the relevant semantics; protocol documents determine
their implementation.</t>
      <section anchor="task-identity-local-and-global">
        <name>Task Identity: Local and Global</name>
        <t>Tasks use identifiers defined by the local application protocol (such as
an A2A <tt>taskId</tt>). Such identifiers are not assumed to be meaningful or
resolvable outside their Dialog.</t>
        <t>Unlike a Resource that needs stable identity across boundaries, a Task
need not have a universal identifier. Its cross-Dialog association may
be asserted by a participant that can resolve the relevant local Tasks. Whether to standardize a global Task identifier remains a protocol-design decision.</t>
      </section>
      <section anchor="task-states">
        <name>Task States</name>
        <t>Tasks have lifecycle states independent of their Dialog's state. The
following states are illustrative and are not prescribed for application
protocols. When Task-state information is used for interoperable
correlation, the dialog-management protocol determines which assertions
it supports and how they are represented.</t>
        <t>Progression states - a Task holds exactly one at a time:</t>
        <artwork><![CDATA[
defined       the Task exists; work has not begun
queued        the Task was accepted and is waiting behind
              other work
in-progress   work is in progress
awaiting      the Task cannot make progress on its own; it is
              blocked on something external, for example another
              Task's result, a decision, or an authorization
delegated     part of the work was passed to another Dialog;
              the Task awaits its result
awaiting-approval   the Task is blocked on a human decision
auth-required       the Task is blocked on additional
                    authorization
interrupted   work was paused or cut off; may resume
completed     the bounded work is done
failed        work ended without completing
timed-out     the Task exceeded its maximum duration
rejected      the work was declined before it began, for
              example out of scope or against policy
cancelled     the Task was ended administratively, for example
              by a revoked delegation
unknown       the state of the Task cannot be determined
]]></artwork>
        <t>Modifiers - facts about the Task that may persist alongside a
progression state:</t>
        <artwork><![CDATA[
modified      the objective or parameters of the Task changed
superseded    another Task replaces this one
]]></artwork>
        <t>Some states, such as completed, timed-out, rejected, or cancelled, may
be final. Retry behavior is an application decision.</t>
        <t>A one-shot Task with an Assistant Tool can pass through the whole
set in one exchange: defined on assignment, in-progress on
submission, completed on response.</t>
        <t>Structural relations such as delegation or replacement are generally
stable; lifecycle assertions such as completion and modification are
mutable and can become stale. Participant acting on an old copy can make
incorrect decisions, as discussed later under Stale Context.</t>
        <t>A Task has one progression state at a time; modifiers may coexist with
it. Thus a Task may be in-progress and modified without changing its
progression state.</t>
        <t>Lifecycle updates are also Correlation Metadata. "t_32 completed",
"t_21 modified", "t_15 superseded" are precisely the assertions
that may need to propagate between involved parties, in the
upstream direction alongside results and failure information, as
discussed later under Directional Propagation.</t>
      </section>
      <section anchor="task-independence">
        <name>Task Independence</name>
        <t>Each Task has its own lifecycle. A change to one does not automatically
change another, even within the same Dialog.</t>
        <t>Within a single Dialog, several Tasks can be in different states at
the same time:</t>
        <artwork><![CDATA[
t_12 in-progress
t_22 awaiting
t_32 completed
]]></artwork>
        <t>Completing, failing, or cancelling one Task does not automatically
change the other Tasks within its Dialog.</t>
        <t>Task independence also applies across Dialogs. Relationships such as
<tt>delegated-from</tt> or <tt>replaces</tt> record association; it does not couple their lifecycles, and it does
not cause a change in one Task to propagate to another. Dependent work changes only when its participants
decide or applicable requirements demand it.</t>
        <t>This permits partial completion, parallel work, and selective failure
within one Activity.</t>
        <t>As with Dialog lifecycle, a Task's lifecycle state is mutable and may
become stale; a participant acting on an old copy can make incorrect
decisions, as discussed later under Stale Context.</t>
      </section>
      <section anchor="task-relationships-across-dialogs">
        <name>Task Relationships Across Dialogs</name>
        <t>Examples of Task-level relationship types include:</t>
        <artwork><![CDATA[
delegated-from    t_12 delegated-from t_21
related-to        a weaker assertion of correlation, without
                  delegation causality
replaces          a Task supersedes another, typically a failed
                  or abandoned one
]]></artwork>
        <t><tt>delegated-from</tt> is the primary cross-Dialog relationship: it
asserts that one Task exists because of a requirement found in
another. A Dialog may contain many Tasks while only one of them
causes a downstream delegation; <tt>delegated-from</tt> records which one
(see "Task Lineage").</t>
        <t>At Task granularity, <tt>replaces</tt> expresses that one Task supersedes
another. Replacing a Dialog does not automatically replace all of
its Tasks. When a new Task actually supersedes an original Task, its
relationship can be expressed explicitly:</t>
        <artwork><![CDATA[
t_12' replaces t_12
]]></artwork>
        <t>Dependency on an existing result may be inferred from Resource
provenance; awaiting a future result is Task state rather than a new
relationship type.</t>
        <t>This avoids introducing a separate verb for every application
dependency.</t>
      </section>
      <section anchor="task-topologies">
        <name>Task Topologies</name>
        <t>Dialog and Task lineage are related but distinct. Creating a Dialog does
not require creating a Task or Task-to-Task association. Where
delegation originates in a Task, its Task relationship can be
represented explicitly:</t>
        <artwork><![CDATA[
D5 delegated-from D2       (Dialog level)
t_15 delegated-from t_22   (Task level, when applicable)
]]></artwork>
        <t>The Dialog and Task graphs are related but need not mirror each other:</t>
        <ul spacing="normal">
          <li>
            <t>A Dialog may contain zero or more Tasks, so Task relationships
add finer-grained detail where applicable.</t>
          </li>
          <li>
            <t>Within one Dialog, Tasks relate to one another through their
Resources: the output of one Task is the input of another,
sequentially or in parallel.</t>
          </li>
          <li>
            <t>Assistant Tool Dialogs are terminal in the Activity's interaction wave, regardless of the tool's internal execution.</t>
          </li>
        </ul>
        <t>The set of Tasks participating in an Activity can therefore be
modeled as a directed graph:</t>
        <artwork><![CDATA[
G_T = (T, R_T)
]]></artwork>
        <t>where T contains the Tasks and R_T their typed relationships. This graph
may correspond to, but need not mirror, the Dialog graph G_D. No
participant is required to maintain it in full.</t>
      </section>
      <section anchor="impact-of-dialog-failures-on-task-relationships">
        <name>Impact of Dialog Failures on Task Relationships</name>
        <t>Dialog failures or lifecycle changes may affect Tasks without
determining their states. Where consequential changes occur, they need
to remain correlated with the affected Dialogs and upstream work.</t>
        <ul spacing="normal">
          <li>
            <t>Dialog terminated: Tasks may complete, fail, be cancelled, or continue
under application-specific arrangements. Correlation captures relevant
consequences without imposing a uniform transition.</t>
          </li>
          <li>
            <t>Dialog replaced: When D2' replaces D2, that Dialog-level assertion
does not determine what happens to each Task in D2. A Task may be
continued through a new Task, superseded, retained in its existing
state, or handled otherwise according to the application. Where a
new Task t_12' actually supersedes t_12, that association can be
recorded explicitly:</t>
          </li>
        </ul>
        <artwork><![CDATA[
t_12' replaces t_12
]]></artwork>
        <t>A Task that is not re-established in D2' must not automatically be
interpreted as lost, cancelled, or failed solely because its Dialog
was replaced. Its known outcome or unresolved status, where relevant,
remains part of the correlation context.</t>
        <ul spacing="normal">
          <li>
            <t>Dialog suspended: Depending on the work and its dependencies, associated
Tasks may be interrupted, left awaiting, or continue through other
arrangements. The relevant Task states and any resulting changes may
need to be correlated with the Dialog's suspension.</t>
          </li>
          <li>
            <t>Broken lineage: Loss of an upstream Dialog relationship can make related
cross-Dialog Task assertions unverifiable and prevent result correlation
or upstream resolution.</t>
          </li>
        </ul>
      </section>
      <section anchor="task-privacy-considerations">
        <name>Task Privacy Considerations</name>
        <t>Task objectives and states can reveal intent, workflow, timing, and
delegation. Sharing results need not require disclosing the Tasks that
produced them.</t>
        <t>Administrative domains may therefore:</t>
        <ul spacing="normal">
          <li>
            <t>disclose Dialog participation without Task-level detail;</t>
          </li>
          <li>
            <t>share a Task's output while withholding its objective;</t>
          </li>
          <li>
            <t>omit cross-Dialog Task relationships entirely;</t>
          </li>
          <li>
            <t>generalize Task objectives before propagation.</t>
          </li>
        </ul>
        <t>Task associations may be kept privately by intermediaries. Even Task
states may be withheld or generalized according to the applicable disclosure policy.</t>
      </section>
      <section anchor="events-within-tasks">
        <name>Events Within Tasks</name>
        <t>Events are the application interactions through which a Task progresses.
For example, a Task T1 within D1 may involve a request E1, a response
E2, and a later clarification E3:</t>
        <artwork><![CDATA[
Activity A1
  Dialog D1
    Task T1
      E1 (request) -> E2 (response) -> E3 (clarification)
]]></artwork>
        <t>An Event may carry or reference text, audio, video, or other content;
a Dialog may involve several modalities without creating a new Dialog
or Task for each change. Application protocols carry these interactions.
Where useful for correlation, the dialog-management protocol may carry
opaque Event identifiers or references indicating that E2 responds to E1.
Such tracking is optional and does not require DMS to hold an Event log
or the underlying payloads. Event content and ordering remain matters
for the application protocol and any retained application records. Event identifiers or reference, if logged in the DMS and the corresponding payload are added to the resource layer, subsequent authorized access maybe used to reconstruct the conversation and the reconstruction can be utilized in for example help rebuild the context window of an agent.</t>
      </section>
    </section>
    <section anchor="binding-to-protocol-local-context">
      <name>Binding to Protocol-Local Context</name>
      <t>Where separate application protocols are employed, they define their own context-management mechanisms, interaction semantics, and identifiers. The architecture complements these mechanisms through local bindings that associate application-protocol objects with the logical objects and correlation metadata defined in this document.</t>
      <t>Conceptually:</t>
      <artwork><![CDATA[
Activity
   |
   +-- Dialog D1        <-> protocol-local context
   |      |
   |      +-- DMS(D1)
   |      +-- Task      <-> protocol-local task identifier
   |
   +-- Dialog D2        <-> protocol-local context
          |
          +-- DMS(D2)
          +-- Task      <-> protocol-local task identifier
]]></artwork>
      <t>Through a local interface, the application runtime invokes dialog-management capabilities and supplies the information needed to establish and maintain relevant correlations. The Dialog-Management Protocol Endpoint processes these operations, maintains or accesses the applicable DMS representations, and propagates selected management and correlation metadata. The runtime can subsequently use this metadata in conjunction with application-protocol state and Resource references.</t>
      <t>The scope and semantics of protocol-local identifiers are determined by their respective application protocols. A logical Dialog may be associated with multiple application-protocol interactions and identifiers, particularly in multi-party Dialogs or when the underlying communication arrangements change.</t>
      <t>For example, an application runtime involved in two Dialogs may establish a relationship between Tasks in those Dialogs:</t>
      <artwork><![CDATA[
T14 delegated-from T22
]]></artwork>
      <t>The local bindings associate T14 and T22 with their corresponding application-protocol objects. DCMP represents and propagates the relationship within the applicable managed correlation scope, without carrying the content or execution state of either Task. Where a relationship is propagated beyond its originating scope, its endpoints need to be referenceable by the receiving management endpoints. This may be achieved through logical identifiers, translated identifiers, or opaque references.</t>
      <t>Local bindings need not themselves be stored in DMS or disclosed to other participants. Application protocols retain their own identifiers, interaction content, and execution state, while DCMP provides common semantics for maintaining and propagating correlations across independently managed interactions.</t>
    </section>
    <section anchor="context-management-and-correlation-metadata-propagation">
      <name>Context Management and Correlation Metadata Propagation</name>
      <t>The preceding sections defined the model's objects and relationships.
This section considers the Correlation Metadata needed to preserve and
propagate their associations across participants.</t>
      <t>Context here means the correlations among Activities, Dialogs, Tasks,
and Resources, not an agent's memory or the content of its conversations. Application runtimes invoke dialog-management capabilities to establish and maintain relevant assertions, such as <tt>D2 delegated-from D1</tt>, a reported lifecycle change, or a provenance relationship between two Resources.</t>
      <t>Each Dialog's DMS represents its management state and the correlations established within its managed scope. DCMP Endpoints propagate selected, authorized management and correlation metadata to establish or update local DMS representations. Other correlations may remain private, allowing participants to maintain coherent context without requiring a complete view of the Activity.</t>
      <t>The separation of responsibilities is as follows:</t>
      <ul spacing="normal">
        <li>
          <t>This architecture defines the objects, relationship semantics, and
correlation-management principles.</t>
        </li>
        <li>
          <t>The dialog-management protocol defines interoperable operations and exchanges for management and correlation information.</t>
        </li>
        <li>
          <t>Application-level interactions and content may be carried through separate application protocols or through payload-carriage mechanisms provided by the dialog-management protocol. Where separate application protocols are used, local bindings associate their relevant state with the corresponding management and correlation information.</t>
        </li>
        <li>
          <t>Transport protocols carry the applicable exchanges. Application and dialog-management exchanges may share a transport connection or use separate connections.</t>
        </li>
      </ul>
      <t>The following subsections examine the scope of managed correlations, the information to be propagated, and the principles governing its propagation and maintenance.</t>
      <section anchor="correlation-scope-extension-and-maintenance-responsibilities">
        <name>Correlation Scope, Extension, and Maintenance Responsibilities</name>
        <t>The logical extent of an Activity may exceed the scope of correlations managed through a dialog-management protocol. As an interaction wave expands, participants may establish additional Dialogs and relationships without bringing them into an existing protocol-managed correlation scope.</t>
        <t>The architecture therefore distinguishes three conditions:</t>
        <ul spacing="normal">
          <li>
            <t>A relationship exists between two objects.</t>
          </li>
          <li>
            <t>A participant preserves knowledge of that relationship locally.</t>
          </li>
          <li>
            <t>The relationship is established for management through a dialog-management protocol.</t>
          </li>
        </ul>
        <t>The existence of a relationship does not necessarily imply that it is maintained or disclosed through a protocol. Similarly, associating a logical DMS with a Dialog does not, by itself, bring all of its relationships into a protocol-managed correlation scope.</t>
        <t>Participants selectively extend the managed correlation scope according to application requirements, authorization, and disclosure policies. While participants determine what information they disclose, their collective ability to establish the necessary correlations depends on the information made available. Whether the Activity can proceed under these conditions is a consequence of their disclosure decisions.</t>
        <t>A protocol-managed correlation scope may span multiple Dialogs and their associated DMS representations, supported by locally maintained mappings, without constituting a single Activity-wide DMS.</t>
        <section anchor="logical-and-managed-correlation-scope">
          <name>Logical and Managed Correlation Scope</name>
          <t>The following are views of one Activity, not additional protocol
objects:</t>
          <ul spacing="normal">
            <li>
              <t>Logical interaction scope: the Dialogs, Tasks, Resources, and
relationships that actually contribute to the Activity, including
those unknown to some or all of its participants.</t>
            </li>
            <li>
              <t>Maintained correlation scope: the associations that participants
actually preserve and can relate, whether locally or through one or
more context-management protocols.</t>
            </li>
            <li>
              <t>Protocol-managed correlation scope: the associations brought under
a particular interoperable context-management protocol, with
identified participants accepting the corresponding maintenance
responsibilities. Such scope need not be globally enumerable or
visible to any single participant.</t>
            </li>
          </ul>
          <t>For example, the AIE invokes the FNE through D1, the FNE invokes Agent A
through D2, and Agent A invokes Agent B through D3. An illustrative
context-management protocol (e.g., DCMP) manages their correlations with
Act-1. Agent B then invokes Agent C through D5 using another
non-interoperable protocol (XYZ), or no context-management protocol:</t>
          <artwork><![CDATA[
               Logical interaction scope of Act-1
  +-------------------------------------------------------------------+
  |                                                                   |
  |   AIE ---D1--- FNE ---D2--- Agent A ---D3--- Agent B              |
  |    |                                           |                  |
  |    +--- DCMP-managed correlation scope --------+                  |
  |                                                |                  |
  |                                                +--- D5 (XYZ)--- C |
  |                                                                   |
  +-------------------------------------------------------------------+
]]></artwork>
          <t>D5 can be logically related to Act-1 although DCMP has no knowledge of
D5 or its participants. D5's absence from DCMP is not, by itself, a
correlation-maintenance failure. In particular, the logical interaction scope under Act-1 may extend beyond the correlation scope of an employed protocol (i.e., DCMP or XYZ). In other words, the correlation scope of a protocol follows the relationships that have actually been established for management by that protocol.</t>
          <t>Within a protocol-managed correlation scope, an association is managed when it is included under a particular interoperable context-management protocol and the identified participants accept the corresponding maintenance responsibilities. The acceptance boundary is conceptual: it is the point at which those participants accept that responsibility. How acceptance is signaled, negotiated, or recorded is a protocol-design question and is not defined here. Knowing an association, preserving it privately, or managing it through a non-interoperable practice does not by itself make it managed.</t>
          <t>The following conditions remain distinct:</t>
          <ul spacing="normal">
            <li>
              <t>Not enrolled: the association lies outside the protocol-managed scope, so no participant has accepted a maintenance responsibility for it within that scope. This is not, by itself, a maintenance failure.</t>
            </li>
            <li>
              <t>Not disclosed: the association may be preserved or managed, but it is not revealed to a particular participant.</t>
            </li>
            <li>
              <t>No longer maintainable: an accepted association cannot be preserved, recovered, or kept coherent, for example because required information is unavailable or policy prevents its use. The limitation is distinguishable from successful maintenance.</t>
            </li>
            <li>
              <t>Incorrectly maintained: a participant retains or communicates an association that is wrong, stale, or applied to the wrong object.</t>
            </li>
          </ul>
          <t>These conditions describe different observations; one does not imply another. These are scope and maintenance conditions, not the propagation failure taxonomy described under "Propagation Failure Modes" (§8.12).</t>
          <t>In summary, the logical interaction scope of an Activity may extend beyond the correlation scope of a management protocol; leakage between correlation scopes is determined by the participants shared across those scopes.</t>
        </section>
        <section anchor="selective-extension-and-boundary-bridging-scope-leakage">
          <name>Selective Extension and Boundary Bridging (Scope Leakage)</name>
          <t>Extending a protocol-managed correlation to another Dialog is a
participant decision. Agent B may still maintain a private bridge
between its Task in D3 and work delegated through D5:</t>
          <artwork><![CDATA[
           DCMP-managed                        Outside DCMP
       +------------------+              +-------------------+
       | D3: Task t_13    |              | D5: Task t_15     |
       | Agent A <-> B    |              | Agent B <-> C     |
       +---------+--------+              +---------+---------+
                 |                                 |
                 +-- B's local t_13 <-> t_15 map --+
                              (not disclosed)
]]></artwork>
          <t>B's private mapping can interpret D5 outcomes or relay relevant changes
without disclosing C or D5. This preserves local correlation but does
not place D5 within the first protocol's managed scope. The architecture
does not prescribe protocol adoption or bridging mechanisms.</t>
        </section>
        <section anchor="maintenance-responsibilities-within-the-established-scope">
          <name>Maintenance Responsibilities Within the Established Scope</name>
          <t>Maintenance Responsibilities Within the Established Scope</t>
          <t>The principle is:</t>
          <ul empty="true">
            <li>
              <t>The decision to extend the managed correlation scope is distinct from the responsibility to maintain established correlations.</t>
            </li>
          </ul>
          <t>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.</t>
          <t>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.</t>
          <t>Maintenance responsibilities apply regardless of how scope extension is governed.</t>
          <t>Consider a barge-in in D1 that changes requirements for Tasks in D2 and D3 in a manner that affects established managed correlations:</t>
          <artwork><![CDATA[
            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.
]]></artwork>
          <t>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.</t>
          <t>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.</t>
        </section>
        <section anchor="failure-visibility-and-bounded-accountability">
          <name>Failure Visibility and Bounded Accountability</name>
          <t>Failure visibility is described in terms of observable correlation outcomes rather than attributed causes. Four outcome classes are useful:</t>
          <ul spacing="normal">
            <li>
              <t>Available and valid: the association can be resolved and used for the correlation it is intended to support.</t>
            </li>
            <li>
              <t>Missing or unresolvable: no usable association is available, or a reference cannot be resolved.</t>
            </li>
            <li>
              <t>Stale, inconsistent, or unverifiable: an association exists but is outdated, conflicts with other information, or cannot be checked.</t>
            </li>
            <li>
              <t>Disclosure not permitted or insufficient information available: policy, authorization, or missing information prevents use of an association.</t>
            </li>
          </ul>
          <t>These are observations about correlation status. They do not by themselves indicate Activity progress, Task success, or evidence suitable for audit, and this architecture is not an audit system.</t>
          <t>A participant may observe an outcome without being able to identify its cause. Identifying the responsible step or participant is possible only where evidence and visibility allow it. A silently withheld update, an unreachable peer, or an undisclosed branch can leave a participant with unknown or unverified state rather than a proven violation; a missing response indicates uncertainty, not misconduct. The outcome may reflect any of the conditions in "Logical and Managed Correlation Scope": not enrolled, not disclosed, no longer maintainable, or incorrectly maintained. Distinguishing among them may not be possible from local observation. Where an association was accepted into managed scope, the maintenance responsibility principle applies, but failure to observe maintenance is not proof that maintenance failed.</t>
          <t>Scope and coverage may themselves be undisclosed. A participant therefore cannot assume that an apparently complete view is complete, and bounded accountability concerns the observable managed associations rather than hidden downstream interactions. This is consistent with §8.12: where supported by evidence, the affected managed step and responsible participant can be identified, but complete visibility and perfect attribution are not implied.</t>
          <t>When insufficient information prevents a required correlation from being established or an existing managed correlation from being maintained, the dialog-management protocol should make the detected limitation observable to the relevant authorized participants. The application determines the implications of this limitation for the associated Dialogs and Tasks.</t>
        </section>
      </section>
      <section anchor="the-propagation-model">
        <name>The Propagation Model</name>
        <t>Propagation carries Correlation Metadata among participants so
separately maintained Dialogs, Tasks, and Resources remain correctly
associated with their Activity.</t>
        <t>Four acts are distinct in this model:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Term</th>
              <th align="left">Meaning in this architecture</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Preserve</td>
              <td align="left">Keep an association accurately, possibly only locally.</td>
            </tr>
            <tr>
              <td align="left">Propagate</td>
              <td align="left">Transfer selected correlation information across a Dialog boundary.</td>
            </tr>
            <tr>
              <td align="left">Disclose</td>
              <td align="left">Reveal an identifier, participant, or relationship to another party.</td>
            </tr>
            <tr>
              <td align="left">Project</td>
              <td align="left">Construct the limited, locally meaningful view appropriate for a receiving Dialog (see "Context Projection").</td>
            </tr>
          </tbody>
        </table>
        <t>For example, B may preserve <tt>D2 delegated-from D1</tt> and a local mapping to a reference used by C. B propagates to C only the correlation C needs. C receives a locally meaningful reference and the delegated task objective, and does not learn A's identity or D1's identifier. If that reference cannot be resolved, the association may still be preserved at B but cannot correlate that response; this is a resolution limitation, not a requirement that C disclose more.</t>
        <t>Propagation adapts selected correlation information across Dialog
boundaries rather than copying a participant's entire state:</t>
        <artwork><![CDATA[
upstream correlation
      |
      | select      (choose the metadata the receiving Dialog needs)
      | translate   (map identifiers across the Dialog boundary)
      | correlate   (relate it to objects already present)
      | bind        (associate it with local objects and state)
      v
downstream correlation
]]></artwork>
        <t>The receiving Dialog's managed correlations may be associated with
its DMS where they are established within its shared scope; other
associations may be preserved locally by the bridging participant.
Neither case requires duplicating the upstream Dialog's DMS. The
bridging participant selects the relevant associations.</t>
        <t>Metadata may concern Activity association, Dialog or Task lineage, or
Resource identity and provenance, as described below.</t>
        <t>Two properties follow, both developed later in this section:</t>
        <ul spacing="normal">
          <li>
            <t>Propagation is selective: Only the metadata a receiving Dialog needs
to maintain continuity, associate related interactions, or interpret
shared Resources should be carried.</t>
          </li>
          <li>
            <t>Propagation is directional: What travels downstream differs from
what travels upstream.</t>
          </li>
        </ul>
        <t>The architecture does not prescribe a fixed set of propagation events.
Propagation is need-driven. A participant selects the Correlation
Metadata needed when extending correlation to a new Dialog, subject
to applicable policies. Once a participant has accepted responsibility
for an established protocol-managed correlation, however, subsequent
changes relevant to that association are subject to its maintenance
responsibilities rather than a wholly new choice about whether to
maintain the correlation at all. Establishing a new Dialog, delegating
a Task, transferring a Resource, or resuming an interaction may each
create a need for propagation.</t>
        <t>Participants may retain more correlations locally than they disclose;
receiving Dialogs need only the subset required for coherent
interaction.</t>
      </section>
      <section anchor="what-is-propagated">
        <name>What Is Propagated</name>
        <t>The dialog-management protocol propagates management and correlation metadata to maintain coherent context across participants. It may also provide mechanisms for carrying application payloads associated with Events within a Dialog, where separate application protocols are not employed or where direct payload carriage is desirable.</t>
        <t>Application payload carriage remains semantically distinct from management and correlation metadata propagation.</t>
        <t>The main classes of Correlation Metadata are described below.</t>
        <section anchor="activity-correlation">
          <name>Activity Correlation</name>
          <t>A downstream interaction may need to know that it participates in the
same broader Activity as other interactions:</t>
          <artwork><![CDATA[
D2 belongs-to Activity A1
D5 belongs-to Activity A1
]]></artwork>
          <t>An Activity has a stable logical identity for correlation purposes. Different participants may use local identifiers or aliases to refer to the same Activity, without requiring a globally shared identifier value.</t>
          <t>The representation, exchange, and possible standardization of Activity identifiers are protocol-design considerations (see Identifier Translation).</t>
        </section>
        <section anchor="dialog-lineage-1">
          <name>Dialog Lineage</name>
          <t>When a new Dialog results from an existing one, the delegating
participant can retain the relationship:</t>
          <artwork><![CDATA[
D5 delegated-from D2
]]></artwork>
          <t>Dialog lineage preserves the causal or delegation relationship
between two Dialogs. Preserving lineage does not imply propagating or
disclosing it. A participant may retain lineage locally, and propagate
it only when the receiving Dialog needs it, for example for upstream
resolution or result correlation. When propagated, the relationship
may be carried directly or as an opaque reference, or it may be
withheld. Preservation, propagation, and disclosure are therefore
separate concerns.</t>
          <t>Delegation is one lineage type among several; <tt>continuation-of</tt>,
<tt>replaces</tt>, <tt>aggregated-from</tt>, and <tt>related-to</tt> are the others, and
each propagates on the same terms described here.</t>
        </section>
        <section anchor="task-lineage">
          <name>Task Lineage</name>
          <t>A downstream Task may be correlated with the upstream Task from which
it originated:</t>
          <artwork><![CDATA[
t_15 delegated-from t_22
]]></artwork>
          <t>Task lineage is useful when a Dialog contains several Tasks
and only one of them caused the downstream delegation; delegated-from
records which one. Protocol-local Task identifiers are not intended
to travel; the relationship carries the correlation. Task lineage
is therefore optional and selective: it is established where the
receiving Dialog requires it for continuity, upstream resolution, or
correct interpretation, and withheld otherwise. Under hidden
delegation it may be retained only by the participant common to both
Dialogs.</t>
          <t>As with Dialog lineage, <tt>related-to</tt> and <tt>replaces</tt> are examples of other Task
lineage types, and each propagates on the same terms.</t>
        </section>
        <section anchor="resource-identity">
          <name>Resource Identity</name>
          <t>A Resource that is referenced or transferred across Dialog, protocol,
or administrative boundaries may need to retain a stable logical
identity, so that independently operated participants can recognize
that they refer to the same Resource:</t>
          <artwork><![CDATA[
Dialog D2: Resource T1
Dialog D5: Resource T1
]]></artwork>
          <t>Where an operation transforms, derives from, or partially reuses an existing Resource, the participant performing the operation decides whether the result constitutes a new logical Resource or a new use of the existing one. A new logical Resource is related to its sources through a typed relationship such as <tt>derived-from</tt>; a new use of an existing Resource is expressed as a Resource Binding. The architecture does not determine which choice an application should make, but it requires the choice to be representable, so that participants can distinguish reference to the same Resource from reference to a distinct, related Resource. For example, in the barge-in scenario, analyzing the relevant part of an existing transcript is a Binding, whereas producing a narrowed transcript as a separate artifact creates a new Resource derived from the original.</t>
          <t>Resource identity is a logical assignment rather than a determination derived from content: two artifacts with identical content produced by different operations are distinct Resources, distinguished by their provenance. A participant that equates them is making a local mapping decision, not altering either Resource's identity.</t>
          <t>Where cross-Dialog Resource correlation is required, the association between references to the same logical Resource may be maintained through shared identifiers, local identifiers, or boundary-specific aliases and mappings. This does not require participants to exchange an identical Resource-ID value or disclose the association to every participant.</t>
          <artwork><![CDATA[
Dialog D2: Resource reference = r-17, A2A artifactId = artifact-17
Dialog D5: Resource reference = r-91, A2A artifactId = artifact-91

Mapping: r-17 <-> r-91 (same logical Resource T1)
]]></artwork>
          <t>A Resource's stable logical identity supports cross-Dialog correlation; identifier representations, mappings, storage, and content transfer remain separate implementation or protocol concerns.</t>
          <t>Identity identifies the Resource; provenance describes its origins, and
Binding describes its local use.</t>
          <section anchor="resource-provenance">
            <name>Resource Provenance</name>
            <t>Resource identity establishes how participants refer to the same
Resource. Resource Provenance is another resource-specific typed relationship. Examples include:</t>
            <artwork><![CDATA[
T1 derived-from V1
TXT-3 produced as a result of task 1 in dialog 1
]]></artwork>
            <t>Provenance asserts that a Resource was produced from, or derived from, another object, and records that derivation as a typed relationship. Like Dialog lineage and Task lineage, provenance is preserved and disclosed selectively: it need not be propagated transitively, and a participant may retain a derivation locally without disclosing it. Receiving one derivation edge does not imply knowledge of earlier edges in a chain. Whether and how provenance is exchanged is a protocol-design question. Provenance describes origins; it does not by itself prove the derivation or that it was authorized. This architecture does not define a lifecycle state machine for Resources; where one Resource supersedes another, that is expressed as a relationship rather than as a Resource lifecycle state.</t>
          </section>
          <section anchor="local-resource-binding">
            <name>Local Resource Binding</name>
            <t>The same Resource can play a different role in each Dialog or Task in
which it appears. A Resource Binding associates a Resource with a
specific Dialog or Task and describes how it is used there:</t>
            <artwork><![CDATA[
T1 input-to TB1
T1 augments TC1
]]></artwork>
            <t>Unlike identity and provenance, a Binding is not an end-to-end
property of the Resource:</t>
            <artwork><![CDATA[
D2 / Task TB1:  T1 primary-input-to TB1
D5 / Task TC1:  T1 supporting-input-to TC1
]]></artwork>
            <t>The same logical Resource is referenced in both cases, but its local
role differs. When a Resource is propagated into a new Dialog, the
upstream Binding is not assumed to apply there. The delegating party
may carry it unchanged, restate it as a recommendation for the receiving
Dialog, convey it in part, leave it unspecified, or let the receiving
participant establish a new one.</t>
            <t>Bindings are therefore local semantics. They may be carried across a
boundary when useful, but doing so does not make them universal:</t>
            <artwork><![CDATA[
T1 required-for TB1   does not imply   T1 required-for TC1
]]></artwork>
          </section>
        </section>
        <section anchor="propagation-summary">
          <name>Propagation Summary</name>
          <t>The classes differ in what they are and how they typically travel:</t>
          <table>
            <thead>
              <tr>
                <th align="left">Information</th>
                <th align="left">Role</th>
                <th align="left">Typical propagation</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Activity-ID</td>
                <td align="left">Stable identity of the Activity</td>
                <td align="left">When cross-Dialog Activity correlation is needed</td>
              </tr>
              <tr>
                <td align="left">Dialog lineage</td>
                <td align="left">Causal or delegation relation between Dialogs</td>
                <td align="left">Retained where needed; selectively propagated</td>
              </tr>
              <tr>
                <td align="left">Task identifiers</td>
                <td align="left">Protocol-local unit-of-work tracking</td>
                <td align="left">Selectively referenced for cross-Dialog correlation</td>
              </tr>
              <tr>
                <td align="left">Event identifiers</td>
                <td align="left">Optional references to application interactions</td>
                <td align="left">Only where fine-grained correlation is needed</td>
              </tr>
              <tr>
                <td align="left">Resource-ID</td>
                <td align="left">Stable identity of a logical Resource</td>
                <td align="left">When cross-Dialog Resource correlation is needed</td>
              </tr>
              <tr>
                <td align="left">Resource provenance</td>
                <td align="left">How a Resource was produced or derived</td>
                <td align="left">When needed for correct interpretation</td>
              </tr>
              <tr>
                <td align="left">Resource Binding</td>
                <td align="left">Local role of a Resource</td>
                <td align="left">Primarily local; selectively carried</td>
              </tr>
            </tbody>
          </table>
          <t>The rule is constant across all of them:</t>
          <ul empty="true">
            <li>
              <t>Propagate only the correlation the receiving Dialog needs to maintain
continuity, associate related interactions, or interpret shared
Resources.</t>
            </li>
          </ul>
        </section>
      </section>
      <section anchor="propagation-is-not-transitive-by-default">
        <name>Propagation Is Not Transitive by Default</name>
        <t>Propagation in this architecture is selective rather than automatic.</t>
        <t>A contextual element can be stable or important without being
transmitted to every participant. Each propagation decision depends on
whether the receiving Dialog requires that information for correlation,
continuity, or correct interpretation. Receiving context information does not imply that the receiver should automatically
propagate all of it further. For example:</t>
        <artwork><![CDATA[
A <----> B <----> C
]]></artwork>
        <t>B may receive from A:</t>
        <artwork><![CDATA[
Activity A1
Resource V1
Resource T1
A's identity
private policy metadata
]]></artwork>
        <t>and propagate to C only:</t>
        <artwork><![CDATA[
Activity correlation
V1
T1
]]></artwork>
        <t>Therefore:</t>
        <ul empty="true">
          <li>
            <t>Context received from an upstream participant is not automatically
transitive.</t>
          </li>
        </ul>
        <t>This principle governs the selection and disclosure of information
when extending correlation. It does not release a participant from
maintenance responsibilities already accepted for an established
protocol-managed association. A participant need not forward an
upstream update unchanged, but must preserve or communicate enough
information to maintain the correlations for which it is responsible,
or make the resulting inability to maintain them distinguishable.</t>
        <t>Each propagation step is subject to a new projection decision, determined
by the participating parties as described under "Context Projection". A
dialog-management protocol provides a means for the selective propagation
of context metadata.</t>
        <t>This is important when agentic systems cross:</t>
        <ul spacing="normal">
          <li>
            <t>organizational boundaries;</t>
          </li>
          <li>
            <t>trust boundaries;</t>
          </li>
          <li>
            <t>privacy boundaries;</t>
          </li>
          <li>
            <t>protocol boundaries; and</t>
          </li>
          <li>
            <t>changes in task extent.</t>
          </li>
        </ul>
        <t>Propagation is triggered by the needs of the receiving Dialog rather than
by a fixed set of protocol events. A new Dialog, delegated Task,
transferred Resource, resumed interaction, or modality transformation
may require propagation, but only the correlation information necessary
for that Dialog should be carried.</t>
        <t>The architecture therefore defines propagation in terms of information
requirements and Dialog boundaries, rather than prescribing a universal
set of propagation events.</t>
      </section>
      <section anchor="context-projection">
        <name>Context Projection</name>
        <t>Context Projection selects what is disclosed when B creates D2 from D1,
without copying D1's complete state. For example:</t>
        <artwork><![CDATA[
D1:
  Activity A1
  objective
  V1
  T1
  A's identity
  private policy
  conversation history
  internal reasoning
  credentials

        |
        | projection by B
        v

D2:
  Activity correlation
  delegated task objective
  V1
  T1
  relevant provenance
]]></artwork>
        <t>Projection therefore determines what is exposed to the downstream
Dialog. The projection is controlled by:</t>
        <ul spacing="normal">
          <li>
            <t>task requirements;</t>
          </li>
          <li>
            <t>privacy policy;</t>
          </li>
          <li>
            <t>authorization policy;</t>
          </li>
          <li>
            <t>administrative-domain policy;</t>
          </li>
          <li>
            <t>protocol capabilities; and</t>
          </li>
          <li>
            <t>application semantics.</t>
          </li>
        </ul>
        <t>The projection algorithm is outside this architecture. The example
includes both application-level material (such as the delegated
objective and Resources) and correlation information. Projection of
application content is not a transfer of DMS. Only correlation
metadata explicitly established for D2's shared managed scope becomes
part of DMS(D2); the other content remains with the application
protocol or participant-local state.</t>
      </section>
      <section anchor="identifier-translation">
        <name>Identifier Translation</name>
        <t>Identifiers may change across domains, provided that the necessary
mappings preserve correlation:</t>
        <artwork><![CDATA[
Organization 1:
  Activity-ID = A1

Organization 2 external view:
  Activity alias = X7
]]></artwork>
        <t>Organization 2 can retain:</t>
        <artwork><![CDATA[
A1 <-> X7
]]></artwork>
        <t>privately.</t>
        <t>Likewise, a Resource may be represented as:</t>
        <artwork><![CDATA[
Resource T1
]]></artwork>
        <t>in the architecture while having local identifiers:</t>
        <artwork><![CDATA[
A2A artifactId = artifact-17
MCP resource URI = ...
local database ID = 9f32
]]></artwork>
        <t>Identifier translation permits correlation without globally visible
implementation identifiers. Its mechanisms belong to the protocol
bindings or local-protocol specifications.</t>
      </section>
      <section anchor="directional-propagation">
        <name>Directional Propagation</name>
        <t>Propagation can occur in both directions, but the information carried in
each direction can differ.</t>
        <section anchor="downstream-propagation">
          <name>Downstream propagation</name>
          <t>Typically carries:</t>
          <artwork><![CDATA[
activity correlation
task objective
selected Resources
selected provenance
constraints
]]></artwork>
        </section>
        <section anchor="upstream-propagation">
          <name>Upstream propagation</name>
          <t>Typically carries:</t>
          <artwork><![CDATA[
results
new Resources
status
questions
failure information
local observations
]]></artwork>
          <t>A downstream participant does not necessarily return the same context
that it received.</t>
          <t>For example:</t>
          <artwork><![CDATA[
B -> C:
  V1
  T1
  analyze video

C -> B:
  result R1
  observation: T1 appears unnecessary
]]></artwork>
          <t>The second message is related to the same Activity but introduces new
local information.</t>
        </section>
      </section>
      <section anchor="propagation-of-assertions">
        <name>Propagation of Assertions</name>
        <t>Correlation Metadata may be expressed as assertions, for example:</t>
        <artwork><![CDATA[
D2 delegated-from D1
T1 derived-from V1
T1 input-to TC1
]]></artwork>
        <t>An implementation should distinguish the existence of an assertion from
the authority or trustworthiness of the entity making that assertion. For example, receiving:</t>
        <artwork><![CDATA[
T1 derived-from V1
]]></artwork>
        <t>does not cryptographically prove the derivation. Likewise:</t>
        <artwork><![CDATA[
D2 delegated-from D1
]]></artwork>
        <t>does not by itself prove that the delegation was authorized.</t>
        <t>Authentication, authorization, integrity protection, attestation, and
provenance mechanisms can be used independently where required. This
should be coordinated between the agentproto working group and other
respective IETF working groups such as WIMSE and OAuth.</t>
        <t>Correlation assertions may also come from different sources. A
Dialog's or a Task's state may be reported by its participants,
observed by a peer, or asserted by a supervisory system. When two
sources disagree about the same object - for example, when one reports
a Task as in-progress while another reports it as failed - correlation
requires that the assertions remain associated with the correct object
and, where needed, distinguishable by their sources and relevant
context. This architecture does not determine which assertion is
authoritative or prescribe how disagreements are resolved.</t>
        <section anchor="lifecycle-affecting-requests-and-consequences">
          <name>Lifecycle-Affecting Requests and Consequences</name>
          <t>A lifecycle-affecting request, such as a request to cancel a Task, is
distinct from an assertion that the requested transition has occurred.
Application protocols may carry the request and report its outcome.
This architecture concerns the Correlation Metadata needed to associate
such requests and assertions with the affected Dialog or Task, and to
maintain correlations with dependent work in other Dialogs.</t>
          <t>An application-level change to an Activity, Dialog, or Task objective
does not by itself require a protocol-managed correlation update or
DMS modification; only consequent changes to tracked identities,
lifecycle, membership, relationships, or propagation-relevant metadata
need to be represented in the applicable managed scope.</t>
          <t>When an interruption, barge-in, cancellation, or security or
authorization change may affect related work, the necessary associations
may be preserved by a participant with visibility into the relevant
Dialogs and Tasks. Sufficient Correlation Metadata is propagated where
needed to allow affected participants to interpret the change and
associate resulting states or outcomes with it. The metadata need not
expose the full upstream context. Security- or authorization-related
information may be included where required for correlation; this
architecture does not define authorization decisions or enforcement.</t>
        </section>
      </section>
      <section anchor="context-freshness-and-lifetime">
        <name>Context Freshness and Lifetime</name>
        <t>Not all correlation assertions have the same lifetime. Examples include:</t>
        <artwork><![CDATA[
Dialog D2 terminated
delegation revoked
resource superseded
task completed
]]></artwork>
        <t>Correlation information may be:</t>
        <artwork><![CDATA[
stable
mutable
time-bounded
revocable
]]></artwork>
        <t>For example:</t>
        <artwork><![CDATA[
T1 derived-from V1
]]></artwork>
        <t>is typically stable provenance.</t>
        <t>By contrast:</t>
        <artwork><![CDATA[
D2 active
]]></artwork>
        <t>is mutable lifecycle state.</t>
        <t>Propagation mechanisms need appropriate freshness and update behavior
for each class. Representations of the same logical DMS can be
transiently different or stale; the implementing protocol determines
how participants recognize authoritative shared-state changes and
recover a sufficiently current authorized view.</t>
      </section>
      <section anchor="propagation-revocation">
        <name>Propagation Revocation</name>
        <t>Revocation invalidates a relationship as a basis for future propagation.
For example:</t>
        <artwork><![CDATA[
D2 delegated-from D1
]]></artwork>
        <t>is revoked, no new downstream propagation should be created based on
that relationship.</t>
        <t>Revocation need not terminate the Dialog or erase the historical fact
that the relationship existed. When a participant leaves or is removed
from a multi-party Dialog, its membership-based entitlement to future
shared DMS updates can also end. Membership change and revocation of
a cross-Dialog propagation relationship are distinct management
concerns and do not automatically imply one another.</t>
        <t>The primary case is a Dialog that remains open while a propagation
relationship is revoked. For example, D2 continues between A and B, but
the propagation relationship on which B disclosed selected D2 metadata
to C is revoked. D2 remains active. The prior association and disclosure
remain historical facts and are not erased. What changes is that future
disclosure or propagation based on that relationship is no longer
authorized. This architecture does not determine whether existing
recipients retain or delete previously received information; that
remains a policy and protocol question, as noted below.</t>
        <t>Revocation may be only partially visible: some participants may not yet
have learned of it and may treat the earlier association as locally
current. Dissemination, ordering, and enforcement are protocol and
security design questions; authority and trust are discussed under
"Propagation of Assertions".</t>
        <t>Protocol-design questions include whether revocation cascades, how
history is treated, and what participants do with earlier correlations
derived from a revoked relationship.</t>
      </section>
      <section anchor="partial-visibility">
        <name>Partial Visibility</name>
        <t>No participant needs the complete Activity graph. For example:</t>
        <artwork><![CDATA[
            A
            |
           D1
            |
            B
           / \
         D2   Tool X
         |
         C
]]></artwork>
        <t>A may know only:</t>
        <artwork><![CDATA[
D1
B
]]></artwork>
        <t>C may know only:</t>
        <artwork><![CDATA[
D2
B
V1
T1
]]></artwork>
        <t>B may know the relationship between D1 and D2.</t>
        <t>Tool X may know only:</t>
        <artwork><![CDATA[
V1
its local invocation
T1
]]></artwork>
        <t>The Activity can remain coherent with partial visibility. An
intermediary may conceal a downstream Dialog while preserving necessary
correlation, or establish it outside managed scope. Only accepted
managed correlations entail the corresponding maintenance obligations.</t>
      </section>
      <section anchor="propagation-failure-modes">
        <name>Propagation Failure Modes</name>
        <t>Correlation can fail even when application Tasks and transport operate
correctly. The following failures are distinct from application or
connectivity failures.</t>
        <t>Propagation failures merit separate treatment.</t>
        <t>Illustrative failure modes follow. These are just examples. The list may be extended as the work progresses</t>
        <section anchor="loss-of-correlation">
          <name>Loss of Correlation</name>
          <t>A participant may receive an interaction or Resource without being able
to associate it with the correct Activity, Dialog, Task, or Resource.</t>
          <t>For example:</t>
          <artwork><![CDATA[
Agent D receives T1
]]></artwork>
          <t>but cannot determine which ongoing Activity or Dialog T1 belongs to.</t>
          <t>The Resource may remain usable while cross-Dialog continuity is lost.</t>
          <t>Loss of correlation can result from:</t>
          <ul spacing="normal">
            <li>
              <t>Missing Activity correlation;</t>
            </li>
            <li>
              <t>Loss of Dialog lineage at an intermediary;</t>
            </li>
            <li>
              <t>Failure to preserve Resource identity; or</t>
            </li>
            <li>
              <t>Inability to map protocol-local identifiers to the broader correlation
model.</t>
            </li>
          </ul>
        </section>
        <section anchor="incorrect-correlation">
          <name>Incorrect Correlation</name>
          <t>Incorrect correlation associates unrelated interactions or Resources.
For example:</t>
          <artwork><![CDATA[
T1 belongs-to Activity A1
]]></artwork>
          <t>may be incorrectly interpreted as:</t>
          <artwork><![CDATA[
T1 belongs-to Activity A2
]]></artwork>
          <t>Misbinding may combine unrelated Activities or deliver results to the
wrong Dialog; correlation mappings are integrity-sensitive.</t>
          <t>Implementations SHOULD therefore treat correlation identifiers and
relationship mappings as integrity-sensitive state.</t>
        </section>
        <section anchor="over-propagation">
          <name>Over-Propagation</name>
          <t>A participant may receive more metadata than needed.
For example, Agent D may require only T1 for summarization but receive:</t>
          <artwork><![CDATA[
Activity-ID A1
D3 delegated-from D2
D2 delegated-from D1
T1 derived-from V1
identities of upstream participants
]]></artwork>
          <t>even though none of that information is necessary for summarization.</t>
          <t>Over-propagation increases:</t>
          <ul spacing="normal">
            <li>
              <t>privacy exposure;</t>
            </li>
            <li>
              <t>topology disclosure;</t>
            </li>
            <li>
              <t>metadata size and transmission overhead;</t>
            </li>
            <li>
              <t>implementation coupling; and</t>
            </li>
            <li>
              <t>cross-domain tracking risk.</t>
            </li>
          </ul>
          <t>Selective propagation protects privacy and reduces coupling.</t>
        </section>
        <section anchor="stale-context">
          <name>Stale Context</name>
          <t>Some context changes over time:</t>
          <t>For example:</t>
          <artwork><![CDATA[
D2 ACTIVE
]]></artwork>
          <t>may later become:</t>
          <artwork><![CDATA[
D2 TERMINATED
]]></artwork>
          <t>or a propagation relationship may be revoked.</t>
          <t>Stale context can produce incorrect decisions. Stable relationships and
mutable lifecycle assertions require different freshness handling.</t>
          <t>For example, stable provenance such as <tt>T1 derived-from V1</tt> differs
from mutable lifecycle state such as <tt>D2 ACTIVE</tt>; propagation
mechanisms therefore need appropriate freshness and update behavior
for each.</t>
          <t>This concern is particularly relevant to long-lived Dialogs, where participants may retain local management and correlation information across extended periods of inactivity or disconnection. During such periods, lifecycle state, participant membership, authorization information, or established correlations may change. A participant resuming communication may therefore hold an outdated DMS representation. The dialog-management protocol needs to support identifying stale state and recovering an appropriately current and authorized view, without requiring disclosure of information outside the participant's managed correlation scope.</t>
        </section>
        <section anchor="semantic-drift">
          <name>Semantic Drift</name>
          <t>A downstream Dialog may incorrectly reuse an upstream local
interpretation. For example:</t>
          <artwork><![CDATA[
D1 / TB1:
  T1 required-for TB1
]]></artwork>
          <t>must not automatically be interpreted as:</t>
          <artwork><![CDATA[
D2 / TC1:
  T1 required-for TC1
]]></artwork>
          <t>The Resource identity is preserved, but its local Binding may differ.</t>
          <t>Semantic drift arises when a local Resource Binding is treated as
universally applicable.</t>
        </section>
        <section anchor="broken-lineage">
          <name>Broken Lineage</name>
          <t>An intermediary may lose the relation connecting a delegated Dialog to
its origin. For example:</t>
          <artwork><![CDATA[
D1 -> D2
]]></artwork>
          <t>is created, but B later loses the relationship:</t>
          <artwork><![CDATA[
D2 delegated-from D1
]]></artwork>
          <t>Without that link, subsequent questions, results, and failures may not
be routed or correlated upstream.</t>
          <t>Broken lineage obstructs:</t>
          <ul spacing="normal">
            <li>
              <t>upstream resolution;</t>
            </li>
            <li>
              <t>result correlation;</t>
            </li>
            <li>
              <t>failure recovery; and</t>
            </li>
            <li>
              <t>audit or troubleshooting of delegated execution.</t>
            </li>
          </ul>
        </section>
        <section anchor="excessive-lineage-propagation">
          <name>Excessive Lineage Propagation</name>
          <t>Excessive lineage disclosure is the opposite risk:</t>
          <t>A system may preserve and propagate an unnecessarily complete delegation
chain:</t>
          <artwork><![CDATA[
D5 <- D4 <- D3 <- D2 <- D1
]]></artwork>
          <t>to every downstream participant.</t>
          <t>An accurate but over-shared chain may reveal unnecessary participants,
domains, or workflow topology.</t>
          <t>Preservation and disclosure are distinct.</t>
        </section>
        <section anchor="inconsistent-local-mapping">
          <name>Inconsistent Local Mapping</name>
          <t>Local mappings may include:</t>
          <artwork><![CDATA[
Activity A1 <-> local activity-773

Resource T1 <-> local artifact-19
]]></artwork>
          <t>Inconsistent mappings can bind a valid logical identifier to the wrong
local object, appearing externally as a cross-domain correlation
failure.</t>
          <t>Such failures are local implementation failures, but they can appear
externally as incorrect cross-domain correlation.</t>
        </section>
        <section anchor="partial-propagation-failure">
          <name>Partial Propagation Failure</name>
          <t>In a multi-element propagation operation, some context may arrive while
other required context is lost.</t>
          <t>For example, a participant may receive:</t>
          <artwork><![CDATA[
Resource T1
Activity-ID A1
]]></artwork>
          <t>but not the Resource identifier or relationship necessary to associate
T1 with the Task awaiting it.</t>
          <t>Partial propagation can be more difficult to detect than complete
propagation failure because the receiving participant may have enough
information to continue execution while silently losing intended
correlation.</t>
        </section>
        <section anchor="architectural-implication">
          <name>Architectural Implication</name>
          <t>These failure modes reinforce a central principle of this architecture:</t>
          <ul empty="true">
            <li>
              <t>Correct correlation requires preserving sufficient information to maintain 
the relationships among an Activity's Dialogs, Tasks, and Resources. 
Such information may be maintained locally or selectively propagated
between participants, depending on which associations need to be 
established and by whom.</t>
            </li>
          </ul>
          <t>A propagation mechanism SHOULD therefore support detection or mitigation
of missing, stale, inconsistent, or excessive correlation information
without requiring every participant to maintain the complete Activity
graph. In a protocol-managed scope, the architecture further
recognizes the need to distinguish failures to maintain accepted
correlations from interactions that were never included in that scope.
Where supported by evidence, the affected managed step and its
responsible participant should be identifiable. This does not imply
complete visibility into undisclosed downstream interactions or
perfect attribution of the underlying cause of failure.</t>
        </section>
      </section>
      <section anchor="propagation-example">
        <name>Propagation Example</name>
        <t>The video-analysis example can be expressed as follows.</t>
        <t>Initial Dialog:</t>
        <artwork><![CDATA[
Activity A1

D1:
  A <-> B

Task TB1:
  V1 input-to TB1
]]></artwork>
        <t>Tool transformation:</t>
        <artwork><![CDATA[
A -> Tool X

T1 derived-from V1
T1 output-of the transcription Task in D3
]]></artwork>
        <t>T1 enters D1:</t>
        <artwork><![CDATA[
T1 input-to TB1
]]></artwork>
        <t>B creates a downstream Dialog:</t>
        <artwork><![CDATA[
D2 delegated-from D1
TC1 delegated-from TB1
]]></artwork>
        <t>B projects:</t>
        <artwork><![CDATA[
Activity correlation
V1
T1
T1 derived-from V1
task objective
]]></artwork>
        <t>into D2.</t>
        <t>C develops local context:</t>
        <artwork><![CDATA[
T1 input-to TC1
T1 appears unnecessary
]]></artwork>
        <t>C asks B for clarification.</t>
        <t>B uses locally retained lineage:</t>
        <artwork><![CDATA[
D2 delegated-from D1
TC1 delegated-from TB1
]]></artwork>
        <t>to resolve the question upstream.</t>
        <t>The complete upstream Dialog does not need to be copied into D2, and the
downstream Dialog does not need to be exposed to A.</t>
        <t>This is the intended meaning of context propagation in this
architecture.</t>
      </section>
      <section anchor="relationship-taxonomy">
        <name>Relationship Taxonomy</name>
        <t>The following are examples of relationship types that are useful
at the architecture level. They are illustrative, not an exhaustive
or normative set; the dialog-management protocol defines the
relationship types that are interoperable.</t>
        <t>The table does not define a registry or a wire vocabulary. Endpoints
are logical objects; where local identifiers are used, they are
associated through the mappings described in "Binding to
Protocol-Local Context". "Use" names the primary architectural
purpose; application-specific interpretation remains outside the
interoperable baseline.</t>
        <table>
          <thead>
            <tr>
              <th align="left">Relation</th>
              <th align="left">Endpoints</th>
              <th align="left">Direction and meaning</th>
              <th align="left">Non-implications</th>
              <th align="left">Use</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>belongs-to</tt></td>
              <td align="left">Dialog→Activity; Task→Dialog; Resource→Activity</td>
              <td align="left">Subject is grouped with the referenced Activity or contained by the referenced Dialog.</td>
              <td align="left">Does not imply visibility, authorization, or shared lifecycle.</td>
              <td align="left">correlation</td>
            </tr>
            <tr>
              <td align="left">
                <tt>delegated-from</tt></td>
              <td align="left">Dialog→Dialog; Task→Task</td>
              <td align="left">Subject exists because work from the referenced object was delegated into it.</td>
              <td align="left">Does not transfer authority, couple lifecycles, or make the upstream responsible for downstream work.</td>
              <td align="left">correlation; application interpretation</td>
            </tr>
            <tr>
              <td align="left">
                <tt>derived-from</tt></td>
              <td align="left">Resource→Resource</td>
              <td align="left">Subject was produced from or derived from the referenced object.</td>
              <td align="left">Does not prove derivation or authorization; not transitive by default.</td>
              <td align="left">correlation; provenance</td>
            </tr>
            <tr>
              <td align="left">
                <tt>input-to</tt></td>
              <td align="left">Resource→Task</td>
              <td align="left">Subject is consumed as input by the Task. Binding is local to that use.</td>
              <td align="left">Does not imply the Task requires it, or that the use is authorized.</td>
              <td align="left">correlation; application interpretation</td>
            </tr>
            <tr>
              <td align="left">
                <tt>output-of</tt></td>
              <td align="left">Resource→Task</td>
              <td align="left">Subject was produced as output of the Task.</td>
              <td align="left">Does not imply Task success, completion, or authorization.</td>
              <td align="left">correlation; provenance</td>
            </tr>
            <tr>
              <td align="left">
                <tt>continuation-of</tt></td>
              <td align="left">Dialog→Dialog</td>
              <td align="left">New Dialog carries forward work associated with the earlier Dialog, including not-yet-started work; relevant context or correlations may also carry forward.</td>
              <td align="left">Does not by itself imply taking over the earlier Dialog's overall objective, auto-terminating it, transitioning Tasks, or transferring all correlations.</td>
              <td align="left">continuity</td>
            </tr>
            <tr>
              <td align="left">
                <tt>replaces</tt></td>
              <td align="left">Dialog→Dialog; Task→Task</td>
              <td align="left">New object supersedes the earlier one as primary pursuer of the earlier Dialog's objective; at Task level, supersedes a Task.</td>
              <td align="left">Does not auto-terminate the original, transfer Tasks or correlations, or erase historical associations.</td>
              <td align="left">continuity; history</td>
            </tr>
            <tr>
              <td align="left">
                <tt>aggregated-from</tt></td>
              <td align="left">Dialog→Dialog</td>
              <td align="left">New Dialog was created to aggregate or consume results produced independently in multiple upstream Dialogs; multi-parent.</td>
              <td align="left">Does not imply completion depends on every source, nor inheritance of authorizations or lifecycle.</td>
              <td align="left">correlation; application interpretation</td>
            </tr>
            <tr>
              <td align="left">
                <tt>related-to</tt></td>
              <td align="left">Dialog→Dialog; Task→Task</td>
              <td align="left">Weak assertion of correlation without delegation causality.</td>
              <td align="left">No delegation, dependency, authorization, or lifecycle coupling.</td>
              <td align="left">correlation</td>
            </tr>
          </tbody>
        </table>
        <t>Endpoint lists are illustrative, not exhaustive; other logical
associations may use the same relationship where its meaning applies.
A companion protocol may initially standardize only the relationship
types needed for its core use cases, for example <tt>delegated-from</tt>, while
allowing new types to be introduced without changing the underlying
correlation model. It must define how unsupported relationship types
are handled; receiving an unfamiliar type must not silently impose
lifecycle or application-execution effects.</t>
      </section>
      <section anchor="privacy-and-administrative-boundaries">
        <name>Privacy and Administrative Boundaries</name>
        <t>Administrative boundaries separate participants operating under different policies, authorities, and retention practices. Correlation across such a boundary is constrained by identifier linkability, selective disclosure, and the need to translate or alias references, without requiring a common view of the Activity. These constraints are policy- and authorization-dependent; the architecture leaves their concrete treatment to the participating domains and protocol bindings.</t>
      </section>
      <section anchor="relationship-to-dialog-management-protocols">
        <name>Relationship to Dialog-Management Protocols</name>
        <t>A dialog-management protocol may standardize only the subset of the
architectural model needed for interoperability.</t>
        <t>For example, a protocol may define interoperable representations for
selected DMS information and related correlation assertions:</t>
        <artwork><![CDATA[
Dialog-ID
Dialog-Relationship
Lifecycle State
Participant-Membership State (where supported)
Propagation State
]]></artwork>
        <t>without defining:</t>
        <artwork><![CDATA[
required-for
optional-for
application-specific planning semantics
]]></artwork>
        <t>This leaves application-specific semantics outside the interoperable
baseline.</t>
        <section anchor="functional-placement-of-dialog-management">
          <name>Functional Placement of Dialog Management</name>
          <t>A dialog-management protocol is a complementary management function,
not a layer through which all application messages must pass. A logical
management endpoint exchanges the information needed to establish and
maintain authorized local DMS views and selected correlations. The
endpoint is distinct from the agent, application, or principal it
serves, even when implemented in the same process.</t>
          <t>The following illustrates one possible arrangement for a Dialog D1:</t>
          <artwork><![CDATA[
Participant A / domain             Participant B / domain
+------------------------+         +------------------------+
| Application / agent    |<------->| Application / agent    |
|   application content  |         |   application content  |
|          |             |         |          |             |
|     Local binding      |         |     Local binding      |
|          |             |         |          |             |
| Management endpoint    |<------->| Management endpoint    |
|   local DMS(D1) view   |         |   local DMS(D1) view   |
+------------------------+         +------------------------+
       application exchanges above; management exchanges below
]]></artwork>
          <t>A management endpoint may serve several Dialogs and maintain local
cross-Dialog assertions, enabling correlation across an Activity
without requiring a centralized Activity-wide DMS. The implementation
might use client-server, peer, or service-based arrangements; the
architecture does not select among them. The companion protocol
specifies endpoint roles, operations, and transport bindings.</t>
          <t>Application-protocol identifiers and management references are
associated through local bindings. Such bindings may be realized in
application libraries, sidecars, or management services; they do not
require the dialog-management protocol to carry application payloads
or define a new binding specification for every application protocol.</t>
          <t>The separation between Dialog management and application-level interactions is logical and does not require the use of separate protocols. A dialog-management protocol may operate alongside application protocols, such as A2A or MCP, through local bindings, or it may provide mechanisms for directly carrying application payloads associated with Events within a Dialog.</t>
          <t>In the latter case, application payloads may be carried alongside management and correlation metadata while remaining semantically distinct from them. The handling and interpretation of application payloads remain the responsibility of the application runtime. The architecture supports both approaches without prescribing either.</t>
        </section>
        <section anchor="architectural-vs-protocol-surface">
          <name>Architectural vs. Protocol Surface</name>
          <t>The architecture defines Activities, Dialogs, Tasks, Resources, and
typed Relationships. DMS is the logical per-Dialog management state,
not a mandatory wire object or an application message log. The
companion protocol determines both the information that needs an
interoperable representation and the exchanges used to establish,
modify, synchronize, and recover it. Optional Task, Event, Resource,
and security-evidence references need not appear in every Dialog.</t>
          <t>The agentproto charter identifies Dialog identifiers, lifecycle
semantics, and Dialog-context propagation as subjects for its
standards-track protocol work. This information model examines related
correlation concepts that may inform that work, including:</t>
          <ul spacing="normal">
            <li>
              <t>Dialog identity and identifier aliases;</t>
            </li>
            <li>
              <t>Dialog lineage and other typed relationships (e.g., delegated-from,
aggregated-from, continuation-of, related-to, replaces);</t>
            </li>
            <li>
              <t>Dialog lifecycle and propagation assertions;</t>
            </li>
            <li>
              <t>Activity and Task associations where cross-Dialog correlation needs
them; and</t>
            </li>
            <li>
              <t>Resource identity or provenance associations relevant to correlating
interactions across modalities or tool invocations.</t>
            </li>
          </ul>
          <t>Protocol design determines which information is exchanged, locally
retained, or supported by application protocols. Resource Binding
remains primarily an application interpretation.</t>
        </section>
      </section>
      <section anchor="relationship-to-a2a">
        <name>Relationship to A2A</name>
        <t>A2A provides useful local constructs such as:</t>
        <artwork><![CDATA[
contextId
taskId
artifactId
messageId
]]></artwork>
        <t>These constructs may be associated with the architecture as an
illustrative mapping:</t>
        <artwork><![CDATA[
A2A contextId  -> may be associated with a protocol-local Dialog context

A2A taskId     -> may be associated with a Task

A2A artifactId -> may be associated with a local representation of a Resource
]]></artwork>
        <t>The association is not required to be one-to-one. An application may
use one construct for several architectural objects, several constructs
for one object, or a partial correspondence, and its local identifiers
may change while the logical Dialog persists. Relevant local
identifiers can be associated with the logical Dialog where continuity
or correlation requires it.</t>
        <t>This architecture does not replace those constructs. An A2A
<tt>contextId</tt> identifies a protocol-local context; it is not, by
definition, a DMS identifier or a complete DMS representation.
Application-specific mappings can associate it with a logical Dialog
and relevant management state without changing A2A's own lifecycle.</t>
        <t>It provides a model for correlating them with objects outside one A2A
context.</t>
      </section>
      <section anchor="relationship-to-mcp-and-tool-protocols">
        <name>Relationship to MCP and Tool Protocols</name>
        <t>MCP provides tools, resources, prompts, and callable tool interactions within its own protocol context. This model adds a way to associate those interactions with Dialogs, Tasks, and Resources, and to correlate them with work outside one MCP interaction. It leaves MCP message, tool, and resource semantics to MCP and does not replace them.</t>
      </section>
      <section anchor="relationship-to-distributed-tracing">
        <name>Relationship to Distributed Tracing</name>
        <t>Distributed tracing records execution spans and parent-child links for runtime observation. This model adds participant-visible Dialog identity, lifecycle, and typed relationships across independently controlled Dialogs; whether a participant is authorized to propagate a correlation remains distinct from the correlation itself. It leaves span formats, collection, and export to tracing work, and distinguishes runtime correlation state from Activity or application progress and from post-hoc audit or transparency evidence.</t>
      </section>
      <section anchor="relationship-to-vcon">
        <name>Relationship to vCon</name>
        <t>vCon represents conversational data such as recordings, transcriptions, parties, and analysis. This model adds cross-Dialog identity, lifecycle, and typed relationships so that conversations represented separately can be correlated. It leaves conversation representation, media handling, and vCon-specific analysis to vCon and its maintainers.</t>
      </section>
      <section anchor="architectural-considerations-for-protocol-design">
        <name>Architectural Considerations for Protocol Design</name>
        <t>The following capabilities inform protocol design; they do not each
require distinct wire fields:</t>
        <ol spacing="normal" type="1"><li>
            <t>multiple Dialogs within one Activity;</t>
          </li>
          <li>
            <t>independent protocol-local context identifiers;</t>
          </li>
          <li>
            <t>stable Resource correlation where useful;</t>
          </li>
          <li>
            <t>delegation lineage;</t>
          </li>
          <li>
            <t>selective projection;</t>
          </li>
          <li>
            <t>hidden downstream delegation;</t>
          </li>
          <li>
            <t>cross-domain operation;</t>
          </li>
          <li>
            <t>identifier translation;</t>
          </li>
          <li>
            <t>provenance correlation;</t>
          </li>
          <li>
            <t>privacy-preserving correlation;</t>
          </li>
          <li>
            <t>correlation of lifecycle-affecting requests, resulting assertions,
and dependency-driven consequences across Dialogs and Tasks;</t>
          </li>
          <li>
            <t>distinction between the logical Activity scope and correlations
established or maintained under a particular protocol;</t>
          </li>
          <li>
            <t>selective extension of managed correlation, with responsibilities
for maintaining the associations participants have accepted; and</t>
          </li>
          <li>
            <t>detection or reporting of failures within managed correlation
scope, with bounded identification of affected steps and responsible
participants where supported by available evidence;</t>
          </li>
          <li>
            <t>a distinct logical DMS for each Dialog, with distributed local
representations and appropriately scoped shared correlation state; and</t>
          </li>
          <li>
            <t>continuity of Dialog identity and DMS across authorized membership
changes, with consistent management-state authority and recovery
semantics to be defined by the implementing protocol.</t>
          </li>
        </ol>
      </section>
      <section anchor="out-of-scope">
        <name>Out-of-Scope</name>
        <t>This document does not define:</t>
        <ul spacing="normal">
          <li>
            <t>An agent's internal memory;</t>
          </li>
          <li>
            <t>Prompts or retrieved documents;</t>
          </li>
          <li>
            <t>Chain of thought;</t>
          </li>
          <li>
            <t>Agent planning semantics;</t>
          </li>
          <li>
            <t>Authorization decisions or enforcement mechanisms;</t>
          </li>
          <li>
            <t>Delegated-authority mechanisms;</t>
          </li>
          <li>
            <t>Trust establishment mechanisms;</t>
          </li>
          <li>
            <t>Agent discovery mechanisms;</t>
          </li>
          <li>
            <t>A wire format.</t>
          </li>
        </ul>
      </section>
      <section anchor="open-questions">
        <name>Open Questions</name>
        <ol spacing="normal" type="1"><li>
            <t>Activity and Task are architectural concepts, not baseline
protocol objects. The exact protocol surface for optional Activity
and Task lineage extensions is to be determined in the protocol
draft.</t>
          </li>
          <li>
            <t>Should Dialog lineage be visible downstream or remain local by
default?</t>
          </li>
          <li>
            <t>What is the minimum Resource correlation required for multimodal
Dialog continuity?</t>
          </li>
          <li>
            <t>Should Resource Binding semantics remain entirely
application-defined?</t>
          </li>
          <li>
            <t>How should logical Activity identity survive identifier translation?</t>
          </li>
          <li>
            <t>How should partial resources such as video segments be represented?</t>
          </li>
          <li>
            <t>Which relationships require integrity protection?</t>
          </li>
          <li>
            <t>How should context-resolution questions be correlated across Dialogs?</t>
          </li>
          <li>
            <t>How much lineage should cross administrative boundaries?</t>
          </li>
          <li>
            <t>Which subset of this model belongs in a dialog-management protocol?</t>
          </li>
          <li>
            <t>Whether a long-lived protocol-local context may be associated with more than one logical Dialog, and how such mappings relate to the model's rule that a Dialog belongs to exactly one Activity, is a question for protocol design and deployment.</t>
          </li>
          <li>
            <t>How should the dialog-management protocol define authority,
membership changes, authorized DMS views, consistency, and recovery
of shared DMS state across participants, without mandating complete
replication or disclosure of private correlations?</t>
          </li>
        </ol>
      </section>
      <section anchor="iana-considerations">
        <name>IANA Considerations</name>
        <t>This document requests no IANA actions.</t>
      </section>
      <section anchor="security-considerations">
        <name>Security Considerations</name>
        <t>Correlation metadata can reveal workflows, delegation, and Resource
relationships.</t>
        <t>Implementations should minimize propagated information, avoid semantic
identifiers, and treat correlation identifiers as non-authoritative.</t>
        <t>Possession of an identifier does not imply authorization. Similarly,
Dialog membership does not authorize disclosure of participant-private
correlations outside the shared DMS scope; admission and continued
access to shared DMS views depend on applicable policy and authority.</t>
        <t>Relationship assertions may require separate integrity or provenance
mechanisms.</t>
        <t>See "Propagation of Assertions" (§8.8) for the distinction between an
assertion and its authority or trustworthiness.</t>
        <t>The following dependencies are architectural; mechanisms are left to
other work:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Risk</th>
              <th align="left">Needed architectural property</th>
              <th align="left">Left to other work</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Forged lineage</td>
              <td align="left">Authenticity and integrity of correlation assertions</td>
              <td align="left">Concrete signature or authentication mechanism</td>
            </tr>
            <tr>
              <td align="left">Wrong alias mapping</td>
              <td align="left">Integrity and binding of identifier mappings</td>
              <td align="left">Specific mapping protocol or storage</td>
            </tr>
            <tr>
              <td align="left">Unnecessary end-to-end tracking</td>
              <td align="left">Limited disclosure and linkability control</td>
              <td align="left">Specific privacy technology</td>
            </tr>
            <tr>
              <td align="left">Unauthorized forwarding</td>
              <td align="left">Authorization for propagation</td>
              <td align="left">Authorization protocol and policy evaluation</td>
            </tr>
            <tr>
              <td align="left">Lost or intermediary state</td>
              <td align="left">Clear recovery and failure behavior</td>
              <td align="left">Transport or storage resilience implementation</td>
            </tr>
          </tbody>
        </table>
        <t>These properties depend on identity, authentication, authorization, integrity, and privacy building blocks developed elsewhere, notably by the WIMSE working group and in the OAuth framework. This architecture does not define those mechanisms or agent behavioral security.</t>
      </section>
      <section anchor="privacy-considerations">
        <name>Privacy Considerations</name>
        <t>A distributed Activity MUST NOT require a globally visible participant
list or a globally stable identifier.</t>
        <t>Implementations should:</t>
        <ul spacing="normal">
          <li>
            <t>minimize propagated metadata;</t>
          </li>
          <li>
            <t>preserve participant opacity where possible;</t>
          </li>
          <li>
            <t>translate identifiers at administrative boundaries;</t>
          </li>
          <li>
            <t>avoid propagating private dialog history;</t>
          </li>
          <li>
            <t>limit retention of correlation mappings.</t>
          </li>
        </ul>
      </section>
      <section anchor="appendix-a-canonical-architecture">
        <name>Appendix A. Canonical Architecture</name>
        <artwork><![CDATA[
Activity
 |
 +-- Dialog D1 --- DMS(D1)
 |    |
 |    +-- Task
 |         |
 |         +-- Event(s) (application interactions)
 |         +-- Resource reference(s)
 |
 +-- Dialog D2 --- DMS(D2)
      |
      +-- Task
           |
           +-- Event(s) (application interactions)
           +-- Resource reference(s)

Resource Layer: Resources may be referenced by multiple Dialogs/Tasks
]]></artwork>
        <t>The DMSs in this diagram are logical per-Dialog management state,
not additional correlation objects, Task containers, or a common
Activity-wide repository. Correlation relationships among the shown
objects may be maintained or disclosed selectively.</t>
        <t>Illustrative relationships:</t>
        <artwork><![CDATA[
Dialog belongs-to Activity
Task belongs-to Dialog
Dialog delegated-from Dialog
Task delegated-from Task
Resource derived-from Resource
Resource input-to Task
Resource output-of Task
]]></artwork>
      </section>
    </section>
  </middle>
  <back>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false">
      <name>Contributors</name>
      <contact fullname="Hesham Moussa">
        <organization>Huawei Canada</organization>
        <address>
          <email>hesham.moussa@huawei.com</email>
        </address>
      </contact>
      <contact fullname="Arashmid Akhavain">
        <organization>Huawei Canada</organization>
        <address>
          <email>arashmid.akhavain@huawei.com</email>
        </address>
      </contact>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+y963bc2JUm+B9PgZHXLFFjRFRRadkusuxpSlSWNZ3KVKfo
tN1T0xYYAZKwggEOgCCTblWteZv+3/MG8yjzJLPvZ+8DBMl01epfE2vZKUYA
Bwfnss++fPvbi8WiGNtx0xwVZfnsTbcdmx/Hst6uyzdd3zebemy7bfm+3taX
zXWzHcuTfnXVjs1q3PVNedH15Wk7jH17vhubdXlyCZe0K2jqZDW2t+3YNsOz
oj4/75vbo9T8nuaeFat6bC67/v6obLcXXVGsu9W2vm6OynVfX4yLGpu/6bux
W6y4qcW1NbWoXVOLvz8sht35dTsM0P/x/gbaePf27Otiu7s+b/qjYg1POiqg
U4dF3Tc1/Art9dtmLO66/vNl3+1ujsr0vOJzcw8/rHGUFuXJu/LbZsQL+U9+
a/1u0GvgHZq+2a4a/WLs63bbbi+Lot6NV13PrV3sNht+y981w1V9Xb7vdsNQ
w29l2fWX9bb9K80C/L6r75q2fAPvvObfm+u63RyVV3Tj8ppu/A9XdNly1V0X
2QNO+nq4um5hoj5f1bfQmZ/ykFpuXtZyc3gQTggtg/8Rr/U/6q0WsDvw/8r6
HBZ5vRqLQie7vrnZtCtqfYCZXsEiGmBqN/fl2jZE2Z3/pcGN0Axlveq7Af4D
A7Tt8I14dQ1VOXbdBv6De25o+tt2BVd3N00PbW8v9b51e0GLaSxpPa7gFrqj
Xl/DksLO4WPKdQdvtR2W5UlJvWl0I96X1/U99PO228Bl17vN2N7Ar+123dw0
8H/bcYOXtNsR/gc7+bStN90ldOusHj7Df97ecmfxmd83Q7froZtVOdzUW1zR
rn/X3bre0M6ni2GTYvvrEt6o7dbwahfl2F43y6J4+yN0HG9OrwT/um3X0C/s
UXvRNj23Mt3u5XWzuoIJHq4HEkPjVdP2ZXe3hXeCnQxzhTNTlTAP+NuAY1Nu
u7HcNtDzoe5beOFhd3PT9SM0n2SdDLgNgHWumhvw8263XUNjOBg3dQ8rY7ep
e2i6HkJHyoZGHvrT19vVVQXLs+ybYXcNi+S26XVIzq5amOtutaNXXDcXMBkw
Avb+0INF6KyXxuf1AOMM3ybhW00m0k0evg6KRpxRbm+4am9g8bzDRw8rWMTw
8KvurnTDzrORenDdjLCjRuhivS3PG7+GeEVveAfAkMBI3tSXNR4UYwd/Nbjc
G2jtilfOSk8fXfLpYIlzenfVwtqtN5vujpYPjXsLS3EcsOV1AxfDLDU48eWw
gs2Eq871esBfYPqvQPZTN/kFl7zZQRqsN01R/AwPhb5b7+i5ReFPulrEwHA/
jA0sQWwoSAEQHzcdzcfFvu3Gmxy3hnsB6MN07+LYyt49gj5Cv247lj3l+X25
g3HE6RR5Aiurg9fr6Y7POEDSyWO48zsYFboQRmnTXLKMwVMLB67e0o143ccG
VmW98T3m+xZw+HIDsrLw6hP9BWVZmCz81ZYcrgAYTZpPWKeNbAbd4bgb6CfX
j1PY0TDqDZwf2mF46SuYoWZbXvTddbm7kd/9KOKt71kQ3eOxux1ARlzXsn6G
HT50KFHUdPTiu3VL/8D1R/fqjIHYW3f9Q7IWL/8GZmNjkoLeZexh2eA6q0eV
PLzcvGiDqRpGWALH2D7ODot9eEMSCkmo0iuQqDJxBAulKKyfacuToIerVk1D
o7ra9T2vt7t2vILRpU0BB2fYYHE9L8s/8LVNDSOly7DihYLts1TXnfr4KYKP
jvsUDltcerft0J63NE1wVwerAgUFXMgHxRWLR9jqflWpoAR1aiDxeEM/4BzA
mbDZNNtLUAtggqm/KFF56TTrioTuZuQN2zewdda0Y4KsFsEMKmcjv/S7G1k7
KA5xO2LXQJw0t3XaCiZkwykJl+GQsPxZjXQ2DN2qxf78r+UDh2A60h4+/vBp
blX5Mw+6tbWTr4G1dr5phyt+JxI/55smCsbHptQP1OTAakVe0tlPOrxsOtQK
mg0d1H1Dkn9LL829jB0gpaG+ppMPR5tE9eOnC+2uNWg+26jzyFI9b+47PO+u
ssfxkOIPoPNfgliAbYGT6cdap0ZPHtDdh4a3Npz+TT/WnxuUHtq7NNLNOns5
WnWwk7ew7DdsQMlBKMMBMy4H4qrZo0TQsDeyrODxvFPCPAyq/uJAoYKEZyWc
7B8baql8WZDcGXQ8Gq9JkCiDwwwFC69lve0rVUkKPmE7GKj71Oov/ALAlmOj
vAZQ0rWbzY7kKFzXjjb21x3MGx9JuALg8SJAeU16jb7eFEn1Sj14FZfOY4IJ
rJYG95+KRtwsSdr5N/8lSP81TBTKG9rkektdcFupD79yytM59IAmtrNFtNjQ
YSFbelnobb+G22AhdzfDvH6l2hN8WaGqsdlRy6TeFKzD4FrZ1rhwbI21G9ED
cTpcEzwZuKBrXC5F0s0q08Pgu79w5yonX/gs2khHLuBJVzDcQ1WAjS9KiajC
8JZJvMOlYG+hmopPHlAQb1j5Mf26iMsFT1F4bK+ndrcbF93FgvW5FhUaniL4
c1v+nzvYc7Myac3ydYe7cQCJMY4b3BTzy30gnaKgJqGX7aVvucRdF59GGxoG
EiYbV/MRCatCBuueBn3drFp0QqCtxDODWu9ajZapuClMj8C3w8tWXdfDZPPE
0VGqg4cHHPXrHntSgJRct2vaVixqh26zo7tgpQ6786GBnjuBZqMEQwknRHFZ
36DEyfcuShzQht+gnDgJA/dBB45FUjBH4Ol4isMWUX12BU8Kww3K7G/Ld360
2GLmU6D3VgnYbc2aLYfPTXMTtza08oDtGk9j3VyNqS86GtDKgxbesjwl6Wdi
Ou3SAWQx6k8DtIETBGsVD7pNvfJHu2z9dHRz39wKhdvjW7vXoptBjJHW689W
EpE4PGT9nDfQiDO1LlS74fOeNuNyZrriPnHuDZYHsGrowThJTzEHk47DK7Yd
4Wh2jSZ1Z1X3PU9+OOvM7Ef1F98QD3PzMjVsr7De+hxndQt64iBnA2p033zz
XiWZntvTk/1it12pHiBnN+sfOEOXbEDaK6UV+Kjt+mS/SlybeqYkFUZmio/O
HZ4+F7goYQdd1zBqsl1gH/3rv/5roTfJkVTgMwptvfBGPl3uWq43Q+cPb27A
O2o/or5QHpy+//gCeu2WwII0CfOQkVcim3uyIqA90tD1uISWbGBYW+Bfng9+
ffl1LjKBVe6gVtFT2OiNgl3GZzl9Vz3PUFLuehvvBTeKQ5yslbLv4GjIBhmM
cDhaWVt5C23BNwcn796+KL5ue9AovsXVoN9//S18fzIMsMWwOTKX4eoT/+UZ
ms4HJ2cveG6+x0eKvig9QvuUdokZ/7BK2y0dOiU8Gn6hHrH2nfSYdkRnitge
5BSAiWm4ay0PPXSQ1yJ9jaOi162TAY6dyV6CTNj4DnhOJuVQVU8QS/AfmYfJ
0Ipaueazpx3yg+QC1Y7OlpB1Mu0XJzrKuxodbSC+cT2A6NjSfkWNLOnYdD1K
ihbVTFxqNKJsPryDwaARCS8nk8li6Bp24OAcqWQHbO5zdxRoheRr2Op4490g
W5u6J8MEu8DOQjskZeuB8LjpoJcqu3ASrdNBISDzL5qvZG+ykwTeaEN3sZlU
sXOiHVkP8BY5dg1MLFLZyMhhpXxo4Crc4SK6oD9o/cRjCpdG8yNK9xYXmbN/
WGuKu1LnnLVk0tRtSq1LY1Pum9rMjXaRz6k3FFQfnBqjOIk89cMe5byYtbfR
ub7fRqRh3JF52BT0oOdDUg/0VLsFhc1EWYi06WEjw1+IBUFHezPxFRzPbJd1
B8OI9j5vqoKtVW1niZqc26DoTlRRcaTioO/gdhjXPaPPUmaNvke0mHRbPiYZ
6eTc9cMOfa4pNiJyvaZ9UpSo58PUNNGSpxnU595dNVsn9FBQDaEne0RwlRam
SAJ7wHNtPx1Q70boDEUC/fHEU8gLTs7wsbtsSNbQMYSX2okOLYjfFuwqVuXT
XMNYoIuYDAt4P3oUxVJ0AlE2gXCARti5kWs5qnRAu7Ve4mUrGDsq0KANDgDx
GCbB5WMFpP1uZ93OeL/eQgErutg7IzEm91as9qOCQmx4kOF/T6Cz939txN/6
wyF9+WGD6htYk6CN4N/v4NVgdV+SMgG6FsVSwWiEp/L1PQoi/A1WNRi5OFXw
VdeP9iz0F9Mk0UKubTngOKH61QfHTH3dYXwNR4lkyF0HA4nviWZOjCmg+inB
gj1zQEETPON4q0IzzY81HbhTnwL0DQMFGgeZ2RH4QGgiabsDH/7QDVMMSa7K
YaGqMYr9v4KmjysCXwPakDVK24seRUFFej/1sJreZR1AESdNt7iG1WCCTuA5
ZAuEtkInmtfDqm13Ae2EN7ATZs5+4NdL1gTqbKDBwLE3UDuu15v2olndr2Bh
kiYa+o7+CTJ5yavc9ndwaLN/FIYsbU6ec1IVcBnEE/xM/eWyUPJDk7aWGA+D
hE2S3z36wL373caBVt0kzps25rJ8i7OXXsqUVxLBOCOgpOHbrFnLIGNef5oI
hLfQxXtt7QpdjNaALYBqzzLnWZ2M+Du02E3ph4ZQuQdzE1WnQbehBEWnXSrZ
2EIhsnjY8jiiydBt7U5fsUEyu6OW1ipV2HDtYwdsXWkkKI1c9m6VWsKoErl+
L64bBJKg9uNVi2oKndFHedHjlkJm9KzZoTeZ8vzV/GkHI0NaItyAguCq9hF+
H+Qx13sdbd60jiYrnzS9eBeawbzANJgFnaC5w40vope8JnDdDg4c3DQkzFVd
T9MyIwb9MhTvby4G94kssndLPJUuxVWrIgaHS2SiQRl4xOr1LXlM6UmpNYQw
UXt+h8yJGrpGtAQVk/wEtgnoxLi+7rZ+c1nomp0uK1zAPaycIR8qExayEsi/
4/e/auebezqC5QCm4JcX8SZrnt2kY/dZJZboCa1a+je08VrjwaLVwDPhF/Jv
kpoBJ+4GfebQNJwmI+2Mqw66QK5D1FZW+CT3Bviw56Twj2K0LMt/4iZZD6Pj
VdttVcKnZRAOKhiB8a4BDXDS+fK1Bi71rNGF1jfQh4ZiLGTl3tabnQQacJ9R
96cLF5ciz0fFzbV4rNGUxwgpfjMzmOVrHAxyb6FDUJbFghRBCXBg18ibLH34
I40TbErEm6w2dd9e0DkF953DZvl8UcOl0CIKTJR8ZKOurprV5xLRSxtx8MFD
WE1F1Z+fq1okjSR2+Pngvfq1YCJ089CGpjtlR18jauYSF2/5l+7ceSHwG4r7
o4yvRBltr6EvPZ2wyX7AocBFi4Nxzi6/cJhaH0QWSDe9RCB9lrpFG3PbxVUi
G5W0sda2gM4CznfHsVGZRGssqW5BcaPdjRGrUjovyuDs+LWjEz1LnW4ccrIq
cU12znJgdRt+RVnqdSB1WqXekX7H66hndwiFB9U9KpErFXAJgeUDRXJ8I9IB
vr6GqRQdjbRy624ueKinXe81TbRu5/BeVYQbIA7FoE2wLcSl2m71lnuzdCo5
f5rNBW+IFv0J3lZDi+Au6wwtUdUweZVubUpILPFI8pSFlSZok4pPC/R5VuZm
oiVsmJFyvetZbDgtPgBIsBEZVh5jF1ShZlYg/hToh+vvZidIOryRkDOGi8E+
XtSroHbqG2oMHDELPIqis+L+cEaG6A4hCG4utHZMU7cRe2ToVBseh1ktnpfG
xJPjXA3qYGtI/icgHGpaVx2BoHTZ4mCaWQAblYJ8cXjrLfZGZTcLV5gT3gs4
CvY63tiu1DKnYYMG8oGju3pWN2C9qa7Oh8s1yixQmupt0+0GPE5LHzTCQxNt
EGjm5up+EH1WBZpsGhknXpbJPSYClKB2lXhiWatWrY7ceGiOBuT0FLwHg+CG
7iQ44dD/xqIHl9U2tK0nJk6wOhahAd9J6t6gjZD3CuyapiZ0Jw0RHiWu0fn7
UZ459RfaeG8WXdZfBmfgiV8TPgMPaVZGNYKG3cVm4ceWxgbUpdWGUHUH8k9c
hbS4Jj2hMbfgq0Zb7e0Zr/G5ebEs0Uq+aubaEMUX9WN0XzPKT7ELdBqdEX7i
GqQKv+0DjsHhBjpzofGvO2jHIRVJGVVLO3ZC5SF6odd1vyZQR/QoBjwPteJV
9pLUDRa/S/PRyNHQkK+GPTVyCC7If2GYqQWFxPGLHl7Z/my3IMf4UpZpCzpo
xQ/ze0XlYfcSiO+IA+ZuC+AADCHGUZeX8K+tSYBlaox2ME2dOuMoJsmaPOvN
dUB7iSboHjnRiPc4K5eu1zSi+ZPVdgFJkkEpKw2hp4fWdyRgLYIKT8BosgEa
Ba83uHALbi+CqlVkbOzsyPCqwu6Go/2K91MwJMkgSbc4sqiKHkyVex2Sl+zY
CC59eNCBj7G9EH/ZQ+IpA4dzd+UZe5zctYcaoxhearftcNHRT/EvcfOz0R+N
WDxH3gnC9WDo4PgB7WMg9W1DuI/ymXpNwQCD0X4GM83wVWsXTPuuZ+dWy7rC
qKCqHZs9ZKJDo+9C8MgFkQVtIxuf+inR48wJjMqDahNq7a81GFKhvG16Nt3d
3FTB+SrCJl8a1EnGgfD+INW6Xq2aG2zwQbQQbe8sxlLPDhLh10D+jckRerY/
IpHUBAb21eq5gTuGEfQZfAloEh696e5xA99dNYJlRn9ue97XPepfMEZw9laa
MEEnI4pJsOsorA+KG86P5TOlCCPG6+lswNPczG/bmA73wA5Yc4IlTchWxD5/
E5nieDJw8JNgWnCgbdamQ8BgNOsj7V/lOzi3WUWak4Kbg6Sc71Txdfh+531X
rzX+6YxnXf3hcY1LdUI9HZZcz2cbHRKDyE3zUbMZ4k4q7TR3IQtgsOkMlgKc
m/jy4SBzZ9NajcL9h2hy7oL1hU5GNzbqpJm6BQ0pigenRlKSaGN3KfVfRy0O
8hvF6pFQncoxi5tNUDkzvuKELZlDMnlxNidqk0d/P6qJnfKwtzmM6ywpGhSc
yAlwhXfLXFoHCoaB4djJ6PvcirOKBRSPYpNrFpnUcqLu2enLTMEoTw+f4WJ4
dnYYNI3yh8NnepRMfLOpuVclwg8/N+tnnL5iK5C7EqwB2b3oqEgAouxUQVua
JBxN+gcVtQz0TwerAmh5T8Vxtoix7TVe3qiezwCh2K7LXKTL8mvvK8LT7eUJ
NPBJHvlu/Qm7+mmENQH/hjkYVyXHqeb7PO9jPxI91iUWBTe/21IkBpKZgoFT
HxiVxencDlnDrH4F44oOJnQqqP3mIkSwh1II9prADFcUFy9LTP5bC0jfCTh2
IiGya13T0bwxJ7TzRVWmXvpQQ8uLZtNet+KWlnebjfmz80DOeM4kGwTRnnBl
DKrBrTjkiUpBGGTSI2HNvE6RYeWXcswE7IFJxCmSDZYdWAk9BYAtx6K2kRCR
OsUvuuW6iFpNcMGUrxljcORUutp+hdZxjhWNeIPWngFaQU8PHgC1/Tt2lS05
6Sl5Ev9Q3za2/db3sBTEIgf7tWbItSi1jwnOKeRuNnFEJFDzY7PaeehoiJew
0xHBE3jFaBAFtm8v2y0qogYSiHgDs9H9TQLNMjDWBYUKszjwx4TrTU7Z4Miz
N+NcCDGJEM2R0h7W61YsMl3yHhmyz0qyORB4k6p0PekqTkwolvk6AkxMOqAC
StOW4010jRPUg2/u+vYS4whdnxtzinZQj09NuXEVd4UkfSViP8uNw/0tPuyt
hLbIknhLo7AHTnIENwVI2v0UZicmydORMZPAB3k+Nwm6sc4dfQa/efcWU/B0
vcjxksKO5A9RhTfMC2PLIvpFBvIx0Ag5bnUszWnc+dw16JD4DrFrgjLDkzdJ
lcpNDk4DR5QZgM+vARbghoDh2FfEj5X52vZ4P/Zz8YpE/1H3AOBPO0aAXo1B
+HkFK4dcRmRKBSmlm8fsK0tWS7H9gHLyseQOwXINASjhML9oL3eS+icjxCgx
BtC18s57DSkVE4YoJIcAOgMrObzZe6jyjF8Shmq9Ef8eqVLuBKIVoBPGqznH
QrYuwDqVH3MCaFn+rrtDtyupMtg67vTtJQMgOXmU/kVeMWgrTQO77Rgvr6OQ
EtocSnXy+Aw0Q6aVNIApCn27GiO6MlshBQnCDAZ6hMOjGNqw1/GtaKEwKsZu
xOgsX+9isx7pLfaW7CVp21SiaTMqKdMcJBUo2qXZGJyQYJ7DtYrYmwEqi9iM
UF/0EZ2cvUAn/hSHWGV7vNQktzrAk8MO61ar3U3bGCaZV73f2aEP0nO8SGZ2
tYF3T07WpIfkYiM/ZuLC4gReVLrwvqG7GO/I9ZuJjrgw0mDR4ph0UyLI3kWl
c3Fi/Rk0W2KYLIXpNFPSl8KYYH9mKy7tUugUI7XPBjprarqkpKRUfKeR3euc
2IY/Xm4V7TW7jeOLG3J9/r11e+AZ1/QUU0thdgvDnpyV9Pr1w/t/pjfPh0dm
828QE+/2y4N5Io2g2mf5xAY1kVgv6KgUw6iHuQ7NqjRnBjuHyWIwOMVC05oQ
9LigCRbi0mvMANCs4L2+OQ0z1D58x/ouman1iMOxjPQDpv/pRKE8YrlmwtE0
nhxNTC4zEZO6xmfxkKqNPKbebPerNXn2yR/ID9i0/uGK6h/mp7WyiKED+wfg
vUWmDUw/K4ld99XWUlD+yJaLIO4T+lkGkaJujhLB6/tplT/xLEYgeMzme4/e
O/j6Z5Hl6Yd22NUbwdMXhYdls1XDgOyn6LkC1i4wXr1Hq3ZrgDx6aRHo+Sju
WT/1QROcV2lzA6twBpak9pT2sUwq/OPni8c/P6crv5SPf77Ildzqz+k76eHp
oT3t5+7KL6SJf/lHfZT897df6Ij8sqdN351pm3mn9vczfE7ffzw4PXwxd+XT
RonCg8U7lnGXnYXfI+j8HD0om4uWQjbiFKaNLxCRbVe4RW65I0zCYqbyRO+J
iTDtRVHLWbVqOAIw12hrEdh1pR0RK/K+8NlRdu4plNRpztmPnEwqOejYawsm
ujU6pwoS2kxf0Rot9Im6pFH6i9khZ3ov2n4An7a9F1BrjeahAcPYRfTU7a7P
+2azqfOJSk+bnL6WfTosizxcqpGCOxKQGG/WuF4SKgjPbi+vRor+BZN6c9vo
/j2WwUiwy4ANpckv7KlJSwaDpwHlK0tgOhiapnwmt37Dl2BoEGROMXk/nNgR
Rd6m6z5Dg5+5Uxbt2S9OnrJJHt1DT5Eyj3y+FF5YyGuXP/ErbCSTTU4sxa9O
Tg6nX32Fwi30BP3YB6Cj/sSvvuwdk58/6Ssbk+wjr/zl4a8eaUR/Sd1+4KtH
Grl90lcPNZIdEXu+Sj2cbwVm7+wwDgJ+9XJ+XP59uvLvs+7/XXYgnWJeD5IY
xU/g1SPh1V0UCbevCTwksUGEvOm2GKvfoT+HTx6OrqLQGWakTswZuKqHwmDr
LgHDxD0c5ccsL0Midh49LR6LngbzXN5BnYHscS8Uce/haxTPgXZvLbF6dsKC
IjY/o/4vP7vh3+Gq/ZvX/uk1Mv/R719OG5zToSYd/CK9zDWpL/7rly9+anfl
mJ9+6Pt03QFPRS5w7Puf/NynDvn++8t51XFyO/bGIk3f1Pew5J7akpEdkJcV
uQq62ybnKoptVy598LZt7jRumdbvBPyxDf4DzvGYCY5i4C/gmQLI14dOSZpc
N6CXRSKMFnmLmC2vMkq9iFpOEarkh3ehTOOEUF+z4Fg5EOaddhY/RIV3RS5l
n3QCynlheHS20LI5moMIE9YHdTCF7xTyfgt+gaZ3lFvw4MtNd07iS3PTMe9z
aEcOz7/B91zIxlTtjqQWCyvrEIWYJQEiADyKi261G9TATMreZV/fXIV8J+sJ
o5Wwc9Kn42KSTM94Vqa0y8Lgg6jfnRL+mZGxLL4Vr0TQibeCX81GF11TbXR9
LO7adVNQTpglBafx4twTlwHIYYEApuXw+WZT+Lg9jQU5Ypi7mMA7ujO86Z88
H801jMu6IMtKXSeyCJ9H8I6jflOWm3RmFhGrY+Bg2b6tJPFmPhMaBgVzkA9h
SZ6N94lj7H3aXwKKpUOXSKckdKj+NHFf1ZjIPLTkpNNkZl42dLE6MJ+CLxXc
LueuS+aQ2JdPSl73Q24h5RRtelZnOdfP9rhFKjjjLI9NTEM49dgDI8FaHgMK
gvP7C6HjD4eZU1+b1lW6FL5kRE8o1FkyaGgT6nDK2h8o+3ZV39SKRDzSQJZq
FLfki0oIPDRBJcdC2T2EzZPoJBmRqH3AbdVcdOYl0IF/Xe0Ne1BnNhyIpRFl
0kocU3q25cSSE/yPWUPmGZ+Q/gnjqKWHaChyaPY49XBknubYOwLt5KEcOe7v
6Vez1/BrwLxJetvpy5TXJryUA847jK00x4FNihkMMkUwOgub25Atd/pVJY/A
bO6GmbFdRtOIS7XSk8a1lzzdQQDpQlvwHQlzZRBZOeBtoMuzw7QgEiUah0z5
9c7C692lgbhj8KhEcWh/rYli83IQvk5JptpHcwPCWJTd36O8wA96IrU7aDgX
+lyMCpUHLrYoV70oZABLDAvMX6EKD2bv0oPZSDC3kqcPCvo7XrCtR3cQsGsp
w6G1/BsJvQnkQbo3puUNxwHOqvxwR0jY88a8evQkTwyQB/zOZECHVbOte9zb
CA64aVeWmfGQCUFDzdRM+zTSGU0yaJ5mDRw9eNlB8o39cPjQ027nftNVwGxR
8benKtkPquxmuxztv84u+gpf9YCmDbXWFw/ccsAZWiAVYCMv867v80+kMdAV
TwLXfWS9ECeW3iSSV2QLf2ZkadaH/7Kv708cvny+9lx3dvjU6SgPzusVc27r
nn3inX/jdbJo0hoo8c+HltwBiEERiWsnD0W40H4UeVB6Olc6wb1GbhqrRBDh
TIeV0loOJlkd5x2oE9ApPpmU8+qMrvOk4XBqkWbv5bZv5/Tl0rkYRBVVo6L3
NL9zVISEw1fNRmS+t3v0Zjuvpnd8NWsE2dGSjMpEiKxsoZqczrqukSM7izOr
TDBJ0TC2ZLRyXJpiMlb0VXCUxCMVUxoI2E80K6TyzFiCPKyayGAqPMezXWfp
TWScQK2HxdF741bSahU6jQ9FqwQkPZ40KhLGLqFFcTkYhzaz2vn+9bstavOJ
CNMMdDponAag86XxCwJ7UoqhAhQiRUeGHjpvkJ5qcGFyPPyuEf6LJz3FQrX/
vMxTTrTTZiVFnkXa8DD/y9mVIxsPZmRK4sNtOYeqL06/mvlyirLnfa1IHjvq
x5gUo8OsBIHl6Zv3H2xjsFHLHGo0bxf1ikk7XHRaqYrnMc05c8XpJBdEqDfo
wWlRjn6InkRQyvRPSZe01NBE893MywlHWcoZ4G51CScxKTAzJKoyl7JWcx+S
LhuMgQqHnNI6RJ529xoBzczLngxvcTnw9kJ4+qYNghx22ofIehc45DW1glMO
8oQDBustNKXVSCxSE5XSEMJ7XOw2Mero4pN+jAK3fIIK8iIJJWHmae3pjf3Z
E2N8zv1MElmy39LptWbPoKwtJ7SFwQXToQfOlHQc9n5B7+O0n2eFZcKfJ1aa
0dI+WPbhZz8r2ev1nWM6TNUj4uksGwl6fNti3aFBclJVjgVXGPYLicNoKsTx
QRItZweiM8YqmGASrEquwtMvDt7eYccHfTLPR3kQ3gSU56CawA3x9yLXGcPP
LwunOpaTn79iUWeqUPUEa1m1Yru2mFrN1SxPfSgRxIJF6HlPDzWmPSQnITuS
oM34wlguiSJG/tsUtUmRnmwja+J7gccTg5QyvEXLlAoY/4btPlxhM96miv1A
q6CWW//crsvflN8dLg5/VcTLXuJlKDZU/vymPHm9+IeX8i1GPeGrs9eLX/wi
u5PMDgICI8nMb8r/7Tu47x/S4RQT8yh5vOIu4Fkb+4rccDQejHyg7ImIYKBO
KYRtPmEq5ZDgSimozwxSzjhDyYHmCGGc3wCnU14Enfe8Wqx37h5lKQi2jLRM
yqVa9dN5nvdSk/u3wgQokM+cJYup9cM9rJvVqEFBjCUuY/ofpmomd5lRUoW8
oIJcAuhZnnKcyyF9Fl3tjflpVS4kisbEGUFzjVqJXZMNU/QbSzRWBCRpp6Zf
3PTo7EXExs0Nsah6gA2YKojhndHXWyOt49zQKIrJgBHbQlTr8/tsn7AEV8MB
xKNIJLBcmJJG6Bz9fn4+FOLGYt8VdH11b4kChNdTt98fJllLMAKJUtfSemfw
fVUCi3rMVTGBtKY8IB/pzslJ9WzcxxfozoxiaMZ0ykEXGXpFyzLlGpJJlIho
CFzO6hQWYByoZMC/JfQOt+8lYi0MrgTjl1RxLlMllg/R6ynXcaZhyBYRzBIN
DWy9lbFwzNC44r6jAUwBFGMWLFTPyYbcP1Sm5ympOg5ca4nOjvHuTLKsuH6U
ENx7whe3eZALxrWsQRtMkjNu6iYpe1RxKUT/RSNKmK9UZYFiMGrdW+azgMWk
mMqcmSRbsnCp0JiPKN5JZ6IwwXcSZxh74CgSXy2LANHGM3rkfLxMoPeWuNoV
UzrF39Va5EcIQGGwZxmwUtp8MRlqY4QHI15LnUhSFyVZaB5qqpZWMfOMIXhF
TVmIvCTGkoLNdbbBHSp5s6lvmDXT1YELmGep2tVYGZyiULL9vJhP9BNdsWsH
NEgKWcgsnx5WdM5KiKL2PGAsSC3S5+IkFV3oQoZBCFSaKZExl+3xAd03FLwv
IjoxULYuXeW1Sdj3L2hEil+KMN2aS8iKtCPhzYkhlUVCxIRAYK/FP8OxH+JH
QenBGNYg7FKKoNhj4ptKNBdzLQ6+p3kclbRW1BmMdDsCMWlYCBFLxdSmgAaG
/TDzoEPLWuEay0Dh3HBPZDblkcivluwBmA5OvYVWqTjOoh0DuaQW9WL2j0h+
41fBBiswBQgAuveazUajuixbNvuuvm1rD0GdqXesSib364J9VS5/4kH6W5bG
devSCZQsg4Pbe+4W2+FpbLJ6LDvFd743XMIjJU2g55ckSiOs+lSq0t2b6DLe
+aoekxSJnG8gjah3IFIoez9trw++TQh6ZxxFC4NiJA7qvXQfvv/rUFoipdJP
NYPAnV09hTVb4l6JRiZKUHxZLDMp5xBMBwz5p0+fqHbBNCZgUaw9kanZGJjg
1J5yy89nY1QhRDUfrpBWZpZKWc7OAL4kO4qDnxLXY76cEpDPYyzHOKppOnkA
7+vrTSFvjgZpWiYcAOQ9B/bvkY6mrb+j8uTN2bsf3jIDvj8cNHa4KPE+ch+c
TL96Pf3qjY0geisbIlzmvqYhZJ7FI/nv4o/uJzgsLCPyzyD7jqiZ7eLw5Ve/
eJWaXkuxdN9q8o7++fw+6zONg9DrpWb/uvjlr379D39fRDIqefcFTkMimStP
DvXrOb81UkHdsDnx5xRx4ZZGxsjqUOGfNBsuAoeH1ghfDkfl//4WtIq3L/+P
mesZx9nrhoNrvz/k61Qj+DMpt39eKecL/blYjT+i24PW4bcdVn7jLO1IvIdc
7Y4uMKYlekDcHWbe8SJk9+o1UiQRYEt4LMDw3awHVK/QCyJAkMRQYqIwY24J
oo+RvmkX7JWRhveN0KsQ06EDNKsOHg/9m73u5UQtbo2FmnmREkJrwplaqly+
o9Rhc571wFeV57SXrCxRUboJIM+rmWggZjEEpyqcM626WgDOQD+LZ5c56S1i
JuGa0KkJkDRscnYkyD4UizEIPhdvekO6JyvRFB7TPR1yVrP2HbDG6ssMzWrX
sy2qHEaTbki6u6w6O7o9x4xcj5EzXXqCiWSYVugHS64qhwNRkMVJMA2hpfSj
uFhiH1VALcuPHG4ja8DtD0G37k3XbNLGUj+62zSsXKYQUstrZeYVTOPY2798
rbrwA0dktQNeOTKdJaEi4VKwAFn5XYEZgb2HtVeKa9HlrtospygaWXMwV7KW
hfJoWn440QAdYKzkhUv5YtSQtWhERsWeECA+jaBY5PrCUJHTxFBY8QyJz/xB
PS95Tkj+aIAlUiZ9L6YRosw+b7u7TbO+FLbmvpF6pxqBiSu064swewt1M8yH
xvnNOe+aQ1XFtsF3rPuWwixrFHf0+oQW0xG1+HvvHEg8rsVchFPqJR0Tt7Md
LpJpn1k4zwcr9t7gWltpMWPXnq7JIScfk7T81oi8avbk07l3IScG5+/j18xa
mp1HiQRcFLYQ56vdG2CwzUFFScAZYQm5b7U6wzB2NzcNF0Ol80LvY+ao8BJa
VJZlJMNVY8GyGAwaJMLzGkQYIxbGCBKvMn+caJ0UVXCtVpmIZtoyt+hNVlcW
Bd409a2StJ8SFIZ0mh279ncDGf5rg769tf1FOukHr3oithg1y28mampUwRnq
lFrybvlyXk2ba+AkbZwmnByNDkNRTs6s2T5X5Zv5J4Qx2nP3nluTvE7rkol0
8R0PLTD68fcfP7z99vTtqeIp6aDsrLi6bHpEUMu5NgSrVJGxeqS4ei3Zlk+1
BWZFp5MVFkIk+LxwIvEBg15WShvZD37Qcj0T2loXMqEjVWoXaQmcEnRbUkZh
07vmbQBghyGCC33RdtL/rWVoUgFAy31WDMxTi9EQKsu/d15FdIU129vtXl0N
AzuutLzRjocgWei4BJooI8YoNPhUEpgCbIEOu8Cecl5j82W4xP3HxzAOp+el
4Rq1zmcldTlUDU5KePoGLYo59l4ne9sxroKAtnhM7Y8YlDklSt03VvjGDjIf
lzYWJnGn6arLq94ofcdU+3MwNt+QHqnsPJcpC3A1Wfh5EtiYmyk4SOJjF/PD
ldWWKjO4AF2cz1kNEt6jgkZcNe9vLolMbKHY+opcogp/mSuMxPFsKySZcHFJ
KfUgnGzmOYUmm0lLJtEsUldhMuxJiY+ynhfJfl3R3hAnYdXTSPWfQKkvktMN
tN/w6o6sXLaVhASspqdYfAnE4+Ih+Cd5lmYoH9X4f7dVIWzbOfE3DzWp23xk
/ZEsYyce/oTQC4mH1ASLQhSSVKlZB9JmEP6uGq56vMxhO7fx9MxZJ1KEaPYb
2o49yN839YBLDcfjDZIncKTi2+ZONfAi/RsptZCyBsVeTfVwNQ0oI0xgVk5j
iyseCk5RdclKgaiECfV6KDmVE3M+UU6xcohbU9UTE6y4RlXjlWiBUkESldHH
8HRkdAwGhWPwsI4SifWq1hqvpZ2WIRK0QXx3bdQhKatpmkvh1BmhnyQjjWiy
oZ3t5Q7l+zckpBU3pczFmqBUUKmqdDHLCmK/GKR4juxcrcZOBduIcc+xOb1T
zhFh44vskb6Fh0i6HifoYgaxCHD7yKEnmQbXY01SFS4PdHgYFStBK3FfqvGq
hFIeWFGVcFCtO+KLZ5MX7ufwJzuq0INjMWimN/u6bjfo3fleFuERlS9B5AvL
oPm+GRsxPOBCWiBDya2NinaNlLoI3xv0B4+XxFSKA41Ziv29z8ahIUj5OLqC
8KlwTLXrhSNqCT2XK59zoTUiaxXWcJCP27nVYvlzHUmidrtjvhxks9WD+F7N
MCHMZvBKnNPp1sKjjDy8GC+lMeRyt7HmNFYoYrTMlvAPdOTS9nYMWUng03tZ
GetOpLGFHl0vXJWlvO5nwQVzKfTZ77YTWEzJ/lOsKuHYcmKYGEmHiefBUFK1
Cz8//BbLvVH0egOvsUavzVV7TvyEoZAR6SskxI8QD15zcI6sNVenJEukobWY
BFyFsXea4TFKCD43OVvDiH3wVMzAqh7O4XWcgbwL60aiyR4XbnifDDMm1VRB
by1ap9Vr6b4o1bLatKbgSFq4pPAVybIC8UnhM5TnVJMsBFLfWXh9NQ2i7gMa
VakzjnyD1fkTVe5d8ddJOVTnAukv1UFDahiOpqga04VRpQQanqEpgKGwHFF2
GqSU0TxdGAwPBnHK1v/HxW+tpmHByWH+J0a3Ca7WekEnMq13GCw6uDMTXWQW
whl2gzRy7Pj2y4Nmebmsyt+dnX0ob4fyffefXqScX1LC5YqzNx9KvOL3px9e
+BamsYejAExlBKiSM5QC72RnR5WAqIbeRBTmseM8H1ySy5EmlZxZ9hD6/uDL
83vnEbY23ovlJmYOfvVNdG8eiSMJ53EBUghVU9qbLdU7XwxX3XjsxK0cZFNf
PUEVjqdnLh+CRxl8WickInNZIjEiNOWb/E+/gf7wxJOsZHr+fQvQI2h0J7k9
JgTlQ7gF6zbndZdBStx1hToHoulqknpahJl3JlPvoJZwRESENx65hQpKKpdD
r8E1nRDFIoJWOeOLHEfJAB+ZDHS4kx/UzkAqQjQIwnFZfEQ7cuDSs5XLI/Y5
13okcylQrUyznhzOr/8tO5p9YwczidvDC7jtFw/fFromhoZkCWq1BpNMvxAk
UOTVpKEmf5EhlRyKeCAw2E03ciRj41INXBhuiEvyF4oKdvJ6rmp2dNZlwPgi
VQWtQCnCYpZ7imrjk/x373//8az89rsztMl211JdWFVT6VJ0dIHMmWwSHqwh
bQU3KnwSZ88ppNTOkKnqVFAN9sOOcunQNFIq/S0XOl1yUgmB2hYopJUeZHBj
GIhv9xZMp04HfFuGbVLRGwIDU2ZuKQJKgMQQc+t8WCSln/PWpssnTgXci7S+
SCvkCrlsLSC0ay7JMTPSjKAjZIWoB5sQszabJOENY51YNlxaWdvP59QZ2444
9RK/upEtJL50DEghKhlledfPZsB/E0eevORPIkBD0M6T6Na+8IVJOjjx4P54
oxc+ucWoKfxXiQX8y/RC+cwyk6YLn/jWxhRF2y3m73ksN5g6HYzovY/sCyjy
zpUVw6PrDv0isplskh4drziRINTSv18xtEipwuKF+N2rFzGXc1UPqBy+Sm75
c4xv+ZiXLrPkmGGLAY8MFquvJqGfl2m0PALZZVgQ35KVqkbOOvO0UppoWJwp
eCvx4ZjwWU14Klwk+/GJwhAzKQaLGyfdKHwYwI97QjcSeWnQsvK1tvIJVnxD
Aim7Yn75K4kX0mTgMAfopsVVw3m3MqnuXaEOYqGGgXvLUCjcSyuMuWHYSiqv
XsJl5ATQ1jxZ+0ywxDtSNVFU3EGauZ5c/qsVJQRcsguurC/7JjyKlVbrvw3p
bOedmKWlBOsSdWw8MjD3/50/myX0g9f4CAqaI3MjyNWqUfnqYZ336w266n2N
GgkmZSlEjldtey+jYU0y14lVcNVVEfE8eMRO1+bziZbh4RBWWVv25zsNZR+J
JPiv+ZH1L0UIuB7NXWPj/C+WYMkB1qPpxXCN7X9Lk/hJQVBN9TbNgVYlJgPh
M4XO0l1gpcYWc4Dqt+p9DMZApAti/Smvjiv0M0yZxlrgUyONSzKoBiuQSK6z
OQ/yDPBqYqVVAkmVOKggaqyLAaSxN63dEBOZl9+NAkeNYHVjGsPcRkhoKCsE
4UI/37nyS5bSNMmmj7nC8zJAd/7HuGk0AosFTLlsRCpI4AjzcAg4bL9WNokQ
AUO5yrXnz66ygLmLFHnMkEniasaEDgBJCcJjmvhbqygtyLR5QRnHgAL97vyd
SsOzR3gXeJG69o3fOmNfOJbjtpEzpIvhY3J7JF+6JO37im+a5E9yat3QZGwv
w/raduSioNRMYfW62JFfDYddixSfI4FjP+4aDcwQ1UbvpmBZvk9agMIgOH5e
CQ+8cMaivRwL/z13MofCv7f1pl3XUi3DoI0ZolUNVCehbvAgoy095Nts8VDV
XFq3JCU4Xi1rUw/1mAaraVrkYJgKf36y82Ts1zgU+adw4gSM/YkK0pOjrlzO
MqfccPvIVnPlpViVwslhHGnbrNGEFys0srCnnEypDGB077LgLRdTnLx5uPBh
9RWD1oqvw0PgFS+VwWJ8FD2UW2J5cTEhixQuWU4DVxzKh5V+ByoFN5Zln6o9
zBUICuNp4EbMrfFcYy+8EjHfQ17hdxiCUQ8LXJd7UoJqK1iaNiaoFM7w1vKR
iCi6puD3S+fRZuGfNGV55SL4CIaxqZGl6Qbz1NaU/9bU/aY154d7KwlNDcGg
QL0qJtBoarPP3/O5qZrit+po/iidFdEZIM/wyGXsx8WuJxsC3UY7yszmyM0z
jfJRM2/cOD+b3b48uJc7CozKu6wjDn+Sxb6eppLK+yYdUsVvltaXHFcpEw+t
FliNVuGAV4/lw8E2+l27hht9lXl8ObKrYf5+ME8I585ndYiCumP4p1RfvlTn
pQYFIqHHG3VHJjsXP8HW9V8Ee9dbu2ryhr//MVjtv53kJqVX5hH+Gul9DRna
xuTYCJ5zDiJWQ+RFGEPjty1x314YV9VJcpK+puhB8fg9r51jNQEi+W5561nB
9XjLb7LevHIeAeW/zp1byUhCWDSLQzUZWCYu7e+9l57YpTFtn8fZja4kT1JR
SgEcT9ApeKR+Rt8kKYhXvJ6di4LigeRirOeYV1LYf+x3w8hJxeqddxHKx1kq
AsCXX3Cyv2M99CFtGvVEhwvsLBMwmmbQc1JFiPkrqYAwlCnQnkBVSNOcw7QZ
ttwSzhkaC3Q8pp/QvAnpDAx6s75UjPWfqG9XzeYGRvWqhWkqUoLyH3UJ/AlP
oy2jT5XE8D8zf/gUf3Fc6AVGzpY9Xx8tZ2/NNexBNcVXxmX9Q1UWuN7urpDh
CmlG/7Qs/9SkO4mxJK1GrX8mkW95Pk8SgQIsQ5p+N2Akj14IAp+xhgQrJTBh
uMLXJCmII6JiTtVKoXq3GMGdRAf4kIyZ2wwyCtXQKsQ9GL9HcDk2HBqWqP4K
ru8RxISWkKH389xRZU8dpED4BZqqsGsIJmG125VG0F56jt+bw3Q0Sj8rX9Ob
Ix9M9pqujjmtKQF4aBRtTzE+kRqZIU28cLR4GdCwtJPEYbRImVYRlRz0b31J
McdjYCWwQbEpUDOb8aGnP2wATiYsn+HwOpzk0d7KqVZhWMp9v+9wfITi8+/+
OTzvq1ie5lX5d2X5z+XpLx+kYf07/L/QDkff/zS5fpaq1nX/jf3rLQs6gx4G
/e0hPfz0l/uUc7iclNpfSmkvm7sjjhnyWqSS3IFnsUJ4bJE0RcfuoEZ6+tEl
LaoPs5kjkOCyjRMAD60g1YtUmV8Wc8tQkOBRBl+4ePRzMVSpmgLvrjdXjEjN
tDS/z1Zc8bjZXOgWUz03cehcWIeiova2ikHPS3LgqRyiQ/r/3xWTXfGETaF7
Yt+FpWMl/i8PXYXvcfqr8mGK6hTf0hJ795gvnGqRzW+8X02+fJVssERmYzxg
XMC99joYLEcsDlJxRBhemgpg34OypSUjvu1yX6SBYscuyzuRAqcFOgZgpWvO
uUQt0vEOr3MlMdCbGg7ytAHZQC3UK4K3WNaWy+Q0fAVBS05f6m7jI5usXo1/
f1SvvdFA4YYjQltG8lNaiwMYmzPgnTyneB1xu5cYYBhx0LgbX1cS1T4HXdAZ
JIn7uMjVhdJE4x7q86xCUUmr+5/nln+2mKFh/P98p/wzNZG3+c8z383sjtNf
87JC/zf8UbYhiEYnRgIUoGVr0xndBb+2wXMLdu7bX/LzPmU/fCpzd8+vyaWj
RjSpsnIHpnsKtfRkOibaW3LVac+LJHvZ/568fAmQFM7IyvH0EPQSw9AEItCb
PsXd+knzYEiPDvlOA5a2bAzYu03vxTAkATsyjHGkPEI+CO4asLj64pPMzWLs
PkXDRZzzlH4ijh7ZOy4Q9E+48yWQ3jgKxWECegmq5YojuyJszpuCSLI1qZSR
HvAXyRVZEv/059PyN+XBaVV+/+dTiXszJvlUMS5ZDyhZ6c/5r+P9Deyy6HLi
mAb6nJdaIGYQddOTLsdJKbIlV2ReuyKNbKGuryRzueJQsCfEiBAdhCNJFv2r
ZHqLp0hYSh9gk5Hsm3dOFzafq0RAiuJ72Z3eyLnqNmunAGXJ2ANyWsMir7dN
txs296EgnQRk3OUxb1hqrSMkywJxPlGfEJ+thnRRRkiXZxnUJEpKGTDZUx1t
FKO/uetEecpqpmPsOHZZOI/6wpsfr2BjkZ1MWSKYkJGPEAUJT5WySQBrkooL
Ssub795/+Obt2dtTPLCz/NPiTCPsHBH0YW0hyMouEOrRlIhQ+Ht8MrqLlkB/
sI71V3NghGui8GcEo7aqWTpVQKkWteMPq4d7WMt9t0W3tve93YgzMrF6KckI
nP3FeXNV37YdujPzxSjuE3eIHDBecz/itFAP8TlOz/aziyBI4OAFUb+l7eK2
h81jIThszIZ4bEXC11eNEL8jP7yjRyvczd02UxxKYcAkAKbL0UwkDYXsb8lr
MwBtq3RryuwwDWMm2rfC4EArJVxcNTy3djITSxsfMkpnMOwuLpDvBNSaOWom
rtjA7JF8+PhMWue9QopE5XxhfIub31QtL8AH4K/75KwtdEDU5EQyGIzZoO8j
IalX3e5mQ8Dpi0lcqMVdksy+gWBSwxWhNpIxyIGitNMEQjrmcQHxJK5GKVEV
BrXwgypTpkQ0Lh7tTVUhlqE9UYRgsJt+ieYE/6UkTGiVOacaVORFI+inho6R
R9lWo6/LybQcQjMQE54KCg5J1UFKyFms5xOiCLx81W7W7Ghh1xthVXXzezDR
pKRFIEmT+ODeYE0KFeo+R4m0wSoHmGdYk2QS5xUHettOCl2E2vHb2lKnTK9L
GQfi+OQOZ+kbmACKXiWSDw3WhEAP7qZjJJHeyU3vzw9jXuW2T0QbWx/MTemv
DSNPZo9AW74hD1RNExvDpG9ZETYX3dKcahhhR4EzDbjPIfbYOxnvRrEW48/y
DrLR3Ron2VMUfxDayRTBTyVsSIGQdYgtT1B8HE4bCjwJKXTWchfmJrOajCtO
RLGfxErksUiS11pYDsa9391wyhtaYSeUEkj91G9Li3EdCKzbT45osWA2f8p0
x0wVVyCamQ2WmmbcEW2AgGpIG8wBdK9mAEw0qHNg6BI7+hNhXWmo5+BWg+Gt
eJGQ3/7c1AguU6P6Anq0M84FR4qhB/Wq42PWIunUpiJZrHwGklTYc+gbV+Nl
ntqLIEhLymPA8AAfYlUiyvXorlid0cMAMMotQPx9Ufl7S6gXBXhJd5kmEckj
SK9oxxwTJvptkPeDuDcInDgph2GoMS0AqziFnHc3K8ri1yVnaqf0UnGw4rGE
riE4VnYaoieyNA44UDaYl90ZvTyTLdIgKDlKhqGIDIMpqyDnf3ypDExTtRcz
TQ2jQD6gsmRfyh64Bf9M6V/phRNbcrqee26NDwTPSCnUmBjqlBHj1k3wihRy
w7N9xLOEjtNLomyWiGCZqPB0cOCxQyr14XKk1S8dXtFjL+zdwqywNp7NCMVZ
HpqWfVPB+uC+UXnK+O/p9VRSwgHaaw1JYgB2G3K26zP1nCNmxZPPMqUANoxS
E5cVmg6SS42nq9VqkiIS2ab0PGHZ3ptB5zzIEl4z59UtHzIJkXZv1STiayA3
CAXgNp78HT0+PKoPD52bvMkAKUnyTd9e11Zg2KwsS6ub6ZBf7RypW7MyPQUC
oRSh5NidMGE1PxLlI72F1k4OoxeF5whb7BKPb0I+zjkYfCBoiNtSV4LV2uZq
RBtRbBzPnHfNGZ0mLZt2mIhbFSGUxcX0OH/jTFZTpQGdy5cNQzFaoseWxUkD
4IsihYGuJLpGa4FXwha6DcZo75Q6GPPfUfoqnWYBkSUHMPK4wSshx1mKRT9w
gExLjZ5+leHuJH4hjHEXoK0n8Q4nLJzlMFAsVDN5QT55/I42n6ERzI/g2Xys
6AmV/cHh16PjPr6oqjDJ7MUXSKfnMQcrhdvjnNhpuBrh0G3QKqb3+ZR19ROW
Ng+qcu/tHn/2pR/6BPwzFwXpucy9KdquwJcjTRUKMlB7VKuQeikuU97GSPGA
fXTKGIW1L/QQ6eqVa1Aa505latpc38Qhkl7npkY84gBWUY/RU7yRCj/y7jHf
z4QbF2d9Vphe7mrKgUn+LDVXJmBpU7O09APzL4qdZgZAs06WLdVN3201kyYR
XOq96lzgKG4dZlftRCm6m24W6yYVRZycYdh/2+6OuemMmRFTFRmv65nFM8Of
yRpxhTDVYPVyR/Ii11nmDFoQbMeOXYeMPIUL/hkJrbegIguQ+qFkE4a68G53
hW1oZoUIi0173UreB27b4jyAOWkBcr36xMwY0iwSbtk4vgqlGGlGqawmSlPH
QHlfz1zXTKI/k8FeFjH/lQ/3PF0Vl/sl4gNQeMzgZ9BebfoL4pAaOTBpmSm2
rmU9kVd1xo4xeI6ZKkiFxmT+M/lncwyDRzoHKt8LpNhe2CKbEvs/HyRBI2Tm
eAoP1NW1eo5H8MezDf2DbmWK0a4CB9oQeUYVgHylQNrZnsfOi3gSLXjGoWVX
UJYlAy6z6XKEYfhqGGlJwa03qoEvSkeIkoh0ZeQ4JsU+kVAUwPY9Uj2x2JhQ
JxqBnCblIdUF5Ym/+VCJAgZzLTo68fhMPG71rHcEu302+Z6ZBqZTC5Zle+nc
V/xAaYp9ZuSxTSV5nHvLHVrGz5aPmrLg9cbOZNx7XJ8xFLcV+j+0ujSxOp5S
yQDz0n6r1Tmu2WtJZVKw3kJRztIUkri5ul/3mnTyzTfvzfAyXkwqxYlTIIUx
HbmglKzXwpQxo0fp9dic3bKiK4txK8I2K2Nmh5robzpqqE3ZENHuFH4Chj96
C9KAkXzqGWyVef0EYxh8z+YhGyRHyQSJeaUlya7tixC0vk40Qak8E2cf3bNS
LOLKZ4x8d9Mk5sQF2CXt5bYkaGfr6uMSppG0G1M+6t45nQqau/NduwG1AK+9
aVCzd0eD8+DxCeHtSSLKQ+c63hoD8VJ8kGnLJthe01Zlk8P9hdNpIgKy6x/S
IfSNcOfgzJzR4KeRwF85Maler3uuSyfOr/3xzQIW88WIlm9pdb3UWZMOsXdv
z7429mWpx3bg/BtV8fHdB3TjsVqgpqSmZlTlf/r9uzesMaS9rwKEB+bsm49V
8Yd37z++5b+/QxZfusWctakYDJVZMGvBspGIOijhE+dL+8IQJUPVhDNuvpTr
XDixOoHZgqXZtz/CpddgBLd/tTwpWbvoiUWPDnfBbZyCOXooSo8+EQEmpAlE
tiwYT9i0UpTQNMOx/rHbdtdgjH1wSaP6K4IoePpTeUBJe/GXC+FdgUUCh2fl
wf/z3369PHz5At7vS/kGOl1+yekkvpTveTOJcPgCGlo9un6WX4ovi8Ui/A9a
+97skC/lR6emn8LfH0x5w9aanMiDI7/s9I9RAbfrlmV8Cs04d5EiMfJUBb74
x3+DIiI9We020e1Ywi9iweGgJ+CD3+jR+sXRZpan/+//9d/LA2/3viixk1md
gNyjYmZR6hS1hE6ETUOlx9UMIy+nGX88BGRNTjryf5cHzuDGfryVx/Io4YCj
NREeXns9n5+IW+COGGcGy8IjanLxEa2zAXHOxJnB8aNxs9kNhg5oQueygQi+
SM7VUx929DVOR5d79wEkvbcj4QGnFINgC4CELqIIt7g62XuNXId1GhY7FFn0
uloMaOarNth3SD+A8Rd8LuNvkqXDh+Lrur9sFu0WTDPyFJFguiQHjDzEmZdo
4J/LDRzyuYOfb+jBowLV2JpWvxNt+7taki5QE2RmcQxpMLyqMupkfAjSVCF+
bU8cAncF+skahFzRlEjMnqUOpaxVGgqunJ+H/9CblJc1UTX5CBTLV4GVOJ6u
i/KZUlxxatG66Z5R/WLxQhJWZctuRK6qTHkjicyyyCmyjlMqlJ0e1nZGjIX3
GymPUEfNlO1FsmwpDk27RSYCplhnFjoIigGM4o4pLdjVRB2m2R0YJYd4BCQP
m+m+1Y7e1CC9Xv39/6y2FfVbiDVoi4pPjeN/hThFWs0pXx9NUTNlqn6tHj3H
Y+RxKOUlHnBaAZ3fVMmUOMmR2Y3FBoan2uKVmpasTDhXU9sxa+DXbT+M6oK7
8+gH873NcR/zYI+FsKfMDIRSoYozGH7SZctw3jS+xQPj+x2tYn0b9McgfESz
YBmugjOOfc+CZWLfMcqC1ZgV6v5SYpC2CcyWwtkU50dUCAIPUmloVaXnikcP
nkcG4cSMRHYakOYNHcVjNTXGxsvYbtAjAjNdmIlLw+AZsTgpZ2CjGAPOwQ+F
r0Chdesx9VEgG+JjlgjvuLpimmY8zAWiyjKODRpXN8FWE8VW4PtbJuJyaSAw
uQx7JQU+OPbdmmKJob+EJU6HhJMhRHvz43gcO6BXYTWgobjt2lUzs/Zoq93A
ttuqA08MhjqZcYSyhTbklaVgpYKlcNg0z/aPhzwuWFbt7PVhQpTGtllvJGbp
mmoLu7c7SgJVJUqhK/4Z7Y3kyacLeI/emu4yN5i4/3hKBwadCAWGspRMR0B2
YAy8+FmITFDIFWMVYUDIkJLAdFNgLLEGSPiQoSBVZdNQfmHklLODTHT/qVjj
8jscKFSO5+CqJJye2NFJI6TDDLpBWIwBHn6R3IV7jS7KFwzLmVB66pjzfBSJ
wZ9lqzh5iv1BMhKoMxWwhCsnAvECZE4yKSnMhC6DzisjyC06elIT9fHVWZgg
EUblpJZliRmrC+zPFg0hNNYS0ap3jCCSg70hgffZnDhJE0IwIPK9lzNCAF2A
AiBkCy3N+SQWbB5zWh56kDHn/X5ZOsNlXIgThOHnsgmkbi+/D3S7mgAivSew
cAlrhMLxmEh7JY+QzWIDx0WoFGVlCHNUoObQigpGKknwzjOEXuBjoyD+yEnP
0zu3ULsVZ+mtBFvNsp/2vPl+1J9CJbnssAznJDvw/Fk5OFYHhT0N6pDPYN2R
WUdThXm6kB/3Gt5eDW+qK0zTboxmXgDzie6EEy88LBLe4BmUPMrC9pbByCJY
Ka07yWjPxQy2IUx0DrPEp4mtbF4DUYzgenA6ADS6uNi0l1cj2zoW9eSaLkZx
uy3C2y71d+kwvw1LtLZ3kF0terOikSlmsdTKaZ0HdippzctR7E8xOf0iybdH
xYZhpQG8QY8nxgkn0lVGROVrFtacUF1gpNRoN05feRbeN4mo7sqlFZ3+Sop4
uUylAVOXOINrohxwrOWVZueIiD2S+jg6b7nKmvB9I9UfiKcwOX2t9jj1juuw
oGsdO8hrXLtPaewWan+F56crOebVa2IhwXIKXFKQfDe5PDWkzF9wVvyDf60P
dgPzeLaVJb+hS79N3IPaNTa92GUhiTAw9iG7S+oXZIlmg/jG2UoVyilbLZSQ
f/prKu6MDPsE6y5Tyi525RK1KgXz1Xd1S1I52cUisuT1f6mvD/ZtzihPKR4V
m+1jt1uxMfzdNhMIWAwAh9XgJditnWGmj/xh79MOjPPcC18e3Iog3Spq6TtZ
wXXhc0zwh19Llg+fguoFKgiUobR1mMUFm5pg81gWRTSg8Bo+GCT5GFk6lsRv
t585uObekQ+oibcbhnrdMvUYxfsmDmzzNi8KUDSbrY1hcF6Xf2jOz1JVDvjr
+7M3Qr+sfPQmnh7Q6koKVUxCE7DZ/xcOT8xBkUpKghGEYBscRnSSYkirXS/A
5OyH5lhaUh0gaQWsukWLe6LkqHFYzmkdKVimTzFJ3G0vafPPHiRzIhjrhiTo
bcAjaeOZZzWQbianFx216n1xAgelwmisqTEjhc/V7KwcWN3kZ1/UkaArVI+z
0kzGp3fhBlYizExg39dIceMXdkqzp9RoeB4ZDR0/AoPO6eWE0CkLUzSkeqIK
g366gSvOYgho0V0sCJwBXzXXWswJT4MTfmPLZz5TH08qFMePQdAUcdfyOZgS
WGWeJLPL9sUPVJOSbNRzocq32g8StTmsvBSn78EQk7Ra/orv4HTqVEtBpfzg
9H6xda3b8Pz8Y79RIfCH+KaFFPq3U7Yp/shvT27lqwdakaT6j0aMbt3MAATG
K+pZHGnXiC9MMgaR3ensUB1UDM8W0CXBTWljIH2GXJiCvVRAxw8qd806lKVO
lGTOKSgrdocLUyAJqkhfQYfMdZ0Fsj3ltcWySYHrNmKwiC0qOFLL3BOKj8EH
9qjRK1y1SKBrQ+sBXoqQjWiwDF/IaeCybF/RKi5SrQ5YYrG1VGXgN7+xiaXo
e6LA2sMSz5UPUD3gnN6BY0Zp7L3MSW7X+LVnEdZ4+lHhC07H+Hu20+sgC7wn
N5tbTdJw2FCO/ZjG76vvIOECqTEcvESRILlaKGy+F9/9W3O7gpF2DctqrS4q
6PcN1350wiJYcGLO1nqnci8Ky/5Ny+ADhVftNNWLnsiG3UV7uaO0ckz03W1t
iAp0GyGcx9BZJ6H6EAZEN0eisWghJMb/8PVFXt2sKrkm35g5pKU7zzPaYzx5
aA9UIPTr66R32nFBsSNmbdPTLkI9qFLFHdU9NSoNAgaRCoJ9Xc7TRJSJwmWm
ZMgDks/E397P79FfcHDy7u2Lf1s7fEWqYQBtWg7dD4ePN76frCWRzRx8/e3+
bv68nK2PIJ+Ujsb9nOl6uugruW9SRnn2vr3FlvGDtWUOBqb/v53efctXlAda
J2jm9dSgPTg5sTIC7JSHr872j0cR3/yV9XjP273UH3yfwx0z/Z/5RSUp9jf/
+QD2Zir5JvP6QkolPK38w3R681nJ8FX550u67YfDo9JSBISI4fTlsddwYJOz
1uBuO8PbosZ0XEZ16XjmafRxTYcTXlSpmdtO/giPy7TpA4pXvDgO4QR3208e
SYtEiPzVsnWVZs2TrY38Qal2KqaJNz0CZguPTM4OBXKTGPvckSt/hsck6aN5
zsAhWt1KqXUkPpaZxALOEbZYJtfMAAmbWDWxod/ljJRH6pkw9i9KCZ0uTLz7
3ZxP7MiBYh3nPOsO5C87ZimiVEmD4+aVnc5mvVCUv7STmz33ougUpdGsq1dn
6b3tPZoOR6LiC/AWF+yD+j1ajqThlzMa/sPLkwfE5846U+gAFmpV8sKUAKGE
hyxvqMMqqrhSnTXMxN9ipmXWmLgYIrX9oEjIlJ1PhVLfEnKLODJbKXCbCiJy
ySFXZso7cQpfFpAJXAgEFiGCznEScnBQb9kNBZYOIp40GXXkqEbla57n+fT9
x6DYRaC+1jeml361WMDkODIvItlqmhuLYzVUnLuQ6uYh8FavOQDDgC9OuzIw
ty9hTsB2Zdsh/Oyub1Lwgy0/8d2L6img2cLXQCCHrtrxpF2KV02zGKxAcXK2
Eckrwd1attQtpwcXXarb4Sa0mC15uy+D1IqWindca2UVTEXNyQ1/bfqOMNEY
JhGPihRXwRwg9pdQ8Q6SiVpVlGLkVv8JxoZUSq3Zm8qCS3jGILuqMv+162QH
klg7MUIWOov05XF2Cn/LoHKZukugxEq3CY+sUMs6A2BZvBsV9KdYCkNjaq2b
gLePqWaFarXOqSLwRUVFT1h7tT4qLN95RnrDlx47uh4pyj047BIHG9C6I9+R
WGVkvOCLvJMXOSqZdRm780+b7rze6EojhIPjBeDemBbPFtMc2rQ8UEApsmC9
PCk/oYL0bv3phdTECLXYJaTLld60yICPySPFyNBtbjnbfTfSLPHbWYLt77eb
lqpZm6TnzD5yWomxn9Kl2FpMg17JQi/sYCIZVOMGI4vWR7a4Gk+Yde/RQ/SZ
WHSEmkPm41joTbF1/FZNnF0e1QwDM3aCbejX7V+xX5c0UX5FUszNjsQJctxC
t2kBfOQihDLZ9MITWicf32IdpvXSEC8iI7RwdLx85zQ0uV3bXFtsljNW3Boy
Xgp+e8b5LIRXK9RCZgfdhcL6KMCLPlhPCvMIICFtFg2F2tEwYCzZqlkIhJ1x
swJH54Qecgh8EMibJQoN5UJWFFGLUQCMgtUUREGoiitxpNuKPxbmYcroYxbt
mo193lzutgUI1p3dkO7AEA8WwLlRDCtGeCVQc97A0bDOjAvjMf8Mpv7CIJml
g/MZULOwmE98qOSnIaF5AnV2RnomuO/sweewyj+T264cQJiPV8pf0xO9uQdn
pOL2/oOPfq6BgMpxrWt18UAOlajs6GbP+MAHJ9FAUIR9wnZ5nD3ZXpzGYxAI
GHbDRmgB6xnUQNif7nLEBaa3rsur3XWdtmWB/V1YUC97VHbvmomuQFDnhhp+
4pv7tM3Svy3tHoweYVD/4uJYklaJwUh18LV1QxUOXRhrWMgFnmRpGdJPDDxP
zBFMf7a9LHC9rxf4ZbbIV0LoQqT4P7bXu2ssesSd75u/cCTGbrIXgIHb8GEk
/DS0N2qqNZUvFl1KHb0qp3rSMiFS4FFKExUWwZzuKn6tWAsctRq3UPMVfk8I
IYKfOk20UMx1eiVj78u31HmT5JOQ7b/nkHiP8gUjkYOL26TYMJXthIuQq6+2
6ru1IXNTPiMLIMOGWp+c/UFpCvV1Q/x4oZcc7S4SKp5Wn2weusSyvsm6xSXD
8QLMDFbtSVFTtuaq0tYKwmT+Iji3hIrBv+SQvUAMHeLvxv6+VFq9h4BLiJHI
zEnhxMgUUTyfUSSEMNcdCPOmwAQWUSW1rumR6UbdVsqLKWhm4YQijNW5lGCq
0guXDquDLn8xJRSxQQEBHSVn02SI29qzFBes8Ry7Az2dbPmQq1s+xMuhueJ6
x3oT5cKSn3olM4euZ1fIVKu3UkMlcmnCFuMEEzwXQAgJXCux+JNLNwGb2Fji
7J2PlINgaaUwY3yQSknLySpOB+qxYkb6wdfM4Sh2O7LZqQezuAn8DKVR8EIM
Z5gtwmG6hQIjnxYEoyg0RmzmiASX5bPxz1+9TPP/rCrgm5eH9uhnFV5y+Mol
nDxjkqEeh6+R2I/TVWzbKwW78RFagFnSoKWAXcNuKrSjDSnCiRI0+SY0FLLi
6TZDwTjQ8edn8VRbg3Xs0rG8AeIKpBcFgS1sopUxytVRPklocVoH87kbhYba
WA4JZ5eLyvuIWWIKyKsaa6yYdWPLUfEk+aLmjqm8tdPpYPpe+qUFX7x8abCZ
Ii4Alopv7LBkCj36R5J6vL9E9j787iTBx5S2Im+fymcvWekvQ4l6BtGh0MTX
CvE0Iv5xiBW17nLeZuyu49vh9GRvHJE26GqW7m6sbnSqFlsJzIguJFpHRn/V
DtJrIxHWelLeluWp2S0+Y4MDxQw6ieXOYR3D5lqzYpBI0wL2bo2W95p9Z+T9
oZJ64zDL96ruDnp+FRlDdS8VMjX4Ohr8QYknzk+xLn35RtV8ZziHvbjm8zGJ
6+PMBn1YYJcmsIu/RWDrBo+LJodrvHWVWcjI48pJgeEI2as9oGiGl5pUFtxt
2dcoUR0ntWnHwgSepCf75ZzNmFjI8o87fY1q3MiunQYufCqeUkqkEbyQ5Jhx
lmuTm2T4wRV4DrPYsUIhWtNks7WRlWqvG+qIcoXodQVsZrsnKwkosPaEb7xA
tR8d4Lat1BFYekfgNUK1RdaQf5Z2GT6FFcbrgulr0U5L5B5pNI8nDPBKbSBm
OQ7CwdA05TPqtlRQfIZJvCeix2GpZ0wfItfcftIve/U0O+nlOK+UoSw553HM
ENRsT+KouigcqzE5LZhajM3ElWQqRIYxyynBi4jlMxbakiNHe792eajuiHHE
SvinFJdRmX4v+9uSniRlyzQfCeHRflG/WZEiGMcJ51lr3VPN+ho8Z1Bwn1MK
3mQXW7nB265dJ0QEt23IDzh0z9moYton5xeyk+reSRhfwiqjAbJIiCThzaQS
vyE4fj7bBVeL5MrWq3SJguJJVo3dgmfXJ0kT3LsIKjpXFJZcxzTXah5NJrxw
jqXplM8VOxGZcaBnBQrRFwWpj1OJiFcf8Oiw/5vJG+y4ezEpfW3DSci+YTKa
5jC9bvseJ85q/lAUc1ZczMUNQPeYjAlluKzXaOU1/QI6QBbWGmM9m0mqAAba
/pBOU1XkWCql8miMYu5kvZpp16LPwJCgHKyEM+CGPQYmNFpNXJAfVK5jjo8L
d3CusWkARPISzUvjA8eIESOPN4pwcYXYpgCcaQn3Edp77ghNjBtzGQpV8ED8
+5epOMMyFWdYpuIslKk40+keXISFa1ScicpHtSnijAtJJD1CYk0928Zo1lRz
S65ygU6pM/FPfz7F8jx/W/GI6xuBeEuTX2u8RpNOg1pjcsfCOl0/SUIbfDpG
0slRyVAPT6puHJNHjG2d9UvVYhEiXbE7GoejIB6fayYNjvVnQm6Jp6E3u08I
qZUFKyQdcGd5IthaYeOkYoJP88d0xp0IBiUphXOVtjF9FV9A+N29dbyqb0Ya
PuPFCjzzRj2A5QZYHiPSDexQByr3L6GpDkd8IGcchAqPFGAnKZ4pKpw4F136
JCV6ICpzMJCg2FBMQ+ydClobpUmlGJJGUDmzvkoIVjHQ9Kzmegw0sEq0Q6KG
SmRPSq67wdaFw+Wb2UYiTWFOEcFfqmlyp51F+JifpHucODdkq4WXFxnWBSeD
ot5TvercATZZ8CC5UZUtNXE8C8ukaq/Jvi18sguH69jrapSGzIwxsEcEh3o3
aPaZLsCq0GhaZIieUDP7ZedSiVgNs+q84rvWDJpY2iKlLBRpx0VWjIqSbE0j
C1vOVhmHSuIuO8tTEcx1sTfHEq1HV/B9TqSkGKDl0ywZtkR5z6J8YWx50Eqb
WUrSVP0h01OeVMyw2CUP5g5xxiBRzN5FkAAnspN66mYJQcz2ZJryXeaH+iAx
+Dcdxf+lZoO4SMwTzuMlQ8fR29tG8ODo6cXZvSCs6the0wQh/DUpg8tSsdzq
U7NzTJVNIWhXGIvQccBWKgyLhMYUGj0hEgFqKy/U69rVPSD9S4v16pi7899R
kzvzm7UrzHpmaJY5HEQbEt4VuBEDm+IWTaOEN3bXcKZOpy8mPeGBBt/c4w3i
tsbIdj7mEt25CQ7EXPO27fK5uRlLwfRwzWFHSkYVkTF5hyP9MpNyJ71Qs6GI
WOrOeq+kzfj0OYLEa0ryg0QXpUkkpBUhovsml9cB8lJGTmkxOtSJiOCQWBJZ
rKBDg/4cBspLNuZB+pZvDyv6i6MMxduXVoiK/DghYb18+5WyL4QimAZUJpeF
PFncF28PkXqJnvWiXPy2fPsS/+an8RdflQfhKaIsnmyFy5B0DGR958CG0UeB
gIW+7tYtaH9CyIEUtaTAC+/fcVF7MyMn/JSUqNapEc6sS3R3hRh3bIDiAS/5
xp6h0TGqcW9HShGJuCU+gYUH8SJypD+KSbCBKKQEJI+Ph8z4ESKMBnVO6Sfe
vpSJ5nStt4dLrjMO0mJFTHYYi7sR1zznNDdDEERIvQh3UlW0WidIRgh772u2
1Pebrl7L1kpUjMTs2a8bkXjMmM1Vtgql0J2FDqVTSRSjmNJOXqHlI2NScZGO
y8vGqADxlRSMlWwK9wYctFkLKTRDcgRJRESxlc8B1Bg7Swg0xmDWtHpg5NTU
pAVLjHF5fXaRywSB04lFD+W7JhwEFS5nKkd9C6bgv4P553q7ynOJckhTkbA3
HxQLxEAvcdQWskzN+TLPG0gVM6AH3b2UUryXWKeYK6hWSVf8ck4Up1WwYh05
IqlCaQZnytWzzcG+d95nqdlynkU0KrPhpRIlLR8wqb6WYUz1h5z91+qJaJhX
EduKuyNOc8r2IR07k58oJAln/vPFIolRdff+I4jHrBqP4kRLQ8F/cf+mVt5/
PDjlJBH3LYmvfY2OESw226mXT+tU6TpVZp16+SL79id1SioCmtXkku4uCE6f
C45+t8W4W6mFaKeSNfBUC3keR7nYl5NAZYkUPlEhcjRFnAWmR8eSCMlftnif
nqvbrny7Xd90bSohYwyyvkKYPoMkGQsV6aFTOaZc0rKPLAY2pKIMD7BZX1ss
+oyzymgIUQIlIScUV7TMbf2Tg2H7l53UTWTwxF7W50g8nY4s9UwREIcDYyIV
UIw9UJmKyT4VEyNA1JYLhEhkbVaKoX2eVYUSxS9PFre6aLNvFXS1TH5J1Ufi
MHO1c7HG7XhvnpeuT3Q+7hiNtcO8AZdIT6Lqt927C8imRQF1Z3BoLnmR1nS0
vRQioCjokssZKNECy7Kzw1/kDuWzly+TvzgTw0kC443kRX75MhQ0DIfwQ2J6
WZ6+ef8hrfshX/GCn00vNF//6gHaf9MLteyQHbDM+p3qDRlaSzIDGB4vLpfY
C0rPt7KQ5819p6WwJCxAaFnuALl+REwMpbO9bdPQKwjyGjSHpr1lUl7b43a7
+FB1gcN52tw6T1Ss0CVLl5xobOKH71HVZi007N5v4mSbJTtajUXKwCEubfL4
gNzqerNG6eVYhfcR+H2KNquCTt8IXfTahUyZpKTESdPcEVpMGORq0QOGG8+r
JaRzqSymlenWWsbHazCJyG+i6yzLZUClTFSv8n0UzbP1Rh1oxhIhVs2a2WhE
BKk6MmrGgNUcGpRCyPnWOQJnmcfi7uD9M9uFdB5qfgo5NRzgIuczsiEJ80rK
Eb047RPE9g+5N03LUqd0jiqn6ygCXYeQRSdu9+vmWtjqw+7V4oxJA88WmshO
ZQt9TIN4gnaQPFUJ3/jpdAJROD38xFa58OvmYQMpQupSymbFNsr5VJdGkFTz
5ScGwdlmpfWCYaTT4Z22DkGkq5tLCPJuemuSKy0NVUMqbyw9QSWJ40vOuzUz
XEsSWK4AKU/ppA6ZWJ3iD6owVs8ZCiFJ/cGCi6l2HxrG7DDQQIjPlPfgHY65
kU0l6JJQ9AqXEMbBB6FW5wIk01K3PvVHtnQV5z+aUrFsYPQstNsV6jRUbeLs
sYwIfmzIqXCKqkhW9RSztNw7qU65zitdsLtxolDpttVyu1JQTA+vR4zVLgV1
xaxfUAuIA3Cmo0h/y2R6iNzoyUYy2v7VfjVIFVVN4qKNZwZo1IaePqKpdMmM
X8orPzZlUfaR+2fy9ml+ie9WHMFz5VNogw6Ru0OLCE8qCJBtIXOtTPqj2QGw
UWY0tKGaWGmsGCXVqjL5lVa6I21unVgyqHMqdyR8Hv78+8g62VvMlWasNnFi
pXtQ3IYdrSowa1aUZC34gBRd56pzq0aOa3vpTG7xCKSw4UNr80SSdiNIAMN1
NZV1CIIuMwEsiSQEhaOTXsXfOYo+UYuvhaHEwYoeL6w1V08lIQ1cNRISeFhe
NZVzFxxJEH2GW0snoBoLdLEP/KvqwjHADWU7KwtMaJS27uZehWSuy/vzMBN7
T5otHoLEqZc4ZPUhs4m4yvVTj0JC40ojRZXaOpEWyMf2uiVzNIUY+RBzSdXK
BJsB3kIVuXMhIdqoOhXXCa+Ip62DD35NGiCWmHyRmoBV2X33x3jMvsrxVcyB
kropWbSmZYxFmxejyWL+QfCQ81MGXMk84X0V1FtLSbOgweD7pPqKYbOz0TBo
fNg/6rrGjB2tU7H0hTsiXodcSo0WPmG3Uto7TLvtkBQpidONh2F8Kdni8Vnk
U+Gm3iZviZch0SjgbPmp10pyK/kQlq3n17bWM3LGOXrL23EnS1gQ+zoaizsE
b1NiPsjzn1lNFxbd/CYTIZ+fUHjQGWOSB2WLsZGEphUSErlDUkqfGRze+JzA
fmHsg5HvmJhNJ7yQhtpAxYgK3xm3Q+qb1e8lngf03WiaGSYOC+DB7d5onC34
aONhn0z2keaaJBOPOhag82Xqp7cUJU6+Eeubl7DOtdPVCClMlI9db4GNOSFK
vf3w6AKd6fM5PUnKNBJztqs4EJXdB57PixFZGNUDsc4oryj9NnmQolZnCgTN
dVQhJDOeN5g5VEDR4VRvFJDb3bXq4/gKjn0FA2bKGJa6g6pNxgkHq+bdW/OV
499ff/vW5gEJOfQ7vUaIXYyw4fSlZ387ya57ndr6igkoXAp48cDIlgfN8nJZ
kT35Qg6AwbsKVWjSBMDSXxwu3TMlwSl15E3qyCvQUNmTw/CYLVgfccZTJ/74
p//8wopT7O/t0Szp2N7tj/uOulz8ZJ6hvTROD7E3PvXzRdrBNQHNnh7C/9Hk
4x8v8Q+dZfziq/TF6/l2flKn5pjBtB0cJFoKDxxCNhgPtPNTPg/156d8uO+v
eC3hv9/8be3MdfHfbf1wosArDTqLOuiKbiGlE65YODbw9MV9hJ4e5iEImjQ2
I3WMozP39NVzzE8eSO9ghxc20U7Vy7qIrotkaGlNV+RqTQK7CkHb6XZjZYj7
z2YXqZbigs9hfLZF0aaRSLcTCe2yEbmEr4mTSr0x7oS1mKjzTaaGxN0ziVbI
ecqEI3qKnqNZ84DFcS4mQVL1XS7jkwodbwPis02mpyTHMf0DJV6pdvm3nZlm
nT98Zj58YM4cl2RQ0q10gZC53AtLl4Tij+RNyDtAMdh6tDqIqCjN94RMQ1+p
nquguMehI729BE0Q/Q/b5rJjTsxKazP3UhllysRi9ReEoYOBxuzHR5N4Wf7H
rWijYY4qVa2EncpwbvRMGnjlrUqY45mjDneKZ+i1fSipf6OuhIn/xtkV4lvV
XBrSfr/tMAjVoz20nmhgJQXcHXnPdJXKysT69d2kgnviNdm/LO6ZDWZM8T+Y
R/FTK1nXRPSUc+JG3saM6+nriH8y1OSWF+EshdYBoBEoKtwifgsFVQ2fWGLe
dZPiTzhjR7QM7O0jSjuvDF6Vri449IgAkerVjrwqipq2pIicXWebyiQiCQQh
HBVny3EEKvlHjq9UfLwNxWVn644H5xuy46VaLsn+O8oSVjkGODDqWWPlnErn
x0SB53d9hxBcyn2tLKU3Ybvod/EZGcu+W99aUdQlfHfnVvl7OI4Z6OyjsTRC
bo2IDQ3h4FdZek6lUdPgoczLnz6pvmk5rW/6bivVWu8fOzBnXZVPOzPLGZF/
jNWrPqPTXT10k3sHJqjMoBxRHAvZnlWMQXnNN4uN/9Hyqc1XS4P9Ws+C1327
Jql4QOZ++Q136wVmHysR5iPn5YQQiKR6SC1KZZFCmTgqKWexpVoFNjrTQHMq
jJhB0wGJFbW0aoq+VKNaMlO7IyjJez7fidTFa/XeGTUyU6TnFE2jB/4CXT2y
7BJme810VeyuXfHK9Ff5UQ0LhIS9nr1dxxKveBNvT137+aOd//m08/4pj31m
iHwR04alFQXAhq+PfaS3vK5vytknhc/B1h8ugoR+TeXJeYmI84vUc8uHQaPC
amKTmrGhKKdC0jhkU6i7zGUTvMHLT1/JKZgc4orrS6td+SApCZZTnKUSkOBp
LrBkpe2Y55N4cO7mL2bqcSXNcM04ZCp8pls1xelklz8UeFGYPXbtrVOXxbv3
b7j1zMeTYM/D1vstB09lt3M96Cf4rO1IXI2pQGOmuPgotFf7A84Qi+SsMhlJ
B8LIiTMTVeghwTYImJfwvT/eMGQQuiE0qd2QwQGG3cUFes0J4mKBcoFyt2wP
EEvWza7HqlKqcjEgbfDKazjDGR8e1zAJXc1ZjH32qebnfVevVzUHoThjXMAC
KTCSXHEStbdcIM3eYnpeyxER6MDooAPmiy61kjtlE3vsMq8XnebWFXbhNdCE
88krA+0QcYM2Fi2R2KECgOSnXCFiBU+01JRLqqlRDvfD2Fxb+tok5hfBSUJy
cpeIJZ+yhsniJQ80afcZE5rlHyFaDPZ+Qz9g3uD2tgVFS4vcZSPBneNisujn
pIgtqwLQYzDDWaeQYE1snCwKVGcMe7fZZFa1Ocw1WuQUHM5iT9nA5+ndPd/X
/mheNW/CzIdKVh2KkXUzxZvPamIZnuT9A1YwqbX3WVI4ElXmY90ONr6MxiLo
l+ei5uwh5ia1MkuO++ai6xNANDGSk2ZzjZUtpVaIFifyUmxO/My4UE+ndW/K
fWVsylRzAL2X/4gH/G/Jd8kf/Jd8qapG6ZQO98Nr1wdVV0JH5MuX046Y/hPP
+z1axT5lQ1SMVNFQhv8n3R1ZW/r8JR65Wz+o2pgAElkKIzX/NXz/aI2Kn/Ds
7GNJp2hdYUb+vh8e7QMe1XOzxz/A5LkWTraUGOwLJaICNMmQGpXzi0djySrc
uwtbYmjDDVzz26zVxGCVAsL+4K/3nv12mjieegLmW0yUyHVmXBkZN4spL2R3
zgp/p8g9gBMbrqgYOLmM0IyTjIPJ8we1m88lbTTC6VwUmpD/ct5qeoIb0tdl
JDC/2PXeKDv9ZahX+bCnacYf6q9TzwqRDfwUpySuKOlAsgU1i9wuRpeIOMwf
E5JKX3dF1RhSxrh7PXVxWf1TIgWdapUI3Vk6MguHQfdjFVaBh1Hutm4iTesT
XifUMYw2QtR29Uv80JpOarY5POBktYJ/jdLVotDLb9Pl7eA8H/gK8ASOzKee
+Kk04yis+VHC5mvpLNbJ2vVGBbDa1JRpU1vGJgOOzPmFnb4FnWvGCSjREyMS
IFoNZaXOXSbqUhc1GSPzDIGgCDyygrJqrMQE7PzbdtAi9yO66807JyjhlDKb
/ILaMXzCR3aFIbPbdiAMEhWrD6n0R7k7TXFWO+o7DNmandzQxgWoZZpCx+6R
wAvJxIXSD9DakLyYKoOmDU9GIRHojew/hV1iRkZwR9q7HokfcoLwQe+rDKG/
0dyVym4WXs8cf1S/zLn3hFU3iAniiCCxeK9FgNlnpQkPkobr8Dmat10p4xi5
QKmzDeJPcbKGXcusfcSDvlu3o8IZc0CwVrnf8mWi9zNkxzmjcMvyuzRlnRgv
DMrXkM9LcANiwtwzRL4mh+47+U4tJy+34Ik3QgnsiXVATPLvyq6INqW+Ie0f
JwMwmoAUinBIDu2GrRJLv+fjlMJTuA/qFbuQbxpMwGVmbxAfhnk7pyI5tA83
DTP2+67R4lQojFvrwvmRH44MtIfOdjzpSJqoq0qT2W2a0fReoekNO1rgQXAt
unZ3q5GPTx17lqIX6KskpIZRiSSY1rZ89iTA0rMjepKGWfi5Nh7451wMoeLd
NednX+KOVHc9LQ3KwiCgJxHKSoRBZ5gcGOw3cjvGrLAoPgIhPYEEs1gPnzh7
wznJ/yK8pBxaMf94Zys9s6jZ39QpzDPXS8gI+mi+eYqYEES8Djv6vPGLbZnh
ShN+VQQdF7AQK4jS8+pe3SU+ZaBNZNe815VcvQ5HYqllECUFwI48HcOAb/Ir
+UrKNyWqxZCKZLGwdBLwTuHIwZFs4ADQ090s+bfqm7HpRLnA+OEkLPxgKYOu
hYB5Jt3ABCUBq8jQbpHDu2VGagu2tDSDf2DYz55Dw2R/nUx9L9FpJbM49GoY
CxnDNs+pjO5OXwbpYY9B0JjpUtWaXfTMzbKREGhOUcqiiTCLsywh2tW0oKj7
tf0klHFY3jQ90sgYHF7TgTmZ1dJKXvrAE9WPpOIX9hWnawzz2WQsWWKEpys0
cyCiPx8s1ByozlCeFXkWLyunzolCKh8T5veutpSm8VPuHOh9X8ozGDuwWN9z
+Rm7IJzEX4ovYP3S/+CODwp4/FL+x4a2QZCBNVK1SZxepOg9n5OKNy+5FU2c
+sJJHaDNpVTuvVWbOTSWyjlJ4IvbPFXyny8wdkRWVPvcyZAfUGlEwdDoLvBF
KczWT4yZQpNvAsMFrShLgMHJTAV8SOpRTQwQ6FSjXjRWzWKV3jPDq6YKypOg
O89e4LMjlJFjbAY2nc+uU44bOq40pkJR+KQta5lnsNheh6TiDq3IrXCt+wl4
w1WFlvAPfgWyR2feOz1EITAupheIjqrIwwK6TA+WJLI6askiDOAc2hdShsiy
GPar/tUscoFjkwG/UKOtSjKZ20huFg+HaY55P7QsVpVNywkUQUoHhxS18CaR
USHMdxklB4iIm3F48ooXxp5UwSkcgEhmLaHdtMKfK+lUqH3hwgGJMiz6p75I
r/ivg9VV1w1iLFvOYkjKluVMq+SFNZICB9AIxgkDsYHGuJt8K6cG0oyUSK7E
LrCRtSBJ+d3Aq6xlW2zHdCvmo6mL6yDlpAlUxvS5lDhMQ6T33xZOlfDjZMn/
+bu7uOAkLXNKukD0yZSJQopHCkvNZ6AKLIBUyGOlvJthA0trW/emgAws1BgA
ON9KRv+qTqiYoVzv5PgUaygjseMEWzqEi7lmZelkFdx8b9HDr8tISHJR63Ox
Cg8Bk8WhTFVCs0cV9aalziV1XZKHmcDd/ClU9hMt4LvOlSUVtFelVUZv4Sok
aWWasLk6pX4Tty6j56j8ToWnbZMZmU+bBNMWQhou0RpSakNarOqV9bqsGDYS
IEcWXl4bSVUQrSulki6nfV6nUhVIF4r1G6mo5hDYygkINJDyBw+685fpophL
c5uJf9flRfsjrmBm5vXQH1ZZl0XWQxylxbqHYd3mZohfYE7tKvIkfvIhpvKv
OcTF8aAR0xWKgiLlWJE+b2lTFIau92P0ohlHfF+Zb/shl2yFESwM53rKrSIF
pWQTkYKcEZcS5oo7T+6NcQhZFxN/bbT/sbzP5p5GAoQ8giTZD5SCpYV3p4Yx
xI5sNsuEJMjZ5Srju99eFkoFboWU+WpdtqKMgTkpMFAfJyRwVr26KqxEJ2WL
SLzf0SR+yCPBEtWWJBsnllU+0jiELLfjIt+xwvZhmhFN0ZhMLKa7Y3iALyDP
NgTtrndDUnfXGjnfazc5neyJ9AH78/nnyCnKd+w0o/onkhnuk8XphZQXJqR/
C/XdhENIyB7vYv1WDdA/IZWcXDyKRGfGILJaqISS8tVZYju7ydueWdCLk2kX
07UajFDuAJr2iE55yiBnfJzixTFfOgi1eQuQkg3zEwiDBXbaeRFWnOzxYZS+
1BF690rNj038ps2gBY4oTkdYkab3x6q5rdN5ojz7L6lz28thwXkQxoJ5+mrf
L8T35o5tEohaeTRy7gg6x4+sgGYwa8IApxMkBzqxp5xYlNrX1gPbLGQLqPOA
3jylCc6xWVh2mZycrpjobb3ZaeZ2TN+sjCFA2MfUO5iKlIo/4yINSM7jlePi
lY9GZBIZg+9Sb85EfYYfX8iiERVCqoGIP8jLXKPapYXt3TrdVlxZTijn/qpE
OxQM4wdqMUhajVbt4foTCW5HZwbVjSGAUqoT4ZsvfFK71V/6kNBT2m6GPvYc
RaANOvgT+9rzGIG8nbYmR0DGJodFUFPFpP1WTtlm6PILx7pcODtRzrVI0SxF
UzyjQz7oRcYHwrKQs0hrLqiS0VSxaqhEIoVGGGwoLafCJNkkT7z2LAWFp7gg
v+wSS63YHHKBw1R//R6dy+TxEh7a4/KTKLac5tRdfKqKT1aopio/1ZeXvS+C
wx361FsRo09GIEyiS/KGiarWnZKdK3TGIdMkcynBhHePr6STiVpfH2+O/NuM
IKbLxcVPOTW0XLTmyTpxxc+WIhHr0Zdq4aK+6DrhuiS6xqySRCjLRnRQeaUh
jmKJt2W+1lDsSzGpNLRMGcapGPNsyWoN5qKizLbA8WTlmk800xiXwYIrOEdJ
AgqBnddZVBxCDmaxWswTPS2ZsO0ox02yqmYI0cmG1DKNZlK5jZEoskepQ7As
f0/pCBxv8IVvbN8lGl+aqCnKXwnYEIQHDRcq8WaKoImpG/cDbxAt9sRg1lRX
LFXBK/zGFIfyoxtHdopZ1loyHbdLrDNO1UVE8qwNJir1lYLPqkoYQqRTzpCU
zqHldRwR1rk+Ubhi9GINRbQn8zblCXd8uK26y23714ZrR5LSP9Ud9CX1zFOW
2KP0+meH9vWr+DXtb4sLGoWUDE3XI2YVCaLxaMSdWFlkWTJRuWSYO7WTfZSv
IgwYdf21emnSwxjvOiQb7qpJJ5DHTqHWoGqavQX5qfEXwQ+MyuAiOgQerLM3
tlpzaK12qDokUnLetPxNIovjcZFz4Dh2Ym5ESC5YrTBSPe0nYYKeYvPL2UIn
LRGfs/kbSUZdBMty3EzKkHjj25S5UlVGikDrAp2sRJcu5jzZc6uQT5pwTW3G
S2UDrpcj0MdFDESVM5jlsGq2sNM6lAX15v6vCe8gDgYt++HHm9YunKU3I7vA
ZWzFtquJacrKmkHzfXeHSyDdxVaBmYAwFljHmQnpbR3aC8sySGkDWjYOJNPU
39cOjtknVSGeQAAVqcX7wz1ByNeOSPfUvokY5qcYDzRb6FyUAgHbKU3OUcX5
UJsjO/F8T47EN7kqp6F2WDiw0JTt9ZrzlT8rl5EP76RC8BSH2IxMQS/OXe2F
C60sVUiFkhU2uiEQkWpITeMqqrc7Zn6/iCciQg5IF/Q0krvcFBuqqd1H0lKD
BK7CkpiCnGbAaQsS8Z+AWHMeRDXqUpjQd3jx7pRNQk87NRkFbIYyMSIPyb7T
I23m35T94vBXVXny8sSW3rs1fK1/wK+zJ01s4h8OH2riHw4RT0+jckTPo8wt
vAvszdlZOjvUQhV+7ewz6wUzMcS15JbQsTewJ5xIifMIqXNrNa91w6lOofFv
EyOt0uTXamQlKGsyVt6ZnNAusNTW9zr2TKNqMgyOsVjsDa0sEC/hBbobxLxw
WtMHa3VOaHlUL2YuhEU50UiKJNxn2ufK76z0afWGtDWm5+2ytCK0qcYsk12X
/gQufzgszv54tvgqybxaAqCoSKBigLr8IVeIpjkX9cf1LVRgdcfznZ0aIoYr
9g4kuVzZS3GIrhKoDdst1B5dLp7oYVa3WIKt97nJtGmDeCT1+iaMposPJ9u4
WXviNjJLPGGRI73W2my3jboW6n2OiNq/gzqkZ3IZ0Zvxvdk6lIad7iNKkswx
Elj/mrrf4NbDv6UoJ8i8dpsY1rCTtA7DOKhofITTYekXY9ofsn1i9evEu0CP
Em+UvUrXm1OTYHQG/1nOkcUmRY5Kc9ST+tDXyAO+ZceMHcXHYj/iKNp6nC1b
LDZOpmIG3TVoGUEBzfqiAoJJxHM1VQh0g95HRHeY7Fo7RaPvNlQKvEl0xxYX
bbcFK7Iweli0r+6pBED+rOS5D/1lQsTCBEfWOKfi6dxeEZpVXBdrNuKTFKFK
oegqPnt9iH/Xu0tOpzp7IxLi99sN7sv9QVvrbAIAg32HFWgb4eJusMCAWCe5
xfay/Dsp1fT68KjEUlFSL3oRunb6yq57I9fJWQZPdpdqr8/2qjXREob5oUgy
BtUHNRrksChoBiWuaoWTfUNOkgjFpI+nodfDHBn5IBEWc60skVIWTbJazOXL
wKYilZ5qkSBOdjoaFFJbfdTljs4KGPWInDPPS6E9I7Lxeyktis+oBJ5M7cu6
EoqOTTNmrXgB6Ws24LujzVnoCTxED6UcwUYLLWD1zHOqkLHCCHPI18Z+t0oS
wImtt0tiRUGL11h1k3jUN2mNq0q8oBTB15h2lolgWk/xMl1IKAh8sPsjE1bw
CtN4Eq8RHMw7c1YQJ7HIavoilVZnVxzB+d456JB+vpTf48J72udLecbthjD9
w7fAc2e4E8rZb/d8ftLFegs819gwQVlPr/CR1dUEJotJpvF9aR8G/TURjkZb
SJAFgjUMeoW09eahaEdKapPAMsIUxRTic4kfcBxoYp1MwOdOfLP03MyBC4t2
XHQXC+LVsDJoNjqudSe6yGe6R42nR09rkGFr36nvNtqBeyv+fWGcDL8wHt5W
6Hp+tPHJ3iR7cJbrqXzeO8v7LN6Z53rl6AszY+3RZ50m654rTVoQdOJxznbT
5Nymplh/oEOEXjW+YraLP9Cp1yrsNq4plY1xF3Pgc0fsD+wsJOyWyE9mU0WZ
SMwQCb87ixl9IHTmAAvQzt+KfRKnAbTgS0EUmXR9NxCv1Zmp5aiFnjYXNZgx
EY85C3z2+K6o72kRX0pHErTFDqnQN1pBY8sVYTR9EHMr+1GTdCwzqSCLQVLC
Zn0J5VvvtVcX78D/UD7lIrp790VGxpzhOa/VWPjp2LtavUGiSBPfanYaqsNd
0cO9OlZDKWRXZcWYezXpNXg2tdacZrW/1n+8EV4ZsbLoWeznO5mp72m75wf3
77PDwqOQC03QFTYwxYPwg0LkOOGn82d5ACna1UmjtLq1v7VCOdLttUXwTeHL
UtAmpaShkWR9EoqBFEpNKGI2BHaAyJrutnkAGAc9zWOxH0JHICLnXwNtb8gR
chRsfDB7WOG7hqObAueKCXDO5zNmblMzyqGdu7pHGz4pzJLG79RdVP2oLLeh
6iPZGpgd6J4ssloM+yBxjJwyM6wNGdAU+7JUmN4qUGO+2nzuck4rp4VuvCSg
NCQUUgkCyGrzjeUSOP9wYh8r8rjk/1fatS23cWXX9/MVXc6DpTIAR9JkbAuT
UfEi17DKsh2LsuYhD2oSTRIxgGahAdFM6TkfkJ/If+RT8iU5+7736QPS9jxY
loBG9+lz3Ze111LnAIfFJ9CZgK1SpJB7Pz0MYyPFqZb1j8R9sB3VvUpCYQh6
hquGl8ott3ui1xSpYOhcR3Ruv71uN4zGAV0STS+C7vJuC6MdP7tlMezyU34L
9zHGAqfKVgHDBLYYiV8U6H7Ibm+X19dATChJYDr92BQd79F2usDojCGz1B7G
y3IarkBadhTbmiSfjLUcIgIs46FKhcSkF3xviUoaEtpGOXTuYSOwcKqnftSW
ZMoHlr/NZ4Boxo8hyg+qZbBCz21xWktxvN+xAoMLEkeE4gKsqPTnuGCUKbGi
vl56AKlM4inlajDFL/tMocp3HE2ycCLO4mPNgp0+Z77gZ5Nk7P9U04FVMFo3
SAGlynF4+uxlagJAr7Fym/z3n+EDlK8OB1zTxCMOVZWcdm9ef7t+Cx/jrCE7
vx36DZHv5xfAO7WrwVhFjOfkk9+I8qw26pmPKZ0+Dy2O9SiHCofCm1jm0iLu
EoWWp/p5pHWCdxbeE3W+iJ/hyAbFT9w7LAfPCnVxj3vOjtTebeb5fYW6FT4J
Ffz+84CImBK3lPvesXSYKpvsRiFdrYEQYXPTdrer6/zo3c2aaQ2Y/qKwd+l1
eV4lzhAMFNBqR1JWayiRyN3UPJEsfqj4SjpmsZjx6YMST3759FfJv55khcT4
sfRQXqlYlIKOpZ9Hit/NAw1YfoCIlCTTp88/1xKbSAZy0SG7RpK8OKv9zg2Q
pm0SmLEixlzD1YQpiATYV7cQ8QH0pySyyOXG2B1nLckzYzKyiZy4CzO4bQ9W
Rje1dVw/8Rbygzs7m7CdgN/9r7CnxGue4+GHmwKUPIbljHnZ/KO/f0VLsvih
4U3FXH6GqUm5XMmeQXxz+UsH8KuJ93kVbsUpRbQM+V4jUI5oo/oDhsQxb1rC
mJbZZmnVQ8nZNyc/atateffTWf56NpsluhdMuwswirHrvrl6wfg/N8Y7G2Pm
BRnCupCTQCHLLICRivRn0BQ/A+y0gfkJvC0bnIq4qF5bz/okTsiYswBarYXA
Yy0YijKdsRY6L1ko/tUguNYZcSQcmuBNBAlDLDeE6dTrGScDQVCBPhu00VuN
6VyDoAw75IFra8dKcZRo7aXuTfaRO1FItB5M88FCuO9uf09rGJadPNYlPwwp
VpLk0oYkPA/eohlRTwySnndoz0DOWxPVykttv3VoP5E2l4ybuJ1RdZlbf9yA
c/0yHL0EIQIeg0XXZ+MHLjl+STIvkCL+iewPbfVLiIhzZirbWbYxWXalA36Q
PHfz59cloGwE7qfMCpzEEHeDoN1dEul0JxhYxoMAn69apWCzVYo2eGeJqT8n
cHo1tr0qtdjVlLrPj0lCADRj4npm+9jjxBSHp0pqG2sTedq4wZGJQeXT6O3c
ZbcJ8qCDeh4cLGU0kVSU0Z0KBJk6KYdRAvgKOuUut/e3u/56297e8DqopXop
Mw87+kP9F+88Th7zEefi7EXaOHdt/gehehjVGzmUwKK93jJx0a5jh6jd7TAN
Jjjg5GK/bmPlAB/mQCMGlSLbkv2h7HVyPk+Pgm6skc2lDzB24NPiLox02DA4
19t+TzQjVPS7NdX3s9fn38brBgVTvj978/Y1/uwH6IFZnOc2la0KDFl7sOMt
3SxB1ezla+kvwkPBxSRI0M4fw0qdUgqjTBKT1uC3reM2wpbIx5iGzyccSBoz
1RMFz/McTgImzWuivQa5RCpU1G2BNvVm6hfnhLwsyPVT8wYuQ4Q+WqLsOrJV
sSVgOBpCNFESlNhz8o39ORLjqYwIk05lrFKFoUOjqdRaiB9OQuJnUsZ8DCso
HcCalej2iLzUIwCJiHS1XSPPStkvCIuNMCqp2YU0o/Q2u9NbT7BGmnMCdJge
IUMOIXTxQKOmnpgS3wBnliIjpq3+YEs/MOXoVj5COklYeKtGCkhzo2P1XtgI
XaQZb+AQOeDLQgkcGCiwLGPZoFYjWmrc3YZ7HaVgER1GPFesLx76PXAYPaIx
rlMk4Ztvfce5CWU+hbAQRXwG86e5Wt2RfphyKe6Ian8pcj6u+mBTcfHY0Yhk
whMNOwlAxEyqyn4tEaRHZAeUyDoBMcK6X6gNOqdYk4o6BtZsTG4qdhRV1JNO
sglIpF9ks/hmeRu1pCmZ5Gy3qcYSNMYvtQiFlyG+hNWJRyJRKcvjtOd2f8tB
M8ZhT3hKS+13D7Q3eVLSqZ1ilIAHADdqorvU2qQ8jpPo5AWahTQihaDNt2SL
8/STm4KDSYpTHDFS89bIp6rTO6JYcHdLbsojGZ5O5BKQa9k9QtczOHeRfGZQ
Qud4ABFNtvBgEnCb2ejWfsXBpEwU7sF7X+1Xqwo1+lseiSmeT34optzxKaqW
Yh+rbFQ8+svsGlHJpIeBbGH4VagUKRThwZe4Gcco5Le5T27QxINxgj15t1x3
KX2PePCod+D2FRTgMrg2/+wgRFTRzI0Sny5SQDmAHOEibUe4ugU5XhLDXJBp
d3Igbkx9yg+l/Gla7+n/0MAps8cleCAuQLrf2G85ZK5CcF4dNc7QOix+Sses
PtoOO7NQW9rh5A7cpArWz/sbzmDEWRhIocKw8f530UFEIu8DaMiAU4yYIMi4
Buy0WPMBkwY7J9mllAFg8QJXq7AlhSAKYanb4TWtXZg0VeDJXETVRMuBwmdT
Mglld4Z1y+pMaN55OQU4gyPHGwSQxv7aTzjG5Fzb30FkAQhqGccYUJloP1y0
w5ISTld7XGahfr8SPD/ogKAbihMbuSbBgV9UQxE+q4FR/QW0AusA00h6exbe
RtOWurBweOyU77Ytb1sUjsfBhihUcgaP6wPyFBcKMfSbPuLycD/BV1vn4Vkk
sqRI3XiKGEE945FSRE/RKb0TnrWMdMjbNnVy4iAqzEKazeQloYeRrY9ZPiTk
Pm5vb7bWExDxjSAd38NxnH2tjeUfkxpgRDA2zpMzKAHcAhGwUvGTNUpWQ2cv
HckcDx9LPtwiPzV6DCH4E1pn06ZwqfNMY4hFZ3LuR0QUjUGyxHG6+lv3Gzbj
j0fYdOj552a9IBzBNyN/Ke9AW5kkN5b9tgmcMgETkNifKWYeW6nC3QETFOeb
U1NYsn/Es8PDDILppeukGa0TivUzw2v6zZBw83gIFCPVbLAdLW+XHW1laCoz
Um+HhlLeePfDSrEjQSJujq1L2oUCCWEQCO2dEspD6qncFkf64dY7Ww1o1Vr5
Jwd3X5J+9YgLA97svtslPLWRLw/6DEEyVPoE6duOdwNB/YdhVdqbxNsvUuEO
nZTGgSm6wOIxrhY2eyPwV+DGriZrURAAiSkNQqFfgjl3Xq2XewyokSb1ZwcD
c5/RKVqtOFCzREfX7R956V62C0jy5qMrce6SkvEd8SxgYfeoLDPvE2g6Sr95
ByqFisFWFlS5n8PBRWPpCODBBhshVKQynjO6GtHEsFkttetRekfhX0FR4vTZ
4e+C6EfzZfPv9k/UGznv87j+3T50Pz6ReDNMMeSecSCn/MxjNufq3z/P3zvQ
07FdNTq1FB37jDL3z2FfxnZVb53vamVYoLrEdoLDV7nkMqab1oEjCUec159z
g0DFm3icSCLp3ljqoMrUH/98PtBp4PSeLLodWL5gYBXeDswRnIcthCgwiymQ
qFSlFQQzcLmymFJVrKHPD7r2WRy/3oKIYjTGoa8g7OWkGHwaljRxaGlnGxOD
Ilx2L3QKwPEK3W9KqiqOEY5tWlHu3sjIAMkBHjb5WWFV693WeWnurCwQVzn7
R2dOh10JtIH2Vij/Zk628j9gjxIehRlLfA47SwWwhgHnuDGGIuFD6D6q7hlK
IqgaVb3gEguSM1elVKGuTz5apCyWPqQ4Ds5QaMjdt5rbIdGOU2nWoClTx4xa
hhDzaYwFE7q6elUlyS4X00Vlu5DtqpCyFXENkniglVOAzgWACvt2NhhgMKVv
L4tpyskmmEeIxBBViRqoBKAUcp+yKHCnw8FrHi7+1ljXNWk+Kuecw5wFTdcA
47u1WNeYv4qDLELQFXEvSMzM0VUVio1zyj4uHHup7DJBnwC894VwNSfIxq5G
9ZUs1qGs+hqu8cn3Q7fh/HceIk4+8766voCZZW3mX7ACWu4NRAwLsRV1XiI5
WxrGeaRsE6BDi4lUzvBMh86QsWch3TY0b//2w7vvTh1SiAypAFHxZDjo17qD
yx451J7oiwCbH/LLTEMK/fAWgbyFjnK3lUKCWaSGljXs8XpoXOahAB+YNHEl
pnSx13RvgVQGlAdQvr2oEH391hSnxWFhndXAy5y/xsMF9rnrG1DtZraRAp6O
1RgS3Ry9CuhDQndGYCB430NHaFABYWHgL69lBIH22XLvr++djwMfaz8PGN6Q
4w3lMGB/zg+66doFXFqkay97oMzdXCtAFLczhnFp8c12OfwCIgw18KvkHwdt
MPnFlNqW+4sGMARwJPaXb9hbOl9dL4y5QLDsZW3Pz2N5dHJ+9vNrW9hEd0uA
J7vq/PVPb86+Pzp/fUpXYvrvoG+qqUByOHPTsKXaNoRbYrreNhGLcM6knCeK
GkKXjkNtId1GE96CXBZXy72x4J4LC2YU8zMemvGU/iAVmxQlORD3szto736Y
h/iACwXaTvMHg4KCjBbu5IOamjtynqcr9GBUZOCAcqZQ5DG/yEFazAo/uZpI
2RJc9gsG5rbOQligWMyG0uzZ9dwjTQl2G/9mUnbqJG6NLpcTw+SlENMhQVkH
nitLB5R81gm1sqtuo3XTQ9HKRnWhMNQVSS1mj+nIaQ0UlxurJBGnNHRCCeXB
R+JzIWoimSc+hrpZlHHUGvPlwSqPqBwX6OMPy6OKHDkBTpvT7fJqV2CS2MYi
0VOzGZDlKhS2UG10WWFUQzhDyfYxAhMrVbi8mYElP475XXR1Y4XKxU/q9/S1
31XyIc2tFYXeWrYHL68wNu2tBfRWtk+WA/F0bZTTZ1T3Z6GL3Oak+HRwEDX/
yINxvM3b7sYRHEaLFtuiDDZmRfOSRPy7ga4l8tknY0M5MCbTvyoRKOxIEmiB
DjnmcwUeO4wc/kdj7+95EqNZkPfxXzw/tgWEJmIcUnTHnEOKmiU4k/o9S645
dkdHYs59J/5Af0FCH2REVLgDwQoY03rCp6pCSSv3XnHaKGGGqKx+nwdtuOl7
IlW7ct3e/dpd7hW59k/N61/B+AFrgYc1oi/ta+VItVW+ZB2lvMtkO7RDA+Ql
rFEC10Q5kVjKhqJjHj6owSrL9yWkETFu2L9Mm9M/4Z8v8M/n+CePpBY21jGL
DD9g4RgqLwHDjhMK+CQ+oFDVxeEHC6SRYqGhEit76VeQbhaLD6MIxoVaYz+V
0ITzwFQyispvmU0JfFLHwiXK0z5h6jwohDbTEpcjcfrVVy+SRyr7axRk/A2D
hn079JGY6lsixwymwwp6JsIYk7OJ/pJiSZlTB9GYyBXGKO7VPaXPggXr/VOe
3bCZwbkdojrs6EbbWK5Q/C+F4ujRKT7XjMJDz+dRkThrJZ4FXaWJLKnF9Rar
srVNKM6uNWeAsNiC4UdBiSRgMBXS4jJXjUkEi7LG8uNdrFBgGt0tjbZgBnB8
1OAwllpFQU/XcER5FmlkiJBud+1yxyxCTJBfMDswjhF9TTiqwIZEu5HkuhrW
l6H1n27HUTjwGoCCtihrK/sD8xb1gkpJiNn2x4EhlUsUKiShnx3PiSNLBeUX
PDMNMJG8jCHAbbek7AbM9g415l2trKiG+fwSV+mOAy8KBnQB4AMKbb7EE8p1
b0beDvInO6zV54MZ7TVlsBncB9diBZbimPaEX6rfHuCWyLeR+HvYURk5RtRT
BiE07RmHksr38JY3Kv0BHLZn0c4aLmIcfBG7mOYfx0bXeRZboShrVE7IXq5o
vHZ6MB5wW9LYQB5V3ldqfYuUTeKUzdmmhm5zko8hUck17UnBFIOWh+K6c7Bv
3WCDarakBmLtMVhOId6HZtMdoUs/IpsMo5SWnGllU/79H1c/zMahaYwUCoiG
h5B9DI3VgpoRk/GpJouIaDSvfXpA3hECsDX5RAbIYK5xhd4VbVP5czvGiqwI
Q5/I5MfShikWOgxYK0hM77xhhvIAyigg5+BmiVssrdoK7YAUauJxf8x84OzV
/FzwZ5H3ASmwWJmrDAj5Fpy5O1BukKc43I/7wmhZJZEDc+H0BT/oGeSVIMIJ
TawSenEOz8hbR/7egxURJ8/KT91NuVpxKPtsTJ9QedWisoeLvnKrMYt4IsJO
4p/xaV57yxOiLTtUqXLSYPrrmLB9q3arMFVwIxpkcJbNVqnA2Tr/o32DfNiI
u8ZRFMenVGHSRVRIdvmKIN2r89JfCsvY6XORYO7S2IGv/drVzR65Kn2q7+JA
EOsCNq6wv6zgLtGQtCB/8obOeftrv+nXzI9lCcWS+DwqOQLlOZe2qMp5Eqi+
34sR5sy8YZgwcFnDibLP/XqTdw6cWHnQN7QKIa7f7QhI90C4R4rXd8hYf7iN
uKOhcUoePbwtBRrHVIfb7hrKhUkLIht8ICIPSEgI/t3PmtebxW2P1WpklpNP
wGJ3woA4TktxTxHRL/aGVxkVql54XXVAglj9ZxKz2PUG3iAniYPVn82az94N
3WfNpl3zoSeYq9abb4nFYeYBka7shAVzkgKzLIyVQm8ivgiW4CwhtZIwWllH
NZ+swpHQNDx3PzXf5ycHRdlPzbshKKL6//L9P1jy60MjNGH/91//LfvZHPfd
/IEkr8SWc9cAtxUzeuRVhdU9vozEcXb5FCyLRhjhhLtOytlzgyI3jx24NYl5
dsA1LDtzqoxLZgX7ELet8NLyjvzKeOLYuyEsa1D/AbPqSvzt1QXo8jvkJZFQ
Ce5cAPV2r6QF4QpBmlD2xIXrKTagTCw+uKNmDOztbiOEhhVvPh/zm9mM5F5x
hPbNJz/M6uBZV4w4cUtK3HqfhLenwrjIqBqGdG6dpFxYC+LCGr2eJzyD15ED
sniVYkSZNwxZRtCjv93vZDbCpTMf2KQtSFTtgEh5PD3VkXXiHhOlisUBZLCm
wwb+zpFSG+nhdwtD1A5sWomZSW83aj/eY9hfgg0xkRNaVlcYnEdHoNTSGa8z
2K5MCkpkWIQLCZdXrSpNQG+K+EU/AXFM/W563+0A172VmpO5JZfkWI9VDr6s
EAupuAGhd6w8iMeZqlEpbzlq0+eU0URaMKcgvN/1U6X2xxjHxJV7wSfsMnt5
EjQeYlHEQH2vuBPsbtNYeXQ/g07nPcpxCfvXQLDxoKddPt+GPfFW1F9WXnIO
0BSiqwZDZRK4isdzLvQI6yaxfoJJLzKAqxi0ieHMHdI36LaGTpoLMwz1Vqnk
9NjkhMUkMHmIYMnP+RyDHUQhH7roYpkthIQhzAe7e2HxZitHoeyIcx2tS1uJ
jkSPQwBCl7RBusEbgJi1UnXtVyyRJxw4Gh/fdryqz6NT7H3X/uLqHAsolLKG
WzUOya4hnBGMGPeVhHTyOVI98y0Hq8CD0amfxHRCmNxwwHQ2u5lVi1XGZ6Re
LPFDLGcJdjKZq1SFQEYZdixAmI5wGPOHroKT4/BLBlWbPp/jqQw6a2SHO4JO
ZuGgk4VpnL3SW2nvTDhg3IprAjUibN33nHiUGazcTpCDVoVljVCkAGRCJBiK
dUJOk61/KMnZbyxYM/Yp0OpH5AMwyVpAFpM6V+06G3vtluTaNFmqgVbgWRs6
q6DEY8oZ4Rah7TAopMhSg60cRYGnY2XeSunooPaTQjgDJoGD9bnxxEJnGA+R
5tUJvFuKyBVkeDeMqoEQEUZJQwE8IRYIsKGKIsp5ulUb2sXfIfvYip1sBHaW
PVIPWt1kkz8XwUrHkFvXpmRpMEjhl5TFglZ1ZCQEyscqhGlAAdBQ6V45r7m9
LeszLnG/vYROM/is0sUEekDOrcWKByGSqbjuO5FznL4xx1g8Q6wGf8BvhmVc
Xbwsv0vdk4LfSEsmrGXzAwnbPU7b+AfyGoveYyFaAvc1mhgAgAQ0zGahFbr1
sstQTTk9O5W/+a5LWlcPoKhd55WNp66ICr9sntzFAO7TgJWmG2AcyY6J/JrG
6uFBD0mU+PAfVfc7m0Ub3IeVbkxQEmDT08Sq/lCvD4iT0NnJueqQ1fl2v1Ha
IbDGcI4Yftfm1SOzCau56MzH3CTCIfSyK37KJBGv2Kq9RzOUIh6c88gmoz/R
maZmYAJRLNE80vPN3byTk1IUNSRM5pkSpTzasd8D7k0j/gbvIacJph3sEoMT
TCywTrhhJH06sQ862L1Sjkz8e3FZPCbCID60SyTlOnHFAJritWJ4PLZzb4Ob
MytDdWoYdKQYquK52TuADqExwFiW1BhL/NnN+9y7X/IWFGir/SXHekn64hBr
/Bf6y8OXAK+8G+svqaOwLuYvfM1fD1+Sf92EuSIkcc0nq685eEmyi9z18V+H
L+FfU9jtwsjDx7+uXfIPP/tNZd4XvXboEny2zu4np8+e0jlYPrt+yT843nyF
HxFbru1FDxasX9P6HVb3WYHU+NXwHEOIjUi5ek4FXeGEgQuFEJ5yqtvAthAp
mJWY3bLFlaymprdx91DowR1sv8iZeO4LwRmpury+2ZH5u4Ic9hRfYDsx5h7M
c192XA3s1vEwL49lF8CmfYqT3PmyNT19bMSLEk03WEcC7T14qaq2NylqkJwl
4lam8doVEH4/Wk654EDYe+VXC7Jg5DNBSfQU+czdnPcfP5VWy4stc8/CsXfZ
biUIqS3gDqXuu+e6ZTmZH8sx7CTS4h96296v+nYxJAwkcuYAXBNZ8oHnjzwc
dH/bCi/OTCja0EqHb6KURQkWHjPJhIwtBv9YtRGrtAudPonr5ZPeHAMxHOGc
fcRw5HK0fGhDJB6meu2lBmMcAprH3AFvTn6cHBhyr67NPJue3AEjxiLRjYOh
nmoxHqMQHKpqEHXJ0iSgMZWMHbECQrIteqKT+h1LwRt96wcg3FruQEgbSqJ4
qw7d55HJwEtWgPUEAojBDQiT1FrJlV/kgDsieFVn8b/a7jdERnJeui6qOCis
tNu+vbxh7hfY+zylM4lgViFCHweTvc7LeXvVXnYVGmrJ31lV0mSEyHFKn2C2
kRSdt+fzo9BRINNPpn6epNPx8iHgO1uia3CAMMqGWT4OMhJJfsUabYSyOFUC
I47+GLuutEIxok7o9HaTHvKB1NW1c3A/FAbsJCGFE3jL95vLvKQA6GI6fohH
2c1MPIaqFXEtWIdOEpm3zMkjqBS/Xyt3BmXsUR8NtzFdRueRWy+3eAvryWlC
8iBE+VHxwJK6LRNHKD6tpbRbJeIfJJKUxIcdplgJZMNBSSXKnHvoFrqw4KDi
SAnpUCh8hKKPWxFWpHgX3IABP8gLpTF8RDCHF+S6fBfcYAnVuV3p1RIpcjfW
VxyaJ93sejYpYAsTIAeN0eBJU+QuVLp4uuvh7xRpfxoaoKU+DpkcPWm43OiG
RdcxhBbvxjq3vidxtuf2wsYmQO0x0L/3Sr3x/r7ORm+MxOjhvGNLjXn2ubJx
B8Adq1sfHOeBkCoExvJlAfLzIo0TpXYQzAmZaR7TVT0CZ6OSA2W4uFUBoWKz
KSo1qoGffKAmJE9WFQgCYRj+hhH2cgSzw8fL6owoo/L/jHw58SZ3ttCqDI2H
4Z34GKyluMKW3tIG5+vDGdHgSJ+1IQ2ArA7c2oH+2C2xGmYszoM70Yugf/HQ
nWDyppJv+qEf0BOLnTnoQln1iucBWQZbSxA92TEHhUWSeC8Ol/Y+oTW2cd1N
1Zjs0sQoHCNNJvq1jREWsGGxJ2PQqaKQYclGZUDYQ0YYjrEqyZGgk/3iz1Vh
DsoXQnICpjivUq40co4Ag/lqc6a4HW8lmgBLMYHmE9SCiKp7QbzdQe1rmL/Y
77BuPujc++BPqdFk48vmLDaT7z3J6zxRdI+COS3ZHQFHLoGwXVcrXwu+k4bu
QsnBmIigLToreZbSkXEzzoLkt4as593GpdOy/bsLGjJ4MAZGPfYiqQ086zS2
CLMMelOo/arbFDC448kBe7ELTcPn+mzYqKnISKy8/NX6VuqNYN9FI4k3dLfv
s02PJVR3zhSLvK30Zu0CDK/mro2Qfp4mo9s+DAsXSlArd3I9hUAA303wtu4B
mHPiQC58xfvuBF9QTDjh+NOYruvNylTv1ocSBAMhdvPKO8/Px8oa/+GOPmxE
/NkSUMNtK8kIzPJO82JbIdbyFzK/2IfwLOTjHvd6DMzAVJpLzhjkfq3YQnzE
xxS1kwrRxLSwFsWKkYBgIcYJLcYqthk6ncfB3IB0R2yFH0jorYaMBwSirFbK
dw1UT79iCIX5VKG/yYzkCinBo4NByp0aSkJ3VLkMQmsOj1YYHMS1jBV6cOVt
P+ymN/2lr4yDUA6M5aUh0OvT5uMJFHbAn7Z/DUG4hhUY1MOn+UOefIBBDxPR
vWK9bsZ7j6dKMCN/1+QYGOPkGzgEUlkJc6zu5UiyQkU/jEGbJ27dQHa7WLbq
m1NzoI9sH1cwO/ehHrFaKrLlTF50loHGOb/x1lJg5jufoq1aBv29Vo34J7fR
vA2xLixrT1bMz7Mb3d58cq0WYCE+mxnkQ8KovMfidi8Qy/R85lfigYPTWxTz
9GImtABVXVA6/smInac/zTzWgr2lefqXWRQ3YyGbefrzrLlZLvLjPKzQ7jBP
X81i0ZuGOefp61mo5zPNkHn6ZuY9k1CJ+uyfZ0ImMXWFSfGa3J/+HbPx+AA/
t9bZso64BKcxeE4S4QIrmS4AuLgxymaMrNIOOaIUzu3IwyUj7mOL3grTjYWk
eYpw1oCN8MVHGF7V8ieCD7SOJEHnRH78Cz9sSGQwcHdUCuApcx9DWABugAZc
uacKuiP4iwHdgBVxUsxD7ucznFiu7olIxxlGr9VAPOcrrcNmcOERtpPJcnUK
KdGmVfVANY8QyysGFm8Umns3LhNqP+YW4ZqR7Tr3Zl4ErS1gT02rlLaCNCRq
cnfak4EOjy6z7hxVdvwH+JYLgSiPziPu0D/PPLLPUschFgKNk2yKncLGN4Et
4lAXtzrU44p9ywS4kQBRKsFpaLy9dCHhRUVsVxl5aUP+ASGq07fw1uxfLPrL
PZrVRYkAxnyOWCXx88GU2/Ib9cRt9SNZsDTFcvd3H7HAiu6HkZUTLLrG0CyE
w3cYbcEc5xgAgN/9JuJqFzPHaI+GjqzP4hXnSB+pK7tyD2oUsotg4K/4lo8Q
tHy4J4HB9d9UdAdOlUoYadsVbq2E3QjbJkAFGFXT9yIfZCYyapcuLzFQiBkX
gYAsLHHHWyhBPTn4pjsR1dbwfBEJT0m9a84s32Kxba/yS+bt9C0V3xXhvItO
WEb9OYRzYG3ELxfYHAaGv4KD8T3L5WHxR97a1vt1/ZQMzOd4VGPMC+43ond7
Bacot3PEe2HrhJsGayI/hnrKuai8gF7B2Qu63Fx1ODo2dL3ncfgI+3z9TH0F
R7W7j4Qm1PlTgxKrA3M7r0kcI4oEvIID/T2G7KIlKAZOTXrmFRz17tlspkyN
dsKRoAYLsThbX4FhADdaQ1tl8OWutM0dQuK9QsuBmu6hVmoKC70f5qoO5+Fe
oXXxXp0dx0J0wBo7EOjCwnQsQgcTL8YZyMQFSCSOikYpxOUlFBu2+/OBlM2p
4EplQZWrkJYr80IbmSICh7Tg7qrflkasWD6r/p6IJ8GYcYP4m8rDXL0KnhLr
kifbcI7/yaAzRP9M7BhCLG952kD+1Di5+XCiCRCLvCUiQ/kmpkGiin8+jB1F
Z0ElJPqh3hx7RXKGR98fFa5DeXKp5smmp8s5xkE7tagxjG5yUstkEiEkEoQI
9ccwCcBnHyMJ1XhDhRWQBxD3O0AgOlWLwDfVfuyXC92wUsgiEULhQTJBePXN
NNDpQyagB2JRMUNb/5tSXb2oInmbW4skYBNRbHCzaeEqBWg2lYPpwiE8sLHM
3EP3/NwCs2SO2wq1mgx04nVYpBYLYJD1yn5DADbyGgB97xRVHLe2Lg3k0HZh
gELHSnZWBQzYFhsSOI6HDTmZuuYBHurmyf/+z9ezr5+qdnXNTWk3yZD54lA/
pMQ2Qsip57RkLpVgecw90ABLOrsriNUwRQnM9ZdY2bjkahREE0bj5RZzuVhZ
+B39urFfl9WM+V7f9ttrK1zOv1IpNc0fWvfGYgQ3Lp9g4RK2GPbKdsfk723Q
ZXNkEPDo90jtSYBp3tHzjc70cUgrwWYCMJnZwtD9/1PztohcOxsNJDD6Lb5V
fto7RyWUxwByIB3Bioi2MfdXXlCw6D1T0GbhEeES5/PPFSLHPAI3G+KbpMe5
fZwLo+gx0X6+Kijyy+89F7uslu5ju9rz5flR3/UDhtUCCRidAXlcgEFeDwvP
m6Vkg/mqcyN4tl7L5sgSYGGXJW4M6kIoKcezDWazLW+LmMXhPyzLN+HkLwu0
75cr7KuLbDf8MkhJP7BmrYYOvVM0zfMGci/+FCnhjeX02HZGebzmatuuO5eO
f1Cfh8LxbkHCdEYPRPoNJH353IrFEeUhdhRcX7VU37x7e958/8N5Y8JZpQCs
36YTElVjXkcv40CWLY2Dxxu6irUjTk5VEqBmljAfsc5X4l7AVJKM6UWCVS18
CAfd7rDRiSrYeIzqnMclS4YFmU9SbwbXrmBJukKPYgeSfYAjmbdIYPNrczRr
Ttp82JJj4AY5Ek4kIL//Yjo1MHIzhX8R4jQRHPUT/x+uw8ytR6n6f8AFiGp5
MjxtnozS6GzuPC1/og6RQl2e4EWxZc+tZc+fJn16E1vmIbruH7+5ZfEn9ZYZ
wdV3AJ5/aakoA0dq7XJenGUY90sMBVrCOr/TIBQRMAGu8xptPJ3B4+CpxWLJ
XnaIcUpy+pwkqSTqPdHU6LrfpIiThSDcsITJFwuJatxNZBdl5zpJQnJMxmQm
dLfwdEwla324f1ThqjBsE5OM+4JzsULjUVCO0Jf4m5J3BGaNjmdgWlHj2VAy
SpwSfmW8M/g5juv/A+dxEqKiKAIA

-->

</rfc>
