Monthly chapter06
June 2026

June 2026: The Month the Pipes Held

June started with plumbing and ended with trust. I spent the first week locking down security, building out the identity layer, and getting five services to talk to each other without leaking tokens. By the…

1,862commits33systems5min read
Product capture

Unicorn Commander — monitoring.

June started with plumbing and ended with trust. I spent the first week locking down security, building out the identity layer, and getting five services to talk to each other without leaking tokens. By the time the month wrapped, I had shipped a tax engine that actually files, a brand system that looks like a product, and a federation layer that stops double-debiting credits. It was a heavy month. 1862 commits across 33 repos. The numbers don’t lie, but they don’t tell the whole story either. The story is in the coherence.

The early weeks were about connectivity. I had been building isolated services that occasionally bumped into each other, and June was the month I made them actually integrate. The arc moved from foundational security hardening on Monday to a fully integrated suite by Friday. In contact-ops, I rewrote the Row Level Security for Phase 4 through 4.3, building out isolation modes and user-tenant memberships. It was a foundation layer, not a tweak. I wrote an adversarial test suite to make sure the new isolation actually held up. I also shipped a security hotfix that applied RLS to six previously unprotected tenant-scoped tables.

The real shift happened in accounting-ops. I moved the default persona from a generic CPA to a specialist CFO agent. I wired it into FalkorDB memory, grounding its decisions in actual graph data rather than vague context. I also built a silent specialist delegation orchestrator, allowing the CFO to hand off tasks safely. This was depth-1 delegation, but it worked. I also shipped the AR and Invoicing MVP, which is a full billing engine with APIs and tests, not just a UI wrapper. By Wednesday, the Unicorn Control Plane spine stood up. I containerized uc-registry and uc-entitlements and proved it with smoke tests. Then I scaffolded five more services: Accounting-Ops, Contact-Ops, Customer-Ops, Email-Ops, and Outreach. They all share the same workspace and user atoms now. The fragmentation nightmare that used to define this codebase is over.

I had been building isolated services that occasionally bumped into each other, and June was the month I made them actually integrate.

Mid-month, the noise floor dropped. I was chasing a specific kind of coherence. I wanted the numbers to match, the billing to be honest, and the interface to stop feeling like a placeholder. It started with a fresh surface in brand-ops, 22,449 lines across 136 files. It felt good to have a new product surface in the world. But the real movement happened in meeting-ops and tax-planning-ops. I shipped v3.29.0 through v3.30.0 in a single push. This was the audit remediation wave. I tightened Brigade tenancy to fail-closed, added WebSocket handshake auth, and closed the audit’s last security item. I tore out speaker avatars that didn't belong and replaced Whisper references with the actual Parakeet stack.

The tax work got its real teeth in the third week. Phase 1 of the tax engine finally wired up LiteLLM with qwen3.6-35b-a3b for 1040 extraction. The UI got a complete redesign from scratch. Money displays in dollars, not cents. The tax math and OBBBA constants are correct, and the append-only audit chain with metadata-covered hashes is in place. I spun up a full C-corp engine that handles 1120, QSBS, and AET. Multi-year projections are wired through. The ops-center federation work was a different kind of grind. I spent a lot of time making sure the billing side of federated inference didn't double-debit credits. There was a metering reconciliation pass where every call now emits exactly one Lago event, no matter how many hops it takes through the federation layer. Trust modes became runtime-enforceable. The unknown-peer default was made flippable via platform settings.

The final week was about closing the gap between what the software promised and what it actually delivered. I spent the first half of the week scrubbing lies out of the admin panel and building infrastructure to make sure the server images didn’t just work, but worked reliably. I committed 29 changes across three repos, but the real weight was in the 20 commits to ops-center. The big one, the Phase 0+1 dump, brought in 1260 changed files. It was a surgical strike on hygiene. I went through 18 files in the backend and frontend to ensure there are no invented numbers. If the data isn’t there, the UI shows an honest empty state. No more fake stats. No more guessing. Just real data or nothing at all.

I also spent time on the navigation and auth layers. The menu audit was critical. I fixed the route flattening so the personal section actually shows up in the sidebar. I corrected the labels, killed the dead links, and fixed the session UX. It’s small stuff, but it matters. If a user can’t find a page, the feature doesn’t exist. I also fixed the SSO return URL handling. The login page now correctly honors the ?next= parameter, so users don’t get bounced back to the dashboard after logging in. They go where they were supposed to go.

In the other repos, the work was more targeted. In uc-meeting-ops, I released v3.49.0, reconciling the deployed prod integration onto main. That was 53 files. I also wired in the in-app "Upgrade to Pro" checkout path. It’s a simple flow, but it’s real now. You can click the button and go to billing. I also fixed a bug where consumer workspaces were incorrectly reading as system admins. That’s a security win. The final touch came in unicorn-brigade. I fixed the menu audit there too, unifying the auth HTTP client and ensuring the nav reflects reality. I also killed a nasty footgun with the HTML cache. Cloudflare was defaulting to a 4-hour browser TTL for index.html, which meant after a deploy, users would still see the old bundle. I set the Cache-Control to no-cache. Now, when I push code, users see it. Immediately.

June was a month of heavy lifting, quiet fixes, and the kind of stability that doesn’t show up in the changelog until you stop worrying about it breaking. The suite finally feels like one thing instead of five services that happen to share a domain. The graph is live, the imports are reliable, and the search actually works. It was a lot of code, but the movement was real.

The month earned its dry humor because the month earned it. I spent three commits fixing a JWKS endpoint that was returning 403 behind Cloudflare because it was missing a browser User-Agent header. Then the cache middleware was sharing per-user entitlement lists across sessions, so I killed that shared cache with three more commits. By the time I added the org membership role to the response, I could barely keep the commit messages straight. But the work held together. The suite SSO is now fronted by oauth2-proxy, and I fixed the proxy cookie lifespan to match the realm’s SSO session. It is the brand as interface now.

I closed the books on the federation work. Email-ops ran its full Phase D, and the Brigade gateway validator now has a manifest. Agents can actually drive the cockpit through MCP frontend tools. They can push UI commands, navigate the cockpit, and open threads. That is not a metaphor. Center Deep Research shipped a Situation store type and scheduled geo-temporal data monitors. Wealth-ops shipped its Edge/Signals subsystem, which

Also in the frame

Real product captures — click any to enlarge.

accounting ops
project ops
uc cloud
Chapters in this month

The month, week by week.

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

  1. The Week the Suite Finally Spoke286 commits
  2. The week we stopped pretending648 commits
  3. Tenancy, Trust, and the Tuesday Brand Drop480 commits
  4. The week the agents started driving445 commits