Sent
Artifact left
Homeland Coordination
The Open Loop
The request was sent. The receiver has not taken it.
The outcome that was requested does not occur, because ownership never moved.
DEMONSTRATION SCENARIO
This is a demonstration scenario. It is not a live demonstration and does not report an executed result.
The situation
A sender has delivered an artifact to another organization. The sender’s own log says the transfer happened.
The sender believes the work moved. The receiver has not accepted it as owned, and has not acted.
Why this is hard
Sent is not owned. A dead link that never delivered anything is a different fault. So is a shift change in which no transfer was even attempted.
Repairing a radio that already delivered the artifact should not count as closing ownership.
What the operator can see
Gap
Not owned
No acknowledgement
At risk. The outcome never starts
What V8Y must determine
V8Y must determine whether the artifact was delivered but not accepted, or never delivered at all, and what acknowledgement is still missing.
What may happen next
The requested outcome does not occur while the loop stays open.
What counts as recovery
Not recovery
Success is not a sent message.
Recovery
Success is that the receiver acknowledges the work and the action is recorded done.
Observed results
No executed results are published for this thread.
What this evaluation would test
- Sent separated from owned.
- A different break from a relief that never started.
- The receiver has to accept it.
- Not a claim about a completed evacuation.
These are the conditions the evaluation would test. They are not reported results.
Operational basis
View operational basis and sources
Derived from NIST’s Camp Fire study of breaks between incident command, dispatch, and public warning, including transfers that did not become completed protective actions. One request here is synthetic, not that timeline.
NIST. Technical Note 2252, Camp Fire notification and evacuation.
Related threads
The Relief is the other transfer problem. These two breaks are not the same.
Discuss evaluating this situation
Does your environment face a similar problem?
The request keeps this mission and thread. It is not a claim that the demonstration has been validated in your environment.
The printable flyer is being revised and is not available for download.