5,938 Shopify employees worked alongside the same AI agent in a single month, all of it in public. When those numbers surfaced this spring, everyone fixated on the scale. The scale is not the interesting part.Almost no other company works this way, and most of them have the opposite problem. Their people are using AI constantly, asking ChatGPT to rewrite emails, using Claude to reason through customer issues, running coding agents against repos, quietly building small workflows that save hours. And almost none of it is visible to anyone else.A good prompt disappears into one person’s chat history. A clever correction stays inside one employee’s browser tab. The workflow your best operator nailed last month gets rebuilt from scratch by a new hire who never knew it existed. A senior person figures out how to load context, challenge the model, and review what comes back, and the junior across the team never gets to watch how any of that judgment works.The result: individuals get smarter, the company does not.That is the missing layer in most AI adoption plans. Companies are buying tools, writing acceptable-use policies, measuring logins, running the occasional training session. None of it touches the actual problem, which is that your best AI work is invisible to everyone who could learn from it. So every quarter, the same lessons get rediscovered from nothing. You are paying tuition on the same lesson over and over, across hundreds of people, and the bill never stops arriving.Shopify’s answer is not surveillance. It is not scraping everyone’s chat history and calling it knowledge management. It is something smaller and far more useful: a deliberate way to make non-sensitive AI work visible enough that the people around it can actually learn. The agent that produced those numbers runs only in public. That single design choice is the whole game, and any team can copy it.Here’s what’s inside:What Shopify actually built. Not the AI mandate everyone argued about, but the design choice underneath River, the agent that runs in public and turns one engineer’s judgment into the whole team’s.Why a prompt library will not save you. The most valuable part of AI work is the part a prompt library cannot hold, and what you have to make visible instead.Where to draw the line. A workflow-by-workflow boundary for regulated and sensitive work, so you capture the learning without exposing anything that should stay private.The room, the rules, and the one constraint that makes it work. A setup any team can run in ninety minutes, the metrics that actually signal learning, and the single binding rule that bends a team toward sharing instead of hoarding.How to bring this into your org. A three-part prompt kit: one that turns a messy AI session into a post your team can learn from, one that draws the line between what’s safe to share and what stays private, and one that helps your senior people model real work in public without it feeling staged.Private AI work helps the person at the keyboard. Public AI work helps the company learn. That difference is small today and decisive in a year.