{"slug": "your-rough-draft-is-someone-else-s-missing-piece", "title": "Your rough draft is someone else's missing piece", "summary": "SageOx's Ryan Snodgrass released a new version of the company's session protocol that streams every coding-agent turn to teammates in under a second, replacing the prior model where a session reached the team only after the developer exited Claude and the ox CLI rebuilt and committed it to the Ledger. The design combines \"Twitter time\" and \"GitHub time,\" a framing attributed to Venkatesh Rao's Blygger protocol: each turn becomes a line stripped of secrets and sent through SageOx's API to S3, while the Ledger catches up minutes later with the versioned session folder. The post notes that pasted screenshots and videos now travel with sessions, uploaded to S3 and hash-checked, but warns that secret stripping reads text, not pixels, so users should crop before pasting.", "body_md": "# Your rough draft is someone else's missing piece\n\nIdeas from Blygger and Digital Gardens for 40x teams\n\nThe world knows little how many of the thoughts and theories which have passed through the minds of a scientific investigator have been crushed in silence and secrecy by his own severe criticism and adverse examinations.\n\nMichael Faraday\n\nIn performance-blog-land you do that thinking and researching privately, then shove it out at the final moment. A grand flourish that hides the process.\n\nAfter the [Lisbon offsite](https://sageox.ai/blog/perfectly-content-people), I stood up in front of the team today:\n\nWe see how quickly ideas pile up. Small sparks end up as a group forest fire. The world outside is changing so fast that our group sense-making has to be updated as soon as possible. If any one of us is drunk on the status quo, then the right thing to do is a punch in the gut to get them unblocked.\n\nOn the same day, after this, [Ryan](https://sageox.ai/about/ryan-snodgrass)\nannounced a new version of our session protocol, where our sessions are going\nto be shared in real time.\n\nIn the past, the coding session used to reach the team at the end of a session. You would work with Claude for two hours, and the ox CLI would be writing every turn to a local file. And then at the end of your session, when you exit Claude, ox would rebuild the session and commit it to the Ledger. Two hours of your teammate's thinking, and you see none of it until they are done.\n\n## Twitter time and GitHub time\n\nOne of the recent mental models that I learned was from\n[Venkatesh Rao](https://blygger.org/talks/2026-09-24-blygger/). He was talking\nabout his new protocol called Blygger, and he talks about two kinds of time:\nTwitter time versus GitHub time.\n\nTwitter time is the present moment. You post it, it scrolls away, the snapshot is the point. GitHub time is a sequence of states: versions, history, the changing is the point.\n\nThe git way of sharing works well for [complicated problems](https://sageox.ai/blog/reality-belongs-inside-the-loop) which do well with logical decomposition.\nNot so well with [wicked problems](https://en.wikipedia.org/wiki/Wicked_problem) which do not have one magical solution that is going to come out of\none genius's head: these [complex problems](https://sageox.ai/blog/reality-belongs-inside-the-loop) need co-created solutions which involve the entire group's genius.\nWhat we actually riff with is our colleague's rough work.\n\nThe reason why Ryan and I are obsessed about real time is actually not speed. It is that when your rough draft shows up in front of the other person, the one who is holding the other half of the idea, something magical happens. It catches fire, and it changes from small sparks to a forest fire. And over time, this wonderful resonance allows a team to overcome its B.C. norms of perfectionism.\n\n## Session v2: Twitter time and GitHub time\n\nSo in today's revision, what Ryan did was that he basically makes every turn a line, and that line leaves your laptop in under a second. We of course strip the secrets out of the text, and then these lines go through our API into S3.\n\nAnd then what we do is very similar to Blygger: we combine Twitter time with GitHub time. The Ledger catches up with a sweep, a few minutes later, and publishes the session folder into the Ledger with the normal history and versions. A live path in Twitter time. A versioned record in GitHub time.\n\nAnd one of the really interesting side effects is that suddenly images and videos come along. The screenshots you have been pasting into your sessions get shared with your teammates too. ox uploads them straight to S3, checked by their hash, and the session line points at them. One honest caveat: secret stripping reads text, not pixels, so crop before you paste.\n\nSo now you can watch all of this in both Twitter time and GitHub time, and you don't have to wait hours until your colleague's sessions are published.\n\n## The mirror image: speech over MoQ\n\nThis is the mirror image of the work that I did a couple of months ago, when I\nwrote about how we\n[stream audio and speech with MoQ](https://sageox.ai/blog/one-broadcast-several-jobs). One of the\nvery opinionated choices we made was to choose MoQ and not WebRTC. That\nargument, which I picked up from\n[Luke Curley](https://moq.dev/blog/webrtc-is-the-problem), comes in five parts:\n\n1. **WebRTC is built to drop.** \"WebRTC aggressively drops audio packets to keep\nlatency low.\" Fine for two humans on a call. Wrong when the listener is a\nmodel or an archive you promised never to lose.\n2. **The last packet is the one that matters.** A model cannot answer until it\nhas the whole prompt, so there is time to retransmit.[\"A voice agent should never ask the user to retransmit a prompt.\"](https://moq.dev/blog/webrtc-is-still-the-problem)\n3. **Machines are faster than real time.** They can catch up, and they can talk\nin bursts.\n4. **Every listener gets its own latency budget.** On one SageOx broadcast, the\nlive transcript waits milliseconds, Voice ID waits seconds, and the archiver\nwaits for everything.\n5. **WebRTC scales like a phone call, not like a CDN.**\n\nSo what we're doing is investing deeply in foundational technology, to make sure that our human-to-human and our human-to-AI-teammate conversations are of course becoming part of the SageOx context. But we are also making sure that they become part of the SageOx context in real time.\n\n## Getting over the fear of ridicule\n\nThis stops us from having this idea that there is a need for perfectionism, and it is how the fear of ridicule gets overcome. Because almost everything that we talk about is shared with the team in real time.\n\nAnd then what happens is, when you're talking about a deep problem, especially\nduring the kind of magical hackathon that we had in [Lisbon](https://sageox.ai/blog/perfectly-content-people), you can start\nriffing off each other's ideas, and get a sense of where the other person is at,\neven without them knowing exactly what you were doing.\n\nI think and talk a lot about the incentive systems that would make people get\nover their fear of ridicule. And I realized that I'm walking down a path that\neconomists of science have walked before. Science runs on credit, which goes to\nwhoever publishes first. [Paula Stephan](https://scholarlykitchen.sspnet.org/2013/10/14/stick-to-your-ribs-interview-with-paula-stephan-economics-science-and-doing-better/)\nputs it best: \"the only way to make it yours is to give it away.\" The problem is that you want to have the acknowledgement for what you do. And so\nthe same race that makes scientists publish makes them sit on materials and\nhalf-finished work. Even the money waits for the finished thing. At the [NIH](https://www.nigms.nih.gov/), it\nwas common to say \"no crystal, no grant.\" In structural biology, the hard part is\ngrowing the protein crystal you need before X-ray crystallography can show its\nshape. Reviewers wanted to see the crystal before they funded the work to get it. Hoard in private, release in GitHub\ntime. Faraday's crushed ideas are partly a product of that incentive.\n\nThis is an incentive mechanic that just doesn't work in a world which is moving at 40x speed. And you can see that the communities of people working where the rate of change is the highest, like ML, have gone around the system by working on arXiv and Twitter. The credit is still there. It just runs at Twitter time.\n\n## Designed serendipity, as a matter of course\n\nBy now, we see it clearly. Human attention is the most important resource we have, and right now it is getting whiplashed around and very inefficiently allocated. Every day there is a new model, a new tool, a new way of working, and everybody is trying to keep up on their own.\n\nIf everybody in the team gets to see each other's rough, dirty, small ideas, the entire team gets to make its way through the first, second and third order implications way faster. One person sees the idea, the next person sees what it breaks, the third person sees what it makes possible. Nobody has to do all of that thinking alone in their head.\n\nAll of this only works if there is no fear of ridicule.\n\nAnd I will make an even bolder claim. 40x teams are only possible when ideas are shared internally in Twitter time, instead of the B.C. GitHub time.\n\nYour rough draft is someone else's missing piece. Let them see it.", "url": "https://wpnews.pro/news/your-rough-draft-is-someone-else-s-missing-piece", "canonical_source": "https://sageox.ai/blog/your-rough-draft-is-someone-elses-missing-piece", "published_at": "2026-11-18 00:00:00+00:00", "updated_at": "2026-11-19 17:15:17.245573+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools", "ai-tools"], "entities": ["SageOx", "Ryan Snodgrass", "Venkatesh Rao", "Blygger", "Claude", "ox CLI", "Ledger", "Michael Faraday"], "also_reported_by": [], "takeaway": "SageOx's session protocol v2 emits each agent turn as a line to S3 in under a second, with the versioned Ledger record following a few minutes later, and secret stripping covers text only, so screenshots must be cropped before pasting.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/your-rough-draft-is-someone-else-s-missing-piece", "markdown": "https://wpnews.pro/news/your-rough-draft-is-someone-else-s-missing-piece.md", "text": "https://wpnews.pro/news/your-rough-draft-is-someone-else-s-missing-piece.txt", "jsonld": "https://wpnews.pro/news/your-rough-draft-is-someone-else-s-missing-piece.jsonld"}}