Projects
This page is organized to help reviewers see direction first, then evidence. The flagship projects below are the most relevant to how I currently think about secure software, auditability, workflow integrity, and defensive configuration.
Flagship Project 01
Security-focused authentication demo showing session-based auth, backend RBAC, CSRF protection, rate limiting, temporary lockout, and audit visibility.
The value of this project is not just login functionality. It shows deliberate control design: how access is enforced on the backend, how common misuse patterns become visible, and how reviewers can inspect the logic quickly.
Start with the README, then inspect auth middleware, authorization rules, and the logging or review surface that exposes sensitive actions.
The gallery uses a clean review-first layout so screenshots stay readable and aligned as more images are added.
Flagship Project 02
Workflow-integrity payment demo built around ledger-based balances, role separation, controlled request states, and reviewer-friendly backend logic.
This project was selected because it makes backend integrity visible. Balances are derived from immutable ledger lines, state changes are constrained, and reviewer-facing logic is easier to follow than a generic CRUD demo.
Start with the README and request lifecycle. Then inspect ledger rules, role separation, and how state changes stay controlled across operators and admins.
The gallery uses a clean review-first layout so screenshots stay readable and aligned as more images are added.
Flagship Project 03
Defensive Ubuntu Server hardening lab documenting baseline review, SSH/UFW/fail2ban/AppArmor decisions, verification steps, and recovery notes.
This project is useful because it treats hardening as a documented decision process. The important signal is not only which controls were added, but also how the baseline was checked, how changes were verified, and how recovery was considered.
Read the project as a defensive operations walkthrough: baseline, change, verification, and operational consequences.
What I Emphasize
Supporting Projects
These projects are intentionally secondary. They help show progression in structure, UI flow, and JavaScript fundamentals, but they are not the center of the portfolio narrative.
