AI applications, data systems, and operating controls.
Explore the problems I took on, what I designed and built, and what changed as a result. These six case studies cover AI applications, business research, publishing, and production automation. The Home Automation study is coming soon.
Training, recovery, and race analysis
Apex Human Hybrid
CoachAI → Apex Human Hybrid
I evolved CoachAI into a training platform with structured workout history, recovery calculations, route analysis, and web and mobile clients. PostgreSQL/PostGIS and FastAPI support coaching decisions and longitudinal performance tracking.
I built a workflow that collects job opportunities, scores fit, and prepares application packets for my review. The September 3, 2026 snapshot contains 40,081 canonical job records. Every application is submitted manually.
I built a privately hosted learning application shaped by my son's feedback, with 3,158 playable missions and four reusable game engines. An offline AI pipeline prepares content, while practice sessions, mastery tracking, and arcade rewards run in the browser.
I built a pipeline that turns Texas permit records into business research and assets ready for review. It preserves source history and human notes in Google Sheets, with 6,100+ normalized records and 98.7% coordinate coverage in the local artifact set.
I operate and modernize a production WordPress Multisite platform with checksum-gated changes, custom OIDC identity, focused MU plugins, and offline AI content validation. Fourteen tests check claims, dates, and affiliate markup before editorial review.
I built maintenance and recovery tools across household Macs, network storage, and container services. The system combines verified file transfers, PostgreSQL backup mirroring, restore checks, and retention rules that preserve older backups until recovery is proven.
A full-stack Home Automation case study is coming soon. It will cover the shared container platform, integrations, automation rules, state, recovery, privacy boundaries, and the reasons the system evolved.
Backed by reviewed code, prompt and knowledge files, tests, dated operating evidence, or active use. Each project page names the verified component and current limits.
Owner-confirmed
Confirmed by Brett without complete component-level repository or operating evidence.
No AI
Conventional software handles this reliability workload.
The labels keep verified evidence, owner-confirmed context, and conventional software with no AI runtime distinct.