The Great Docs Expansion — and Something Enormous Is Coming

Two things today. The small one first, because it’s already done: the docs library just had its biggest expansion ever — five new deep guides in a single drop, taking the library from seventeen guides to twenty-two. The second one is not small, and we’re going to make you read the whole post before we say it properly. Hint: it’s already in the picture below.

The biggest docs drop yet

The documentation has been the quiet backbone of this studio since the support sites went up — the place where “privacy-first” has to stop being a slogan and start being a spec. It deserved more than incremental patching, so it got a wall of new material instead. Five new guides, written to the same standard as the original seventeen, all live right now in the docs hub:

• Prompting & task briefs — how to brief the agent so it works instead of guesses: the four-part brief pattern, weak briefs made strong, and why constraints become acceptance checks.
• Artifacts, files & deliverables — the full path a deliverable travels: download cards, the artifact panel, uploads, and where every file actually lives on your machine.
• Recipes — eight real-world workflows — end-to-end sequences you can steal: pre-ship review rooms, Studios websites, print-ready documents, research briefs, data cleanup, image work and the weekly ops sweep.
• The Sonderr glossary — every term the product uses, defined honestly, including the ones that sound grander than they are.
• Your data, your machine — the local-first contract as a spec: the complete data map, what crosses the wire and what never does, backup, migration, and how to wipe everything.

That brings the library to 22 guides alongside the 65-skill playbook library in the runtime. No numbers were rounded up to make that sound bigger — the library just got one third deeper in a day, and the guides it got are the ones people kept asking for in support emails.

Now read this part slowly

Here’s the other thing. For a while now, one question has sat at the top of the whiteboard: what should a Sonderr update actually be? Right now the cadence is whatever one schedule can carry — fast when it can be, silent when it can’t, honest either way. We are now seriously weighing a different model: four updates per year. Every quarter. But giant. No trickles, no patch-noise — each release a genuine event, loaded and finished, instead of twelve small ones that never quite feel like anything. That’s the version of Sonderr we think you deserve, and it’s the version we’re building toward.

Which leads to the sharpest sentence in this post: the current version could go EOL within a week. Not a scare tactic, not a marketing beat — a real option on the table as of the day this was written. If the quarterly-giant model is the future, the current update line may simply end — end-of-life, clean cut, no zombie branch — and what comes next gets built without looking over its shoulder at a legacy line. We may or may not do it. We are genuinely undecided. But we’d rather you hear “this could end within a week” from us, plainly, than pretend the current shape is permanent when it isn’t.

And here’s the part where you come in. The expansion post asked for hands — a co-owner, staff, people who commit and actually carry workstreams. The reason that post mattered more than a hiring page usually does is simple: the more people who commit, the harder Sonderr comes back. Not incrementally harder. 5x harder — that is the honest size of the gap between what one schedule can ship and what a committed crew can. The quarterly-giant model, the EOL decision, and what’s after that all scale on the same variable: people.

And beyond that — there’s something bigger being planned for when those people arrive. We can’t talk about it yet. What we can say, and will: something ginormous is coming this year. 😉

What we can say, and what we can’t

This studio has a house rule about unreleased work: no clues. It’s why the teaser above can name shapes but not names. To make the boundary explicit instead of coy:

• We can say the update model is being weighed: four updates a year, every quarter, giant ones.
• We can say the current version’s update line could go EOL within a week — undecided, genuinely.
• We can say Sonderr comes back 5x harder when people commit, and the doors are open: co-ownership, staff, builders.
• We can say something bigger is planned, and something ginormous is coming this year.
• We can’t say what it is, what it’s called, when exactly it lands, or what it replaces. If we told you more, we’d be breaking our own rule — and the whole point of the rule is that when we finally do talk, everything we say is already true.

That’s the whole map. Everything else is a rumor, even if you read it here first in a dream.

How to be in the room when it happens

If any of this made your pulse move, there are exactly three doors. One: the co-ownership seat is still open — email dxn1.0day@gmail.com, subject “Co-Ownership”, with who you are, what you’ve built, and the first thing you’d change. Two: staff and builders — same inbox, subject “Staff”, same honesty about links over adjectives. Three: sponsors — the first sponsorships in studio history are open per the partnerships page, subject “Sponsorship”, same non-negotiables as ever.

And if none of those fit: use the docs. The five new guides are live, the library is the deepest it’s ever been, and every person who actually reads the manual makes the next thing better built. Then watch this feed — the giant version of Sonderr, and the thing after it, both get announced here first.

Something ginormous is coming this year. The docs just got enormous so you’ll be ready when it does. 😉