WEBVTT 00:00:00.000 --> 00:00:02.819 So if you're looking at the same ambitious goals 00:00:02.819 --> 00:00:06.259 again this year, maybe for the third or fourth 00:00:06.259 --> 00:00:09.119 time, we have to start with a tough idea from 00:00:09.119 --> 00:00:11.769 the source material. it's probably not a lack 00:00:11.769 --> 00:00:13.589 of discipline that's holding you back. Exactly. 00:00:13.589 --> 00:00:16.230 It's really more of a software mismatch. You're 00:00:16.230 --> 00:00:18.929 trying to get these powerful new results. You're 00:00:18.929 --> 00:00:22.609 installing these demanding, high -performance 00:00:22.609 --> 00:00:25.129 apps, so to speak. Right. But you're doing it 00:00:25.129 --> 00:00:27.469 on a brain that's running glitchy, outdated, 00:00:27.829 --> 00:00:31.250 mental software. Okay, let's unpack that. For 00:00:31.250 --> 00:00:33.009 this deep dive, we're really getting into the 00:00:33.009 --> 00:00:35.490 mechanics of personal transformation, but through 00:00:35.490 --> 00:00:38.810 this metaphor of a system upgrade. And the material 00:00:38.810 --> 00:00:41.109 suggests we move beyond what it calls hard mode 00:00:41.109 --> 00:00:44.689 willpower and into, well, into God mode identity 00:00:44.689 --> 00:00:46.289 programming. That's the mission. We're going 00:00:46.289 --> 00:00:49.090 to diagnose that root glitch in the system, define 00:00:49.090 --> 00:00:52.409 the three crucial layers of change, and then 00:00:52.409 --> 00:00:54.969 actually implement this multi -step reprogramming 00:00:54.969 --> 00:00:57.469 protocol. So we're aiming to systematically rewrite 00:00:57.469 --> 00:00:59.829 the rules you live by. That's it. So the first 00:00:59.829 --> 00:01:03.729 big idea is defining why we fail. Why does willpower 00:01:03.729 --> 00:01:06.530 always seem to let us down? Because willpower 00:01:06.530 --> 00:01:09.129 is just a temporary override. I mean, think of 00:01:09.129 --> 00:01:11.569 it like a short burst of emergency power. No 00:01:11.569 --> 00:01:14.969 way. It's taxing. It's not sustained. And it 00:01:14.969 --> 00:01:18.909 just, it cannot compete with automatic programming. 00:01:19.230 --> 00:01:21.349 And that's the core issue, isn't it? Your default 00:01:21.349 --> 00:01:25.069 OS, your programming. That's all completely automatic. 00:01:25.269 --> 00:01:27.829 Right. So the moment that physical or mental 00:01:27.829 --> 00:01:30.189 stress hits, and it always does. It always does. 00:01:30.209 --> 00:01:32.430 That default program just automatically wins 00:01:32.430 --> 00:01:35.069 every time. You start the morning strong. Yeah. 00:01:35.209 --> 00:01:37.700 You know, optimistic. Yeah. But by noon. The 00:01:37.700 --> 00:01:39.700 old codes back online. And you revert to old 00:01:39.700 --> 00:01:42.060 habits. You feel confused. And then you spend 00:01:42.060 --> 00:01:43.920 the rest of the day rationalizing why it didn't 00:01:43.920 --> 00:01:46.739 work out. It's not a moral failure. It's a technical 00:01:46.739 --> 00:01:49.180 one. You can't outperform your default. You can't. 00:01:49.180 --> 00:01:51.340 You can only replace them with better defaults. 00:01:51.359 --> 00:01:53.079 I found this concept of the pattern recognition 00:01:53.079 --> 00:01:56.700 problem really, really insightful. Every January, 00:01:56.739 --> 00:02:00.040 we set goals based on who we want to be. But 00:02:00.040 --> 00:02:03.180 every single micro decision we make all day long 00:02:03.180 --> 00:02:05.739 that's based on these mental patterns that have 00:02:05.739 --> 00:02:08.639 been running for years. That cycle is just exhausting. 00:02:08.979 --> 00:02:12.379 You set the goal. You use that temporary override 00:02:12.379 --> 00:02:15.680 for maybe a week. And then stress hits. A bad 00:02:15.680 --> 00:02:18.719 day at work. An argument. Low sleep. Anything. 00:02:19.240 --> 00:02:22.060 And that decades -old default just takes over. 00:02:22.159 --> 00:02:24.360 You revert. You feel that guilt. And the system 00:02:24.360 --> 00:02:27.259 learns, ah, that goal was just a temporary thing. 00:02:27.520 --> 00:02:30.259 This really highlights the need to define the 00:02:30.259 --> 00:02:32.860 system itself. The sources break it down into 00:02:32.860 --> 00:02:35.539 three parts. The hardware, the operating system, 00:02:35.639 --> 00:02:37.419 and the applications. Right. The hardware is 00:02:37.419 --> 00:02:39.919 pretty simple. It's the physical brain, the neural 00:02:39.919 --> 00:02:41.759 network. And the applications are the conscious 00:02:41.759 --> 00:02:45.259 goals, the things we see. Lose 20 pounds. Start 00:02:45.259 --> 00:02:47.819 a side business. But the key to all of this is 00:02:47.819 --> 00:02:51.039 the operating system, the OS. So the OS is everything 00:02:51.039 --> 00:02:53.379 running in the background. The deep -seated patterns, 00:02:53.599 --> 00:02:56.639 core beliefs, the whole identity structure that 00:02:56.639 --> 00:02:58.919 dictates how those applications even run. Exactly. 00:02:58.939 --> 00:03:00.960 I mean, two people can read the same book, right? 00:03:01.039 --> 00:03:03.340 The same application. But if one person's running 00:03:03.340 --> 00:03:06.360 an OS built on self -doubt and the others is 00:03:06.360 --> 00:03:09.740 running on curiosity and growth. they get wildly 00:03:09.740 --> 00:03:11.500 different results from the same input. Because 00:03:11.500 --> 00:03:14.659 the outdated OS is creating friction. So much 00:03:14.659 --> 00:03:17.539 friction. And that friction shows up as what 00:03:17.539 --> 00:03:20.740 the sources call code -based ceilings. And these 00:03:20.740 --> 00:03:23.219 feel like external forces. They feel like bad 00:03:23.219 --> 00:03:26.180 luck or market conditions. They do, but the argument 00:03:26.180 --> 00:03:28.780 is that they are almost always internal code 00:03:28.780 --> 00:03:32.229 limits. They manifest everywhere. Take the income 00:03:32.229 --> 00:03:35.370 ceiling. OK. If your internal code says rich 00:03:35.370 --> 00:03:37.789 people are greedy or even something simpler like 00:03:37.789 --> 00:03:40.909 money is hard to come by, you will unconsciously 00:03:40.909 --> 00:03:43.449 sabotage high value deals. So you'll hesitate 00:03:43.449 --> 00:03:45.530 on asking for that raise. Or you won't follow 00:03:45.530 --> 00:03:47.569 up on a lead. You do these tiny little things 00:03:47.569 --> 00:03:49.509 to make sure you stay at that familiar, quote 00:03:49.509 --> 00:03:52.490 unquote, safe income level. Because the success 00:03:52.490 --> 00:03:56.270 itself feels threatening. It challenges the identity. 00:03:56.680 --> 00:03:58.699 It does. And you see it in relationships, too, 00:03:58.780 --> 00:04:00.979 with the relationship ceiling. If your code is 00:04:00.979 --> 00:04:03.319 people always leave or I'm too much for people. 00:04:03.520 --> 00:04:05.919 You'll push away healthy, stable partners. Yeah, 00:04:06.020 --> 00:04:08.240 because they feel unfamiliar. They feel weird 00:04:08.240 --> 00:04:12.020 compared to the kind of the fragility that you're 00:04:12.020 --> 00:04:14.400 programmed to expect. The system rejects what 00:04:14.400 --> 00:04:15.900 it doesn't recognize. And the health ceiling 00:04:15.900 --> 00:04:17.990 is probably the most common one. Oh, for sure. 00:04:18.110 --> 00:04:20.790 If your deep identity is I'm the chubby friend 00:04:20.790 --> 00:04:23.810 or I just have bad genetics, you might lose some 00:04:23.810 --> 00:04:25.829 weight for a bit. But the system will trigger 00:04:25.829 --> 00:04:29.110 behaviors. Like compensatory binge eating or 00:04:29.110 --> 00:04:32.329 a sudden complete lack of motivation, all to 00:04:32.329 --> 00:04:34.970 pull you right back to that comfortable, familiar 00:04:34.970 --> 00:04:39.550 baseline. So if these ceilings feel so real, 00:04:39.649 --> 00:04:43.430 I mean, so emotionally charged, how does simply 00:04:43.430 --> 00:04:46.399 recognizing them as code? suddenly make them 00:04:46.399 --> 00:04:48.800 feel liberating. Because recognizing them as 00:04:48.800 --> 00:04:51.899 just patterns, it allows you to separate the 00:04:51.899 --> 00:04:53.839 pattern from your personal worth. You realize 00:04:53.839 --> 00:04:56.399 you're not flawed, your script is. It moves from 00:04:56.399 --> 00:04:58.680 an existential crisis to a debugging project. 00:04:59.019 --> 00:05:01.600 Exactly. Understanding these limits are patterns, 00:05:01.660 --> 00:05:04.990 not a fixed reality. that opens the door to change. 00:05:05.189 --> 00:05:07.430 So we know willpower fails us. If we want something 00:05:07.430 --> 00:05:09.209 that lasts, we have to look at the architecture 00:05:09.209 --> 00:05:11.410 of change. It's defined in these three distinct 00:05:11.410 --> 00:05:13.610 layers. And most people, as the sources point 00:05:13.610 --> 00:05:16.310 out, only ever focus on layer one. Right. Layer 00:05:16.310 --> 00:05:18.350 one is just the applications or the behaviors, 00:05:18.449 --> 00:05:21.310 the most visible stuff. Going to the gym, cutting 00:05:21.310 --> 00:05:24.569 sugar. But the problem is that layer depends 00:05:24.569 --> 00:05:29.790 entirely on motivation. And motivation is, it's 00:05:29.790 --> 00:05:32.779 volatile. Behavior is just an output. Trying 00:05:32.779 --> 00:05:35.259 to change behavior without changing the OS underneath 00:05:35.259 --> 00:05:37.560 it is like, it's like trying to make a slow computer 00:05:37.560 --> 00:05:40.060 faster by just typing harder. Doesn't work long 00:05:40.060 --> 00:05:42.319 term. And it uses up all your energy. So then 00:05:42.319 --> 00:05:44.740 some people try to go a bit deeper to layer two, 00:05:44.860 --> 00:05:47.420 the RAM or our emotions and mindset. Okay, so 00:05:47.420 --> 00:05:49.480 this is positive thinking, stress management, 00:05:49.639 --> 00:05:51.620 that sort of thing. That's helpful, right? It 00:05:51.620 --> 00:05:54.439 is helpful, but for a short sprint. Emotions 00:05:54.439 --> 00:05:57.000 are temporary. Motivation is a fuel that you're 00:05:57.000 --> 00:05:59.759 constantly burning through. So the initial high 00:05:59.759 --> 00:06:02.670 of a new goal always wears off. Always. And if 00:06:02.670 --> 00:06:05.389 the OS hasn't been updated, the old system set 00:06:05.389 --> 00:06:07.470 point just snaps right back into place. So it's 00:06:07.470 --> 00:06:10.470 necessary, but it's not sufficient. Which forces 00:06:10.470 --> 00:06:12.870 us down to layer three, the operating system, 00:06:12.970 --> 00:06:15.569 the identity. This is where the core beliefs 00:06:15.569 --> 00:06:17.850 actually live. And this is the essential shift, 00:06:17.970 --> 00:06:20.470 because when you change the core code here, the 00:06:20.470 --> 00:06:23.569 behavior changes automatically, almost, almost 00:06:23.569 --> 00:06:25.370 effortlessly. You don't have to try to save money. 00:06:25.740 --> 00:06:28.480 No, you just save money because you are a financially 00:06:28.480 --> 00:06:31.480 prudent person. It becomes a natural extension 00:06:31.480 --> 00:06:33.279 of who you believe you are. So the difference 00:06:33.279 --> 00:06:37.639 is huge. The old way or hard mode is forcing 00:06:37.639 --> 00:06:39.819 a behavior and just hoping your identity eventually 00:06:39.819 --> 00:06:43.000 catches up. While the new way or God mode is 00:06:43.000 --> 00:06:45.480 updating the identity first and then letting 00:06:45.480 --> 00:06:48.040 the behavior just flow naturally from that new 00:06:48.040 --> 00:06:51.339 truth. OK, so if layer three is so crucial, but 00:06:51.339 --> 00:06:54.699 it's also often invisible. How do we start finding 00:06:54.699 --> 00:06:58.379 those specific personality files, the beliefs 00:06:58.379 --> 00:07:00.500 that are currently installed that might be holding 00:07:00.500 --> 00:07:02.920 us back? We need a diagnostic. We have to find 00:07:02.920 --> 00:07:04.939 the corrupted code that's limiting our income, 00:07:05.079 --> 00:07:07.319 our health, or our relationships. Which brings 00:07:07.319 --> 00:07:09.500 us to the practical framework, the reprogramming 00:07:09.500 --> 00:07:12.500 protocol. And it all starts with step one. the 00:07:12.500 --> 00:07:15.060 diagnostic auditing the bugs right you have to 00:07:15.060 --> 00:07:17.040 find these deeply held beliefs a lot of them 00:07:17.040 --> 00:07:19.079 were installed in childhood and you've probably 00:07:19.079 --> 00:07:21.040 never even challenged them and this step requires 00:07:21.040 --> 00:07:25.040 what the source says is ruthless honesty it does 00:07:25.040 --> 00:07:27.519 the idea is to complete these sentence stems 00:07:27.519 --> 00:07:30.639 without filtering your answers at all don't write 00:07:30.639 --> 00:07:32.379 what you want to believe write what your subconscious 00:07:32.379 --> 00:07:35.500 actually believes so an example would be something 00:07:35.500 --> 00:07:38.339 like i am not someone who and you just finish 00:07:38.339 --> 00:07:41.120 it runs marathons makes over six figures whatever 00:07:41.120 --> 00:07:43.959 it is or to achieve high level success i would 00:07:43.959 --> 00:07:46.980 have to and your brain might say sacrifice my 00:07:46.980 --> 00:07:50.060 family or become a ruthless person yeah that 00:07:50.060 --> 00:07:52.939 unfiltered thought that is the code you're currently 00:07:52.939 --> 00:07:55.420 running so once you've found that corrupted file 00:07:55.420 --> 00:07:58.819 step two is the socratic debugging yeah and this 00:07:58.819 --> 00:08:01.220 is important because we know that just forcing 00:08:01.220 --> 00:08:04.839 positivity you know repeating i am rich it fails 00:08:04.839 --> 00:08:07.300 your brain just rejects it as fake because all 00:08:07.300 --> 00:08:09.759 your past data contradicts it so instead of forcing 00:08:09.759 --> 00:08:12.959 it The sources suggest we treat the belief like 00:08:12.959 --> 00:08:15.319 code, not like an absolute truth, and we just 00:08:15.319 --> 00:08:17.199 generally question it. Right. So if the code 00:08:17.199 --> 00:08:19.939 says success requires relentless grinding, you 00:08:19.939 --> 00:08:23.060 just ask yourself, is this absolutely 100 % true? 00:08:23.259 --> 00:08:25.180 And then you challenge it. You challenge it. 00:08:25.300 --> 00:08:28.139 What evidence contradicts this? Do I know anyone 00:08:28.139 --> 00:08:30.740 who is successful and not grinding constantly? 00:08:30.980 --> 00:08:33.159 And the most important question for any piece 00:08:33.159 --> 00:08:36.100 of code, is this belief useful for the person 00:08:36.100 --> 00:08:38.639 I want to be? If it's not useful, it's garbage 00:08:38.639 --> 00:08:41.259 code. Exactly. The goal is just flexibility, 00:08:41.500 --> 00:08:44.279 not totally destroying the old idea. Which leads 00:08:44.279 --> 00:08:47.720 to step three. Install the patch. The evidence 00:08:47.720 --> 00:08:50.899 log. This is the actual system upgrade, and it 00:08:50.899 --> 00:08:53.700 depends on data. Because beliefs are just patterns 00:08:53.700 --> 00:08:56.419 the brain has logged as true over and over again. 00:08:56.519 --> 00:08:59.340 So to install new code, you have to feed it new 00:08:59.340 --> 00:09:02.399 data consistently. You write the new, more useful 00:09:02.399 --> 00:09:04.919 code like, I am someone who handles uncertainty 00:09:04.919 --> 00:09:08.840 well. Then you commit to these small, almost 00:09:08.840 --> 00:09:11.940 boring wins. And the small wins are key. The 00:09:11.940 --> 00:09:14.320 source material really emphasizes this over heroic 00:09:14.320 --> 00:09:16.700 efforts because the subconscious mind trusts 00:09:16.700 --> 00:09:19.419 accumulated consistency, not these big dramatic 00:09:19.419 --> 00:09:21.639 spikes of effort. So if you're trying to install 00:09:21.639 --> 00:09:24.200 I am a disciplined person, doing 10 push -ups 00:09:24.200 --> 00:09:26.960 every single day for a month is way better evidence 00:09:26.960 --> 00:09:29.840 than one epic gym session followed by two weeks 00:09:29.840 --> 00:09:32.080 of nothing. It just stacks the data. And, you 00:09:32.080 --> 00:09:33.879 know, I still wrestle with this myself sometimes. 00:09:33.940 --> 00:09:35.779 When I try to install some high -level productivity 00:09:35.779 --> 00:09:38.440 code, there are days it just feels forced, like 00:09:38.440 --> 00:09:41.960 it's not sticking. But the data log, just the 00:09:41.960 --> 00:09:45.019 record of completion, that's what convinces the 00:09:45.019 --> 00:09:47.519 system in the end, not the feeling you have about 00:09:47.519 --> 00:09:51.120 it. That's it right there. Data over feeling. 00:09:52.240 --> 00:09:55.620 Which brings us to step four. Engineer the environment. 00:09:56.200 --> 00:09:58.779 You can't run high performance software on a 00:09:58.779 --> 00:10:01.480 sluggish old machine. You have to optimize the 00:10:01.480 --> 00:10:03.899 world around you. Make it so the new code is 00:10:03.899 --> 00:10:05.799 the path of least resistance and the old code 00:10:05.799 --> 00:10:08.080 is actually inconvenient. Physically, that's 00:10:08.080 --> 00:10:10.159 simple stuff like laying out your running clothes 00:10:10.159 --> 00:10:12.860 the night before. But socially, it might mean 00:10:12.860 --> 00:10:15.080 distancing yourself from friendships that run 00:10:15.080 --> 00:10:18.240 on a scarcity mindset. People whose default programming 00:10:18.240 --> 00:10:21.480 is just complaining or helplessness. you don't 00:10:21.480 --> 00:10:23.360 rise to your goals you will always inevitably 00:10:23.360 --> 00:10:26.059 fall to your systems and the final step is maintenance 00:10:26.059 --> 00:10:30.440 step five monitor and debug yeah just 15 minutes 00:10:30.440 --> 00:10:33.919 a week for a code review what were the wins where 00:10:33.919 --> 00:10:37.220 did the new code run successfully and what were 00:10:37.220 --> 00:10:40.379 the glitches what specific trigger caused you 00:10:40.379 --> 00:10:43.000 to revert you diagnose the trigger not just the 00:10:43.000 --> 00:10:45.879 outcome always the trigger okay so if we're only 00:10:45.879 --> 00:10:49.210 upgrading one belief one file at a time How do 00:10:49.210 --> 00:10:51.509 we make sure the entire system doesn't just crash 00:10:51.509 --> 00:10:54.370 or reject the change? That focus is what allows 00:10:54.370 --> 00:10:56.870 the proof to stack up so deeply. It makes the 00:10:56.870 --> 00:10:58.769 whole system stronger and more resilient for 00:10:58.769 --> 00:11:01.110 the next update you want to run. Let's apply 00:11:01.110 --> 00:11:04.009 this protocol to those code -based ceilings we 00:11:04.009 --> 00:11:05.669 talked about, starting with career and income. 00:11:05.990 --> 00:11:08.210 Most people are running really old code about 00:11:08.210 --> 00:11:10.210 what they're worth. Yeah, the limiting code is 00:11:10.210 --> 00:11:12.190 often something like, I sell time for money. 00:11:12.610 --> 00:11:14.870 The system update shifts this to something more 00:11:14.870 --> 00:11:17.720 like... I create value that can be priced and 00:11:17.720 --> 00:11:20.379 scaled separately from my time. That is a huge 00:11:20.379 --> 00:11:22.960 identity shift. It's massive, and the evidence 00:11:22.960 --> 00:11:25.460 needed to lock that in. It's usually really uncomfortable. 00:11:25.820 --> 00:11:28.279 It might mean studying people in your field making, 00:11:28.399 --> 00:11:31.120 you know, two to ten times more than you. Not 00:11:31.120 --> 00:11:33.820 to copy them. No, not to copy, but to see that 00:11:33.820 --> 00:11:35.840 their value model is different. And then you 00:11:35.840 --> 00:11:38.059 have to run small experiments. Maybe raise your 00:11:38.059 --> 00:11:40.919 prices 20 % and just see what happens. The outcome 00:11:40.919 --> 00:11:42.860 is the data. Okay, what about in relationships? 00:11:43.710 --> 00:11:46.830 If the belief is people leave when they see the 00:11:46.830 --> 00:11:49.610 real me, you're just programmed for emotional 00:11:49.610 --> 00:11:52.289 distance. Right. So the patch you need to install 00:11:52.289 --> 00:11:55.669 is the right people appreciate authenticity and 00:11:55.669 --> 00:11:57.830 vulnerability. And the evidence here would be 00:11:57.830 --> 00:12:00.789 what running these small controlled vulnerability 00:12:00.789 --> 00:12:04.710 experiments with safe, trusted people. Exactly. 00:12:04.710 --> 00:12:07.129 And when they respond positively, you log that 00:12:07.129 --> 00:12:09.879 data. And if someone does leave. You reframe 00:12:09.879 --> 00:12:12.279 it. The system is working perfectly by filtering 00:12:12.279 --> 00:12:14.919 out mismatched connections. It stops being a 00:12:14.919 --> 00:12:17.100 personal tragedy. It becomes a calibration event. 00:12:17.360 --> 00:12:18.899 And for health and fitness, where the code is 00:12:18.899 --> 00:12:21.440 often just, I'm not a fitness person. The update 00:12:21.440 --> 00:12:23.679 should be softer, more achievable. Something 00:12:23.679 --> 00:12:26.019 like, I'm someone who's learning to prioritize 00:12:26.019 --> 00:12:29.379 my body consistently. So you aim for consistency, 00:12:29.580 --> 00:12:32.759 not this massive transformation. Right. If the 00:12:32.759 --> 00:12:36.399 new code is, I move my body every day. Then 10 00:12:36.399 --> 00:12:39.000 minutes of stretching every single day for 90 00:12:39.000 --> 00:12:42.019 days is far better data than running a half marathon 00:12:42.019 --> 00:12:44.519 and then burning out for a month. Consistency 00:12:44.519 --> 00:12:47.139 provides the evidence that new identity needs. 00:12:47.360 --> 00:12:49.320 And here's where it gets really, really cool. 00:12:49.740 --> 00:12:52.100 Let's talk about the advanced concepts, starting 00:12:52.100 --> 00:12:54.500 with the compounding effect of these code updates. 00:12:54.799 --> 00:12:57.299 You're saying the change isn't linear? Not at 00:12:57.299 --> 00:13:01.220 all. It's exponential. Whoa. Just imagine that. 00:13:01.559 --> 00:13:04.559 Scaling these tiny belief changes across an entire 00:13:04.559 --> 00:13:07.919 life over years. The acceleration would have 00:13:07.919 --> 00:13:10.539 to be incredible. It really is. Belief changes 00:13:10.539 --> 00:13:13.100 stack. So when you successfully update the belief 00:13:13.100 --> 00:13:16.019 I can learn new complex skills, that new success 00:13:16.019 --> 00:13:18.539 data suddenly makes the next belief like I deserve 00:13:18.539 --> 00:13:21.419 professional success much, much easier to install. 00:13:21.600 --> 00:13:24.100 The previous update reduces the resistance for 00:13:24.100 --> 00:13:26.080 the current one. Precisely. And then there's 00:13:26.080 --> 00:13:28.460 identity stacking. Instead of just chasing an 00:13:28.460 --> 00:13:31.659 outcome like more money, you ask a better question. 00:13:31.799 --> 00:13:34.440 Who would naturally achieve this result? Exactly. 00:13:34.539 --> 00:13:36.440 And then you focus on stacking the necessary 00:13:36.440 --> 00:13:39.320 identity components for that person. If you want 00:13:39.320 --> 00:13:41.360 to be a leader, you stack the code. I can handle 00:13:41.360 --> 00:13:44.600 uncertainty. I am decisive. I listen well. At 00:13:44.600 --> 00:13:46.879 a certain point, the stack is so robust, you 00:13:46.879 --> 00:13:50.559 just, you realize you are that person who gets 00:13:50.559 --> 00:13:53.879 those results. Yeah. And maybe the most important 00:13:53.879 --> 00:13:56.340 upgrade of all is your belief about change itself. 00:13:56.799 --> 00:13:59.419 If your core code says people don't really change, 00:13:59.580 --> 00:14:01.700 every difficult attempt just feels like more 00:14:01.700 --> 00:14:05.860 proof of failure. But seeing change as this systematic 00:14:05.860 --> 00:14:09.100 iterative process, not some deep personality 00:14:09.100 --> 00:14:11.919 flaw that allows you to stop fighting yourself. 00:14:12.120 --> 00:14:14.620 You start experimenting. You stop judging a reversion 00:14:14.620 --> 00:14:16.960 as a catastrophic failure. And you start logging 00:14:16.960 --> 00:14:19.240 it as a glitch that needs to be debugged. So 00:14:19.240 --> 00:14:21.120 if the whole point is that this code changes. 00:14:21.549 --> 00:14:24.029 What happens when we face that old, reliable 00:14:24.029 --> 00:14:26.990 trigger, that moment of stress, the high -value 00:14:26.990 --> 00:14:29.649 deal, and we don't revert? That calm moment, 00:14:29.769 --> 00:14:32.289 that automatic choice that feels completely effortless, 00:14:32.389 --> 00:14:34.330 that is the proof. That's how you know the new 00:14:34.330 --> 00:14:36.210 code has been successfully installed without 00:14:36.210 --> 00:14:39.029 you even needing conscious willpower. So to bring 00:14:39.029 --> 00:14:41.629 this all back, transformation really isn't about 00:14:41.629 --> 00:14:45.230 trying harder. It's about these systematic, targeted 00:14:45.230 --> 00:14:48.529 updates to your identity OS. Willpower is temporary. 00:14:48.649 --> 00:14:51.690 It burns out. But identity. Once it's established, 00:14:51.929 --> 00:14:54.509 it's permanent and it's effortless. You won't 00:14:54.509 --> 00:14:56.409 even recognize the person you're becoming until 00:14:56.409 --> 00:14:58.809 you're already them. The change really does feel 00:14:58.809 --> 00:15:01.389 invisible day to day. It's just a series of small, 00:15:01.570 --> 00:15:04.830 almost boring choices that compound quietly in 00:15:04.830 --> 00:15:07.029 the background. The ultimate goal here is to 00:15:07.029 --> 00:15:09.370 actively rewrite the system that produces your 00:15:09.370 --> 00:15:12.110 thoughts, your emotions, and your actions. That's 00:15:12.110 --> 00:15:14.429 a foundational level of agency. It is. We covered 00:15:14.429 --> 00:15:16.370 a lot of deep material today, from the income 00:15:16.370 --> 00:15:19.730 ceiling to the evidence log. So the final question 00:15:19.730 --> 00:15:22.350 we'll leave you with is this. Are you willing 00:15:22.350 --> 00:15:24.629 to examine your own code? Are you ready to bet 00:15:24.629 --> 00:15:26.769 on the updated version of yourself? Until next 00:15:26.769 --> 00:15:29.590 time, keep monitoring and debugging your operating 00:15:29.590 --> 00:15:30.070 system.