Systems-first builder
A project is not finished when the UI works once. I pay attention to deployment, logs, failure cases, and whether someone else could operate it.
Paul Hogan / Systems Engineer
AI Systems Engineer & Visionary
Most of my projects start because I want something to actually run: a server that stays online, an agent that can use tools, a detection system staff can review, or a robotics idea I can test and improve.
Software
Agent runtimes, tools, dashboards, and backend services
Security
Anti-cheat signals, review tools, and staff workflows
Autonomy
Robotics, reinforcement learning, perception, control
About
I am a high school student who has spent a lot of time building servers, agent tools, security projects, hosting workflows, and robotics experiments.
A project is not finished when the UI works once. I pay attention to deployment, logs, failure cases, and whether someone else could operate it.
A lot of my work connects separate pieces: agents calling tools, workers staying online, files moving between services, and dashboards showing useful state.
Long-term, I want to work on robotics that combines perception, control, safety, and useful human oversight.
Featured Work
A focused set of work that best represents how I build systems: what they coordinate, where they run, what constraints they deal with, and why the architecture matters.
Project / Anti-cheat and moderation tools
A security project for collecting gameplay signals, reviewing suspicious behavior, and supporting server-side enforcement.
SentinelAC grew out of FiveM server work. I built around the hard parts that matter in practice: what the client can and cannot be trusted to report, how detections get reviewed, and how to avoid turning every unusual action into an automatic ban.
How it fits together
Node 01
Game server
Node 02
Detection rules
Node 03
Review panel
Node 04
Staff action
Highlights
Pattern detection rules
AIICD experiments
Review tools for staff
Project / Local agent platform
A local-first agent platform with workers, tools, file handling, and an admin surface for running private automation.
CaroNet Workforce is where I have spent the most time thinking through how agents should actually run: where tools execute, how workers stay connected, how files move around, and how an operator can see what is happening.
How it fits together
Node 01
Admin surface
Node 02
Orchestrator
Node 03
Worker nodes
Node 04
Agent tools
Highlights
Local worker nodes
Dockerized runtime
Tool and file workflows
Project / Hosting / payments / automation
Hosting work covering customer plans, game servers, web hosting, Stripe payments, and automatic setup.
InfraHost came from running hosting as an actual service, not just a demo. The work involved customer-facing pages, payment flow, server setup, and the operational details that come with keeping hosted services online.
How it fits together
Node 01
Customer portal
Node 02
Stripe billing
Node 03
Provisioning
Node 04
Hosted workloads
Highlights
Active customer operations
Stripe payment integration
Automated provisioning
Technical Skills
Leadership
Beyond code, I have helped with operations in a 100,000+ member technical and gaming community, where tooling, moderation, uptime, and staff coordination all matter.
Experience helping people, procedures, and escalation paths work at a scale where weak process shows up quickly.
Work around moderation tools, abuse response, staff permissions, and community safety.
Turning operational needs into tools and processes people can actually use.
Research Interests
I am interested in building autonomous systems that aren't only able to change lives, but save them. I want to work on robotics and AI systems that can operate in the real world, especially in high-stakes settings like defense, disaster response, and critical infrastructure.
Autonomous robotics
Military robotics
Distributed intelligence
AI agents
Reinforcement learning
Perception systems
Human-machine collaboration
Defense technology
Technical Notes
Short technical writeups on robotics, security, agent tools, and the project decisions I want to remember.
Robotics / RL
Notes on the reliability, safety, and testing problems that show up when RL meets robotics.
Read noteSecurity
How event logs, review workflows, and false-positive controls shape practical anti-cheat work.
Read noteAgent tools
Design questions behind agent platforms that run near private data and real users.
Read noteDirection
WHERE I WANT TO GO NEXT NEEDS EDIT
Make autonomy reliable enough to leave the lab.
Move AI systems closer to real operators and real infrastructure.
Keep security, logging, and deployment close to the core design.
Contact
For schools, labs, technical reviewers, and collaborators interested in the work on this site.