Stack
The portfolio page shows the finished work. This is what runs behind it — the tools, automation, and habits that get it there.
AI & Agents
I build and run MAOS, a framework of autonomous software agents — each one works a task, branches in git, commits its work, and only merges after a review step passes (an automated check, or another agent's sign-off). The agents share MemPalace, a long-term memory system, so they recall prior decisions instead of starting cold each session. Model selection is tiered by task complexity to balance cost against quality, and every change runs through secret scanning (Vault Radar) before it reaches a shared branch.
Automation & CI/CD
Nothing reaches a shared branch without the same gates a human change would go through: linting, type-checking, tests, and secret scanning before anything is pushed out. Recurring work — monitoring, content generation, health checks — runs on scheduled routines instead of being triggered by hand. A self-check layer verifies the system's own documentation matches what's actually running, so "what's built" stays honest rather than aspirational.
Infrastructure
A homelab runs as infrastructure-as-code, with host configuration and cloud-level access control deliberately kept in separate tools so they never get tangled together. Secrets — API keys, tokens, certificates — live in a dedicated secrets manager; none of it ends up in a config file or shell history.
Web & Delivery
The public-facing side of this work — client sites like Glow Latina Cleaning (GLS Cleaners) and this site itself — runs on Next.js and deploys through Vercel, usually wired to Git so a merge is a deploy. Projects like Threat Radar extend the same automation habits into content generation.