The Evolution of a “Justice Architect”
My professional history is defined by a single core competency: Systems Logic. Whether securing enterprise networks or deconstructing a 2,000-day pre-trial detention, the methodology remains the same—identify the bug, isolate the variable, and patch the system.
Phase I: Enterprise Infrastructure & Security (The Foundation)
Role: Principal Systems Architect & Founder
Focus: Linux Administration, Network Security, IT Workflow Automation
For over a decade, I operated at the intersection of business and technology. My work focused on “hardening” systems against external threats—a skill set that would later prove vital in the fight for Digital Sovereignty. This era taught me that a “Runtime Error” in a server is no different than a procedural error in a courtroom; both result in systemic failure.
Phase II: The “Runtime Error” (The Audit)
Role: Defendant / Forensic Analyst (Case 18-CR-01114)
Focus: Constitutional Law, Forensic Mitigation, Competency Law
Following a medical crisis in 2018, I was forced to apply my analytical skills to a new operating system: the Kentucky Courts. During 6 years of detention, I treated my case file like a corrupted database, running forensic audits on discovery data that court-appointed counsel had overlooked. This period was not a gap in employment; it was an intensive practicum in Systems Thinking in Justice.
Phase III: The Justice & Recovery Initiative (Current)
Role: Certified Peer Support Specialist / Advocate
Focus: Digital Privacy for Activists, Recovery Dynamics, Policy Reform
Today, I bridge the “Semantic Gap” between the streets and the server room. By combining technical literacy with the lived experience of the Alford Plea, I offer a unique service: helping others navigate the “glitches” of the justice system while securing their digital future.
Leave a Reply