Sub-Creator Workbench
A 32,000+ LOC full-stack workbench, sole-authored in three months and run as a production service since June 2026, because AI-assisted delivery was directed like an implementation, not prompted like a demo.
The tool needed for daily creative and research work did not exist: five distinct workspaces over one local-first corpus, with search behavior no rentable SaaS product offered. The default options were the familiar ones: rent adjacent tools and tolerate the workflow mismatch, or accept that a solo operator without a software engineering title does not ship durable software. The real question was narrower and testable: whether AI-assisted delivery, directed with implementation discipline, can carry a real product past the demo stage.
The move was to hold the accountable-owner seat for the whole system while using AI as the build instrument. Directed the architecture, the scope, and the verification: data model, API surface, search behavior, deployment, and the discipline of keeping 158 commits coherent over three months. The same operating pattern as the vendor sweep, applied to shipping durable software instead of a one-day data operation. The hard part was not any single feature; it was owning every layer at once and living with every design decision afterward, because the author is also the daily user. Ship meant ship: a systemd service on a self-administered VPS, not a localhost demo.
Five workspaces over a Vite + React 19 + TypeScript + Tailwind frontend and an Express + better-sqlite3 backend. A keyword-first hybrid search layer (QMD, book-schema two-pass with boolean operators, hybrid fallback) over a 144-book knowledge corpus that is curated and operated rather than engineered: existing tools do the conversion and embedding (content-to-skill ingestion, qmd embedding), and the owned work is choosing the books, running the ingest, reindex, and embed cycle, and wiring the search layer to consume the result. A vitest suite across 16 test files. Deployed as a Linux systemd service (workbench.service), reverse-proxied by Caddy on a self-administered VPS, in continuous production use since 2026-06-17.
Without it, rented tools that almost fit and a workflow bent around their assumptions. With it, a daily-use production tool with months of continuous uptime, and the product-owner experience that only comes from operating what you built: every design decision surfaces again at usage time, and the author is there to answer for it.
Not a demo: a service with uptime, a test suite, and an author who lives with every design decision.