Dispatch 250
Week ↗

Shipping the Listing Suite and Taming Transcription

Friday, 2026-05-08. The big move today was getting the listing-ops suite to version 1.0. I pushed the full operational suite into the repo, and it was a solid 6,418 lines of new code with 106 to remove. It c…

Commits
7
Systems
3
Read
2min
Product capture

Meeting-Ops — live session surface.

Friday, 2026-05-08.

The big move today was getting the listing-ops suite to version 1.0. I pushed the full operational suite into the repo, and it was a solid 6,418 lines of new code with 106 to remove. It covers the whole spread: orders, offers, messages, shipping, and RBAC. I spent the morning tying up the API endpoints and the scheduler so the thing actually runs. It is nice to have a concrete milestone like that. A version 1.0 means the core plumbing is there. I can stop worrying about the foundation and start worrying about the house.

While that was settling, I had to wrestle with the transcription pipeline in uc-meeting-ops. The goal was to let users pick their own transcription options per upload. It sounded simple until I realized the backend needed to track those choices and route them correctly. I added a new database migration for the transcription options. Then I had to wire up the UI so the SessionCreator and Settings pages could actually show and save those preferences.

I pushed the full operational suite into the repo, and it was a solid 6,418 lines of new code with 106 to remove.

The tricky part was the diarization. I had to implement the actual logic for separating speakers. It lives in the services layer now, talking to the providers. I also fixed a routing issue where the STT registry routes to whisper.cpp on :8178 That was a dumb bug, but it kept breaking the speech-to-text flow. I also made sure the registry honors per-org Parakeet selection. If you have a specific provider preference, it should respect it. I added a cloud-build tab to gate those features so they do not show up for everyone until they are ready.

I also did a bit of housekeeping in unicorn-ecosystem. The federation work is moving forward with phase 1 trust modes. I added the schema and the brigade-stable @mention proxy chain. It is mostly schema changes and migration files, but it sets the stage for how these different services will talk to each other. I also updated the ROADMAP with the byok_manager org_-prefix short-circuit and the magicunicorn user_credits column rename. The orchestrator agents are now running on claude-3.5-haiku, and I baked the image in ROADMAP.md It is a small change, but it keeps the dependency chain clean.

Also today: I cleaned up the metadata and made sure the migration scripts for the federation trust modes were applied correctly. The listing-ops API is now ready for the next phase of testing.

It was a day of finishing things. The listing suite is out. The transcription options are wired. The federation schema is in place. I am leaving with a clear path for tomorrow. The hard parts are done. Now we just need to see if it all holds together under load.

Also in the frame

Real product captures — click any to enlarge.

listing ops
listing ops
listing ops