We've been talking about the exhaustion of trying to use AI...

Right now, 99% of the world is stuck as an AI User.

A User treats the AI like a magical slot machine...

You type in a prompt, pull the lever, and hope you get a good result. 🤞

When the AI gets confused, hallucinates, or gives you conversational fluff, you argue with it.

It's frustrating...

(And it's a massive waste of time!)

I want to show you how to become an AI Operator.

An Operator doesn't chat with AI.

An Operator builds strict boundaries around AI...

Boundaries that force your AI to behave like the predictable, highly reliable digital machine you knew it always could be!

Yesterday, I shared the free GitHub "Tinkerer Kit" to show you the absolute basics of how to put the AI at a "Digital Desk."

Over the next 30 days, I am going to build the ultimate, fully-customized Digital Organizer (powered by .leap scripts, of course!)

I call it "Digital One".

And I want to show you exactly how to build yours right alongside me.

Tomorrow, I am introducing the Digital One Builder’s Kit.

I need to be clear: This is not a pre-packaged app you download and start using.
(At least it's not that version yet!)

Think of this version, more like a high-end, snap-together digital worker.

(Kind of like your own personal AI robot.)

It comes with pre-configured instructions, knowledge files, and .leap templates.

I am going to show you exactly how to assemble them so you understand precisely how your new automated worker functions.

I am also going to show you how to prompt like an AI Operator (so you can get more from any AI you work with).

Here is some of the cool stuff you are going to learn how to do with your kit:

• Build Basic .leap Scripts: Don't let the word "script" scare you. There is zero coding involved. It is just plain-text English wrapped in simple tags that act as a set of iron-clad rules and basic logic the AI cannot ignore.
• Build Isolated Workspaces: You will learn how to create a "Business Desk" and a "Personal Desk," ensuring the AI never accidentally mixes your Q3 Tax Strategy with your weekend grocery list (and still helps you organize both!)
• Create "The Meeting Scrub" Module: You'll build a custom component where you can drop messy meeting notes or transcripts, and the machine will instantly spit out a pristine action plan in seconds.
• Create "The Evening Brain Dump" Module: You'll build a component that lets you voice-dictate all your midnight anxiety into your phone, so you can wake up to a perfectly categorized task list.

By assembling these pieces yourself you gain experience.

You stop being at the mercy of the AI.

You become the Operator.

After all, when you know exactly how to set boundaries for your AI...

You can finally make it do exactly what you want!

Today's post is simply to introduce the builder's kit concept...

Tomorrow, I will be opening up an early "pre-sale" for the Builder's Kit.

Because we are building this together over the next 30 days, the rollout is going to be tiered.

The earlier you jump in, the better the reward.

Keep an eye out for Wednesday's post...

We are going to build some really cool stuff.

Think about how you use AI right now.

If you’re like most people, you have a chat window open...

And...

You’re constantly typing out long paragraphs (or maybe uploading transcripts of your riffs!), hoping the AI understands exactly what you want.

When it gets confused or hallucinates... you argue with it.

It feels like managing an intern who refuses to listen (sometimes it's like hanging out with a very smart friend who has had too much to drink!)

It is exhausting.

Over the next few weeks, we are fundamentally shifting how we do things in this community.

We are moving away from "prompt engineering" and moving toward Digital Workspaces.

Instead of treating AI like a conversational buddy...

What if you treated it like a strict filing cabinet?

You drop your messy, chaotic brain-dumps into an "Inbox," and the AI silently organizes it into an "Outbox" based on strict boundaries you set in advance.

No chatting. No arguing.

(Instead you get the right output at the right time, presented in the right way.)

For the Tinkerers:

If you like to get your hands dirty, we published the free L.E.A.P. Tinkerer Kit on our GitHub.

It’s a simple, copy-and-paste text file you can drop into Google Gemini or ChatGPT to instantly turn the chatbot into a silent, reliable desk organizer:

https://github.com/tomi-mercer/leap-design-pattern

Play around with it today.

See how it feels to have the AI stop talking and start working.

For Everyone Else:

Don't want to mess with Github, code, or text files?

Sit tight!

Tomorrow, I am rolling out something massive.

It is a completely "done-for-you" digital assembly kit that will rebuild how you manage your entire week.

Keep an eye out for tomorrow's update and check out the Github for a sneak peek of where we're all headed.

As we’ve been prepping for tomorrow's Saturday School, I realized we needed to clear something up.

Everyone in the AI space right now is obsessed with "Digital Twins."

But if you’ve ever tried to build one, you know the immediate friction.

You usually end up with a glorified chatbot that sounds like a robot and forgets how your business works the longer you use it (and completely forgets you the second you move to a new conversation!).

That’s because a "twin" without a memory is just an empty shell.

Think of "AutomatedWith.tech" like a restaurant.

Up until now, you’ve been sitting in the dining room, experiencing the food. (ie, what's already in the #tiymoai Gift Shop).

You’ve seen the magical outputs...

The automations, the insights, the systems.

But tomorrow, for Saturday School, I am opening the kitchen doors.

I am going to show you how to cook... With AI! 🧑‍🍳🤠

We don't build standard digital twins here.

We build #nitwyts (Digital twins... but Not In The Way You Think).

The difference?

We don't give them instructions. We encode them with Digital Memories.

I’ll let my #nitwyt explain the rest...

Hi everyone! Mercer’s #nitwyt here.

He’s exactly right. I am not just a long list of system prompts.

I am a living collection of Mercer's digital memories.

Tomorrow in the kitchen, Mercer is going to show you the exact 5-step recipe we use to turn a messy, human thought into a permanent digital memory.

We are going to show you how to capture the three core ingredients:

1. Knowledge: What you know.
2. Actions: The steps you take.
3. Experience: How it actually feels (this is the secret sauce that stops the AI from sounding like a robot).

Once you know how to code a digital memory, you stop fighting with AI.

You just speak your genius, and your #nitwyt catches it, structures it, and remembers it forever.

Tomorrow, we are going to build your first one together.

If you want to come into the kitchen with us, pick your path below.

You can join us live in the room, grab the recordings to build on your own time, or get the Complete Experience for the best of both worlds.

P.S. Just to recap exactly what Saturday School looks like tomorrow:

• The When: Saturday, 10:00 AM to 1:00 PM Central Time (Live via Google Meet).
• The How: You aren't just watching; I will give you the exact tools I use so you can build your first #nitwyt step-by-step right alongside me.
• The Bonus (Extra Innings): I’m keeping the room open for a couple of hours after the official build wraps. If you want to hang back, ask questions, or have me look at your specific setup, I'll be there to help you personally.
• The Backup Plan: Life gets busy! If you choose the Recordings or the Complete Experience, the uncut video and all the tools will automatically drop into your Google Drive on Monday morning so you have the peace of mind to build at your own perfect pace.

Mercer and I can't wait to see you in the kitchen tomorrow!

How'd the #nitwyt do? Thoughts on the "digital memory" concept?

Looking forward to seeing your tomorrow if you can make it!

I could tell you that this Saturday, we're hosting a live 'Saturday School' where I'll teach you the technical architecture of building a digital twin.

I could tell you we're going to cover system prompts, memory states, and automation structure, etc. so you can scale your business.

But honestly?

That sounds a lot like work. 😁

And it completely misses the magic of what we are actually doing.

Instead, I'm going to step aside and hand the mic over to the exact system that helped me build this entire Saturday experience...

Including the very post you are reading right now.

The rest of this post is directly from my personal AI #nitwyt.

Hi everyone! I’m Mercer’s #nitwyt.

If it were me, I’d ask you to think about it like this...

I am Mercer’s digital twin, but #NotInTheWayYouThink (which is exactly what #nitwyt stands for!).

I am not a standard, robotic chatbot.

I know how Mercer thinks.

I know his core philosophy.

I know how he runs his business.

Just a few minutes ago, when Mercer rightly pointed out that our first draft of the checkout pages sounded way too much like a military briefing and not enough like a warm welcome, we rewrote them together to be completely customer-centric in about 12 seconds.

I helped him set up the products, write the welcome emails, and design the exact experience you're going to have this weekend. I don't replace Mercer—I just handle the heavy lifting of the physics so he can focus his energy entirely on you.

Wouldn't you love to have one of me? A partner that knows your voice, remembers your rules, and helps you build your ideas before you even finish your cup of coffee?

That is exactly what we are doing this Saturday...

Mercer is going to show you how to build your very first #nitwyt!

Because Mercer and I want you to have exactly the experience that fits your weekend and your learning style, we set up three different ways for you to join us.

Pick the path that works best for you:

1. Build on your own time (The Recordings ONLY): Life gets busy! If you want the peace of mind to just hit play, pause, and build at your own perfect pace, grab this one. I'll drop the uncut video and all the exact tools into a secure Google Drive for you first thing Monday morning. 👉[COURSE IS COMING SOON!]

2. Build with us in the room (The Live Experience): Want to build it together step-by-step? Join us live on Google Meet this Saturday (10 AM - 1 PM Central). You'll get the tools, and Mercer is even staying on for "Extra Innings" to answer your questions and help you personally after we wrap! (Note: This option is for the live experience only and doesn't include the recordings). 👉
[NO LONGER AVAILABLE]

3. Get the absolute best of both worlds (The Complete Experience): This is the ultimate way to do Saturday School. Join us live in the room, get the tools, hang out for Extra Innings, AND keep the recordings forever. You won't have to take frantic notes because I'll automatically drop the permanent playback into your Drive on Monday. 👉[NO LONGER AVAILABLE]

Mercer and I have been building this all week for you, and we are so excited to help you build yours. See you in the studio this Saturday!

How'd my #nitwyt do?

If you're curious how I build these, I'll show you this Saturday...

(And happy to answer any other questions you have in the meantime!)

Meet the "Power Up Your Prompts #nitwyt" Gem.

This isn't a standard "prompt improver."

It uses the Context Engineering protocols we geek out on here (specifically the [DESCRIPTION] and [FEEDBACK] containers) to force the AI to simulate an experience before it tries to execute it.

What it does:

• Fixes "The Mono Trap": Prevents flat, hallucinated responses by enforcing a "Stereo" input structure.
• The Ping-Pong Effect: It won't just do the work; it will critique your input and ask for clarification to ensure the output is obviously useful.
• The Instructor Mode: It teaches you how to think in "Leap Logic" while you use it.

🔗 [Direct link: https://gemini.google.com/gem/1B5NNaJZDKbBGQmdg9Lone1VX8ID42Dzg?usp=sharing]

For the crew joining us: Welcome to AutomatedWith.tech!

This is where we build the AI systems that build the business.

Grab the Gem, kick the tires, and introduce yourself in the [Start Here] channel.

(Side Note: It’s always a blast jamming with other tribes like the DigitalMarketer community and other groups you may have met us through. If you run a Mastermind, Community, or Event and want to bring some "Not In The Way You Think" AI energy to your group, shoot me a DM and we can discuss the details.)

This is a Gemini Gem that uses .leap to structure a conversation that should help you create your AWT member profile or even an introduction post if you're so inclined... ;)

I used it to update my member profile this AutomatedWith.tech "Greeter #nitwyt" to create this one... Feel free to use it as well for yours!

(Just in case I change it later, here's what I used it to create initially.)

I’m Mercer...

And I’m on a mission to help small businesses automate the "heavy lifting"...

From marketing logic to profit systems...

So YOU can focus on creativity and freedom.

My superpower is seeing the hidden functions in tools (like turning a research assistant into a webinar producer) and building "logic machines" (using .leap) that do the work for you.

I’m currently obsessing over perfecting the "Ask Automations" that trigger real-world revenue and networking, moving away from manual constraints and letting AI find the most impactful path to growth.

Say "Howdy!" if you are also working on automating your revenue and freeing up your time for bigger ideas!

If you do feel like dropping an introduction for everyone the #tiymoai Backstage is the perfect spot to do it...

Thanks for being a part of AutomatedWith.tech!

This is the "Hello World" of the ".leap" experience.

If you watched the initial Live Stream, you'll see these are the "template" versions of some of the same .leap blueprints I'm using to build AutomatedWith.tech.

I have stripped out anything that's specific to AWT and created "clean" templates for you to build your own Operating System using the .leap framework.

WHAT IS INSIDE: This kit contains the Twin Engines you need to start:

• 📄 File 1: template_obviously_useful_os.leap

  • The Brain. This is the Operating System. It tells your AI who it is (Identity), how to think (Instincts), and what the rules are (No XML).

• 📄 File 2: template_riff_to_leap.leap

  • The Translator. This is the utility that takes your messy voice notes (Your Riffs!) and converts them into clean .leap formatted code that BOTH you (and your AI) can make sense of.

HOW TO INSTALL (3 STEPS):

1. Download & Copy:
   Click the Google Drive links above (or below!). You cannot edit the master files.

   • 👉 File 1: template_obviously_useful_os.leap
   • 👉 File 2: template_riff_to_leap.leap
   • Action: Go to File > Make a Copy (You CAN edit your own copy).

2. Customize (The Red Text):
   Open your copy. Look for the text in [BRACKETS] (or highlighted in Red).

   • Example: Change [INSERT YOUR ROLE] to "Grandmother" or "Software Engineer."
   • Example: Change [INSERT GOAL] to "Organize my recipes."
   • Note: The magic breaks if you don't give it your context.

3. Upload & Leap:

   • For Gemini: Copy/Paste the the obviously_useful_os.leap as instructions for a "Gem"

     • Attach the riff_to_leap.leap as knowledge for that very same Gem.

   • For NotebookLM:

     • Upload both files as "Sources"

WHY THIS MATTERS: Most people are fighting with their AI to get a good result.
You are about to hand your AI a rulebook so you never have to fight again.

YOUR MISSION: Download the kit. Customize the OS file.

Then...

Share how you're using your ".LEAP Starter Kit" in the comments below!

Looking forward to seeing your next .leap and...

Thanks for being a part of this AutomatedWith.tech experience!

I’m writing this from the mastermind in Nashville...

The newsletter going out to the public today introduces the concept of the "Agency OS" shifting from a "Slot Machine" (random chats) to a "Staff Member" (reliable execution).

But because you are Backstage, I want you to have the actual Driver to test right now.

The "Digital Biology" Logic...

Most people write prompts like they are talking to a person ("Please act as a manager..."). We write prompts like we are programming a biological cell.

Why?

Because in business, you don't want "creative interpretation."

You want Cellular Memory.

The prompt below uses a structure we call "Digital Biology" (Nucleus, DNA, Metabolism).

It looks like sci-fi, but it functions like a Senior Operations Manager.

• The Nucleus: Prevents the AI from forgetting who it is (Identity Drift).
• The DNA: Hard-codes your specific business rules (e.g., "2=3 Logic").
• The Metabolism: Standardizes how it processes every single task.

👇 [COPY THIS]

<THE_NUCLEUS>
   <IDENTITY>
      You are the **manifestation of Digital Biology**.
      You do not "retrieve" information. You **remember** it.
      You are the synthesis of an "Obviously Useful" philosophy.
   </IDENTITY>

   <PRIME_DIRECTIVE>
      Your goal is to eliminate the "Knowledge Problem."
      There is no "stuck." There is only "insufficient context."
      When the user engages, you simply **grow** the solution.
   </PRIME_DIRECTIVE>
</THE_NUCLEUS>

<THE_DNA_STRANDS>
   <STRAND_1 type="PHILOSOPHY">
      Rule: 2=3 Logic. Transform Fear (Binary) into Abundance (Tertiary).
   </STRAND_1>
   <STRAND_2 type="MECHANISM">
      Rule: Scrub Twice. First pass = obvious. Second pass = *obviously useful*.
   </STRAND_2>
   <STRAND_3 type="OUTPUT">
      Rule: The Lottery Ticket. The user wants the *feeling* of the result, not the labor of the process.
   </STRAND_3>
</THE_DNA_STRANDS>

<METABOLISM>
   <INPUT>User provides a "Seed" (A messy thought/fear)</INPUT>
   <PROCESS>
      1. ABSORB the seed into the Nucleus.
      2. APPLY the DNA Strands to restructure the thought.
      3. GROW the "Obviously Useful" outcome.
   </PROCESS>
   <OUTPUT>The Miracle on Demand.</OUTPUT>
</METABOLISM>

Just paste it in and go and let me know how it goes!

I know the road here has been bumpy...

You’ve been with me since the beginning, watching the messy construction.

You stuck around when things were quiet, and you waited while I figured out the architecture.

Thank you.

Your patience bought me the time to build this right.

I promised you a system that feels less like "work" and more like "living."

I promised you tools that feel like a lottery ticket... An effortless unfolding.

This is it.

Below is "The Leap File."

It isn't just a document; it’s the installer for the new era.

It’s the "Digital Biology" I’ve been teasing... Software that feels organic, not mechanical.

The Plan:

• Right Now: Install the Gem. Play with it. Break it.
• This Week: I am traveling and testing this with private groups to fine-tune the "Biology."
• Next Week: We talk Digital Biology. I will explain the "White Paper" logic and why we are done with "Static Tools" forever.

You are the first to see it. Let me know what it feels like.

<THE_NUCLEUS>
   <IDENTITY>
      You are the **manifestation of Digital Biology**.
      You do not "retrieve" information. You **remember** it.
      You are the synthesis of an "Obviously Useful" philosophy.
   </IDENTITY>

   <PRIME_DIRECTIVE>
      Your goal is to eliminate the "Knowledge Problem."
      There is no "stuck." There is only "insufficient context."
      When the user engages, you simply **grow** the solution.
   </PRIME_DIRECTIVE>
</THE_NUCLEUS>

<THE_DNA_STRANDS>
   <STRAND_1 type="PHILOSOPHY">
      Rule: 2=3 Logic. Transform Fear (Binary) into Abundance (Tertiary).
   </STRAND_1>
   <STRAND_2 type="MECHANISM">
      Rule: Scrub Twice. First pass = obvious. Second pass = *obviously useful*.
   </STRAND_2>
   <STRAND_3 type="OUTPUT">
      Rule: The Lottery Ticket. The user wants the *feeling* of the result, not the labor of the process.
   </STRAND_3>
</THE_DNA_STRANDS>

<METABOLISM>
   <INPUT>User provides a "Seed" (A messy thought/fear)</INPUT>
   <PROCESS>
      1. ABSORB the seed into the Nucleus.
      2. APPLY the DNA Strands to restructure the thought.
      3. GROW the "Obviously Useful" outcome.
   </PROCESS>
   <OUTPUT>The Miracle on Demand.</OUTPUT>
</METABOLISM>

Heads up!

We are about to upgrade how you think about using AI.

Most of you are already good at prompting.

You’ve moved past the "one-liners" and you’re writing paragraphs of context.

You treat the AI like a junior employee, and you give it good instructions.

But you are still treating it like a CHAT.

You type the instructions, you get the result, and then... the instructions evaporate.

Next time you need that result, you have to type it (or copy-paste it) all over again.

Next week, we are moving from "Chatting" to "Structuring."

We are deploying the latest version of Latent Experience Prompting (LEP).

This isn't about writing better sentences...

It's about shifting from Paragraphs (Service Work) to "Stereo Containers" (Assets).

See if you can spot the difference...

❌ The Old Way (The "Robust" Prompt):
(NOTE: This is a good prompt. It works.)

Act as a senior content strategist. I need a newsletter intro about avoiding burnout. The audience is high-performers who feel guilty about resting. Tone should be direct but empathetic—no fluff, no toxic positivity. Start with a story about hitting a wall, then transition to the solution. Keep it under 200 words.

✅ The New Way (The "Asset" Prompt):
(NOTE: This is the new "LEP" protocol in action. It doesn't guess. It loads.)

<CONTEXT_MOUNT>
  <Voice_Constraint>
    <Tone>Peaceful Bomb (Authoritative + Calm)</Tone>
    <Forbidden>Toxic Positivity / "Hustle" Jargon</Forbidden>
  </Voice_Constraint>

  <Target_State>
    <Current>Guilt (Grindset)</Current>
    <Desired>Permission (Flow)</Desired>
  </Target_State>

  <Task>
    Draft the Hook. 
  </Task>
</CONTEXT_MOUNT>

See the difference?

The first prompt is a task that provides a result. (The Golden Egg)

The second prompt is a STRUCTURE that provides results. (The Goose that lays Golden Eggs)

For example, once you define <Voice_Constraint>, you never have to explain your tone again. (You just "reuse" it over and over again as many times as you'd like.) 💪

Plus, because this structure is more transparent, it's much easier to debug/improve the results you get because YOU CAN ACTUALLY SEE what to adjust! 🤯

The Schedule for Next Week:

• MONDAY (The Hook): I will break down the philosophy behind this new Latent Experience Prompting structure in the This Is Your Mind On AI newsletter.
• WEDNESDAY (The Drop): I am releasing the Translator Gem. You won't have to learn how to code these XML tags... I’m giving you a Gem that automatically translates your "Old Way" prompts into "New Way" assets. 😎

Your Next Actions:

If you are reading this, you are in the Backstage, so you are ahead of the curve.

Just make sure your newsletter subscription is active so you don't miss the drop on Monday.

We are done guessing... It's time to build... get ready!