The Fortress Ledger
Experiential design logs and iteration notes from Cloud Fortress
PROJECT LEDGERS
the foundation
This ledger exists to document real work.
Not polished announcements, not marketing beats, and not hindsight summaries—but the actual process of building things: the decisions, the revisions, the dead ends, and the moments where something finally clicks. The Fortress Ledger is meant to be a public record of progress as it happens, logged honestly and without a fixed schedule.
I’m a solo developer and designer working under Cloud Fortress. My approach to building games and systems starts from the inside out. I don’t begin with feature lists or abstractions—I begin by living inside the experience. I try to inhabit how something feels, how it moves, how it breaks, and how it holds together before it ever becomes formalized. From there, the work becomes about pulling that experience out into something real and then refining it until it can stand on its own.
That process—experiential design followed by iteration—is the throughline of everything recorded here. Ideas don’t arrive fully formed. They’re tested by externalization, challenged by reality, and shaped through repeated passes. Some survive. Some don’t. This ledger exists to make that visible.
Right now, the focus is on two parallel efforts. The first is finalizing a Champion Spotlight for Varonis, a complete, focused artifact intended to demonstrate execution, clarity, and follow-through. The second is the early groundwork for GARRISON, beginning with a tightly scoped Phase 1 designed to prove the core identity of the project before anything else expands.
Work on these projects happens in what I refer to internally as The Forge—the place where ideas are stressed, reshaped, and iterated on until they either hold or fail. What comes out of The Forge is what gets logged here.
Entries in The Fortress Ledger won’t follow a strict cadence. Updates will appear when meaningful progress is made, when decisions are locked, or when direction changes. The goal isn’t consistency for its own sake—it’s clarity over time.
Everything after this builds on what’s laid here.