Report Validation Behavior
Requirements
The behavioral requirements for this tree are specified in the Requirements Catalog:
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 next figure shows a Report Validation Behavior Tree. To begin with (A), if the report is already Valid, this behavior does nothing more.
---
title: Report Validation Behavior Tree
---
flowchart LR
fb["?"]
check_valid(["RM in V?"])
fb -->|A| check_valid
i_seq["→"]
fb -->|B| i_seq
check_invalid(["RM in I?"])
i_seq --> check_invalid
i_fb["?"]
i_seq --> i_fb
i_enough(["enough info?"])
i_fb --> i_enough
i_seq_seq["→"]
i_fb --> i_seq_seq
i_gather_info["gather info"]
i_seq_seq --> i_gather_info
i_no_info["no new info"]
i_seq_seq --> i_no_info
ri_seq["→"]
fb -->|C| ri_seq
check_ri(["RM in R or I?"])
ri_seq --> check_ri
eval_cred["evaluate credibility"]
ri_seq --> eval_cred
eval_valid["evaluate validity"]
ri_seq --> eval_valid
ri_to_v["RM → V<br/>(emit RV)"]
ri_seq --> ri_to_v
ri_to_i["RM → I<br/>(emit RI)"]
fb -->|D| ri_to_i
(B) The report can already have the Invalid designation. In that case, the necessary actions depend on whether the behavior needs more information. If the information in the report is sufficient, no more action is necessary, and the entire behavior returns Success.
However, a previous validation pass can leave an indicator that more information is necessary. In that case, execution goes to the sequence that runs the gather info task. If the task finds nothing new, the entire branch returns Success, and the report stays Invalid. If the task does find new information, the branch fails, and execution goes to the main validation sequence.
(C) The main validation sequence runs when none of the conditions above are true. Two conditions trigger the validation sequence. In the first, the report is in Received and no one has evaluated its validity. In the second, an earlier evaluation found the report Invalid, and new information is now available that calls for a new evaluation.
The validation process shown here has two main steps: a credibility check and then a validity check. Our introduction of the Received (R) state describes these steps.
As a reminder, a report can be in one of three categories:
- (a) neither credible nor valid
- (b) credible but invalid
- (c) both credible and valid
If the report passes both the credibility check and the validity check, the report is Valid. The tree then moves the report with \(q^{rm} \xrightarrow{v} V\) and emits an \(RV\) message.
(D) If either check fails, the validation sequence fails. The report is then Invalid and moves to (or stays in) \(q^{rm} \in I\). In that case, the Participant sends an \(RI\) message when applicable, to tell other Participants about the related state change.