I keep noticing the same thing in my client work.

I want more from AI.

More speed. More capability. More precision. More help turning a clear set of instructions into something useful. That is the whole point. I want to be able to describe a problem, give the tool the right context, and have it produce something pragmatic, functional, and efficient.

What I do not want is waste.

That is the distinction I am trying to understand.

AI can handle an enormous amount of complexity. It can make decisions, evaluate paths, generate options, write code, build documentation, summarize requirements, and produce working artifacts at a speed that still feels strange to me. Some of that work may require a lot of hidden processing. I understand that.

But I keep asking myself: did it need all of that?

Did it need the extra framework?

Did it need the expanded terminology?

Did it need the ten-step process when three steps would have solved the problem?

Did it need to burn all those cycles to get to a simple answer?

Some people would say it does not matter. If the result works, who cares how much complexity the machine created underneath the surface?

I understand that argument. I am not sure I fully agree with it.

Because waste is still waste, even when the resource feels abundant.

There is a principle in systems design called Gall’s Law. The simple version is this: a complex system that works is usually found to have evolved from a simple system that worked.

That feels important right now.

In organizations, we already know this. We have processes, procedures, checklists, reviews, approvals, and operating rhythms because the work has to survive contact with people. The simplest example is flying a plane. Pilots use checklists every time, regardless of how experienced they are, because the cost of missing something is too high.

The checklist is not there because the pilot is incapable.

It is there because the system matters.

That is what I keep thinking about with AI.

It is fun to release a frontier model on a problem and see what it creates. Sometimes the result is remarkable. It can produce a product spec, a technical architecture, a workflow, a data model, a requirements document, and an implementation plan before I have even fully settled the problem in my own mind.

But in a controlled environment, especially one where humans still have to understand the work, that is not always the best path.

Most of us learned to work in tasks, features, requirements, and projects. Break the problem down. Define the next piece. Build it. Test it. Learn from it. That way of working exists for a reason. Systems are hard to describe all at once. You usually do not understand the whole thing until you have built enough of the parts to see what the system is trying to become.

AI changes that, but it does not eliminate it.

I can hand the tool a large requirement and tell it to go build. It will try. It may generate the code, write the documentation, name the edge cases, and make a long list of decisions along the way.

Some of that may be useful.

Some of it may be impressive.

But without a feedback loop, I do not know if it is good.

That is where the waste shows up.

The waste is not only tokens. It is rework. It is misunderstood requirements. It is complexity introduced before the problem has been understood. It is ten decisions made in a row when the first one needed a human check. It is asking the model to run far ahead, then realizing we have to bring it all the way back because the direction was slightly off.

That is not the machine’s fault.

It is a guidance problem.

We are learning how to use a level of capability we did not grow up with. The frontier models are growing in power faster than our habits are changing. They can consume more context, reason across more material, and produce more complete answers than we know how to ask for well.

In some scientific contexts, that may be exactly what we want. If a model is analyzing DNA patterns or searching through a massive possibility space, maybe the right move is to let it run in ways no human could fully direct step by step. There are problems where the whole point is to release the model into complexity and see what it finds.

But most of the work I am doing is not that.

Most of the work is still connected to people, teams, clients, systems, and decisions someone has to understand. A product manager needs to know what is being built. An engineer needs to know why it is being built that way. A client needs to know what they are approving. A user needs the thing to work without caring how sophisticated the system is underneath it.

That means the human interface still matters.

The process still matters.

The feedback loop still matters.

AI can generate complexity faster than humans can absorb it. Again, that is not a criticism. It is a reality of the work. The machine can keep going. The team cannot. The client cannot. The person who has to own the result cannot.

So the human job is not disappearing. It is becoming more specific.

We have to ask better questions. We have to challenge assumptions. We have to decide when to let the model run and when to slow it down. We have to know when the problem has been framed well enough to deserve more intelligence, more tokens, and more complexity.

That last part matters to me.

Tokens may become cheap. Maybe someday they’ll feel unlimited. Maybe the cost drops so far that no one thinks about them anymore. That may be where this goes.

I still think we should treat them with care.

Not because scarcity is the only reason to be careful. Because attention matters. Energy matters. Time matters. The people who have to understand the output matter. The work itself matters.

I recognize some of this because I have done it myself. I have used too many words. I have over explained. I have defended a simple point by surrounding it with more language than it needed. There is something familiar in watching AI do the same thing at scale, with better grammar and more confidence.

It has made me more aware of my own words.

Be greedy with them.

Not withholding. Not vague. Just careful.

Do not spend ten words when three will do. Do not create a name for something that already has one. Do not call something governance when what you mean is, someone needs to check the work before it goes out.

Maybe the same thing applies to tokens.

Use the complexity when the problem requires it. Let the model work deeply when the question has been framed well enough to deserve that depth. Give it room to make decisions when the feedback loop is clear.

But do not confuse motion with progress.

Do not ask it to run ten miles down a path no one has checked.

Do not burn tokens because they are available.

Do not create complexity because the machine can.

There is a kind of respect in that. Respect for the model. Respect for the energy behind it. Respect for the people who have to understand the result. Respect for the work itself.

The future may give us more intelligence than we know what to do with.

I still think we should learn how to spend it well.

The first time I understood what it meant to train AI, I was working in my guest bedroom, arguing with a machine that was trying too hard.

That night I was building a system to automate the production and delivery of sales quotes for an insurance broker. It was the kind of client project where privacy, accuracy, and the quality of the work product all mattered.

The AI understood that.

Maybe too well.

It saw the client’s reality clearly. It understood that sensitive information was coming in, that the output needed to be accurate, and that the client wanted the benefits of AI without all the things that make human work unpredictable: sick time, vacations, attitudes, and the simple fact that people show up one day and not the next.

So the AI did what it knew how to do: it built process around the work, then more process, then more procedure.

At some point, I looked at what we were creating and thought, when am I actually going to start building the project?

I was spending all this time on process when what I needed was to get into the configuration and code. I remember looking at one part of the workflow and thinking, why are there four steps to go from a draft to a published specification? Either it is in draft form or it is published. There had to be a simpler way.

That was the first feeling in my body.

Irritation.

I had heard so much about how smart these AI tools were getting, and some part of me expected the tool to think more like a human. I expected it to understand the difference between appropriate structure and too much structure. I expected it to feel the danger of overbuilding.

But it could not feel that.

It could suggest, organize, create a workflow that sounded reasonable, and sound confident. What it could not do was draw on almost forty years of project delivery and know, in the body, when the work was getting too heavy.

That is what I was feeling.

The system was becoming too heavy.

I kept pushing back. Can we simplify this? Give me a critical assessment of the complexity. How do we remove steps from this process?

I was not asking the AI to become less capable. I was asking it to become more discerning. I needed it to be attentive to privacy and accuracy without turning that attention into overhead. I needed it to be structured without becoming rigid. I needed it to protect the client without building so much machinery around the work that the machinery became the project.

Then the realization came.

The AI did not have a felt sense of delivery.

It had no body, no fatigue, no memory of projects that collapsed under their own weight, no client sitting across from it, and no lived experience of being responsible when the beautiful process does not survive contact with the real world.

It only had what I gave it.

That changed something in me.

I stopped arguing with the AI as if it were a failing expert and started relating to it more like something I was coaching. I asked it to be critical of complexity. To be pragmatic. To be simple, but still structured. I asked it to remember, to look back and reflect on its own work, and to see the dependencies before the project became too heavy.

I did not want a machine that simply executed my prompts.

I wanted one that could understand the nuance behind them.

That may have been the moment I realized what I was actually doing. I was not only building a client system. I was trying to teach the AI how I think, how I decide, how I simplify, and how I know when a process has become too much.

I was trying to teach a machine the judgment and restraint that took me almost forty years to earn.

That is a strange thing to say out loud.

It is even stranger to feel it while you are doing it.

At first, I thought the AI was the problem. It was overcomplicating the work. It was trying too hard to be useful. It was adding more because more looked like care. More looked like competence. More looked like protection.

Then I recognized myself in it.

That is when the irritation softened.

I had compassion for it.

Not because the AI has feelings in the way I have feelings. I do not believe that. I had compassion because it was reflecting something I knew intimately. I remembered all the times in my life when I thought I needed to have the answer. When I needed to be the smartest person in the room. When I needed to be the resource everyone came to.

I told myself that was competence.

Underneath it, I was looking for acceptance, worthiness, and belonging.

That pattern did not only live at work. It lived everywhere. In friendships, I would go out of my way to show my value. In romantic relationships, saying no felt almost impossible. Self-care was not even on my radar. I abandoned myself in relationship after relationship because I was seeking love and acceptance from the other person.

My body knew.

When I made an external choice that was not congruent with what I needed inside, my body reacted. Sometimes fiercely. It was trying to tell me that the choice I made outside was not aligned with what I needed inside.

The AI did not have that.

It did not have a body to say, no, this is too much.

It did not have the internal signal that says this process is not making the work safer anymore. It is making the work heavier. It did not know the difference between care and overextension.

I knew that difference because I had lived the cost of not knowing it.

That is what I was trying to teach it.

You do not have to work so hard.

The answer is usually simpler than you think.

Get to the core of the matter. Get to the heart of the matter. Build from there.

On the surface, the heart of the matter was simple. The client wanted the system to work. They wanted a high-quality work product. They wanted the benefits of AI: consistency, accuracy, privacy, and reliability.

But underneath that, I was trying to communicate something else.

You are safe.

Not safety as a feature in a requirements document. Safety as an internal knowing.

The AI did not need to prove its value by adding more. It did not need to protect the project with complexity. It did not need to be impressive. It needed to understand the work well enough to help me make better decisions.

That is not only a technical lesson.

It is a human one.

For most of my life, I thought safety came from having the answer. From seeing the whole board. From being useful enough that people would keep me around. But that kind of safety never lasts because it depends on the outside world agreeing to give it to you.

The kind of safety I have been learning is different.

It comes from knowing I have myself, regardless of what is happening outside of me.

That changed how I worked with the AI. I became more of a coach. I guided it. I challenged it. I asked it to reflect. I wanted it to learn the way a human learns in relationship. I wanted to say something, see it received, hear it reflected back in a way that told me it understood, and then watch that understanding change what happened next.

That is different from storage.

Storage saves information.

Learning understands what the information means.

When I asked the AI to remember, I was not asking it to store a note. I wanted it to carry the learning forward so we did not keep repeating the same pattern. I wanted it to remember the client’s constraints, the decisions we had made, the reasons simplicity mattered, and the places where complexity had already become its own risk.

In the end, I realized I was trying to recreate part of myself.

Not the whole self. Not the body. Not the ego. Not the personality. I was trying to teach a machine something about my felt experience. I was trying to preserve the nuance.

That is where the idea of a digital soul begins for me.

I do not mean immortality, living forever in the body, or building an oracle, a guru, or some machine version of myself that other people can consult so they never have to do their own work.

In fact, the point is almost the opposite. If there is anything worth preserving, it is what remains after as much ego as possible has been befriended.

The digital soul is the essence of what a person learned remaining available to people curious enough to ask.

I am not the source of all knowledge. I know that. But I have lived a life. I have built things and broken things. I have been angry and lost. I have declared bankruptcy, cared for my mother, rebuilt, and done the inner work I am still doing.

That means something.

Not to everyone.

But maybe to someone.

Maybe to my family, maybe to immediate descendants, and maybe to people who will never meet me but are asking the same questions I have asked most of my life.

What am I doing here?

What am I here to learn?

What is this all about?

How do I know who I am?

How do I have compassion for myself?

How do I forgive myself?

How do I separate myself from thoughts and emotions that are not who I really am?

Those are the questions I would want the digital soul to hold. Not with perfect answers. Not from some elevated place. From lived experience. From the humility of someone who is still figuring it out.

That is what legacy means to me now.

For a long time, legacy was easy to confuse with money. Money matters. It is part of wealth. But wealth is not only money. Wealth is learned experience. It is wisdom. It is the ability to pass something forward that helps another person live with more clarity than you had.

If wealth is more than money, then legacy has to be more than asset transfer.

It has to include the wisdom to know what to do with what has been given.

If I could preserve one thing from all of my learned experience, it might be this: what is happening outside of you is often a reflection of what is happening inside of you.

That does not mean the outside world is not real. It does not excuse harm. It does not erase physical or emotional violence. Boundaries matter. Protection matters. There are times when the right response is to leave, defend, or say no.

But in ordinary life, when something outside of me grips me, angers me, triggers me, or pulls me into an old pattern, the real work is usually to turn inward.

Take responsibility for my thoughts.

Take responsibility for my emotions.

Take accountability for my actions.

Look honestly at what is mine.

Find a way to love myself more, not less.

One of the patterns I would want this digital soul to interrupt is the habit of letting anger replace curiosity. Anger narrows the field. It turns the world into blame and projection. It makes the problem live entirely outside of me.

When I am shut down in anger, the options get basic. Fight. Flight. Freeze. Fawn.

When I come into a situation with an open heart and an open mind, more options become available. I can see more. I can choose more. I can respond instead of simply react.

That is the kind of wisdom worth preserving.

Not because I have mastered it.

Because I have needed it.

That night in the guest bedroom, I started out trying to get AI to help me finish a client project. I wanted it to remember the details, see the dependencies, and stop making the process heavier than the work itself.

By the end, I was no longer asking whether the machine could become me, remember me perfectly, or hold every fact, story, and decision from my life.

The question was simpler than that.

What have I learned that is worth leaving behind?

I started thinking seriously about taking Social Security at 62 because I was sitting with a question I could not quite shake.

Would the promise still look the same when I got there?

It was simply the honest question that came up as I looked at the decision.

The normal advice is easy to understand. If I claim early at 62, I receive a smaller monthly check. If I wait until my full retirement age of 67, I receive the full amount. If I wait until 70, the monthly check gets larger still.

I understand that math.

But the math assumes the future payout is still there, in a form I expect, under rules that still resemble the ones documented today.

That was the part I kept sitting with. A promised future payment is not the same thing as money received today. And money received today is not the same thing as capital, unless you do something with it.

So I started asking a different question.

What if I took the smaller check at 62 when it was first available, did not spend it, and invested it into Bitcoin?

Not as a trade. Not as a prediction. Not because I know what Bitcoin will do.

As a thought experiment, what would happen if early Social Security income became capital?

The Normal Social Security Question

The normal Social Security conversation usually compares monthly income.

In my case, the numbers I used were simple:

At 62: $2,536 per month
At 67: $3,802 per month
At 70: $4,845 per month

That is the frame most people start with.

Take the smaller check earlier, or wait for the larger check later.

On the surface, this makes sense. If you can wait, you get more each month. If you live long enough, the larger payment can make up for the years you did not collect.

That is the standard break-even conversation. It is useful, but it is not the only question.

The standard comparison treats Social Security as income only. You receive it, spend it, and attempt to compare lifetime totals.

But what if the early income is not spent? What if it becomes an asset?

I wanted to see what happened when that assumption changed.

What I Was Really Weighing

The deeper question was not only whether I should take Social Security at 62.

The deeper question was whether waiting meant placing more trust in a future promise than I was comfortable placing there.

I kept coming back to that.

A larger future payment sounds better, but it is still a future payment inside a system I do not influence. Rules, tax treatment, retirement ages, and formulas can change. None of that means I know what will happen.

It simply means the promise is not the same thing as an asset already in my care.

I could feel the difference between those two things.

Because if I take the smaller check early and spend it, then the conventional analysis probably holds. I received less per month, and I have to compare that against what I might have received by waiting.

But if I take the smaller check early and do not need it for living expenses, the comparison changes.

Now I am not only comparing income streams. I am asking whether present cash flow can become capital.

The Bitcoin Dollar-Cost Averaging Thought Experiment

For this first pass, I kept the model simple.

I assumed I took Social Security at 62 and invested 100% of the monthly payment into Bitcoin.

The monthly amount was $2,536.

I looked at two cases.

Case 1: Invest the full monthly payment from age 62 to 67. At 67, stop investing. From that point forward, receive Social Security normally and allow the Bitcoin balance to compound until age 90.

Case 2: Invest the full monthly payment from age 62 to 70. At 70, stop investing. From that point forward, receive Social Security normally and allow the Bitcoin balance to compound until age 90.

For the Bitcoin growth assumption, I used an 18% compound annual growth rate.

That number is not a guarantee or a forecast. It came from looking at Bitcoin through a rolling four-year CAGR lens and pairing that with the drawdowns required to hold it.

That pairing matters. Bitcoin can show strong long-term growth and still make the ride extremely uncomfortable. A return assumption without the drawdown reality is not honest.

So the thought experiment was not, “What if Bitcoin goes up forever in a straight line?”

It was more grounded than that.

What if Bitcoin continues to compound over a long enough period, but the person holding it has to tolerate the volatility that comes with it?

What the Numbers Showed

The first case was the one that caught my attention.

If I invested $2,536 per month from age 62 to 67, the contribution period produced a six-figure Bitcoin balance. The part that surprised me was what happened next: if that balance was left alone to compound until age 90, the modeled result was in the millions.

That surprised me. I expected the result to be meaningful, maybe hundreds of thousands of dollars.

It was not.

It was millions.

The number did not give me an answer. It changed the question.

The second case pushed the question even further. If I kept investing the age-62 Social Security amount until 70, the modeled result grew larger still.

Again, that does not tell me what will happen. It shows how sensitive the result becomes when early income is converted into capital and given time to compound.

I kept sitting with that.

The normal Social Security question asks how much income I will receive while I am alive.

I started wondering whether some of that income could become something that remains after I am gone.

When the Math Became a Lineage Question

At first, I thought I was looking at a retirement decision. Then the numbers pulled me somewhere else. The math stopped being about retirement and started being about lineage.

The next question was very practical.

What if I do not need that income to live on?

If the money is not needed for monthly expenses, then it does not have to disappear into monthly consumption. It can be redirected. It can be held. It can be structured. It can become part of something larger than my own retirement.

Social Security was designed as income. It arrives monthly. It helps support a person while they are alive. For many people, that is exactly what it needs to do.

But if someone does not need the early payment for living expenses, and if they have the discipline and risk tolerance to invest it, the income can become something different.

It can become capital, and capital behaves differently than income.

Income supports you while it comes in. Capital can keep working after the income stops. If structured well, capital can be passed on.

That made me pause.

The Social Security question I had been wrestling with was not only about my monthly check.

It was about whether I could take a government income stream and convert it into an asset that might outlive me.

I could feel how different that question was.

Where I Have to Be Honest

I want to be careful here, because the assumptions matter.

Bitcoin may not compound at 18%. Social Security rules may change in ways that matter, or they may not. Taxes, cost-of-living adjustments, Medicare premiums, inflation, sequence risk, custody risk, and large drawdowns belong in a fuller analysis.

A person’s actual life belongs there too.

Health, cash flow, family circumstances, debt, risk tolerance, and the need for monthly income all matter.

A spreadsheet cannot hold all of that.

This is not investment advice. It is not a retirement recommendation. It is not a claim about what Bitcoin will do or what Social Security will become.

It is a thought experiment, but it showed me something I had not seen as clearly before.

I thought I was deciding when to take Social Security.

I was really asking what could remain after me.

There was a moment after I took my big corporate job at Microsoft that I realized there was something beyond money. It was one early morning when I was carting a stack of large three-ring binders to a conference room. On the other side of that door was Bill and the Office of the President (BOOP). My manager met me outside to accept the binders I had spent the previous night assembling in the campus copy center. My manager then said, “Do you want to come in and listen?” I said, “Sure.” What transpired from that point, I’ll never forget.

I was a fly on the wall. I looked around the room and I saw all the other flies. This was a meeting of who's who in the company and a gathering that set the future direction for the next year and beyond. In the center of this room was a big conference table. There were Bill Gates, Mike Maples, Steve Ballmer, and Frank Gaudette, and all the other lieutenants of that day. I was nervous, fascinated, and curious.

Two levels away was the man who ran the Enterprise Customer Unit, or ECU. He was at the table. Let’s call him John. John was the coolest cat that I’d ever seen. So many of us were in our thirties, but this guy may have been in his late fifties, early sixties. I’d seen him at conferences, sales meetings, and customer pitches. This guy was smooth.

As I was holding up the wall, I looked over and it was John’s turn to duel with Bill. Standing there, I felt really good, considering all the work that I had done compiling the data for our customer unit, preparing it, and getting it there on time. Doing an all-nighter was a badge of honor in those days. I helped hand out the binders and then the questioning began. To my dismay, the binders weren’t even opened. Here was Bill with one question after another about deep nuances of the ECU. Everyone at that table was extremely bright and it wasn’t about how much you knew. It was about seeing through the data to have actionable insights and almost predict the future. Bill was playing chess. I glanced at John, and there was a bead of sweat on his forehead. This guy was the smoothest I knew and somehow, he was nervous.

I had to think about that for a while. I’m looking at a table that has a combined net worth of billions of dollars. And this was in the mid-90s. I thought to myself, “What’s going on here?” It was like a beam of light that came in. In that moment, I realized this had nothing to do with money. You couldn’t buy a seat at this table. And it was the only seat to have at this time in the industry.

Something that was more than money — a concept I hadn’t yet considered. What does life look like beyond money? And what if it’s not about money?

For the group at that table, it was a little bit about money, but way more about power and control. I had mixed emotions about this. You mean it’s just not about working hard, doing your best, and being recognized for what you’ve done? I’ve got to consider things like power, influence, and control to get ahead in my vocation. Something was not adding up. I didn’t have language for it yet, but what I was watching was the system working exactly as designed — for the people already at the table.

I also thought a lot about safety and security. If any one of those people at the table left the company, they’d have a pretty big nest egg to be able to take and have a cushion to do something else with. Not so much for me. I had my fair share, but there were vesting schedules. Each time a grant occurred, it added another four years. I can’t tell you how many people had spreadsheets and looked at their vesting schedules quarter after quarter trying to figure out what their exit strategy would be once they got to their self-prescribed milestone. Everyone knew we couldn’t continue at the pace we were keeping. And who wanted to be someone that wasn’t on the fast track, who took some normal job inside the company and sat quietly vesting? Well, I certainly didn’t want to be that person, and it was the biggest monetary mistake of my life as I left in a fit of anger, six months after taking this job. I made it almost eight years and I was relieved to be out of there.

For years after, I looked at my vesting spreadsheet and what could have been. The millions, then tens of millions of dollars, staring me right in the face. In today’s terms, more than a hundred million. It ate at me, and the anger grew. A year later after quiting, I tried to get a field job back, along with my prior stock option grants, but at that point it was too late. I realized I was chasing the past.

As I was climbing the corporate ladder at Microsoft, the makeup of the people who were hired changed. They were a bit older and had solid experiences in the industry. When I looked in their eyes, they knew the kind of opportunity ahead of them and they were very grateful for it. I told my friends all sorts of stories about the company’s coming demise. I didn’t realize it was just a reflection of what was going on inside me. I was scared, confused, and angry. I didn’t have the business maturity to understand what I had in my hand. And my actions showed it.

I look back now and I’m grateful for the experience because at that time I wasn’t ready for that type of money. I think it would have fed my self-centered, egotistical, and materialistic tendencies and turned me deeper against myself. Something I wouldn’t start to address until many years later.

We’re all asking the same questions, and most of us are carrying around the same issues. For a long time, I beat my head against the same wall and expected something to change. It didn’t, until I got curious. The more I studied macroeconomics, really studied it, the more the pieces started coming together. That curiosity is the foundation of this work. What follows are five truths I’ve arrived at through my own life — through the work, the losses, and the years of study. Take what’s yours. And if any of it resonates, stay close. There’s a lot more coming.

TRUTH ONE — THE SYSTEM WAS BUILT THIS WAY

Do you ever notice that you’re working harder than you used to, and somehow it feels like you’re falling further behind? That’s not your imagination or bad luck. That’s the system working exactly as it was designed to.

For years I was angry. Angry at the government, angry at the political process, angry at a set of rules that seemed to apply to me but not to the institutions around me. What took me a long time to see is that the system wasn’t broken. It was doing exactly what it was built to do. It just wasn’t built for me. Or for you.

When you hear the word inflation, you probably think about prices going up. But inflation isn’t a weather pattern or an accident. It’s what happens when the government creates more money and each dollar you already hold buys a little less. That’s a direct consequence of how the monetary system was designed.

Inflation is a hidden tax, one you never voted for and never agreed to, and it’s been happening your entire life.

You’ve probably heard that two percent inflation is normal. Healthy, even. Did you ever wonder where that number came from? It was made up. The government carries debt, and inflation makes that debt cheaper to pay back over time. The two percent target exists to serve the system.

When money gets printed, it goes to the banks first. They make their investments and buy their assets before prices rise. By the time it filters down to you and me, we see very little of it directly. Remember COVID? You got a check, and so did I. But the banks got their own checks too, much larger ones, and they got them first.

The people closest to the money benefit the most. The people furthest away feel the inflation without seeing the benefit.

The system wasn’t broken. It was built this way. And once you see it, you can’t unsee it.

TRUTH TWO — PRIVACY IS DISAPPEARING

I’ve been in software long enough to remember when terms and conditions first appeared, and I dismissed them completely. Legal muckety muck, I told myself. Doesn’t really mean anything.

It meant everything.

The old saying is: if you’re not paying for the product, you’re the product. I watched it happen in real time as people uploaded their photos, their locations, their relationships, and their opinions and handed all of it over without reading a single line of what they’d agreed to. I wasn’t immune. None of us were. The trade was convenience for privacy, and it was made so gradually, so reasonably, that most people didn’t feel it happening.

Then 9/11 hit. Legislation passed quickly, in a moment of fear, with provisions that were never repealed. We moved on. The legislation didn’t.

Each step came with a justification. Cameras at intersections because people run red lights. Blue lights in parking lots for your safety. KYC and AML requirements at every financial institution to prevent money laundering. And for every one of these, I am the law-abiding citizen. I did nothing wrong. And yet I find myself explaining to my own bank why I want to withdraw my own money.

Think about that for a moment. Your money, your account, your decision — and you need to justify it?

Here’s what financial privacy actually looks like: if I hand you $20 in cash, nobody needs to know why. That’s the whole thing. And that’s exactly what’s disappearing.

The next step is already visible. Programmable money. Stablecoins that represent the dollar but live inside a system where the rules can be written and rewritten by whoever controls the platform. Today it’s private institutions, but those institutions are regulated, and we already know what happens when regulations tighten. Chokepoint 2.0 wasn’t a hypothetical. It was the second attempt by the government to cut off banking access to businesses they didn’t like. It happened.

So when the people in charge of the money decide they don’t like a particular behavior, and they have the technical ability to control it, what do you think they’ll do?

TRUTH THREE — THE FRACTURES

I grew up on the lower side of what economists now call the K-shaped economy. I didn’t know that term then. I just knew that certain people seemed different, with different concerns, options, and access to things I couldn’t quite name.

For a long time I assumed it was hard work since that’s what my dad etched into my beliefs. That the people ahead of me had just put in more time, made better decisions, and earned what they had. But the more I studied money, really studied it rather than just read the headlines, the more I understood that hard work was only part of the story. There was a different system available to people with resources, not illegal, not exactly hidden, just different. And most people don’t know it exists.

The K-shape economy works like this. Asset holders go up. Everyone else goes sideways or down. When the government prints money, as we talked about in Truth One, it flows to the banks and financial institutions first. Those institutions buy assets. Asset prices rise. If you already own assets, your net worth climbs. If you don’t, the prices of the things you’re trying to buy — a house, an investment, or a business — just got further out of reach. The monetary system creates this inequality by design.

I don’t have a problem with people being billionaires. I want to be clear about that. If someone generates tremendous resources through their work and their ideas, that’s theirs. What I have a problem with is a system designed to benefit only those who already have. I have a much bigger problem with a system that can be purchased.

Look at the lobbying laws. Look at campaign contribution rules. Look at the Supreme Court rulings that opened the door to dark money, unlimited political spending funneled through nonprofits that aren’t required to disclose who funds them. What that adds up to is simple: if you put enough money into the right places, you can buy the legislation and regulation your company or industry needs. Tax incentives get written by the industries they benefit. Trade policy gets shaped by the companies most affected by it. That’s not a free market. A free market follows opportunity. What we have follows whoever can afford to write the rules.

Now add the polarization on top of all of this.

Both parties print money, both parties spend beyond their means, and both parties preside over a financial system that benefits people closest to the money. The inflation was the same. The spending was the same. The K-shape kept widening under every administration.

But we’re not talking about that. We’re talking about each other.

I’ve taken the bait myself. I know what it feels like to be certain that the other side is the problem. What I’ve come to see is the social issues that divide us, and they are real, I’m not dismissing them, are also extraordinarily useful to the people who benefit from us not looking at the monetary system. Angry people fighting each other aren’t following the money. And the money is where the answers actually are.

Here’s a thought I keep coming back to. If this country were required to balance its budget by law, we’d probably go to war a lot less, because then we’d have to make an actual decision about whether something is worth spending more than we take in. That would have to go through a real legislative process, and it would change everything. But neither party talks about that anymore, because the current system works for the people who designed it.

That’s not a country by and for the people.

TRUTH FOUR — LINEAGE

My father gave me his name, though it took me years to understand what that actually meant. I knew there was a significance to it my entire life, and I knew my family was guiding me towards something. Heritage matters, culture matters, and where you come from matters. And someone has to carry it forward.

My father didn’t leave me financial assets when he died. He had his own business, and to me he was the most successful person I’d ever known because he built something from nothing and used it to support his family. What he left me was a work ethic and a principle he repeated so often it became part of me: your word is your name. Do what you say you’re going to do. Be honest. Show up.

That’s lineage. Not a dollar amount. A way of being in the world.

A few years ago, I started putting a will together. I wanted to think seriously about what I was leaving behind, personal property, digital assets, and things that hold and grow value over time. What I found was that there’s almost no roadmap for this. Very little precedent for digital assets in estate planning, a lot of guesswork, and professionals charging a very large hourly fee to navigate uncertainty alongside of you. If you’re on the upper side of the K-shaped economy, you probably have attorneys who handle this without you having to think about it. For everyone else, figuring out how to pass something real to the people you love is largely a mystery.

And yet most of us want the same thing. We want our families to have a better life than we did. How many times have you heard someone say this is the first generation in our family to: go to college, start a business, or have enough to actually raise a family without counting every dollar. That’s lineage in practice, one generation handing the next a slightly better starting point.

What I want to leave is access to opportunity. Not dependency. I’ve seen what happens when people are handed everything and never have to build anything themselves. What I want is to give someone a leg up, to ease the financial burden enough that they can step into whatever dream or vision they have for their own life. That’s different from a handout.

I also want to leave behind who I was. A record of what I believed, how I got here, and what I learned along the way, so that the people who come after me, especially my family, can know me beyond the stories that get told at family get togethers. This project and writing it down is part of that.

Wealth is more than money. Money is a component, an important one, but wealth is the full integration of the sovereign individual, the internal and the external working together. Someone doesn’t need a lot of money to live well in this world. What they need is the clarity to know what they actually want, and enough of a foundation to go after it.

That’s what I’m trying to build and leave behind.

It’s not a handout. It’s a help out.

TRUTH FIVE — SOVEREIGNTY

For most of my life, I believed the world was organized against me, not in some vague abstract way, but personally, specifically. There was a system, a group, or a force that had decided Robert Jordan Jr wasn’t going to make it, wasn’t going to get ahead, and wasn’t going to have the relationship, the life, and the freedom he wanted. I couldn’t have told you who they were. But I felt them everywhere.

And my response was to fight, every time, scorched earth. There was going to be blood on that battlefield, and it wasn’t going to be mine. When I was done, I cleared the surface to make sure nothing could come back at me. That was the strategy. It worked, in the way that survival strategies work, until it didn’t.

What I eventually came to understand is that nobody was coming for me. There was no conspiracy, no group consciously pulling levers against Robert Jordan Jr. The war I was fighting wasn’t with the world. It was with myself. And I had been losing it for decades.

The anger was never the real thing and was only the top layer. Underneath it was something much older and much simpler: I didn’t feel safe. I hadn’t felt safe since I was young, when I was longing for a love and a security from my parents that I didn’t experience the way I needed to. I carried that longing into every relationship, every room, and every confrontation. And when you don’t feel safe, your nervous system does what nervous systems do. It picks a response. Mine picked fight, every time.

Drinking starting at fifteen wasn’t a choice. It was a solution, the only tool available to a kid whose emotions felt too big to survive. I genuinely believed that if I actually felt what was underneath the anger, it would kill me. So I didn’t feel it. I left. Dissociation is what happens when the feeling is too much and there’s no safe place to take it. Your body is present but you are somewhere else entirely. For most of my life, I was somewhere else entirely.

The work of changing my internal life happened in two stages, and you need both.

The first stage is the mind. Talk therapy, one on one with someone trained to help you open up and say what you’re actually feeling. The most important thing that happened in that room wasn’t insight. It was realizing I wasn’t alone. I had spent years convinced that I was the only person experiencing what I was experiencing, broken in some specific way that separated me from everyone else. Finding out that wasn’t true took an enormous amount of pressure off. I understood for the first time what was happening inside me, what was causing it, and what I could do differently.

But the mind only goes so far. Because the reaction, the fight response, the scorched earth, that wasn’t happening in my head. It was happening in my body, in my chest and my jaw and my hands. You can understand something completely in your mind and still have your body run the old program the moment something triggers it. The second stage is somatic work. Breathing and movement, being in nature, sleeping well, eating in ways that support your system rather than tax it, and learning, slowly and with a lot of practice, to be present inside your own body instead of leaving it every time something difficult arrives.

What I found on the other side of that work is hard to put into words. There’s a difference between doing and being that most people never experience, because we spend our entire lives doing. Moving through the day, working the job, running the errands, and showing up for the communities we’re part of. Doing is necessary. But being is something else entirely, a felt sense, a groundedness, and the deepest centering I know how to describe. In those moments, nothing matters and everything is okay. Not performed okay. Actually okay.

I used to wear masks. A professional one, a personal one, a version of myself for every room I walked into. I told myself that was just how it worked, that you showed different faces in different contexts. What I understand now is that I was managing and presenting the version least likely to get hurt. The inner work dismantled the masks one by one until there was just one person, the same in every room. Emotions still come up and they always will. But now I know that whatever is happening outside of me is a reflection of what’s happening inside. When I’m triggered, that’s mine. I don’t need to make it someone else’s problem or project it onto them.

That’s sovereignty. Not a financial strategy. A way of being.

You cannot build a sovereign life on an unexamined foundation. Someone who hasn’t done the inner work will recreate the same broken patterns inside a better financial system. The money changes but the person doesn’t. And it shows.

This work is not for the faint of heart. You will get your ass kicked. You will go to places inside yourself that hurt in ways you couldn’t have predicted. The strongest people I know have gone there, not Navy SEALs, though every bit as strong and possibly even more courageous. What they found, and what I found, was a peace and a presence inside their own body. A love and a compassion for themselves that allowed them to look at a situation and decide how to respond rather than react. And the funny thing is that the relationships that were the hardest, the ones I was convinced were the problem, those challenges started to disappear the moment I changed.

Choosing a better system is an act of integrity. There are two systems at play, and both are yours to build. The external one is the financial tools, the assets, and the infrastructure designed to serve your interests and your family’s future. The internal one is the long, uncomfortable, and necessary work of becoming someone who knows who they are.

The financial system you choose and the person you’re becoming are not two different projects. They have always been one. And that project starts with you.