Why a game?

People who are drawn to this work are usually not looking for a game. They're looking for something quieter: a way back to themselves, a practice that holds, a life designed rather than defaulted. So it's fair to ask why a program built for that would call itself one.

The short answer is that a game is one of the oldest technologies we have for transformation. Long before anyone wrote a self-help book, communities built initiations, seasons, pilgrimages and rites of passage. Each one had the same shape. A threshold you crossed on purpose. A set of rules that held while you were inside. Stages you moved through in order. Witnesses. And a return, changed, to ordinary life. Strip the costumes off and what's left is a game: a bounded space with rules, where something real is at stake.

Rules are how a container holds

Most transformation attempts fail for a reason that has nothing to do with willpower. They have no walls. A resolution made alone, with no structure and no end date, is open on every side, and the world walks straight through it. The systems competing for your attention are designed with full knowledge of how the nervous system works, and they do not take a day off because you decided to change.

A game answers that with a container. The Catalyst Game runs thirty days, in a small private room of no more than seven people, with a manual you read before day one. There is one move a day and a pause on weekends. Those are not gimmicks. They are the walls. Inside them, the work can be small and honest, because the structure is carrying the weight your willpower would otherwise have to carry alone.

Sovereignty is a posture, not a declaration. Neither is change. — The Altitude, issue 012

Levels are thresholds

The map of the game has seven domains, travelled in order, from the most physical and foundational to the most integrated. Each one is a territory of a consciously connected life, and you move through them the way you would move through the rooms of a house you're rebuilding: foundation first, then the places you live, then the places you meet the world.

Between domains there is a save point. In game language it's where progress is kept. In older language it's a threshold: a moment to stop, take stock of where you actually are, and name it before crossing. You do that by rating yourself, honestly, on the domain you're leaving. Not to perform for anyone, but because a change you can see is a change you can trust.

Play is not the opposite of seriousness

There is a reason the daily prompts are written in a light, playful voice, and it isn't to make the work smaller. It's that play is the state the body does its best learning in. Joy is not the opposite of intention; it's intention at its most sovereign. A practice you dread is a practice you'll abandon. A practice that has a little delight in it, a little surprise, a mid-cycle guest you didn't see coming, is a practice you return to. And returning is the only thing that compounds.

What stands behind it

The game surface is deliberately simple. Underneath it is a framework I've spent years building, and it draws on more than one tradition. Contemplative and somatic practice, because the body was the original system and it still is. Established psychology, because there's no reason to reinvent what's already known about how people change. Philosophy old and new. And twenty years inside enterprise technology, watching how systems are designed to shape behaviour, and learning how to design them the other way.

None of that shows up as a lecture. It shows up as a prompt, a move, a save point, a pause. The methodology is rich; the days are light. That gap is the design.

So: why a game? Because a game is a container, and a container is what lets small, daily, unglamorous work become a real crossing. You don't have to think of it as a game if the word doesn't fit you. Think of it as a season. Think of it as an initiation with a clear beginning and end. The structure is the same, and it's built to hold.