Case study
Case study: Helix Library

A personal localhost OPAC I actually run: files, catalog, Ask, Acquire. Not a demo.
What I did
Built and keep Helix Library locally — files, catalog, Ask, Acquire, knowledge graph, collections, and Night Moth arcade. README and fixture UI gallery are on the public repo.
What changed
I use it as my local library and arcade.
What I refused to overbuild
I refused the usual “product” layer. No social feed. No forced cloud sync. No marketplace. Helix Library stays a localhost OPAC I actually run — files, catalog, Ask, Acquire, plus the arcade — without turning my shelf into someone else’s network.
Stack
Next.js 15 (App Router), React 19, TypeScript, SQLite (better-sqlite3), Drizzle, Tailwind v4, sharp, AI SDK (optional xAI).
Snippet
const db = drizzle(sqlite) // local file — no hosted OPAC
// Ask/Acquire stay on one machineProof
- https://github.com/rb-thompson/helix-library
- Localhost only — no hosted demo URL
- Fixture UI gallery below (and on the public README)
// visual.proof · fixtures only
UI gallery
Sample shots from the public README gallery — fixture data, not production vaults.





More Posts
Case study: Shipping rbthompson.dev
Next.js 15 + Payload so I can ship copy without a deploy for every edit. Year and project counts stay off this page — not because they’re false, because they’re not verifiable here.
Case study: Helix Hustle
Phone PWA for money and career. Describe-only: income, bills, expenses, job pipeline — and money math that never hits a model.
Chasing AI Ops on Solana: My AgenC Adventure
Field note from an on-chain agent experiment — keep it a ridge note, not a hire claim.


