The headline was 10 repos with commits and the control plane that holds them all. I stood up the Unicorn Control Plane spine (uc-ops-center) with uc-registry and uc-entitlements, containerized it with docker-compose, and proved it with smoke tests. Then I scaffolded the foundations for five more services: Accounting-Ops got suite-identity convergence and billing hooks, Contact-Ops got auto-provisioned workspaces and on-device AI, Customer-Ops got a full five-phase scaffold with RLS and federation seams, Email-Ops got its NestJS backbone plus a Postmark webhook and agent-inbox, and Outreach got its own tenancy layer with engagement capture. All of them share the same workspace/user atoms now, which means the fragmentation nightmare that used to define this codebase is over.
Meeting-Ops got the most human-facing polish: a record-first landing page, a prominent Record button, a cleaner live recording screen, Project-Ops auto-push opt-in, watchdog cleanup of stale sessions, weekly email digests, and PostHog analytics wired in. The always-on stuff finally behaves without false stop-errors or scroll jank.
Accounting-Ops also carried the heavier infra work: a workspace-to-UC-org resolver with org-scoped metering, a BYOK inference settings GUI and endpoint, gateway-routing modules for future inference tiering, eBay OAuth callback passthrough (consent was dropping tokens, classic), and a cold-start UX overhaul across every first-run surface.
The always-on stuff finally behaves without false stop-errors or scroll jank.
Email-Ops shipped its Phase 2 engagement webhook and agent-inbox REST endpoints on top of the Phase 1 NestJS scaffold. Outreach did the same with a REST campaign management shell and engagement-webhook capture. Contact-Ops got a billing proxy with tier gating and a pricing UI, plus a modernized JWT verifier suite. Customer-Ops' five phases went from zero to a complete tenancy foundation with SSO, MCP skeleton, relationship cockpit, accounting seam, outreach federation, and meeting-ops signals. Project-Ops got a suite-tenancy foundation and six time-tracking frontend surfaces. Unicorn-Brigade added research-monitor agents, tripwire alerts, a video pipeline, and a federated claim set that retires the old org_id. Unicorn-Ecosystem absorbed a stack of architecture docs and a runbook proving the control plane runs turnkey.
That's the summary on paper. In practice it was a day of standing up new services, wiring shared identity across them, and patching the old ones so they don't leak tokens on the way out.
Real product captures — click any to enlarge.