Monthly chapter08
August 2026

August 2026: The Month of Honest Ledgers

August started with a heavy lift in `valor-ops`. I shipped version 1.9.31, but the real story was the logic for the Claim Plan coach. That was not a tweak. It was a wave of change, over 5,000 lines across th…

628commits39systems6min read
Product capture

Accounting-Ops: transactions.

August started with a heavy lift in valor-ops. I shipped version 1.9.31, but the real story was the logic for the Claim Plan coach. That was not a tweak. It was a wave of change, over 5,000 lines across the backend and frontend. The goal was safety. I wanted the system to stop guessing and start verifying. The new code checks decision statuses before moving forward and handles outstanding claims, interviews, duplicates, and case briefs. It introduces bear and reclaim features. It is slower to write, but it is safer to run.

Behind that, I tackled the credentials story in wealth-ops. We had been storing broker credentials in plain text for the BYO-broker feature. That was 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 wrote unit tests for the encryption and role-based authorization. It is dry work, but it is the kind of work that keeps you sleeping at night.

The month’s first half was defined by cleaning up the lies. I scrubbed the old code out of the site, removing three duplicate files that were unreachable and confusing anyone who looked for them. That was 697 lines of dead weight gone. The Player page was telling a lie. It framed the feature grid as if everything was already shipped. The grid is a plan. It shows where we are going, not just where we have been. I fixed the framing to make that clear. Clarity is kindness. I also fixed the copy. The track counts were false. The download links for the DMG files were dead. It is embarrassing to have broken links on your own site. I fixed the counts and revived two fallback URLs. I corrected a pricing statement. Room Correction Pro is free. It should be free. It is free like every other app feature. The copy now reflects that.

We had been storing broker credentials in plain text for the BYO-broker feature.

Then came the visibility crisis. I looked at the social share cards for the various ops sites and realized most of them were non-existent. It does not show up in error logs but kills credibility the second someone drops a link in a Slack channel. I spent the first half of the day playing whack-a-mole with Open Graph tags. Most subdomains like harmony, email, customer, stable, and brigade had zero OG tags. I added the social share cards to each of those repos. For ops-center, the OG image was absolute but the card itself was not sized correctly. I fixed the real 1200x630 card so the preview looks clean. Accounting-ops was actually broken. The og:image was pointing to http://localhost:3000. I repaired the dead social card and cleaned up the references.

August shifted gears in Week 32. The week started with noise and ended with a bill. That is a good progression. It means the system is growing up, or at least growing up enough to charge for the privilege of using it. I spent 158 commits across 22 repos this week, with unicorn-stable and ops-center taking the bulk of the load. The work was not about shiny new features. It was about making sure the things I built last month actually work, cost the right amount, and do not let random dev tokens break the security model.

I found a hole in the authentication logic that let dev tokens slip past the front door. It was in src/ad_ops/auth/principal.py. The code was too permissive, checking the wrong thing at the wrong time. I tightened the validation so dev tokens only work in dev mode and never in production or staging. I wrote a regression test in tests/test_auth_bypass_regression.py to make sure this never happens again. The diff was small, but the security gain is massive. One bug, one fix, one test. The backdoor is shut.

By the end of Week 32, I made the Suite sellable end to end. I rewrote the checkout flow so it actually processed a transaction. I set the price tags for Meeting-Ops at $22 a month and $216 a year, updating the database, the marketplace landing pages, and the individual product pages. For uc-meeting-ops, I wired up the Stripe client to accept annual payments without throwing a fit. I also fixed the federation seam probes in customer-ops so they address real workspaces. The day added up to a simpler reality. We have a product. It has a price. It can be bought. The plumbing works.

Week 33 was about tightening the belt. The headline for the week is trust. I built a broadcast feed for streaming, but I also spent equal energy making sure the accounting pipeline did not hallucinate confirmations and that email routing did not leak secrets. I spent the day fixing the accounting-ops repo, specifically how posting confirmations were handled. The old logic relied on an agent’s user_confirmed argument. That was a design flaw. If an agent got confused or the UI state drifted, we could end up with postings that were not actually confirmed by a human. I rewrote the logic to derive the confirmation server-side. The backend now makes the final call based on hard facts. I touched five files, adding 285 lines and removing 10. The bulk of that was in app/journal/posting.py and the new test suite.

I also gated the MCP server-side tool allow-list. You can’t have agents running wild. I added the per-agent policy across accounting-ops, accounting-ops-community, and accounting-ops-oss. If an agent is not allowed the tool, it does not get the tool. In email-ops, I closed a mailbox leak where one workspace could see another’s mail. That is a hard no. I also fixed the unsubscribe flow to require human approval. Unicorn-stable got a lot of attention too. The ongoing-call awareness is finally everywhere. Sidebar badges, in-room banners, and call-started toasts are all there now. The stale-room events can no longer wedge the call state. I also wired up the face-style preference. You can now pick your avatar look, and it sticks. The group-call heal is working, so if someone drops, the room stays intact.

Week 34 started with a dose of humility. I went into email-ops to scrub the landing page because the hero metrics were lying. It is better to be honest about what the product does than to hide behind outdated numbers. I dropped the claims from the HTML and CSS, adding three lines and deleting twelve. The page looks a little less flashy but a lot more truthful.

Then came the real work in unicorn-stable. We have a video calling interface that has been a headache when it comes to layout. Users want to focus on one person or one tile, and the previous implementation was finicky. It did not always play nice with every call surface. I decided to tackle this by implementing a per-tile full screen mode. This means that no matter which surface you are on, you can click a tile and have it go full screen immediately. It is a simple concept but it required touching quite a lot of code to make it stick. I rewrote the logic in the guest video stage and the room stage view. I also updated the voice and video bar components so they react properly when a tile is expanded. The core of the change lives in a new hook

Also in the frame

Real product captures. Click any to enlarge.

customer ops
email ops
email ops
Weeks in this month

The month, week by week.

Step down a level without losing the month's arc.

  1. The Week of Silence and Horns340 commits
  2. The Week the Plumbing Held158 commits
  3. Accounting for truth, broadcast for clarity181 commits
  4. The Week the Ledger Learned to Speak24 commits