Dispatch 237
Week ↗

The Fixer, the brigade, and the branding shuffle

Saturday, April 25, 2026. Twenty-eight commits across seven repositories. It was a day of stitching together the nervous system of the crisis management suite while keeping the lights on for the rest of the…

Commits
28
Systems
7
Read
2min
Product capture

Ops-Center — admin command dashboard.

Saturday, April 25, 2026. Twenty-eight commits across seven repositories. It was a day of stitching together the nervous system of the crisis management suite while keeping the lights on for the rest of the empire.

The headline was The Fixer. I spent the bulk of the morning wiring the "Auto chat mode" in crisis-management-ops to route directly to The Fixer agent. The goal was simple: let the system handle the heavy lifting when a user drops a case code. I updated the MCP server to accept those codes and exposed the new orchestrator entry point in the drafts routes. The frontend Drafts page now talks to six Brigade drafter agents, including the analytical heavy hitters like the damages calculator and deposition prep tools. I even added a PDF download button to the drafts page because generating a clean report should be one click, not a terminal session.

The underlying infrastructure had to catch up. I had to make sure the brigade-auth service was sending the right apps:[crisis-ops] tags when provisioning user keys. Without that, The Fixer wouldn't know it was allowed to touch the case data. I also wired up LOCAL_LLM_URL and the OPENROUTER_API_KEY in uc-cloud so the cloud routing actually works when the local model is offline. It is the kind of plumbing that never makes the changelog but keeps the lights on.

I spent the bulk of the morning wiring the "Auto chat mode" in crisis-management-ops to route directly to The Fixer agent.

Meanwhile, unicorn-brigade went through a rapid release cycle. I pushed from v1.7.0 to v1.7.0. It felt like a sprint, but it was just cleanup. We implemented the apps-based access model, fixed the delegation timeout bug that was keeping Keycloak in a loop, and hardened the "think" strip for the LLMs. I also added a billing bypass for trusted service-delegated keys, which means the automated agents can work without hitting the consumer rate limits. The Crisis MCP tools are now in the main TOOL_REGISTRY, so any agent can call them.

On the ops side, I had to deal with the branding fatigue. I deployed three different site themes in one afternoon. ops.genesisflowlabs.com got the Genesis Flow Labs branding with a giraffe logo. ops.centerdeep.online got a new sky theme. magicunicorn.dev got an "underground" theme for special projects. It is tedious work, tweaking CSS variables and swapping logos, but the per-site branding config is finally stable. I also documented the federated SSO model in ops-center so I don't have to remember how the branches work next month.

The rest of the day was noise. I bumped ops-center to v3.5.2 to drop some broken UI plumbing. I audited unicorn-squad for security and license compliance, fixing a few P1 UX issues and the macOS default settings. I added a "Learn More" link to the Meeting Minutes app card on magicunicorn.tech, which is barely a commit but makes the app feel less like a ghost. I also spun up the initial brigade-pdf microservice, a standalone container that generates those PDFs we need for the drafts page.

It was a day of connecting dots. The Fixer is no longer an idea; it is a route in the backend. The billing bypass is live. The branding is consistent. The code is shipping.

Also in the frame

Real product captures — click any to enlarge.

uc cloud
ops center
brigade