Incident
Start Log [T.10.16.52.1]
Log [1.04 Y.2188]
I have had success in recovering past log issues, thankfully. This is good news, not only am I able to recover the majority of the log within the archive, but the corruption has left little damage to the system itself. The only drawback is that decrypting corrupted logs are taking much longer than I thought it would and most of my logs are still in the darkness. On top of that, I need to have my Armor Guard connected to the unit itself if I am able to have any success in recovering the logs. This causes a problem, and it seems I may only download during my hibernation hours.
How I was able to find a solution to the corruption in the first place was almost a fluke of itself. But I have more important matters to explain, so I may go further in detail about how I was able to recover the system at a later date. 1: For documentation.
1: For documentation. I’m still in search of my “John” log.
Let me explain. Here on Choir we use the word incident to describe a personnel malfunction, i.e. death of an intelligent being. Whether that malfunction may be an accident or intention, we still refer to it as incident, never a death, murder, rape, suicide, or anything of the like.
When said incident is an accident or intention, the following must be done.
a. An analysis on the situation that followed before and after the incident took place.
b. An autopsy on said “John[s]” or “Jane[s]”. Even when empirical observation is relevant when said John[s] or Jane[s] became the incident.
c. Documentation on all following personnel whom witnessed the/an incident. Documentation pertaining information received and about the witness[es].
d. All documentation about the incident and John[s] or Jane[s] sent to company headquarters.
e. Remains sent to closest alliance owned planetary control.
From the amount of time I have been on this rock, there has only been one incident. The incident was soon ruled an accident. I don’t believe that official statement.
The Wolf
End Log [T.10.20.22.10]
