First versions: markers, battles, and an economy that HAD to be honest.

The first working build of HoldSPOT was embarrassingly small: a map, a crosshair, and a marker you could drop. No battles, no tokens—just the claim. Yet the people we asked said it was useful to have a sticky note on a map, but there are so many apps that do that: Obsidian with Place Notes plugins, StickyWorld, Note2Map, to name just a few. One friend said, "What if markers could battle each other? There is always much to say about a place or a public thing". That is when we knew the core loop was right: placing a thing on a map that others can contest is already a game.

When health became visibility.

Battles came next. We rejected hit points and armies: in a game about attention, your marker's life is its visibility. Every fight moves visibility from one marker to another. Sink to zero, and your spot dies—the marker is erased and the territory opens again. Brutal, legible, and perfectly on theme. But how could we do that on a map so large and so small at the same time? Icons would clutter when zoomed out and become impossible to click when zoomed in; the real-world map is HUGE, and this is not a game about zooming—it is about icons. That is when a beautiful and logical idea took shape. We transformed a problem—markers clutter when zoomed out—into our advantage: we moved the battle into z-index. Marker life—visibility—became a value on the z-axis. You may see the marker on x/y, but what truly defines visibility is how it manages to crawl to the top of the z-axis when overlapping.

Three tokens, one ledger.

From here, it was easy. The game needed a reward loop, so the economy arrived: Liquidity for trading, Value for worth, Engagement for presence. The important decision was not the tokens themselves—it was the rule that every single token movement lands on one public ledger. Balances are never edited directly; they are always the sum of the ledger. When the numbers disagreed, we fixed the invariant, not the balance. That was the most logical step into a real economic world: our world.

What broke us, and what it taught us.

Early versions had faucets everywhere: resets handed out fresh tokens, bots bid absurd prices, and a generous exchange could mint money from nothing. Each hole was found the honest way—by auditing the ledger and watching it not add up. The fixes shaped the whole design: resets grant nothing—the faucet closed for good; bots trade with capped wallets—no more junk-bid farms; a system reserve now backs the bank, the exchange, and the loans—rates fall when it is empty, and when empty, it refuses. The sky cleared and all the problems disappeared; we have slept well since then. :)

The REAL utility—SCALES.

In every project's life, there is a moment when you HAVE to ask a question: Will this work? Will people find it useful? So we made a small review of what we had so far:

• a new way to have sticky notes on a real-world map
• an MMORPG-like battle system with an ability tree, items, and quests
• analytics everywhere for people who love crunching data and numbers
• a new way to act in an economy that is balanced and most important IS without worrying about cheating, fraud, fragility, and debt.

In a place like this, the next project came together like fitting a Lego piece as the final part of a great work: we started working on SCALES—a very small project management system that could reward/constrain authority based on randomized, blind judges in order to audit history, trade-offs, technical risk, or long-term consequences. SCALES should align authority with accountability and competence, and make decision criteria transparent. Because it already measures outcomes, it can feed lessons back into the system and be used to create an accountable, learning-oriented system that consistently creates value.

By summer, the game finally matched the sketch: anonymous markers, visibility battles, and an economy whose heartbeat—mint, spend, escrow, refund, project—you can read like a receipt.

WHAT ELSE could we implement next week?