Cycle 3, Leap 2 is officially in the books...

Today’s backstage broadcast was a massive one for those of you following along with the Nitwyt Stater Kit (a.k.a. "Digital One Builders Kit").

If you watch today's session (Day 63 of my build), you saw exactly how we are using the system to iteratively test and refine the actual "experience" of Nitwyt OS before we even touch the heavy code.

We ran through different video engines today to demonstrate how the core logic of the operating system is evolving.

The first run was good, but it still had some of that technical friction and anxiety—using terms like "melting butter" for privacy. The second run? Better... It completely grounded the experience in the physical reality of the Level 1 user.

We stripped out all the machinery and jargon. We moved to the MS-DOS Pivot: the user just drops their Fuel, selects a Recipe Card, triggers The Snap, and watches the Frictionless Overlay do the rest.

It ends with Engineered Silence and the peace of mind that everything is tucked safely inside their local Digital Backpack. Casual magic at a trillion-user scale. 🤯

The "Build In Public" Insight...

For those of you building alongside me—you're doing it the hard way, but you are seeing exactly how the sausage is made.

If you are starting to wonder where "Recipe Cards" come from, the curtain is officially pulled back: they are just glorified, deterministic prompts (LEAP files) that strip away the endless back-and-forth chatbot hallucination.

We are engineering a closed-loop system that uses AI to automate itself.

And for those wondering what it takes to build this?

I am not using a massive team or VC funding. I'm using Gemini Gems, NotebookLM, VS Code, and Firebase Genkit.

You can build this architecture entirely for free.

You don't need expensive tools to build your own version of what your Nitwyt needs to be.

The Next Leap...

If you are still hanging out in the audience trying to grasp what this is...

Stay right there.

Keep watching.

It will continue to get clearer as the software itself gets better at explaining what it does.

Tomorrow, we move into Leap 3.

I've already got parts of the Chromium extension mapped out, and we are going to start laying down the actual code infrastructure that brings this silent, frictionless experience right into your active browser window.

See you in Leap 3!