Report: Droids Evaluation & Investigation

[Tonyux]

Attempting to Access Server 'Mission Reports'...

Accessing...

Accessing...

Conducting Security Check...

Security Clearance Granted...

Access Granted...

Displaying File...

---

---

This report is accessible by any Apprentice and above Sith, alongside Imperials.

Report: Droids Evaluation & Investigation

by Acolyte Agran

I must preface this report by stating my limited experience in droid mechanics and protocol interfacing. I lacked prior technical knowledge and approached Unit TX-22's review with little more than intuition and trial. Assistance from Neophyte Kalkoran proved moderately helpful, offering insight into terminology and interface basics. With time and cautious handling, I managed to extract the following diagnostic readout:

Unit Designation: TX-22
Assigned Post: 1st Central Garrison, Alsolun
Chassis Condition: Pristine
Firmware Status: Out of Date
Driver Status: Out of Date

Primary Operational Protocols:
- Anti-Personnel Engagement & Suppression (Crowd Control)
- Asset Denial
- Authority Relay Function

Secondary Operational Protocols:
- Passive Uplink Listening
- Code Fragment Analysis
- Uplink Node Scanning (Tier 2 Clearance Required)

Handler Designation: "A.L" (Full designation unknown at time of review)
Self-Diagnostics: Returned Unknown Error – Memory Core

Personal Considerations:
TX-22 appears combat-ready in terms of chassis condition, but both firmware and internal drivers are outdated, suggesting significant neglect or intentional stalling of maintenance. The Memory Core’s unknown error may indicate tampering, data suppression, or long-term corruption. Clearance level restrictions prevented deeper probing into uplink functions. Further technical support is recommended before reactivation under combat protocols.

---

Unit Designation: DA-SO
Assigned Post: Spaceport, Section 4D
Chassis Condition: Near Mint (Scratched)
Firmware Status: Up to Date
Driver Status: Up to Date

Primary Operational Protocols:
- Standard Guard
- Patrol Protocol

Handler Designation: Engineer Ulan (Last Logged)

Personal Considerations:
DA-SO appears combat-ready in terms of chassis condition, all drivers up to date and no error revealed through both external and internal diagnostics. No technical support is recommended before reactivation and re-deployement.

---

As tasked by Neophyte Kalkoran, I investigated possible tampering of Droid Unit TX-22.

The following summarizes the findings:

I requested from Private Bennu, attendee to Superior Supervisor Harkan, a full list of currently stationed Droid Handlers within the garrison. The names provided were:

• Jea Mann (Imperial Transfer)
  
• Zed (Imperial Transfer)
  
• Lo Ki (Native)
  
• Benevene (Native)
  
• Bo Bo (Native)
  
• Jeaa (Native)
  
• Munjuk (Native)
  

The initials "A.L.", tied to the last access to TX-22, did not correspond to any of the listed personnel.

Further inquiry confirmed the presence of Engineer Ulan, a recent transfer assigned to an outpost. A broader review of the engineering roster revealed no individuals with matching initials.

When I asked whether any other personnel might be authorized to access droids, Private Bennu confirmed that only assigned Droid Handlers and Civil Engineers are permitted such access. No exceptions were noted.

TX-22 is currently held in storage, scheduled for a check by Neophyte Kalkoran.

Personal Considerations: 
The initials “A.L.” may not belong to a real person but could be a fabricated marker or codename - possibly even a veiled reference to “Alsolun” itself. If so, this may imply intentional obfuscation by an infiltrator or insider, potentially exploiting procedural blind spots.

---

File Read Finished...
Shutting Down File...
Returning to Main Menu...
Main Menu Access Granted...