Evaluate Proposed Embargo Behavior
Requirements
The behavioral requirements for this tree are specified in the Requirements Catalog:
- EMB-11 — Enter EM Active
- EMB-15 — Inbound Embargo-Response Decision (Received Side)
- EMB-17 — Late Accept of an Expired Embargo Invitation
Implementation approach
The behavior tree diagram below illustrates one conformant implementation of these requirements. Implementations are not required to use behavior trees — any approach that satisfies the requirements above is conformant.
Legacy design diagram
The diagram on this page reflects the simulator-era design from vultron/bt/ and may not match the current implementation in vultron/core/behaviors/.
See the Behaviors Reference for auto-generated documentation from the current implementation.
The Evaluate Proposed Embargo Behavior Tree in the figure below handles the acceptance of an embargo or a counterproposal to it.
---
title: Evaluate Proposed Embargo Behavior Tree
---
flowchart LR
fb[?]
seq1["→"]
fb -->|A| seq1
eval["evaluate"]
seq1 --> eval
accept["accept"]
seq1 --> accept
em_to_a["EM → A<br/>(emit EA)"]
seq1 --> em_to_a
seq2["→"]
fb -->|B| seq2
will_counter(["willing to counter?"])
seq2 --> will_counter
propose["propose"]
seq2 --> propose
(A) As noted above, the same process applies to the Proposed and Revise EM states (\(q^{em} \in \{P,R\}\)). An evaluation task comes first, and then an accept task. These tasks are placeholders for the actual decision process. Each Participant decides how to do this process. In both states, acceptance causes an EM state transition to \(q^{em} \in A\), and the tree emits an \(EA\) message.
See also
(B) But the proposed terms can be unacceptable. In that case, the Participant might be willing to make a counterproposal. The propose behavior covers the counterproposal.
How the CASE_MANAGER answers an acceptance
An acceptance that a Participant sends reaches the CASE_MANAGER as Accept(Invite(EmbargoEvent)).
The CASE_MANAGER answers it by whether the accepted embargo is still available, not by whether the acceptance arrived before its deadline (MSM-07-012, EMB-17-001).
An available embargo is the case's Active Embargo or one of its open proposals, whose end time has not passed.
- Available: the CASE_MANAGER records the acceptance, and the Participant's consent row for that embargo becomes
AGREED(EMB-17-002). - Held, but no longer available: the case replaced, rejected, canceled or terminated the embargo, or its end time has passed. The CASE_MANAGER refuses the acceptance with the refusal notice and records nothing. When the case holds current terms, it also invites the Participant to them (EMB-17-003).
- Never held: the CASE_MANAGER answers with a processing fault and no refusal notice, because the Participant's view of the case is wrong (MSM-07-039).
The embargo lifecycle describes each answer in full.