Reliability · Post-Incident Reviews
In the spirit of ground truth, we publish every throw that did not go to plan. Each is reviewed, resolved, and folded into policy. Cumulative regret across all incidents below: zero.
A payload cleared as "yeetable" was, in fact, a carton of eggs. Ground contact was achieved catastrophically. Root cause: insufficient shell-integrity modeling. Remediation: eggs added to the registry (DNY-0023); Arc Studio now flags "aspirational structural integrity." Regret logged, then formally set back to zero.
We do not discuss the aquarium. What we can say: it led directly to the formalization of the Do-Not-Yeet registry in 2021, and nothing like it has happened since, because of the registry, which is why we have the registry. There was a goldfish. It is fine. The matter is closed.
An operator yeeted a boomerang. It came back. Ground contact was achieved on the second pass but the SLA clock had already stopped, creating a reconciliation dispute. Boomerangs are now Under Review (DNY-0037). No injuries; mild philosophical distress.
The policy engine blocked a launch 40ms before release when the payload was identified as DNY-0002. This is the system working as designed. We report it because the near-miss is the whole point: the cat remained on the ground it had chosen for itself.
An operator yeeted a stapler belonging to Karen. The stapler was recovered, returned, and Karen was made whole. "Someone else's stapler" is now protected (DNY-0061). We have discussed this.
Yeeterprise™