Productizing one of the ten things — hello from another builder

[nicedreamzapp]

Saw the OSS release this week. Congrats on the 155k lines, and on the framing: "build a product on top of this, and we would be delighted."

I'm one of those builders, coming at it from a different angle. My background is open-source hardware and small-business operations — not law. The free MIT stack I shipped is at github.com/nicedreamzapp/claude-code-local (2,671 stars): an MLX server for Apple Silicon wrapping Gemma 4 31B / Llama 3.3 70B / Qwen 3.5 122B behind an OpenAI-compatible API.

This week I'm opening a paid Mac mini bundle on top of that stack — pre-configured for small firms who'd rather buy hardware than DIY. Three zero-auth agents in the base package: folder watcher (drop a doc, get a structured summary), daily briefing (LaunchAgent reads configured folders nightly), local Q&A (BM25 retrieval CLI). Default-blocked outbound firewall. The wedge is "data verifiably never leaves the machine" for firms whose AI use case requires that as a literal physical truth, not a contract clause.

Not asking permission — your post made it clear I don't need it. But Lavern is the closest thing in the world to what I'm doing, and I wanted you (and the other builders watching this repo) to hear it directly rather than stumble onto it later.

If anyone here is also productizing pieces of Lavern, or wants to compare notes on what works in the legal vertical vs adjacent verticals (small accounting practices, therapy offices, contractor compliance), happy to talk in this thread or wherever makes sense.

Keep building, all.

— Matt Macosko
Arcata, CA
github.com/nicedreamzapp · matt@ineedhemp.com