him (home-inventory-manager)
100% AI-native full-stack side project
100% AI-native full-stack side project — 23 NestJS CQRS domain modules and many pages. Viewed at the page level: the Dashboard · Purchases · History · Appliances pages each call their CQRS domain module, which persists to PostgreSQL. Expiring items flow through the alert module to an FCM push. (Ledger / asset / admin domains omitted.)
Real household-inventory pain points (where did it go · expiration dates · stock levels · re-order alerts), plus a personal motive: prove I can solo every layer — UI planning, frontend, backend, infra.
NestJS + CQRS + TypeORM + PostgreSQL + a frontend + Docker Compose + S3 + Terraform IaC + backup metrics → Grafana. Architecture patterns are lifted directly from work-validated ones. 100% AI-native: AI writes code; the three human nodes are (1) UI planning, (2) code-connection review, and (3) e2e tests. Building self-hosted infra so DB-level user isolation works.
Personal use + 1 beta user (a shared hub), 13+ wiki assets fed back (the 2-stage design process, the 5-layer testing setup, 31 consistency-gap repairs, automated backup metrics, and recipes for both sides of S3 + Terraform). Back-transfer into work happened too — the him UI + current e2e test pattern is being adopted to strengthen the company frontend, and the 4-layer pattern is being applied to the sar-search-and-analyzer backend design.
Only UI-planning review, code-connection review, and e2e tests are human. All actual code is AI-written. I also acknowledge the architecture came from work — but on top of that base, this is the stage that validates the hypothesis that AI-native + frequent review loops can produce something more stable and refined than a solo human could.