Limitless AIOS.
01 /
Internal · The filming plan

Your 8 videos.

Screen recordings taking a client through their AIOS: you on camera, the real thing on screen. They slot straight into the course, one per lesson, mostly in Part II where clients work on their own machine.

Each one is 60 to 90 seconds. Eight videos is one relaxed filming afternoon.

The next card is the recipe that makes them land. Then one card per video, and a full script for the first one so you can feel the length and tone.

Kauthar · 15 July 2026 · click through ›

The recipe · every video

Five rules, from the research.

  • Open on the result, not the setup. Show the finished thing in the first ten seconds, then do it live.
  • Keep any stumble in. If something comes out wrong, fix it on camera with plain words. That builds more trust than a perfect take.
  • No naked jargon. If a technical word appears on screen, say it once, then give the plain meaning in the same breath.
  • Say the cost. Where it fits, mention what the task used: "that whole thing barely touched the day's allowance."
  • End with their move. Last line is always what the viewer should go and do, not a goodbye.

Tone: a colleague showing you something at their desk. Calm, first person, no selling. It is already sold.

Video 1 · about 60s

One window, three doors.

Lands in lesson 4.1Claude desktop app
On screen: the Claude app open. You click Chat, then Cowork, then Code, slowly, naming each.
  • Open on the app: "everything happens in this one program"
  • Chat: ask a question, get an answer. Cowork: chat with hands
  • Code: "this is yours. This is where your AIOS lives, with your files and your memory"
  • The rescue line: "if it ever seems to not know your business, check which door you are in"
Video 2 · about 90s · scripted

Your first /prime, live.

Lands in lesson 7.1Full script two cards ahead
On screen: a fresh Code session on the demo AIOS. You type /prime, wait the real thirty seconds, then scroll the summary slowly while reading bits aloud.
  • Open on the payoff: "this is the first thing you will do every day, and it takes thirty seconds"
  • Type the word. Let the real wait happen, do not cut it
  • Read the summary back: clients, projects, the open promise it remembered
  • The correction beat: say one thing is out of date, fix it by talking
  • Close: "sit down, one word, read what comes back"
Video 3 · about 60s

Watching the ring.

Lands in lesson 7.2
On screen: one real task end to end, with the context ring visible. You point at it twice as it climbs.
  • Give it one job on camera, something ordinary
  • While it works: "see that ring? That is its desk filling up. You glance at it like fuel"
  • The one rule: "when it runs high, save and start fresh. That is the whole skill"
  • Reassure: "it is not an alarm. Nothing here is breaking"
Video 4 · about 75s

/commit, and closing without fear.

Lands in lesson 7.3
On screen: finish a small task, type /commit, then close the chat completely. Open a new session, /prime, ask about the task. It knows.
  • "This is the save button" while it commits
  • The brave bit, done slowly: close the window on camera
  • New session, prime, "what did we do this morning?" and read its answer
  • Land the line: "the chat was never the work. The files are the work, and they are saved"
Video 5 · about 90s · the trust builder

When it goes wrong, live.

Lands in lesson 7.4New: straight from the research
On screen: a real output that is not right, kept in deliberately. You fix it by talking, then make the fix permanent.
  • Show the wrong output without flinching: "this is not what I wanted, and that is fine"
  • The fix phrase, spoken: "that is not right: the tone is too formal. Make it better"
  • Show the second pass landing closer
  • The compounding move: "remember this, so it never happens again"
  • Close: "two or three passes is normal. That is just week one with any new employee"
Video 6 · about 90s

/explore on a real idea.

Lands in lesson 8.2
On screen: you give it a genuinely vague idea, run /explore, and answer two or three of its questions on camera.
  • Say the idea badly on purpose: "I want something that keeps track of my quotes, sort of"
  • Let it interview you. React honestly: "see, I had not thought about that"
  • Show the plan it writes back, in plain words, and approve it
  • Land the line: "the fifteen minutes of questions is the point. It stops you building the wrong thing beautifully"
Video 7 · about 75s

Saving your first skill.

Lands in lesson 10.2
On screen: a result that just came out exactly right. You say the save phrase, then run the saved skill from one word.
  • Start at the good result: "this took two rounds of corrections, and now it is exactly how I like it"
  • The phrase, spoken slowly: "save this whole process as a skill: how I like it done, the mistakes to avoid"
  • Run it again from one word. Same quality, no corrections
  • Land the line: "I will never explain that task again. That is the moment the compounding starts"
Video 8 · about 90s · the finale

The morning brief, and hands into a tool.

Lands in lessons 11.1 and 11.2
On screen: connect the calendar, with the approval prompt shown and clicked deliberately. Then tomorrow morning's brief, already waiting.
  • Set the rule out loud first: "never send, delete or share anything without asking me"
  • Connect the calendar. Point at the approval prompt: "nothing plugs in without my yes"
  • Ask the chatbot-killer: "what does my day look like?" and read the real answer
  • Cut to the next morning: the brief waiting before you sat down
  • Cost beat: "running this every morning barely touches the allowance"
The script · Video 2 · read it in about 80 seconds

"Your first /prime" · full script.

Fresh Code session on screen. You, off camera or picture-in-picture.

This is the first thing you will do every single day with your AIOS. And it takes thirty seconds.

Type /prime. Press enter. Let the real wait happen.

One word. Prime. And now watch: it is reading up on the whole business before it touches anything. Who we are. What is on the go. What happened yesterday.

The summary appears. Scroll slowly.

There it is. It knows the clients. It knows the projects. It even remembers what I promised someone on Friday. I did not tell it any of that this morning. It read it, the way a good assistant reads the file before a meeting.

Point at one line.

And if anything in here is out of date, you just say so. Watch: that project wrapped up last week, take it off the list. Done. It never gets that wrong again.

Beat. Look at camera if PiP.

That is the whole habit. Sit down. One word. Read what comes back. Do that every day, and it knows your business better every single week.

If this length and tone feel right, the other seven scripts get written the same way.

Wrap

How this lands.

  • Film in any order. Video 2 first is easiest: the script is done
  • Rough is fine. Real waits, real outputs, real stumbles all stay in
  • Send the files over and each one drops into its course lesson, with the words already written underneath it
  • Once video 2 feels right, say the word and the other seven scripts follow

The course these land in is live to click through now, and the conceptual videos (the animated ones) are already in it.

Open the course ›
swipe ›