Why Phronesis is already in v3 (and still not a store parade)

If you glance at Phronesis and see v3 before you’ve seen a friendly install button everywhere, your eyebrows are doing a reasonable job.

So let me say the quiet part with receipts: the version number is not a marketing costume. It is also not a promise that strangers can double-click a finished product tomorrow. Those two facts can both be true. There are reasons. 🙂

(Status snapshot lives in Phronesis — where it stands / on the product page. This note is the process half.)

What “v2” actually was

V2 was a real personal cockpit: capture, organize, today, focus, plus a pile of power surfaces for people who want them. Feature-rich. Useful on my machine. Docs and packaging honesty sometimes lagged the code, which is a polite way of saying I built faster than I explained.

That is not failure. It is how a lot of serious software starts when the first customer is the author. It is a problem if you then pretend the missing explanation is a launch strategy.

What “v3” means here

V3 was not “add a skin and increment the badge.” It was a product generation: tighten who it’s for, what the default spine is, what we refuse to become, and how it ships.

In house language we called the closed generation V-Now: standalone-first, offline on this device, no author-run cloud for the world, geek self-host only if you like that sort of thing, calm defaults with optional depth. Sync that tells the truth instead of cosplaying Google Docs. Carry what still mattered from v2. Park what didn’t. Drop the wishlists that were really a second product.

When that generation’s scope closed, the number was allowed to mean something. V3.1 was a follow-on wave (habits, scheduling constraints, today-surface polish, the itch class that shows up after you live in the spine). Still the v3 family. Not a random jump to “3.5” for vibes.

So yes: already v3. Because generations earned labels. Not because I wanted the store listing to look seasoned.

Why that is not the same as “out”

“Out” for me means a civilian can install it without a secret handshake, understand what they got, and not discover that I’m secretly their SaaS ops team.

That bar includes:

• Packaging that double-clicks
• Backup/restore you can trust
• Sync stories that match reality (cable/LAN/self-host when shipped, not Dropbox-as-database fanfic)
• Docs that describe the product you actually have
• A hard no on “Trish hosts Phronesis for your relatives”

I will ship waves inside a generation while that public bar is still moving. Internal version language tracks work. Public parade tracks respect for strangers.

If that sounds picky, good. Organon’s filter is instruments, not vibes. A fake 1.0 is vibes with a confetti emoji.

The awkward social version of the question

“If it’s v3, why haven’t I heard of it?”

Because LiveBytes is a studio bench, not a growth funnel. Because I would rather write Notes that tell the truth than invent waitlist theater. Because Synesis and Phronesis are siblings under Organon, and siblings do not have to graduate the same week.

Also because I am one human who also music-directs shows and occasionally stares at the sky. Capacity is a feature of the plan.

What I’ll do instead of apologizing for the number

Keep closing waves with exit criteria. Keep the product page honest. Say when something is installable without cosplay. Refuse to renumber downward to soothe optics.

If you want the short product posture: Phronesis is real, local-first, Organon by LiveBytes, not my hosted cloud. If you want the longer roadmap energy: there will be more Notes when a wave earns a sentence.

Version numbers count generations of intent. “Out” counts whether I would hand it to someone I respect without a disclaimer novel.

Both meters are running. They just aren’t the same clock.

~ Trish