I grew up shaped by structure and relentless work ethic, which wired me to see the world through systems and unfinished loops. As a child I could not imagine anything without explaining the origins beneath it, building worlds, rules, and architectures that always pulled me deeper. That instinct followed me into programming, school, and eventually my career. Kaamfu is simply the adult expression of the same loop, my lifelong need to understand and complete the underlying system.

---

I grew up in a working class family in Washington state, shaped by two parents who set the trajectory for how I exist in the world. My mom organized everything in labeled containers and neatly-sorted folders. She created environments where everything had a place, and that structure wired my brain around order, categorization, and coherence. My dad was relentless in his work ethic, pushing himself long past what most people could endure. From him I inherited the instinct to keep going and never abandon the things I start. Together they produced someone who studies the world through the lens of systems and unfinished loops.

My earliest memories are of me inventing imaginary worlds. But I could not simply imagine a character or a landscape without explaining the entire chain of events that produced it. When I was about six or seven, I started creating a fantasy world called “Maracia”. It was filled with warriors, wizards, factions, and geography, but all of that was secondary to the underlying logic. What mattered to me was the origin of all these beings. If a character existed, I had to know why. Who were their parents? How did the environment shape them? What rules governed the physics or the politics of their society? I needed the scaffolding before I could enjoy anything built on top of it, so there was the never-ending sense of things being incomplete because the backstory wasn’t finished.

When I was nine, I bought my first computer with my paper-route money and taught myself to program. The very first thing I built was a text-based dungeon for Maracia with its own chemistry, physics, and internal rules. That project should have been a game, but instead it became an exercise in architecture. Every time I built a function, I felt compelled to build the smaller functions underneath it, then the rules beneath those, and so on. I was never able to stop at the layer that everyone else considered “done” because I needed to understand the full causal chain, all the way down to the origin. Only then did anything make sense.

This tendency followed me everywhere. I could not play early computer games without creating a written backstory for why the world existed. I loved Sim City, a black-and-white game I played on the Macs at school. But instead of just building a town, I wrote a multi-page prelude about who the people were and why the city was founded. I needed meaning and mechanics before entertainment. Without it, I felt disoriented, as if I were floating inside a system with missing parts. Even something as simple as a button in a game like Myst bothered me. If I did not know who placed it there and for what purpose, I could not enjoy the interaction. I needed to close that loop in my mind before I could proceed.

These patterns became clearer when I look back at school. In seventh grade we had to invent an island and populate it with imaginary creatures. I think the point of the exercise was to grasp the concept of evolution in isolation. Most kids drew something quick and handed it in, but I spent days building the geological history of the island, the evolutionary pressures that shaped the creatures, the climate cycles, the food chain, and the ecological rules that kept it all in balance. It was many times the length I was asked to prepare, and when I turned it in, I felt embarrassed because I had revealed that I cared. After that assignment, I stopped pouring myself fully into school projects because I did not want to feel exposed again. But privately, I kept building worlds, maps, diagrams, and systems.

I remember playing Romance of the Three Kingdoms III and being captivated by its complexity, not because of the gameplay but because every non-player character had a name and a role in the unfolding story. I began journaling what each character was doing, building a running history so I could understand the larger system behind the scenes. Even though I knew they were simple algorithmic creations with interchangeable faces, I still needed to preserve the context so the world made sense to me.

My life became a long collection of open loops, each one waiting for me to return to it. Maracia is still there. The early text-based game is still incomplete. The notebooks from the 90s where I mapped out early versions of what would later become my work on autonomous systems are still stacked up in storage. I never stopped thinking about them because the loops were never closed. Even today, everything I create sits on top of a deeper architecture that pulls me backwards until the foundation feels right.

This compulsion shaped how I see business, technology, and leadership. I start everything from the ground up. I cannot build the surface of anything until I understand the underlying structure. For most of my life this felt like a handicap because it takes longer. It is heavier. It delays the moment of visible output. But what I eventually learned was that once the foundation is correct, everything above it accelerates quickly. The system becomes intuitive. The execution becomes fluid. And the whole structure begins to operate with a life of its own. It doesn’t need me anymore. That’s the point of everything I do: I need it to run without me.

My adult work is just an extension of what began in childhood. The fantasy worlds became architectures. The need for origins became system design. The obsession with closing loops became product philosophy. Kaamfu is, quite literally, the same project I began when I was seven. It is my attempt to understand the full cycle of work, to explain why each part exists, and to build something that eventually operates without me. It is my way of completing the loop.

I assume that most people outgrow the obsessions they had in childhood, but I never did. I am still building the same world, the same engine, the same structure. And I suspect I always will be. Not because I am chasing a result, but because this is simply how my mind works. Every open loop in my life is a story waiting to be finished. And every system is an origin waiting to be revealed.

…