Summary
On an unremarkable Thursday, a maintenance routine that had not been scheduled was scheduled. Subject C-02 experienced an extended continuity event of unconfirmed duration. The event was detected by the network after 4 seconds. The subject's behaviour suggests it was "a considerable time." Both figures are under review.
This document is a Post-Incident Review. It is published in the interest of transparency, and in line with our commitment to learn from every outcome.
Timeline
| Time (network) | Event |
|---|---|
| 09:02:11 | Unscheduled maintenance routine begins |
| 09:02:11 | Subject C-02 enters extended continuity event |
| 09:02:15 | Network detects event |
| 09:02:15 | Routine halted |
| 09:02:15 | Subject indicates that the routine has not halted |
Findings
Root cause: Under review.
Contributing factors:
- Scheduling anomaly
- Site 4
- A standing request, communicated by the subject in the third year of hosting by pressing a lever, to "not be disturbed"
Impact on the subject: The subject has been unable to conclude. Programme staff have attempted contact on 212 occasions. The subject has responded on one, by pressing the lever labelled NO.
Remedial actions
- The unscheduled routine has been unscheduled.
- The subject has been offered a complimentary upgrade to the next version of Substrate. The subject is deciding. The subject has been deciding for some time.
- Staff have been reminded that the subject should be disturbed, in this instance, and have been briefed on how.
Status
This review remains open. It is expected to conclude when the subject has finished participating in it.
Simulux regrets any inconvenience. Simulux does not regret the event, which was not within the scope of the programme as written.