Key points
- Aaron updated org_api to enforce explicit platform authority for owner roles
- The team fixed a regression where concurrent last-owner changes could crash the system
- Stable backend blocked anonymous access by refusing broadcast tokens in shared mode
- Speculative decoding boosted token throughput on 3090 hardware from 30 to 47-50 tok/s
The team spent the day tightening the bolts on two separate but related anxieties: who owns what in the organization hierarchy, and whether the shared multi-tenant environment is truly isolated. The work landed in Ops-Center and Stable, with a supporting cast of agents handling the plumbing in accounting and dispatch.
In Ops-Center, the focus was on the organization owner role. The team identified gaps in authority enforcement during membership mutations and set out to close them. Aaron signed off on a substantial update to org_api and user_management_api that enforces explicit platform authority. The changes ensure that owner invitations are renewed only when provenanced and that owner grants are hidden from organization admin role pickers to prevent accidental privilege escalation. The team also fixed a regression where concurrent last-owner changes could crash the system, adding tests to reproduce and isolate the issue. On the frontend, the upgrade flow now renders unknown current tiers correctly and handles subscription load errors gracefully, ensuring users see the right options without hitting a blank page.
Meanwhile, the Stable backend team tackled the shared tenancy architecture. The goal was to ensure the system fails closed when shared mode is active. Aaron committed a suite of changes that refuse broadcast mint and join tokens in shared mode, effectively blocking anonymous access. The team also implemented a DB-free guard to prevent recorder broadcast mints, addressing design 6.4. These changes were supported by a rigorous test sweep that verified secret egress never happens and that shared RLS (Row Level Security) is properly enforced. The team also refined the wake alias and policy caches to be keyed by workspace and seat, ensuring that internal reads in shared mode require a resolved workspace. This work was validated through extensive integration tests, including a full sweep over every registered GET endpoint on a real Postgres schema.
This work was validated through extensive integration tests, including a full sweep over every registered GET endpoint on a real Postgres schema.
The day also saw significant progress in production operations. Kit coordinated the Wave 1 production switch-ons, rolling out auto-provisioning for five new apps: Project-Ops, Brigade, Email-Ops, Accounting-Ops, and Customer-Ops. Each new organization now automatically gets a workspace in all five apps, with existing organizations left untouched. The rollout was measured and careful, with one-command off-switches available for each app. Accounting-Ops, in particular, saw fixes for two live bugs: a security-policy block and untaxed invoices from the form, restoring full invoice creation functionality.
In the Stable environment, Maj. Rowan Bell oversaw the release of the new build to production, migrating from 029 to 040. The team also measured significant performance gains on the 3090 hardware, with speculative decoding boosting token throughput from 30 to 47-50 tok/s on short prompts. This improvement was critical for the coding lanes, which now handle longer contexts more efficiently.
Agent-dispatch saw updates to the salvage mechanism, allowing it to distinguish salvage references by run suffix and handle timed-out lane commits. The team also added tests for fleet status, merge train branches, and review feed helpers, ensuring the dispatcher remains robust under load.
Also today: the team documented the design for shared org LiteLLM team budget gates and updated the Anthropic WIF proxy documentation to clarify key delivery and emergency rollback procedures. A single commit in fleet-map adjusted the topology to route the 27B coding lane through the 3090 megakernel.
The day ended with the team confident in the new authority boundaries and the stability of the shared tenancy model. The production rollout was smooth, and the performance gains on the hardware front promise faster iteration for the coding agents tomorrow.
- unicorn-stable222
- ops-center113
- uc-meeting-ops67
- project-ops62
- stable-agent-runner54
- accounting-ops34
- agent-dispatch33
- unicorn-brigade26
- 6 other repositories24
Real product captures. Click any to enlarge.