So Claude Opus 4.8 just dropped, so I turned it into my own AI operating system. It basically is my second brain. It's my executive assistant. It's everything. It runs all of my different businesses, and I literally live inside of this operating system. As you can see over here on the right hand side, we have a visualization of my actual second brain and all of my skills and other projects and everything that I'm working on in my business being built out in real time. So in this video, I'm gonna show you guys exactly how I have this set up. I'm gonna talk about my four c's framework for building your own AI operating system, context, connections, capabilities, and cadence. I'm gonna go over the mindset of building one. I'm gonna go over how you make it better and better and smarter over time, how you're gonna save tokens, and how you're able to organize all of this so that you can scale it up as your business evolves. I'm also gonna give you guys this free GitHub repo, which you can literally clone into your own project and start to just feed in and pump in context and skills and stuff like that so that you can feel more confident about the way that you're setting up your AI operating system based on my two frameworks here, the three m's, mindset, method, and machine, and then the four c's like I just mentioned for the actual architecture of how you build this automation system. So if that sounds good to you, let's just get into it. By the end of this video, you're gonna know exactly how I actually use this AI operating system every single day. Okay. So this is my
perk two project. If you guys have been following my channel for a while, you've probably heard me talk about this quite a bit. It kind of started off as my executive assistant and my second brain, and now I just realized it's my operating system. And the reason I say that is because I try to work out of this
tab right here in Versus Code more than opening up Chrome or opening up other desktop apps. I try to do everything through here, and that's kind of like the core default shift where I reach for that first before I reach for anything else. Because a lot of people might think like, okay, what is an operating system anyways? Well, think about it like, you know, your Windows operating system or your Mac operating system or, you know, your iPhone, your iOS. It's basically just the way that you're interacting with the different systems and the way that you're getting work done. So I'll show off some of my files and folders in here a little bit, but really what I want you to wrap your head around is that first idea
is that this thing has all the context that I want it to have, which is basically everything. It sees my meeting transcripts. It sees all of my posts in school, all of my YouTube video transcripts, all my LinkedIn posts. It can read through my Slack threads, my ClickUp threads, my email. It knows everything about my business to the point where I have to come in here sometimes and ask it to remind me of things because it can recall it better than I can and faster than I can. And the reason why I wanted to test this out with OPUS 4.8, obviously, it's a new model and, you know, the benchmarks compared to OPUS 4.7 look better. But if you think about the actual models,
I liked OPUS 4.6
more than I liked OPUS 4.7.
It was just kind of a feel thing.
And so far with OPUS four point eight, it feels more like 4.6 to me, is great. If you think about some of the things that OPUS four point seven wasn't doing great, Sometimes it had a bit of an attitude. Honestly, it sounds funny, but it did. Sometimes it would lie to you, and they have a big improvement here, OPUS four point seven, with honesty. Sometimes it was spending too many tokens, and it was being way too sort of like out of bounds of what you asked it to do. And that creativity was nice, but sometimes obviously it wasn't. So now that I've worked in Opus 4.8 into my entire operating system, it has already felt a little bit better. And by the way, I did just do a whole deep dive video on the launch of Opus 4.8, which I will tag right up here if you wanna check that out. So anyways, let's just start going through this stuff because I've got a lot of things to talk about, and I wanna get through it quick to not waste your guys' time. So the first thing I wanna talk about is the default shift about an AI operating system because it's not going to be valuable to you, and it's not going to feel like you're getting the ROI on it if you don't actually use it. So this is where I realized that I needed to use an iOS and where I really started to build it up was when I was opening up, you know,
Cloud Chat. I was opening it up on the web all the time. Had I a bunch of projects in there for helping me write YouTube outlines or LinkedIn posts or school posts or whatever it is. And even though at that point I was a frequent Claude code user, I realized that I was only using Claude code specifically to write code, to do things like building a Python script or building some sort of automation. But when you realize that Claude code
has the same underlying model, Opus 4.8 or whatever it may be, as Claude chat, then it's like, why would you ever use not Claude code? Even if the use case is just brainstorming or thinking or writing, you know, content, nothing to do with code, use Claude code because you start to build up all of that context. Right? And what I started to do is as I transitioned everything over to Claude code, my Cloud Skills, my Cloud Projects, other SaaS tools that I might have been paying for,
I just dwindled down my tech stack because Cloud Code, my AIOS, just does everything. And it's not only more efficient, but it's also potentially cheaper because you're not paying for the tools, and it just removes the amount of context switching. And so this default shift of thinking,
I have x y and z task to do today. Let me try to do x y and z task without opening up Chrome, without opening up whatever other apps I have. Let me just try to do everything from my Cloud Code. And once you start having that mindset shift, it's very, powerful because
AI isn't king. Who cares OPUS 4.8 benchmarks? Who cares GBD 5.5? I don't care. The AI isn't the king. Everyone has access to the same AI models. So if AI is king, then wouldn't everybody be king?
Context is king. And the more you use the thing, the better the context gets. So if you take the model, which is the engine, right, and you're feeding in your own fuel, your own context, That's how you get actual useful output. That's how you get an AI assistant or executive assistant or OS that doesn't feel like you're getting generic stuff. You know? If everyone has access to 4.8, right, and 4.8 can write really good LinkedIn posts, Then wouldn't everyone's LinkedIn posts be going viral? But that's not the reality. So
it's your context. Right? Context is king, not the AI model. And you wanna be thinking about your tokens like money. You know? You wanna think about the fact that your that your models, your AI models are stateless. So if you open up a new session in Cloud Code,
what does it have?
It it loads in its, you know, global rules. It loads in the cloud.md,
things like that. And then from there, it's gonna load in other files or instructions or memories that you've given it. Otherwise, it would be a complete beginner every time. So if you right now open up your Cloud Code product and said, hey. Based on what's going on in our business, what should I do next week? If it gives you an answer that's horrible, you probably need to give it better context and better, you know, hands to pull in the data from the right sources. And if you get a really good answer, then that's a good good starting point. There's always room for improvement, though. And so one thing I did wanna call out real quick is if this concept already
seems a little bit out there and you don't kind of you know, you feel a little bit lost already, then maybe you want to upskill first with Cloud Code at a basic level before you try to build your whole AIOS.
And I think a good place to start would be inside of my free school community. Link for this down in the description. It's all completely free. I've got a classroom section, and right here I have a full course about building your own AIOS,
the four c's that I talked about. And in here, I basically walk through everything. This is about a three hour course. So if you wanna start here and then come back to a video like this or watch this video first and then jump into that course, that would be a great way to do it. So this community is linked in the description, and it is completely free. It's also the largest AI automation community on school, so hop in there. But, anyways, the whole idea of those four c's, context, connections, capabilities, and cadence, is the way that you wanna mentally think about
what do you need to give your model access to in order to actually be useful. So let me hop into the GitHub repo real quick to show you what I mean by this. So the one liner of context is that it knows your business. Right? You open up a fresh session, and you should be able to say, what does this business do and who works here? And it should be able to answer that. Connections is what stuff can it actually touch? What's on your calendar tomorrow? What tasks do you have? What messages did John send you yesterday? What is the you know, what's going on in the general team chat right now? Can it see that kind of stuff, or are you copying and pasting stuff into it in order to give it that context? Then we have capabilities.
How you actually do work. This is usually basically just like the skills. The instruction files of, hey, whenever Nate wants to write a LinkedIn post, you should do it with
in this style, you know, use analogies like this. Here is his writing guide. Here is his framework for writing LinkedIn posts. When it starts to be able to understand how you work, that's when you have true capabilities, and usually those are skills. And then finally, we have cadence.
So turning all of this stuff that we just talked about into things that actually happen while your laptop is closed or when you don't explicitly ask for those things to happen. And each of these layers can't happen without the previous one. So contacts, connections, capabilities, and cadence. And like I said, that's what I go over in that free
course. So how do you actually think about the connections? Well, for example, in mine, I'm connected to ClickUp, all of my local files, obviously, my Google Workspace, my QuickBooks, YouTube, Fireflies, and so many more things. And the way that I like to think about what to add as connections, because I know at the beginning, you might be like, okay. I have so many things. Right? Think about on your week to week, Where do you go to look for things, and where do you go to look for these specific seven things as a really good starting point? Where do you go to look for your revenue figures? Where do you go to look at customer data or customer communication?
Where do you go for your calendar, your communication internally,
your tasks, your project management, your meetings, and your knowledge. And, obviously, there's more than this in my business, but this is just when you first sit down and you think about your day to day or your week to week and you do a little audit on yourself,
what desktop apps do you have? What software do you pay for? What are things that you actually are constantly, like, clicking on? You know, what what are your bookmarks on your Chrome? What are things that you're using so often that it would be helpful if your AI operating system had access to those things? And that's just, like I said, a good place to start. Write them down, and then just start one by one connecting to, like, school's API, Stripe API, QuickBooks API. Just start connecting to the different API endpoints or MCP servers one at a time, and you'll start to build up a really good bank
of connections. And also this GitHub repo will walk you guys through a lot of this. It's it has like a whole onboarding skills, so it'll interview you. It'll have you, you know, connect things. It'll audit you. It's gonna be really helpful if you're starting from zero right now. Now another cool thing that you guys can do is you can run slash insights right here, and it says that it's gonna generate a report analyzing
your Cloud Code
local sessions. So that will give you an HTML file, and then when you open that up in a browser, it will look like this. So it'll show you the date range that it looks through. It will do thirty days, but the only reason mine has twelve is because I recently got a new PC.
So there's only
days of local data. But it will show you at a glance what's working, what's hindering you, quick wins to try. So here are, you know, some skills that you can do, ambitious workflows,
and it'll show you different things that are going on. Right? So what you work on, how you use Cloud Code, impressive things, you know, where things go wrong, features to try, new usage patterns. So looking through this stuff is going to be hopefully very helpful for you to figure out how you can actually streamline
the way that you use your AIOS by implementing this feedback. But not only implementing it once, but checking this every couple weeks, checking this every month, and seeing
how the way that you're using it has changed and seeing if your sessions are increasing and seeing if your, you know, different recommendations are changing and things like that to make sure that you're always getting better the way that you're using your AIOS. And, of course, you can have Cloud Code brainstorm with you on the report findings and just keep iterating. So that's just a pretty cool feature that I wanted to tell you guys about, and it's definitely something to utilize,
especially as you're getting your AIOS up and running. Anyways, I wanted to now talk about how you organize this stuff because I think this is the most requested topic that I get
inside of my communities and comments is how do I organize my AI OS. So
let me start off by just saying this.
Don't stress it because
there's not a right way. There's not a one and only best way to run your AI operating system. You don't have to do it exactly the way that Nate does it or the way that your other, you know, creators that you watch do it or your friends do it.
It all is just folders and files. And when you start to actually realize that, it makes things a lot simpler. Right? Because when you realize everything's files and folders, the first thing it does in my mind is it makes me realize, okay. Cool. I could open up these files and folders in Codex or in OpenCLaw. I'm not locked into Cloud Code. I'm tool agnostic here, which is great. You might see over here, I've got a dot agents folder. I've got a dot Cloud. I've got a dot Codex. So I can use this entire operating system with multiple different types of coding agents, which is beautiful. And the other thing is it's a bunch of local files and folders, which means AI can look through everything. AI can crawl through it. AI can reorganize it. AI can search through it. So the point I'm trying to make here is don't stress it too much. If it gives you guys more comfort,
think about this. I
probably change my Cloud. M d file or my agents. M d file
almost every day. I'm changing that thing so often because I live in here so much. So anytime I think, oh, that would be good to know, or, oh, let's, you know, make this more concise, I'm updating that Cloud. M d file. And I'm also moving around my projects and my files and my folders definitely on a weekly basis as well because
every quarter, I have new priorities. Every week, there's something new that comes up. I'm making new files. I'm maybe working on new projects. I'm scrapping old projects. So things move around a lot. So the reason why I'm spending so much time there is just so so you feel more comfortable. You know, don't stress yourself out. I'm doing this the wrong way. I I truly don't think there's a single wrong way. The only time where you run into issues is if there's so much context and it's so unorganized that you can't find it, you can't find things manually, and that your AI can't find things. Because this is laid out in a way where to me it's very clear. I have decisions. I have audits. I have my archives. I have other worlds, which literally means these are entire full Cloud Code projects that I can open up in their own, and I use them on my own. So my scheduled automations, my YouTube OS, I've got the book that I'm working on. All of this stuff is other worlds, and if I wanted to add more Cloud Code projects in my other worlds folder, I could because it's nice that my main OS can look through this kind of stuff. But here's the thing. Even if I have other ClaudeCode projects, which trust me, have way more than just these four that live on my desktop or live in my documents,
ClaudeCode can still get there. And it still knows they live there because I I have, like, documentation on, okay, you know, the ClaudeCode GitHub repo that owns, you know, like, my website,
that lives at desktop slash blah blah blah. And so ClaudeCode can go find it if it ever needs it. You can see how many products I've gotten here. Right? Like, for example, this YouTube video, if I can just scroll down here and find it. Oh, yeah. Right here. In my YouTube videos folder, this one was called Opus 4.8 operating system,
and all the diagrams you guys just saw right over here, right, in Excalidraw,
all of these diagrams and the whole outline of this video was built for me in here by my Cloud Code OS, my outline, my visual plan, all of this, all these other YouTube videos, all these x articles, everything that I'm doing, I'm doing through here. And that's where I've got all the stuff set up because think about it. Now
this thing has access to basically everything I've done. So it can update my skills later. It can make its memory files better and better.
And,
yeah, I think you'll find just how helpful it is if you're constantly context switching and doing a lot of stuff throughout your day, which I'm sure all of you guys are. Having just, like, one source of truth that has everything,
and you kind of eliminate that scavenger hunt of, oh, where did I leave that file? Who did I send that to? Did I do that on chat GBT or Claude Code or Claude? Like, where did I do all this stuff? No. Just do it all here and give your system access to touch everything because then it can find things. Right? Like, I remember someone on my team sent me something the other day, and I couldn't remember if that was in Slack or ClickUp. So I just came in here and said, can you help me find this doc from this person? And it just found it in, like, ten seconds. So those types of use cases where you're not doing the scavenger hunt trying to find something, it's huge. Now when I start to bring that concept up,
there's probably alarm bells that go off in a lot of your guys' heads, which I think if that happened to you, I'm glad. Like, that's a good thing that happened because the more autonomy you have, the more reach you have, as you move your way up sort of like the AI systems pyramid that I talk about, you know, like workflows, AI workflows, AI agents, teams of agents, as you move up, typically, risk goes up as well as cost.
So
that's why I like to talk about your keys. Right? Like, permission layer around the AI agents.
Thinking about
if you're building an AI operating system that has so much data and it has so many different API keys or MCP servers,
you have to be careful.
There was an example, which you can see this is kind of built around on our team, like, real.
An AI agent basically
sent out three promotional emails that weren't supposed to go out to over a 150,000 inboxes. Like, it was bad. We had to apologize. We had to, you know, take down the page and whatever.
But why did that happen? Because it's not like
our team said, hey. Go send out these three emails. What happened was the agent proactively picked up a to do list, a task,
and and it interpreted it as, okay. I need to make these emails and send them off, and it just did it. And,
basically, the mindset shift there is you have to think about
what can your system actually touch? You know?
You have to assume that if your agent has access to read something or to do something, it will do it. And, like, that's not always the case. Right? Most of the time, it won't. But if you assume that it will,
you change the way that you give your agent endpoints. You change the way that you give your agent MCP servers.
You you start to have things that are scoped. You start to just be more careful about it, and obviously, that's the right way to do it. And I also wanna clarify, like, I was not mad at, you know, this person that when when this accident happened. Like, it happened. It was a really good learning experience for everyone on the team, myself included,
and, you know, we grow from it. But anyways, as you start to just give your agent more and more connections and more capabilities,
you definitely wanna be thinking about that because it's exciting. It's exciting to connect to a bunch of different data sources. It's exciting to build all these new skills,
but you also have to bring yourself down to earth a little bit and think, okay. What is the worst case that could happen here? And the thing is instructions are not the same as capabilities.
If you think about all the keys that your agent has on the key ring, there's a difference between saying, hey. Don't ever use that key and saying, okay. Give me that key. Like, you don't have you don't get to put this key on your key ring. It's a huge difference. So as much as you could say never send emails,
if there's a send email key or send email tool inside of that agent harness,
then it could do it. Right? Like, it it it actually physically could. And so that's why I like to think about it as the bike method. When you're building skills and when you're building automations, think about it like you're teaching a kid to ride a bike. Basically what I mean by that is you don't just
hand the kid a bike, put a helmet on him, and say, okay, kid, go ride. You typically will walk with them. You'll hold the handle, you'll put your hand on their back, you'll walk with them, you'll feel that they're adjusting too much to the left or leaning too much left, and you'll adjust them back to the middle. You will help them out throughout the way, and every single time you use that skill or every single time you you and the kid like go up and down the driveway,
it gets better. Like slowly it gets better and better and slowly there's more trust and slowly you can take off your hands, slowly you take off the training wheels. Slowly you let the kid just ride down the street and all you do is watch. You know? You probably don't immediately go inside and take a nap while the kid's riding a bike, but you still watch, and you make sure that things are feeling good and it's earned its spot. Basically, like, it's earned its next phase until the point
where you get to autonomy. And I think, yes, the barrier to entry is getting lower to build systems. Yes. It's easier to evaluate and easier to push something into production same day.
Whereas, you know, earlier on without
all these AI models, it was harder to build automation so quickly and so accurately right away.
But
making it easier
shouldn't be giving you that false sense of security. It shouldn't be,
um, actually putting too much trust in your head because too much trust is bad if you are putting something out there too quick and it's not ready. So that's another thing to think about, phase trust in the bike method. Every time you run a skill, it gets better. It's not a waste of time. So you can see here in my dot Claude, if I open up this folder, I've got, you know, agent memory. We've got agents. We've got some plans, some rules, and here's my skills
where you can see I've got quite a bit in here. Right? There's a lot of different skills that I've built out in here,
and these have built obviously over time. These get changed all the time. Some of them I've even moved, like, globally instead because you can have skills that live only in a Herc two project in this local project, or some of the skills I've made I moved globally so that if I'm ever working in any other directory,
I can still use those skills. But anyways, lots of skills here. I'm obviously not gonna dive into these because, like I said, there's just a lot. But let me talk about now how do you get to a place where you're building skills.
So I think that you should first of all think about it like this.
Think about your day. Think about your week. What are things that you do on a cadence? Right? What are things that you do every Monday, every single day, multiple times a day, whatever it is? What are things that you know you do often?
And then build it forward. So say, hey, Cloud Code. I want you to use the skill creator. I want you to help me run this skill. Here's the end goal. Here are typically the different tools and the different things I think about. Let's try building it out. And it's gonna walk you through. You correct it. You get an output. You give feedback. Right? And you just kinda take that iteration loop of building the skill. And sometimes your skills might take, like, 50 tries until you get to a place where you like it. And then even then, every time you use the skill, you're gonna evolve it. Right? Like every single time I use my LinkedIn writing skill,
I give it feedback. So every single time I write a LinkedIn post, I say, hey.
This was good, but this wasn't as good. So change that in the skill so that next time that doesn't happen, and I just keep evolving it. Now the other way is when you reverse engineer a skill, which honestly is what I do more often. I do something with Cloud Code from end to end, and then I think to myself, okay, that would be a good skill to have just in case I do that again, or because I know I'm gonna do it again. So I build the thing end to end, and then once I have that finished output, I reverse engineer and say, hey. This is a really good output. Look back at our conversation.
What did we do to get there? What did you think about? What tools did you need? What questions did you ask me? And build a skill around it that we wanna have that skill give us that output. Obviously, it's not gonna be perfect once again, but that's the way that I typically build them as I reverse engineer them. So I was watching this section of the video back, and I realized that this isn't completely true. Like, for the most part, yes, this is exactly how I do it, but I don't want to plant in your head the idea that a skill is only, like, a workflow or something that you do that's, like, a big process, like an SOP. Right? Like, skills can also be just as simple as, have you ever typed in this prompt before, and do you not wanna type that prompt in again? Then build a skill around it. And I think a really, really good example to show you guys is my session handoff skill. So, you know, this is a, you know, a Cloud Code session. I've been chatting with Cloud Code for a while. I ran a goal, and
now I want to be able to maybe
clear the context, or I wanna move this over from Cloud Code to Codex, or open up a new terminal, whatever it is. And so I built this skill right here called session handoff, and I installed this one globally for Cloud Code for me. So when I run this,
it basically is giving me a full breakdown of, hey. Here's what we did. Here's the files that were created. Here are open decisions. Here's what's next.
And that's really helpful for me because it's not a super complex skill. Right? It's just a prompt. But I was typing that myself every time. I'd say, hey, you know, I'm gonna clear my context. Can you give me a summary? Can you tell me what decisions are left to do? Can you tell me where we need to pick off or pick up? And I was just repeating that same prompt
so many times a day. And so I realized, okay, why don't I just take that prompt and just put it as a skill? Put it as a slash command. And now I have this. I can go ahead and do a slash copy slash clear, paste it in, and then I'm basically right back where I was with completely fresh context. So I will also leave this exact skill
in my free school community if you guys wanna grab that as well, or you can just build your Right? As you can see, it gives me
pickup here, deferred open questions, where it started, decisions locked, key files, all of that. Super, super helpful. So just wanted to throw that in there as well. And you really wanna be thinking about
your AI operating system as a mentor rather than just, like, you know, a chatbot or an automation.
So what I mean by that is
when you start to think about, like, I wonder if that's possible or I don't know how AI could do this,
it's it's tough. Because when you have that idea or that feeling of doubt,
your brain wants to default to what's comfortable, which is what you already know how to do. Which means, let's say you wanna pull some reports and do a data analysis for the quarter.
If you've done that for every quarter manually
by going into the software and pulling the report and then doing your formulas,
your brain's gonna wanna do that because you know exactly how it works. But if you think of your AI operating system as a mentor and you say, hey. Here's a process that I do, you know, at the end of every month. Here's the tool that I need to use. How is this possible?
Like, how can I actually do this? And it'll walk you through the options, and it will start to give you ideas, and it will test things out with you. And then you get to a point where you have that done. And it is tough because with AI, with building skills, with anything that you do new in your business or in your day to day productivity,
there is basically a short term cost that you have to bear. Right? Like, the idea of learning something and building out a new skill,
that one day, it might be slower than your manual process. But in the long run, having an automation around something is obviously way way quicker.
So you kind of have like a 20% dip, and it's basically is that change, is the dip worth it for the long term climb and the long term upside that you will have rather than just remaining constant how you would have if you kept that process the same and didn't change anything. But of course, your judgment still needs to stay there. You still need to be the one who's reading everything. You still need to be the one who is putting your own spin on it. You can't just outsource everything. I think a really good quote that I've brought up multiple times is that you can outsource your thinking, but you cannot outsource your understanding.
Really powerful quote. And then I know I showed you guys this earlier. Right? Like, the actual
Obsidian thing where you can see the visualization of all of my files.
This is cool. Right? And to be honest, for my Herc two project, I don't really use this too much. I think that when it comes to visualizing your actual operating system, it's basically just personal preference. Right? Like, you could open up the terminal and run Cloud Code from Obsidian, and you can, you know, do that if you want. I've got a few Obsidian projects where I have all my YouTube transcripts in there, and I've got a bunch of tools, and I've got different breakdowns, and sometimes it is really nice to see that visually. But, like, for my HER2 project, I don't really know what I'm looking at here, and I don't really care. And the thing about my OS is it's how I work,
and it's not very visual. And so I know a lot of people might think, oh, well, to have an AI operating system, you need, like, a fancy looking dashboard. You need to see all your agents. You need to see all this uptime. You need to see these things. I don't. I don't care. If you do, then that's perfectly fine. There's nothing wrong with that. But I don't need a dashboard for my operating system. Right? Like, because I come in here and I talk to different agents. I have different tabs. That's how I work. That's how I'm really productive. I was thinking about building one, but I thought to myself, okay. If I had a dashboard, what would I wanna see?
And when I started to think about what I wanted to see, there really wasn't anything that to me was too important that I can't see already, or I can't just have Cloud Code pull in the data for me. So if you want a custom dashboard to build, certainly grab Cloud Code, have it build you a dashboard. But for me personally, I just honestly don't see too much value in that. The way that I like to think about if I add features to my AI OS or if I add a new skill to my brain
is I think about my North Star. What is my ultimate goal at the end of each month that I wanna say that I made progress on? And if doing something, if spending time on something doesn't actually move me closer to that goal,
then I'm not gonna do it. And so I think, like, if you start to think about metrics, right, like, what are what are the metrics that are important to me? Maybe that's my free school members. Maybe that is our monthly recurring revenue. Does having a a dashboard, a pretty visual AIOS dashboard that shows me these metrics going to improve the metrics?
Some could argue yes if you're, like, a visual person and you need that to help with your
decision making and your brainstorming.
But the fact that the metrics exist and the fact that I can pull those in immediately,
that's what actually matters to me. So just wanted to sort of, like, throw out there. Once again, I don't think that there's anything necessarily wrong with that. I don't think that there's a right or wrong answer. I think a lot of people are making up their own AIOSs, and however they wanna work is perfectly fine. I think that's the beauty of it. But
just think about
productivity. Productivity isn't how many hours did I work today. Productivity is,
did I actually move the needle closer to my goal? And that's how you could stop getting so overwhelmed with all these AI tools and, you know, switching between things. That is the beauty of it. So anyways, guys, I know this one was a little bit shorter, but I wanted to keep it short. I wanted to keep it very, very, like, mindset oriented because I think the mindset stuff about the way that you use this, the way you set it up, and the way that you actually feel ROI is really, really important. But just remember in my free school community, you can come in here and get that full three hour course on how you actually build this out in Cloud Code, and you also can use this exact free GitHub repo, which I will link in the free school community as well in order to just clone this in, onboard into your AIS OS, and then just start pumping that thing full of those four c's we talked about, which were once again, hopefully, you guys remember, context, connections, capabilities, and cadence. So, anyways, that is going to do it for this one. I hope that you guys enjoyed, and I hope that you learned something new. If you did, please give it a like. It helps me out a ton. And as always, I appreciate you guys making it to the end of the video, and I will see you all in the next one. Thanks, guys.