INCIDENT REPORT SECAR-004 BL2A 2658-03-17
INCIDENT TYPE: Outer perimeter security breach, by force of arms.
TIMELINE OF EVENTS:
2658-03-10: The Jedi Temple of Coruscant opens contact with the Site Manager of Secure Archive 004, seeking to take custody of the artifacts within.
Contact from organized Force-Sensitives is escalated to the Office of the COO, as per protocol.
2658-03-13: Communications from the Jedi who originally reached out have taken on a belligerent tone, as he believes the COO is an autoresponder droid. Secure Archive 004 is mobilized to alert status 3 upon receipt of [Item 27], a communication that "[he] will be visiting the facility to explain the necessity that the Jedi take custody of [Threshold Corporation's]," quote, "poorly-secured," artifacts, in-person.
2658-03-17, LPDC 1300 (1:2600): Jedi Master K'rin arrives in orbit and is permitted landing, to dissuade use of ship-grade weapons. Nonessential staff are evacuated to on-site bunkers.
2658-03-17, LPDC 1312: K'rin lands. Site Security disarms his ship non-destructively.
2658-03-17, LPDC 1314: The COO and the Site Manager make a joint appearance by holocomm, to attempt once more to explain to K'rin that he is not permitted to access the contents of SECAR-004.
2658-03-17, LPDC 1315: K'rin attempts to utilize psychic coercion upon the Site Manager to cause a type-3B (Nonviolent illicit vault access) or 4U (Nonviolent illicit removal of materials rated below 3 in all risk factors) security breach. The attempt is defeated by standard neurological monitors and a comms shutoff. Site Security arms turrets.
2658-03-17, LPDC 1315.30: Essential staff arm destructive security measures against access control and begin evacuations. The COO chastises K'rin for the attempted psychic coercion and proceeds to attempt to impress upon him the necessity of secure sites that are not located on Coruscant. This backfires; K'rin says he absolutely cannot let Item X-0173 continue to remain in Threshold's custody. Item X-0173 is not stored at SECAR-004.
2658-03-17, LPDC 1318.50: K'rin ceases to engage with communications. Site Security provides warning and engages outer perimeter defenses, firing stun bolts.
2658-03-17, LPDC 1319.27: K'rin damages two turrets while advancing through outer perimeter defenses. Site Security arms mobile vault-interior security measures; breach is not expected at this time.
2658-03-17, LPDC 1319.53: Essential personnel confirm evacuation and successful arming of destructive security measures against access control. K'rin does not attempt to slice the vault controls; he continues to advance on the vault door.
2658-03-17, LPDC 1320.25: K'rin attempts to use his lightsaber to melt through the vault door. Site Security continues to pressure him with stun bolts.
2658-03-17, LPDC 1320.57: Site Security, per RoE, fires two shots from slugthrower turrets, continuing fire with stun bolts. K'rin does not successfully deflect them. The resulting injuries are documented in appendix B.
2658-03-17, LPDC 1321.08: Site Security begins medical treatment of injuries and administers sedation.
2658-03-17, LPDC 1330-1700: Site Security disassembles K'rin's lightsaber, leaving only the kyber in his possession.
2658-03-18, LPDC 0930: K'rin awakens from sedation.
2658-03-18, LPDC 0935: Site Security, present in holocomm, reiterates that further attempted breaches of security will not be tolerated, and informs K'rin of the disposition of his lightsaber's parts (delivered to his ship). K'rin attempts to order Site Security to let him leave, against medical advice. Site Security, while not obliged, agrees that she does not want him here and provides assistive tools.
2658-03-18, LPDC 0950: K'rin's ship departs SECAR-004.
2658-03-18, LPDC 1015: K'rin's ship engages hyperdrive out of the system.
ANALYSIS:
While this event is troubling, it is unlikely that some sort of incident was truly preventable, given the character of the intruder. K'rin, by all accounts, is very, very stubborn once he gets set on doing something. (cf. Galactic Times Weekly ATC2460-11-15, pg. 4C, "Jedi Master with egg on his face, literally, in planetary holiday event.") It is not impossible that he could have been placated, and thus the violence and damages avoided - but that he is returning from SECAR-004 a bit worse for wear may actually help our position.
Nonetheless, it is clear that the Coruscant Temple is at best passingly familiar with our work, which is an item of some concern.
RECOMMENDATIONS:
1) Establish better communications with the Coruscant Temple, building off of existing efforts to secure a Coruscant office. Evaluate messaging once liaison is emplaced.
2) Promote competition, e.g. the Corellian Temple. If the Coruscant Temple is less sure of its utter supremacy in the war of Force opinions, it will not produce as many Jedi who are as high-handed as K'rin.
DISRECOMMENDATIONS:
1) Lobbying to curtail Jedi authority more generally than the specific exemptions Threshold takes advantage of is contraindicated, by order of the CEO. We do not want the Jedi to become a vestigial appendage of the Senate, or its tamed akk-hound; that way lies rampant corruption, which is hostile to our purpose. It is unlikely that we will succeed in preventing that in the long run, but we will not contribute to it.