Case studies¶
Selected builds, operating patterns, and lab projects—written around the problem, what was built, the evidence available, the outcome, and the boundary that kept the work accountable.
Public Exposure Watch
Recurring visibility into DNS, reverse-proxy, and container-port changes in a self-hosted environment.
Evidence: Public-safe review logic and a documented baseline-comparison pattern.
Read the case studyHome Lab Operations
A practical environment for containers, networks, monitoring, troubleshooting, and rebuild planning.
Evidence: A generalized topology and documented operating practices; live inventories stay private.
Read the case studyn8n + Discord Automation
Scheduled operational checks that normalize source data and deliver readable reports.
Evidence: A code-only logic view and documented workflow structure; live operations stay private.
Read the case studyCompliance LLM
A local AI-assisted workflow for organizing control information and review material while retaining human judgment.
Read the case studyIncident Response Tracker
A lightweight incident workflow focused on the right record, clear handoffs, and useful response documentation.
Read the case studySecurity Onion Lab
A hands-on environment for log visibility, alert review, and detection practice.
Read the case studyDomain Research Tools
Structured comparison tools that reduce decision fatigue in research-heavy work.
Read the case studyForza Tuning Calculator
A user-facing calculator that turns messy tuning inputs into a clear, repeatable workflow.
Read the case studyAudio Separation Lab
A local workflow for practical audio processing without depending only on third-party services.
Read the case studyPersonal Wiki Build
A durable public home for project evidence, technical communication, and portfolio development.
Read the case studyCase-study standard¶
Every refreshed case study uses the same accountable structure:
- Problem — the operational need, without inflated stakes.
- Built — the system, workflow, or experiment that exists.
- Evidence — public-safe proof that supports the description.
- Outcome — the result without invented metrics.
- Boundaries — what stayed private, manual, or human-approved.