Building in the open: ParadoxOS, PokerStick, and what comes next

A useful record of the work

A product page gives you the overview. It rarely explains why a feature exists, what made it difficult to build, or what changed along the way. We want to make room for those details here.

We’re aiming for weekly notes about our own projects and the practical lessons that come from building websites and software. Some weeks that may be a release. Other weeks it may be a small improvement, a decision we’re still working through, or something that didn’t work. We’ll distinguish what is available from what is planned.

ParadoxOS: keeping business work connected

Running a company means moving between customers, projects, schedules, invoices, and the people doing the work. When those pieces live in separate places, keeping track of what happens next becomes work of its own.

ParadoxOS is our business operations project, bringing those workflows into one workspace. It is in early access, and we’re preparing onboarding. Version 0.10 is upcoming; this post is not a release announcement.

The question we want to keep asking is whether a connected workflow makes the next step clearer. In future notes, we’ll walk through specific changes and explain what we have verified before calling them ready.

PokerStick: a place to practice decisions

Poker practice needs room to make a decision, look back at it, and try again. PokerStick is our poker trainer and career simulator, currently in free beta. It uses virtual chips and offers decision reviews; it is for adults 18 and over, with no real-money gaming.

The public demo can be explored without signing up. Its reviews use heuristic models and equity estimates. They are practice feedback, not a claim of GTO-optimal play or a guarantee of results.

That distinction matters when building training software: an explanation should help someone think through a decision, and be clear about the limits of the model behind it.

What comes next

Instructor AI, our learning project, is also in development. We’ll share more when there is something concrete to show.

For the next devlog, we plan to take one small piece of work and follow it from the original problem through the decision, the checks, and the remaining rough edges. That is the kind of record we want this to become: useful context for people trying our projects, and honest notes for other people building software.