One Home Screen for Every System

Birdseye. The full story, and the machine that did it, is told in Build Podcast, Episode 1.
Where it came from
Birdseye started in AE Remote Work OS, the office for one person on one phone. A grid of rooms, every room showing its own number before you tap a thing, and the middle one telling you how today is going. A frosted dock along the bottom. The helper on a tab at the right edge.
On October 10 the order was simple: convert every one of our operating systems, on the phone and on the desktop, to that.
Not a reskin
The same night came the part that mattered. A lot of our systems were not showing the right information, or the right words, for the trade they were built for. So the conversion could not be paint. Every system went through three checks:
The look. Birdseye, the dock, the helper tab.
The numbers. Every room shows the figure that trade actually watches, not a placeholder.
The trade. The room names, the icons, the words and the main button are that business’s own: tap in for a nurse, a new estimate for a contractor, a table for a restaurant.
Where it stands
By the morning of October 11, every one of our operating systems opened on Birdseye. And every new system is born on it.
Scope
Fleet-wide migration of the vertical operating systems from a left-rail navigation and KPI-dashboard shell to Birdseye, the home shell first built for AE Remote Work OS.
Reference build
A tokenized stylesheet (palette, type, skin-machine bridge), a three-by-three room grid with a center status cell, secondary rooms below, a fixed frosted dock with a primary action, a More sheet, and a right-edge assistant drawer. Every room renders one live figure from a single pulse call.
Conversion contract
Input per system: its room map (key, label, route, icon, figure source), its API doors and its marks. Output: the stylesheet linked with the system’s skin, a Birdseye index, the dock with that system’s five actions, and the assistant tab wired to its agent. Desktop is the same page at 760 pixels and up.
Industry-fit audit
Before reskinning, each system is checked for (a) a room map and labels in the trade’s own vocabulary, (b) a real figure source per room rather than a stub, (c) a primary dock action that is the trade’s most frequent act, and (d) the drawn room icons for that system. A converted system that shows the wrong numbers fails.