Story code: ST-001099
Part 2: The Trail in the Logs
Arthur did not immediately look at the projector screen behind him. He kept his eyes on the printed sheet inside the blue project folder, his fingers pressing hard against the paper’s edge. Leo watched a slight twitch develop in Arthur’s jawline, though the department lead’s voice remained controlled when he spoke again.
“The integrity of our documentation is the foundation of our promotional evaluations,” Arthur said, turning the page slowly. “To ensure there is no misunderstanding among the staff, I will outline the exact policy I have submitted to executive leadership this morning. Effective immediately, any employee who claims credit for another’s work, or who modifies a project file in the secure shared folder to obscure the original author’s name, will face immediate termination. Furthermore, Apex Solutions will file a formal breach-of-contract notice, ensuring that individual is blacklisted from any partner firm in the industry.”
The room was completely silent. Leo observed the other analysts exchange brief, uneasy glances. No one typed. The associate with the carafe set it down without making a sound.
“This policy is designed to protect the creators,” Arthur continued, his voice rising slightly as he tapped his signet ring on the folder. “It is designed to ensure that those who do the work receive the credit, and those who try to steal that credit are removed from the organization. Sarah, the Q3 market analysis draft was originally registered under your user profile. Yet, the final version in this folder lists a different primary author. The system shows that the original authorship tag was deleted and replaced.”
Sarah adjusted her wire-rimmed glasses and finally looked up, meeting Arthur’s gaze. “I did not modify the authorship tag, Arthur. I uploaded the final analysis under my profile on Friday at five o’clock. The file was locked for my account over the weekend.”
“The log shows otherwise,” Arthur said, lifting the printed sheet from the folder. “It shows a modification. Under the policy I just laid out, the author of that modification must be terminated today.”
Leo watched Sarah reach into her portfolio and slide a printed document across the table. It was a copy of the network access logs, detailing every IP address and user credential that had accessed the secure shared folder over the weekend.
“I pulled the network security report this morning,” Sarah said, her voice quiet but steady. “Since the folder is hosted on the secure server, every modification is tied to a specific security token. The modification on Sunday night at 11:42 PM didn’t come from my account.”
Arthur’s hand remained poised over the open blue folder. Leo noticed that Arthur did not reach for the paper Sarah had slid across the table. Instead, he stared at the document already in his hand, his eyes scanning the lines of text printed at the bottom of his own sheet.
“The security token used to access the file on Sunday is listed on page three of the report,” Sarah added, looking directly at the folder in Arthur’s hand.
Leo leaned forward, trying to see the screen. The projector now displayed the detailed metadata log, and the user ID associated with the Sunday night deletion was flashing in red.