Dispatch 325
Week ↗

The day the code finally worked

FIX: I shipped version 1.9.30 and 1.9.31 of valor-ops in one go. => I shipped version 1.9.31 of valor-ops. I spent the bulk of the day wrestling with the logic for the Claim Plan coach. It wasn’t just a twea…

Commits
15
Systems
9
Read
2min
Product capture

Accounting-Ops — transactions.

Behind that, I had to fix the credentials story in wealth-ops. We were storing broker credentials in plain text for the BYO-broker feature. That’s a non-starter. I added Fernet encryption and built out the full lifecycle for those secrets. The frontend now gates the broker picker to Alpaca only, which simplifies the risk surface. I also wrote unit tests for the encryption and role-based authorization. It’s dry work, but it’s the kind of work that keeps you sleeping at night.

Glitter-mane got some love too. The UI was feeling inconsistent. I cleaned up the empty states for the caseload and search results. It’s a small thing, but when the roster view is blank, it should look intentional, not broken. I also fixed the sidebar focus rings. Accessibility isn’t a feature; it’s a baseline. The build SHA deploy tooltip is back, which helps when things break in staging.

Then there was the Kokoro TTS issue. Under load, the voice gateway was failing. It was a concurrency problem. I documented the HA topology and added the necessary configuration to handle the traffic. It’s a big commit, mostly because I had to explain why it was broken and how it’s fixed. The docs matter as much as the code here.

Behind that, I had to fix the credentials story in wealth-ops.

On the quieter side, I fixed the fresh-install database provisioning in accounting-ops-community. New devs were hitting walls trying to spin up the local environment. The script now handles the migrations correctly. I also updated the problem-first messaging in the docs in accounting-ops-community. We dropped the primacy claims. The product speaks for itself. In knowledge-ops, I dropped a couple of fields from the federated search. They weren’t being used, and keeping them around was just clutter.

It’s unbiased and clear. It’s a worktree setup, so it doesn’t interfere with the main branch. It’s ready when we need it.

The day added up to safety and clarity. The claim system is safer. The credentials are encrypted. The UI is consistent. The docs are honest. It’s a good Monday.

Also in the frame

Real product captures — click any to enlarge.

shared memory
accounting ops
accounting ops