This walkthrough gives the answer away on purpose. Read it once to learn how the evidence works, then play a fresh case for real.
Clue by clue
CLUE 1
A second Git remote in the CI configuration history
How you surface it: Review pipeline config history and repository reflogs.
Why it points at the insider: Developer tooling is an exfiltration channel. Version history remembers what config forgets.
CLUE 2
Build artifacts far larger than their baseline
How you surface it: Compare artifact sizes across builds.
Why it points at the insider: Volume anomalies find hidden payloads even when the file type looks normal.
CLUE 3
Jump-box VPN session overlapping every push
How you surface it: Pull VPN and jump-box session logs and align them to push times.
Why it points at the insider: Overlapping sessions tie a human to an automated action.
CLUE 4
An anonymous transparency post drafted on a work device
How you surface it: Endpoint forensics with legal approval and full chain of custody.
Why it points at the insider: Ideological insiders leave intent artifacts. Handle them carefully — motive is sensitive, and process matters.