Soul OS: Your Personal Operating System for Life Decisions

1. The Moment I Realized I Had No System

It was 2023. The accelerator I had co-founded — iiinno — was in a period of deep uncertainty. We had portfolio companies that needed guidance, team members who needed direction, and investors who needed confidence. Every day was a cascade of decisions, each one feeling like it had consequences I couldn't fully calculate.

One afternoon I was sitting in a meeting room in Hsinchu, and someone asked me a simple question: "What do we do when two of our portfolio companies need the same resource at the same time — and we can only help one?"

I opened my mouth. And nothing came out.

Not because I didn't care — I cared enormously about both companies. Not because I didn't have opinions — I had plenty. But because I had no system for resolving that kind of conflict. I was operating purely on instinct, case by case, mood by mood. Every decision was made fresh, from scratch, with no reliable framework underneath it.

The result was that my decisions were inconsistent. Sometimes I prioritized the company with the stronger team. Sometimes I prioritized the one with the bigger market. Sometimes I prioritized whoever had asked first. And sometimes — if I'm being completely honest — I prioritized whoever I felt guiltiest about letting down. That last one is the worst kind of decision-making there is.

That realization was the beginning of what I now call the Soul OS.

It took about two years to build — through the accelerator's collapse, through my own business failures, through reading and reflecting and getting things wrong in new ways. But I now have something I didn't have then: a system. An internal navigation tool. A set of rules that runs in the background of every decision I make, so that my choices are consistent, coherent, and recognizably mine.

This post is the complete breakdown of that system — all four layers — so you can build your own.

2. What Is Soul OS — And What It Isn't

Your phone has iOS or Android. Your computer has Windows or macOS. These operating systems don't tell your apps what to do — they provide the underlying environment in which apps can run. They manage resources, resolve conflicts, enforce security, and make sure everything works together.

Your life needs the same thing.

Without an operating system, a computer is just silicon and metal — capable of nothing. With the wrong operating system (or a corrupted one), even powerful hardware produces garbage. The most capable, intelligent, experienced person in the world will make inconsistent, self-defeating decisions if they don't have a coherent internal system running underneath their choices.

Soul OS is that system. But let me be precise about what it is — and equally precise about what it isn't.

Soul OS is NOT:

• Religion or theology — it doesn't depend on any belief system and works regardless of your spiritual background
• Philosophy — it's not a body of ideas to contemplate; it's a framework to apply
• Motivational self-help — it doesn't tell you to "believe in yourself" or "think positive"
• A personality type system — it's not about categorizing who you are; it's about deciding what you'll do
• Fixed or universal — your Soul OS is built from your values and experience; mine won't be the same as yours

Soul OS IS:

• A practical decision-making framework built on your specific values
• An explicit set of rules that you've chosen, rather than absorbed from others
• A conflict-resolution system for when your values are in tension with each other
• A relationship protocol that defines how you interact across different types of relationships
• A living document — it updates as you learn and grow

The "soul" in Soul OS refers to your core identity — the values and principles that make you recognizably you, independent of context or circumstance. Not a religious concept. A human one.

Here's how I think about it: most people's anxiety doesn't come from too few options. It comes from having no criteria with which to judge the options they have. Soul OS gives you the criteria.

3. Layer 1: The Values Layer

Every operating system has a kernel — the core process that everything else depends on. For Soul OS, the kernel is your Values Layer. This is your list of non-negotiable principles: the things you will not compromise regardless of circumstance, social pressure, or financial incentive.

I want to be honest about how hard this layer is to build correctly. Most people, if you ask them their values, will rattle off a list of respectable-sounding words: "honesty, integrity, family, growth." Those words mean almost nothing without specificity. They're aspirations, not values. A value is only real when it's been tested.

Here's how I identified my actual values — not the ones I wanted to have, but the ones that showed up in my decisions when things got hard:

I looked back at the moments in my life when I had acted against what I believed — when I had said yes to something that felt wrong, or stayed in a situation I should have left, or said something I didn't mean. And in each case I asked: what did I value more than honesty/integrity/whatever in that moment? What did I choose instead?

In most cases, the answer was: I chose approval. I chose peace. I chose the path that avoided someone else's discomfort. And when I saw that pattern clearly, I realized my stated values ("integrity," "honesty") were not my operational values. My operational values were "avoiding conflict" and "keeping people comfortable." I had been running on a corrupted kernel.

My current kernel values, written operationally:

• Honesty over comfort: I will say what is true, especially when it's difficult. I do not trade accuracy for approval.
• Responsibility over blame: When something goes wrong, I ask what I could have done differently before I ask what someone else did wrong.
• Long-term integrity over short-term harmony: I will accept temporary discomfort in a relationship rather than suppress a truth that will create bigger problems later.
• Action over planning: I will ship something imperfect before I perfect something unshipped. Done beats polished.

Your kernel values will be different from mine. That's the point. A Soul OS is built on your actual values — not on what sounds admirable.

4. Layer 2: The Boundaries Layer

If the Values Layer is the kernel, the Boundaries Layer is the security system. It defines the rules for how you interact with the world — what you will absorb, what you will decline, and where your responsibility genuinely ends.

I wrote at length about boundaries in Why Kind People Fail. Here I want to go deeper into how boundaries function as a system layer rather than as individual rules.

The problem with most people's approach to boundaries is that they're reactive. You set a boundary after someone violates one. You write a rule because you got burned. This is how you end up with a list of disconnected prohibitions that feel arbitrary to everyone around you — including yourself.

In Soul OS, boundaries are derived from values. Each core value implies a set of natural limits. Once you know your values, your boundaries follow logically.

One of the most important boundaries I've added to my Boundaries Layer after the accelerator experience: I will not absorb financial risk that belongs to another party, even in service of a shared goal. This sounds obvious now. It was not obvious to me for 23 years. I kept treating shared financial risk as something I should personally underwrite in order to protect the partnership. The result was that the partnership survived longer than it should have, at my expense, and the eventual collapse was worse than it would have been if I'd been honest about limits earlier.

5. Layer 3: The Decision Engine

With your kernel values and your derived boundaries in place, you now have the ingredients for a Decision Engine — a lightweight checklist you run through whenever you face a meaningful choice.

The Decision Engine isn't about overthinking every small decision. Most daily choices are trivially easy and don't need a framework. The Decision Engine is for the decisions that actually matter: who to work with, what to commit to, how to respond to a difficult situation, whether to say yes or no to a significant ask.

Here is my current Decision Engine — the five questions I run through when a decision feels difficult or important:

This checklist takes me about 90 seconds when I use it consciously. For most decisions, I've internalized it enough that it runs automatically. But having it written down means I can return to it when I'm in an emotionally charged situation — when my instincts are being distorted by anxiety, guilt, or someone else's urgency.

The last question — "Am I deciding from fear or from values?" — is the one I added most recently, and it's become the most important. It was the answer to a pattern I kept noticing: I could identify the right decision using questions 1-4, and then still make the wrong choice because of some fear I hadn't named. Fear of disapproval. Fear of conflict. Fear of being seen as difficult. Those fears don't appear in a decision framework unless you specifically check for them.

6. Layer 4: Relationship Protocols

The final layer is where Soul OS gets specific about the people in your life. Relationship Protocols are the explicit rules you apply to each type of relationship — what you will give, what you will ask for, what you will protect, and what you won't tolerate.

If you've read my post on why kind people fail, you know I use the 7 Roles framework: Coworker, Friend, Leader/Subordinate, Co-founder, Parent, Soulmate, and Self. Each role gets its own set of protocols.

Here's a simplified version of how this works in practice:

Relationship Protocols feel formal when you first write them. They're not — they're just explicit. And explicit is almost always better than assumed. The most painful moments in most relationships come from mismatched assumptions: you assumed you had one protocol, the other person assumed a different one. Writing it down doesn't remove all possibility of conflict — but it removes the version of conflict that comes from each person playing a completely different game without knowing it.

7. How to Install Your Soul OS

Here's the honest reality: you can't install a Soul OS in a weekend. You can start building it in a weekend. The installation happens over months and years, through decisions, mistakes, refinements, and the slow accumulation of lived experience that teaches you what you actually value versus what you thought you valued.

But you can make meaningful progress quickly. Here's the sequence I'd recommend:

• Week 1: Values audit. Do the retrospective exercise from Layer 1. Identify your actual operative values — not aspirational, actual. Write them in operational terms: "I value X, which means I will Y even when Z."
• Week 2: Boundary derivation. For each value, write the boundary it implies. Focus on the 2-3 boundaries you've most consistently violated in the past five years — those are the ones you need most.
• Week 3: Decision Engine. Adapt my five-question framework to your situation. Add questions that reflect your specific weaknesses. Remove questions that don't apply. Test it on three recent decisions — would it have guided you differently?
• Month 2: Relationship Protocols. Start with the two relationship roles that cause you the most friction. Write explicit protocols for each. Share them with the people in those roles if the relationship is close enough — the conversation itself is valuable.
• Ongoing: Review and update. Every three months, review your Soul OS. What held up? What needs refinement? What new values have emerged from experience? A Soul OS that never updates is one that hasn't been used.

I have a Soul OS worksheet that walks through each of these steps with specific prompts. It's free, and it's designed to take you from zero to a first-draft Soul OS in about three hours of honest reflection.

8. What Running on Soul OS Actually Feels Like

I want to be honest about this because I think a lot of self-development writing makes transformation sound cleaner than it is.

Running on Soul OS doesn't mean you always know what to do. It doesn't mean you stop feeling confused or scared. It doesn't mean every decision becomes easy.

What it means is that your confusion has a floor. When you're uncertain, you have something to return to. You know what your values are. You know what your limits are. You know what questions to ask. And so even when you don't know the answer, you're not completely at sea — you have a compass, even if the fog is still thick.

There's another thing it does that I didn't expect: it simplifies your life enormously. When you have a clear Decision Engine, you stop agonizing over things that were never actually decisions. You realize that certain invitations, certain requests, certain opportunities have already been decided — by your values and your protocols. You don't need to deliberate. You just check the system and the answer is there.

This matters more than it sounds. Decision fatigue is real. Every decision you make costs cognitive resources. When you have a Soul OS, a significant percentage of decisions become automatic — handled by the system rather than requiring fresh deliberation. That saves energy for the decisions that genuinely require it.

The last thing I'll say about what it feels like: it makes you more consistent. And consistency, over time, is what builds trust — with others, and with yourself. When the people around you know your values and your limits, they know what to expect from you. That's not rigidity; it's reliability. And reliability is one of the most valuable things a person can offer in a world where most people are making it up as they go.

9. Three Steps to Start Today

1. Write your obituary — the decision-making version. Imagine you're at the end of your life, looking back. What would you most want to be true about how you made decisions? That you were honest? That you protected the people you loved? That you built things that mattered? Write it down. That's the beginning of your Values Layer.
2. Identify your most expensive assumption. What assumption have you been operating on — about yourself, about relationships, about how the world works — that has cost you the most? That assumption is probably a corrupted value. Name it. Replace it with something more honest.
3. Pick one relationship and write its protocol. Don't try to do all seven roles at once. Start with the one relationship in your life that causes the most friction or confusion. Write one paragraph: what you will give, what you need, what you won't accept. That's your first Relationship Protocol. The conversation it prompts — with yourself, or with the other person — is worth more than any framework I can offer.