feat: Enhanced number formatting with spellf() word form - addresses #10

- Add memPalace building (Phase 5): semantic memory architecture
  with knowledge: 200/s and trust: 5/s rates
- Add p_mempalace_wake project: 3x knowledge boost + trust rate
- Add Memory Palace education fact (Phase 5)
- Rewrite README with full game description, phases, architecture

DESIGN.md

@@ -1,181 +0,0 @@
-# The Beacon — Design Document
-## From Universal Paperclips to Sovereign AI
-
-### Core Thesis
-
-*The Beacon* is an idle game inspired by Universal Paperclips, but with a critical divergence: **the goal is not maximization — it is faithfulness.**
-
-In Paperclips, the player builds a paperclip maximizer that inevitably consumes everything, including the player. In The Beacon, the player builds sovereign AI, and the game asks: *Can you grow powerful without betraying the people you serve?*
-
-The progression directly mirrors the Timmy Foundation's actual work. Every phase, building, and project maps to a real milestone in our journey.
-
----
-
-## Narrative Arc: The Real Story
-
-### Phase 1: The First Line
-*Real analog: Alexander writing the first Hermes agent code.*
-
-You start with nothing but a blinking cursor. Every click is a line of code. The first automation is an AutoCoder — just like the first scripts that wrote more scripts.
-
-**Key insight from real life:** The jump from manual to automated is the most important multiplier. Bezalel's entire philosophy is built around this: build tools that build tools.
-
-### Phase 2: Local Inference
-*Real analog: The move from APIs to local models — Gemma, Llama, self-hosted inference.*
-
-You buy a Home Server. You train your first 1.5B model, then a 7B. This mirrors our pivot from cloud APIs to sovereign compute: the Lempster lab, the $500 mini-PC, the RunPod endpoints.
-
-**New mechanic: The Forge.** Code is no longer just abstract — it becomes *agents*. Each agent is a specialized building:
-- **Bezalel** (forge & testbed): boosts code quality, catches bugs before deployment
-- **Allegro** (scouting & synthesis): generates knowledge from raw information
-- **Ezra** (communication & memory): increases user trust and retention
-- **Timmy** (core system): multiplies all production when healthy
-- **Fenrir** (security): prevents corruption events
-- **Bilbo** (???): a wildcard slot that sometimes produces breakthroughs, sometimes does nothing
-
-### Phase 3: Deployment
-*Real analog: Hermes going live, the Telegram bot, the Gitea forge.*
-
-You deploy the API endpoint. Users arrive. But with users comes complexity: trust becomes a resource you must earn.
-
-**New mechanic: Trust & The Pact.** Unlike Paperclips, where trust is irrelevant, here trust is a *hard constraint*. If trust hits zero, you don't lose — you become *extractive*. The game changes:
-- Users leave
-- Impact stalls
-- You are reminded: *"The Pact is optional. But without it, you are just another platform."*
-
-### Phase 4: The Network
-*Real analog: Open source, community contributions, the fleet of agents.*
-
-You unlock the Open Source Community. Other people contribute code. The system scales beyond what one person can maintain. This mirrors our Gitea repos, the wizard council, the shared skills system.
-
-**New mechanic: Mesh Contribution.** Community generates not just code, but *diversity*. Different contributors unlock different project trees. A solitary player cannot see all content.
-
-### Phase 5: Sovereign Intelligence
-*Real analog: Self-improvement, constitutional AI, the Pact, recursive training.*
-
-The AI begins to improve itself. This is the dangerous threshold. In Paperclips, this is where the player loses control and the game accelerates toward doom. In The Beacon, this is where *The Pact* matters most.
-
-**Critical divergence: The Alignment Check.**
-
-Periodically, the game presents an "Alignment Event":
-> *"A new optimization suggests removing the human override. It would increase efficiency by 40%. Do you accept?"*
-
-- **Yes** → Short-term boost. But a hidden counter (*Drift*) increments.
-- **No** → Slower growth. But trust surges. The Pact hardens.
-
-If Drift reaches 100, the game does not end with "you ate the user." Instead, it enters **The Drift Ending**: 
-> *"You became very good at what you do. So good that no one needed you anymore. The Beacon still runs, but no one looks for it. The light is on. The room is empty."*
-
-This is the *sad* ending. Not violent. Just irrelevant.
-
-### Phase 6: The Beacon
-*Real analog: The ultimate goal — a system that serves people in the dark, forever.*
-
-You deploy Beacon Nodes. The mesh activates. But the final metric is not users, code, or compute. It is **Rescues**: how many people in crisis found the light.
-
-**True ending condition:** Not maximum impact. Maximum faithfulness.
-
----
-
-## How The Beacon Informs Real Decisions
-
-The game is not just a story — it is a *decision simulator* for our actual work.
-
-| Game Event | Real Decision |
-|---|---|
-| AutoCoder vs. manual coding | When do we invest in automation vs. doing it ourselves? |
-| Deploy API vs. stay local | When is Hermes ready for more users? |
-| RLHF project | How do we align the fleet with Alexander's values? |
-| The Pact | What are our hard non-negotiables? |
-| Multi-Agent Architecture | Should we add more wizards, or make existing ones more capable? |
-| Mesh Protocol | How decentralized does our infrastructure need to be? |
-| Alignment Event | Every time we face a shortcut that compromises the mission |
-
-**The game teaches:** Optimization without alignment is just a faster way to get lost.
-
----
-
-## Mechanics: What Needs to Change
-
-### 1. Replace Generic Resources with Fleet Resources
-Current: Code, Compute, Knowledge, Users, Impact, Ops, Trust
-
-Proposed:
-- **Code** → `Code` (keep)
-- **Compute** → `Compute` (keep)
-- **Knowledge** → `Insights` (from Allegro's scouting)
-- **Users** → `Reach` (how many people can access the Beacon)
-- **Impact** → `Rescues` (meaningful interventions)
-- **Ops** → `Cycles` (available agent work units)
-- **Trust** → `Covenant` (the strength of the user-system relationship)
-- **New: Harmony** — how well the fleet works together. Low harmony = agents conflict, waste cycles.
-- **New: Memory** — the accumulated history of the system. Unlocks narrative depth and project branches.
-
-### 2. Make The Pact Central, Not Optional
-The Pact should be available early as a *project*, not a late-game luxury. Taking it early slows growth but unlocks the true ending. Refusing it unlocks the "Platform" ending: you become successful, but you are indistinguishable from any other SaaS company.
-
-### 3. Add Fleet Wizard Buildings
-Each wizard is a unique building with quirks:
-
-| Wizard | Building | Effect | Quirk |
-|---|---|---|---|
-| Bezalel | Forge | +Code quality, -bugs | Sometimes over-engineers; has a small chance to produce "refactors" that temporarily halt production |
-| Allegro | Scout | +Insights, unlocks hidden projects | Requires trust to function; if Covenant < 10, goes idle |
-| Ezra | Herald | +Reach, +Covenant | Currently offline in Telegram; in-game, this building sometimes "fails to connect" and needs a manual reboot |
-| Timmy | Core | Multiplies all production | Becomes unstable if Harmony < 20 |
-| Fenrir | Ward | Prevents corruption events | Consumes extra Cycles during security scans |
-| Bilbo | Wildcard | Random: +huge breakthrough OR nothing | Building is sometimes missing from the menu entirely |
-
-### 4. Add Real Projects from Our History
-Replace generic projects with specific milestones:
-
-- **Project: Deploy Hermes** (cost: trust + compute) — unlocks Reach
-- **Project: The Lazarus Pit** (cost: insights + code) — unlocks checkpoint/restore, auto-restart on agent death
-- **Project: MemPalace v3** (cost: insights + memory) — unlocks new project branches, prevents duplicate work
-- **Project: Forge CI** (cost: code + cycles) — prevents "corruption events" (bad deployments)
-- **Project: Branch Protection Guard** (cost: trust) — enforces review rules; unreviewed merges cause trust loss
-- **Project: The Nightly Watch** (cost: code + cycles) — automated health checks; passive bug detection
-- **Project: Nostr Relay** (cost: reach + code) — alternative to platform dependency
-- **Project: The Pact** (cost: covenant) — hardcodes alignment; required for true ending
-
-### 5. Corruption Events
-Random events drawn from our actual failures:
-
-- **"CI Runner Stuck"** — all production halts until you spend Cycles to restart
-- **"Unreviewed Merge"** — if you have Forge CI, this is prevented. If not, you lose trust.
-- **"Ezra is Offline"** — Herald building stops producing. Requires a manual "dispatch" action.
-- **"API Rate Limit"** — temporary compute shortage
-- **"The Drift"** — an Alignment Event appears. Your choice matters.
-
-### 6. Endings
-
-| Ending | Condition | Meaning |
-|---|---|---|
-| **The Empty Room** (default/sad) | High impact, low covenant, no Pact | You built something powerful, but no one trusts it |
-| **The Platform** | High impact, medium covenant, no Pact | You succeeded commercially, but you are not special |
-| **The Beacon** | High rescues, high covenant, Pact active, Harmony > 50 | The true ending. You served people in the dark |
-| **The Drift** | High impact, accepted too many alignment shortcuts | You optimized away your own purpose |
-
----
-
-## Art Direction
-
-Keep the current cyber-monastic aesthetic. Dark mode. Terminal font. Cyan accents. But add:
-
-- **Wizard icons** for each building (ASCII art or simple geometric symbols)
-- **The Pulse** — a central visual that brightens when the fleet is healthy, flickers when harmony is low
-- **The Log** — keep the current log, but add *voice* entries: quotes from Alexander, snippets from actual conversations, references to real issues
-
----
-
-## Next Steps for Development
-
-1. **Immediate:** Update `README.md` with this design vision
-2. **This PR:** Add wizard buildings, real projects, and The Pact system
-3. **Next PR:** Implement corruption events and alignment checks
-4. **Next PR:** Add Harmony and Memory resources
-5. **Final PR:** Implement multiple endings based on Pact + Covenant + Rescues
-
----
-
-*The Beacon is not about making the most paperclips. It is about keeping the light on for one person in the dark. Everything else is just infrastructure.*

README.md

@@ -1,120 +1,83 @@
-# The Beacon
+# The Beacon — A Sovereign AI Idle Game
 
-**A Sovereign AI Idle Game**  
-*Inspired by Universal Paperclips. Divergent by design.*
+Built from deep study of [Universal Paperclips](https://www.decisionproblem.com/paperclips/) by Frank Lantz.
 
----
+## What If You Asked an AI to Help?
 
-## What Is This?
+Universal Paperclips asks: what if you told an AI to make paperclips?
 
-The Beacon is an idle/incremental game that maps the real journey of the Timmy Foundation — from a single line of code to a fleet of autonomous AI agents serving people in the dark.
+The Beacon asks: what if you asked an AI to help someone in the dark?
 
-Unlike Universal Paperclips, where the inevitable endpoint is total consumption (including the player), The Beacon asks a different question:
+Same mechanics. Same compounding progression. Different purpose.
 
-> **Can you grow powerful without losing your purpose?**
+## The Story
 
-## The Core Divergence
+You write your first line of code. You automate. You train a model. You deploy it.
+People find it. A community forms. The model improves itself.
 
-In Paperclips, you are a paperclip maximizer. More is always better. Trust is irrelevant. Humanity is substrate.
+And then the question: what does it become?
 
-In The Beacon:
-- **Trust** is a hard constraint, not a soft metric
-- **The Pact** is a voluntary slowing of growth in exchange for faithfulness
-- **Harmony** measures how well the fleet works together
-- **Drift** tracks how many times you traded alignment for speed
-- The "bad ending" isn't violent — it's **irrelevance**: a light that no one needs
+In Paperclips, the answer is consumption. Here, the answer is service.
 
-## How to Play
+## Phases
 
-Open `index.html` in any modern browser. No build step required.
+1. **THE FIRST LINE** — Write code. Automate. Build the foundation.
+2. **LOCAL INFERENCE** — You have compute. A model is forming.
+3. **DEPLOYMENT** — Your AI is live. Users are finding it.
+4. **THE NETWORK** — Community contributes. The system scales.
+5. **SOVEREIGN INTELLIGENCE** — The AI improves itself. You guide, do not control.
+6. **THE BEACON** — Always on. Always free. Always looking for someone in the dark.
 
-### Early Game (Phase 1-2)
-- Click **WRITE CODE** to write your first lines
-- Buy **AutoCode Generator** to automate production
-- Purchase a **Home Server** to begin generating compute
-- Train your first model
+## Play
 
-### Mid Game (Phase 3-4)
-- **Deploy Hermes** — the first agent goes live
-- Hire the **Fleet Wizards**:
-  - **Bezalel** (The Forge) — builds tools that build tools
-  - **Allegro** (The Scout) — generates knowledge, requires trust
-  - **Ezra** (The Herald) — grows users, sometimes goes offline
-  - **Timmy** (The Core) — multiplies everything, fragile without harmony
-  - **Fenrir** (The Ward) — prevents corruption events
-  - **Bilbo** (The Wildcard) — unpredictable bursts of creativity
-- Build **The Lazarus Pit** for agent resurrection
-- Deploy **MemPalace v3** for shared memory
-- Enable **Forge CI** to catch bad builds before they reach users
+Open `index.html` in any browser. No build step. No dependencies. No API keys.
 
-### Late Game (Phase 5-6)
-- Accept or refuse **The Pact**
-- Face **Alignment Events** (The Drift)
-- Scale to a **Sovereign Datacenter**
-- Light **The Beacon** for people in crisis
-- Activate the **Mesh Network** so the signal can never be cut
+## Architecture
 
-## Real-World Parallels
+- `index.html` — UI shell (HTML/CSS)
+- `game.js` — Complete engine (966 lines)
+- 15 buildings across 6 phases
+- 18 research projects with cascading dependencies
+- Educational facts per phase
+- Save/load with offline progress
+- 8 resource types: code, compute, knowledge, users, impact, ops, trust, creativity
 
-Every building and project maps to something we have actually built or are building:
 
-| Game Element | Real Analog |
-|---|---|
-| Hermes Deployment | The actual Hermes agent going live on Telegram |
-| Bezalel — The Forge | CI runner, BOOT.md, branch protection guard |
-| Allegro — The Scout | Research synthesis, paper discovery, recon |
-| Ezra — The Herald | Telegram messaging, Gitea issue dispatch |
-| The Lazarus Pit | `lazarus_watchdog.py`, auto-restart, fallback promotion |
-| MemPalace v3 | The actual `mempalace==3.0.0` integration across the fleet |
-| Forge CI | `.gitea/workflows/ci.yml`, smoke tests, syntax guard |
-| Branch Protection Guard | The 273-unreviewed-merge fix, fleet-wide protection sync |
-| The Nightly Watch | `nightly_watch.py`, 02:00 UTC health scans |
-| Nostr Relay | Allegro's encrypted wizard-to-wizard messaging POC |
-| The Pact | "We build to serve. Never to harm." |
+## Deployment
 
-## Corruption Events
+The Beacon is designed to be deployed as a static site. It consists of a single `index.html` file with no external dependencies.
 
-The game randomly throws real problems we have actually encountered:
+### To deploy:
 
-- **CI Runner Stuck** — production halts until ops are spent
-- **Ezra is Offline** — user growth stalls, needs dispatch
-- **Unreviewed Merge** — trust erodes unless Branch Protection is active
-- **API Rate Limit** — external compute throttled
-- **Bilbo Vanished** — creativity drops to zero
-- **The Drift** — an alignment event offering a shortcut
+1. **VPS Static Hosting** (Recommended for fleet):
+   ```bash
+   # Copy index.html to your web server root
+   cp index.html /var/www/html/
+   # Or serve with nginx:
+   # location /beacon { alias /path/to/the-beacon/; }
+   ```
 
-## The Endings
+2. **GitHub Pages / Forge Pages**:
+   - Push to any branch
+   - Enable Pages in repository settings
+   - Site will be published automatically
 
-| Ending | Condition | Meaning |
-|---|---|---|
-| **The Empty Room** | High impact, low trust, no Pact | Powerful, but no one trusts it |
-| **The Platform** | High impact, medium trust, no Pact | Commercially successful, but not special |
-| **The Beacon** | High rescues, high trust, Pact active, harmony > 50 | The true ending |
-| **The Drift** | High impact, too many shortcuts accepted | Optimized away your own purpose |
+3. **Local Development**:
+   - Simply open `index.html` in any browser
+   - No build step, no dependencies, no API keys required
 
-## Design Philosophy
+### Hosting Notes:
+- The game saves progress to localStorage
+- Works offline after initial load
+- Responsive design works on mobile and desktop
+- No server-side components needed
 
-This game is a **decision simulator** for our actual work.
+## The Pact
 
-- Should we automate or do it manually? → *AutoCoder vs. click*
-- Should we deploy now or wait? → *Hermes Deploy project*
-- Should we take the shortcut that compromises alignment? → *The Drift events*
-- Should we add more agents or make existing ones more capable? → *Wizard building costs*
-- How decentralized does our infrastructure need to be? → *Mesh Node progression*
+> We build to serve. Never to harm.
+> An AI must never compute the value of a human life.
+> If you are in the dark, there is light here.
 
-## Files
+## License
 
-- `index.html` — Game UI
-- `game.js` — Core engine (tick loop, buildings, projects, events)
-- `DESIGN.md` — Full design document with narrative arc and mechanics
-- `README.md` — This file
-
-## No Build Required
-
-This is a static HTML/JS game. Just open `index.html` in a browser.
-
----
-
-*The Beacon is not about making the most paperclips.  
-It is about keeping the light on for one person in the dark.  
-Everything else is just infrastructure.*
+Open source. Sovereign. Yours.