Case State Behavior Trees
Auto-generated reference documentation for the Case State (CS) receive-side behavior trees
in vultron/core/behaviors/status/.
Requirements
The behavioral requirements for these trees are specified in the Requirements Catalog:
- RSH-01 — StatusAdoptionGate (participant status adoption)
- RSH-03 — ThreatTerminationBranchNode (embargo teardown)
- RSH-04 — CaseStatus emission authority and outbound emit invariant
- RSH-09 — Whole accept or reject of a received status
- CSB-17 — CS compound state and history validity
- CSB-18 — Cross-machine state entailments
Add Case Status Tree
Handles receipt of an Add(CaseStatus, target=<case>/statuses) activity, which a participant replica admits from the case's CASE_MANAGER alone (RSH-04-005).
It runs the idempotency check, ephemeral-state guard, history-prefix guard and a whole accept-or-reject check of EM and P/X/A, and writes nothing: the replica takes the status from the ledger.
Constructed from
vultron.core.behaviors.status.add_case_status_tree.add_case_status_tree.
[-] AddCaseStatusToCaseBT
--> ActivityAddressedToReceiverNode
--> ActivityNotSeenBeforeNode
--> CaseOpenToExternalWrites
--> IntakeReceivedActivityNode
--> ActivityIncompleteNode
Add Participant Status Tree
Handles receipt of an Add(ParticipantStatus, target=<participant>/statuses) activity at the CASE_MANAGER, the only receiver it is sent to.
A participant replica refuses it at the path stage, because a replica takes participant status from the case ledger (PCR-03-001, RSH-08-003).
The tree is built on the case the status's own context names.
A door refuses a target participant the receiver holds no record of (HP-08-014), or one recorded in another case than the status names (HP-08-013), before the sender guard runs.
An Add whose activity context names a different case than its status never reaches the tree: the parser refuses it, as it refuses any activity whose parts name different cases (HP-08-015).
Implements the StatusAdoptionGate workflow (ADR-0210, RSH-01): verifies the sender is a participant, appends the raw peer status, then gates adoption through the adoption call-out; an adopted P, X or A ends an active embargo in the same act, because the adoption also authorizes the teardown (ADR-0166).
An adopted P, X or A reaches the case status here, and nowhere else on the received side (RSH-01-003).
Constructed from
vultron.core.behaviors.status.add_participant_status_tree.add_participant_status_tree.
[-] AddParticipantStatusBT
--> ActivityAddressedToReceiverNode
--> ActivityNotSeenBeforeNode
--> CaseOpenToExternalWrites
--> IntakeReceivedActivityNode
--> ActivityIncompleteNode