@bongos/core 1.24.35 → 1.24.37

package/docs/module-api-changelog.md

@@ -3324,5 +3324,9 @@ is load-bearing: the script throws rather than guess if it is missing, and
         landed since 1.24.33 with no explicit bump. run 41899266144. (task 1002620)
   1.24.35 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
         landed since 1.24.34 with no explicit bump. run 41902956083. (task 1002620)
+  1.24.36 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.24.35 with no explicit bump. run 41919172906. (task 1002620)
+  1.24.37 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.24.36 with no explicit bump. run 42099751558. (task 1002620)
 ---------------------------------------------------------------------------
 ```

package/docs/onboarding/diagrams/README.md

@@ -64,8 +64,7 @@ Source: [`05-versioning.mmd`](05-versioning.mmd)
 
 ## Where builders see these
 
-The diagrams are surfaced inside the authenticated **builders' hall** at
-[`/builders/diagrams`](https://example.com/builders/diagrams) (linked from the hall home page) and inlined in the primer. `modules/hall-ui/public/diagrams.html` references each diagram's `.png`, and [`diagram-viewer.js`](../../../modules/hall-ui/public/diagram-viewer.js) progressively enhances it: it fetches the matching `.svg`, injects it inline, and turns it into a pan-and-zoom canvas (drag to pan, scroll to zoom, fullscreen). If the SVG can't be fetched it falls back to the static PNG. `server.js` serves `docs/onboarding/diagrams/` at `/builders/diagrams/` (both `.svg` and `.png`), so there's a single source of truth and no duplicated binaries.
+The diagrams are surfaced inside the authenticated **builders' hall** in the Primer, each inlined in the chapter it illustrates (task 1005046 folded the old `/builders/diagrams` page into it; that URL now redirects to the Primer). `modules/hall-ui/public/primer.js` (`DIAGRAM_AT_CHAPTER`) references each diagram's `.png`, and [`diagram-viewer.js`](../../../modules/hall-ui/public/diagram-viewer.js) progressively enhances it: it fetches the matching `.svg`, injects it inline, and turns it into a pan-and-zoom canvas (drag to pan, scroll to zoom, fullscreen). If the SVG can't be fetched it falls back to the static PNG. `server.js` serves `docs/onboarding/diagrams/` at `/builders/diagrams/` (both `.svg` and `.png`), so there's a single source of truth and no duplicated binaries.
 
 ## Staying current (auto-update)
 

package/docs/onboarding/primer.md

@@ -18,6 +18,8 @@ This primer teaches the **platform** — how you claim work and ship it, the sam
 
 You don't need to understand the Bongos schema to ship work. You just need to know: *claim a task, work on it inside your worktree, ship it.* The CLI handles the rest.
 
+> **Reading the diagrams.** Most chapters below carry a diagram of the thing they explain, generated from the live system each time it deploys. A **● LIVE** mark is built and enforced today, **⤍ PLANNED** is designed and tracked but not built yet, and **○ reserved** exists in the database with no behaviour behind it. Drag a diagram to pan, scroll to zoom, or open it full screen.
+
 ## The claim → ship lifecycle
 
 Every piece of work moves through this loop:
@@ -47,7 +49,7 @@ The one thing that decides whether your ship is **instant** or **waits for an Ar
 
 | What your change touches | What happens |
 |---|---|
-| **Normal work** — game code, art, docs, tests, most of `src/` | **Auto-merges on green for any rank**, Xenos included. No approval. |
+| **Normal work** — product code, art, docs, tests, most of `src/` | **Auto-merges on green for any rank**, Xenos included. No approval. |
 | **A protected "gate surface"** — migrations, server routes, the ship / deploy plumbing | Auto-merges **only if you are Metic or above** (rank trust). A Xenos or Thetes ship here **waits for an Archon** to approve. |
 | **The safety core** — the gate's own machinery, the deploy switch, the rank / permission enforcement | **Always** waits for an Archon, whatever your rank. |
 
@@ -55,26 +57,68 @@ So your first tasks **ship with no approval**: the newcomer chores — a tile, a
 
 ## The rank ladder
 
-Four ranks, in ancient-Greek-civilization order:
+Your rank decides which work you can claim and which levers you can pull. There are four live ranks, lowest to highest:
+
+| Rank | Who holds it | What it unlocks |
+|------------|-----------------------------------------------|----------------------------------------------------------------------------------|
+| **Xenos**  | The newcomer. Every new builder starts here, with a deliberately small surface: onboarding, safe starter tasks, and your own standing. | Read every public page. Claim and ship tasks an Archon has flagged `newcomer_friendly`. Earn credits for shipped work and karma for ratified ideas. One claim at a time. |
+| **Thetes** | The proven builder, who has shipped their first work. You reach it **automatically after your 3rd shipped task** — no one has to promote you. | Claim and ship **any** task in the general queue, and hold more than one claim. No triage, blockers, planning or task-shaping yet: those open at Metic. |
+| **Metic**  | The trusted builder. Most of the work happens here. | Claim any ready task. Triage the idea inbox, resolve blockers, run planning sessions, file security reports, and propose new version criteria for an Archon to ratify. |
+| **Archon** | The steward of the whole system. | Create, promote and edit tasks and reshape their dependencies; grant or revoke ranks; close versions; confirm ships past the grader; decide vulnerability reports and override requests. |
+
+### How you advance
+
+- **Xenos → Thetes** is automatic. Ship the newcomer-friendly tasks an Archon has opened to newcomers; on your **third** clean ship you are promoted to Thetes, out of the sandbox and with the whole queue open. No fee, no application.
+- **Thetes → Metic** is granted by a standing Archon alone, to a builder whose judgement has earned the project's trust. Keep shipping; rank is granted, never bought.
+- **Metic → Archon** is granted rarely, by a standing Archon, to a Metic who has shaped the project's direction. There is no checklist.
+
+Karma does not promote you on its own (see the next chapter); it is evidence an Archon can weigh. Your own rank, and what the next one asks of you, is on **[Accomplishments → Where you stand](/builders#accomplishments-progress)**.
+
+Rank lives on the `builders.rank` column in the production database and is checked server-side on every privileged request — **with no caching**. A demotion takes effect on your next request. You cannot escalate your own rank by editing local files; the server is the source of truth. See [ADR 0016](../adr/0016-trust-boundary-server-enforced-permissions.md) and [ADR 0034](../adr/0034-thetes-graduated-newcomer-rank.md) for the full trust model.
+
+## Credits and karma
+
+Two separate tracks. You don't need to *do* anything special to earn either — claim a task, do good work, ship it, and the system tracks both. **Credits** measure the work you did; **karma** measures how other builders trust the way you do it. Neither is money. The formulas in full, with the code they live in, are in **[the credits and karma reference](drachmae-and-karma.md)**.
+
+### How you earn credits
+
+Credits are a **contribution meter** for this project — they measure your work and are *not* money, not redeemable and not equity ([ADR 0387](../adr/0387-two-ledgers-credits-measure-work-money-stays-with-the-processor.md)); any pay or equity is set by the project separately. Every award is a row in an append-only log, so history is never rewritten, and your total stays with you if you leave and come back. They come from:
+
+1. **A cost-plus reward on each shipped session — the main one.** The server prices the AI tokens your session actually burned, at the published list price, and credits you that amount in USD **plus 20%** ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md)). The cost is worked out on the server, so nobody can inflate their own award; a session that ships nothing earns nothing, and re-shipping the same session pays once.
+2. **Each task's own reward, adjusted by the kind of work** ([ADR 0023](../adr/0023-kind-multipliers-and-idea-bonus.md)): a captured learning or a resolved blocker is worth 1.5×, a decision record 1.3×, a bug fix 1.2×, a feature 1.0×, a refactor 0.9× and cleanup 0.8×.
+3. **An idea bonus.** Capture an idea that someone else later ships and you get 25% of that task's reward, on top of what the shipper earns.
+4. **Achievements** pay a small one-time bonus, and a ship that **deletes more lines than it adds** earns a small bonus too.
+5. **The security bounty.** Finding a flaw in the system's own walls pays by severity; the live rate card is below.
+
+Which of the two main streams actually pays is per-project ([ADR 0146](../adr/<redacted><redacted>.md)): the default pays both, while a `cost-plus-only` project pays the session reward alone and treats each task's reward as an estimate.
+
+### When credits land
+
+Credits land at the **`confirmed → shipped`** step — when your code actually merges to `main` and deploys — **not** when verification passes ([ADR 0120](../adr/0120-pay-on-land-and-builder-owned-rebase-gate.md)). A task that passes the grader but never lands earns nothing until it does, and releasing a task with `/builder-release` pays nothing.
+
+### The budget cap
+
+Builders are **uncapped by default** — your spend is tracked (it is the cost side of the same coin the reward is computed from) but it never blocks you. An Archon *can* set a per-builder **monthly budget cap** as a brake on a runaway; if one is set for you, you get a warning at 80% and `/builder-ship` pauses at 100% until it's raised or cleared ([ADR 0085](../adr/0085-remove-default-per-builder-spend-cap.md)).
 
-| Rank       | What it means                                                          | What it unlocks                                                                  |
-|------------|------------------------------------------------------------------------|----------------------------------------------------------------------------------|
-| **Xenos**  | Default for new builders. "Sandbox" tier.                              | Can only claim tasks flagged `newcomer_friendly`. Read everything. No mutations. |
-| **Thetes** | Graduated newcomer. You reach it **automatically after your 3rd shipped task** — no one has to promote you. | Claim **any** task in the general queue (not just newcomer-friendly). Still no triage/blocker/scope powers. |
-| **Metic**  | Approved working rank. The "real builders."                            | Claim any ready task. Idea triage, blocker review. Most of the work happens here. |
-| **Archon** | Project keeper.                                                        | Scope mutations, rank changes, infra-level operations.                            |
+### Karma
 
-So the sandbox is short: ship three small `newcomer_friendly` tasks and the city opens the whole queue to you on its own (the jump to **Metic** — with its triage/trust powers — is still a deliberate Archon promotion). Rank lives on the `builders.rank` column in the production database and is checked server-side on every privileged request — **with no caching**. A demotion takes effect on your next request. You cannot escalate your own rank by editing local files; the server is the source of truth. See [ADR 0016](../adr/0016-trust-boundary-server-enforced-permissions.md) and [ADR 0034](../adr/0034-thetes-graduated-newcomer-rank.md) for the full trust model.
+Karma is a **separate** counter that measures **peer trust**. It is earned when Metic-and-above builders upvote your confirmed work (tallied weekly, and nobody can vote on their own), when a proposal of yours is ratified, and when an idea you captured is promoted into a task. It can also go **down** if you break things. Reactions in Discord never mint karma — only rank-gated votes do.
 
-## Example and karma
+Karma shows up on your profile (with a 30-day trend), as a sortable column on the leaderboard, and as one input to your "builder strength" score. **It does not gate rank promotions**: those happen by ship count (Xenos → Thetes) or by an Archon's decision. A builder who ships fast but breaks things gains credits and loses karma; a builder who ships thoughtfully gains both.
 
-Two parallel reputation tracks. You don't need to *do* anything special to earn either — claim a task, do good work, ship it, and the system tracks both. The full mechanics (formulas, the kind table, the budget cap, every karma source) live in **[Example & karma — how your work is counted](drachmae-and-karma.md)**; here's the shape of it.
+| | **Credits** | **Karma** |
+|---|---|---|
+| Measures | Output — work shipped | Peer trust — how others rate your work |
+| Earned by | Shipping (session reward, task rewards, bonuses) | Metic+ peer votes, ratified proposals, promoted ideas |
+| Direction | Only goes up (a correction is a new row) | Can go up or down |
+| Spendable? | No — a contribution meter, not money or equity | No — a trust signal |
+| Gates promotions? | No | No — it informs, it doesn't gate |
 
-- **Example** (called "credits" in code) are a **contribution meter** for the project — they measure your work and are *not* money, not redeemable and not equity ([ADR 0387](../adr/0387-two-ledgers-credits-measure-work-money-stays-with-the-processor.md)); any pay or equity is set by the project separately. They persist if you leave and come back. Most of your example now come from a **cost-plus reward on each shipped session**: the server prices the LLM tokens your work actually burned and credits you an amount sized by that real cost in USD **plus 20%** ([ADR 0054](../adr/0054-session-token-reward-cost-plus.md)). On top of that, each task pays its `credits_reward` adjusted by the *kind* of work (a captured learning or a resolved blocker is worth 1.5×; cleanup 0.8×), and capturing an idea that someone else then ships earns you a 25% bonus ([ADR 0023](../adr/0023-kind-multipliers-and-idea-bonus.md)). Credits land at the `confirmed → shipped` edge — when your code actually merges and deploys, not when verification passes ([ADR 0120](../adr/0120-pay-on-land-and-builder-owned-rebase-gate.md)). Which of those two streams actually pays is per-instance config ([ADR 0146](../adr/<redacted><redacted>.md)): the default pays both, while a `cost-plus-only` instance pays the session reward alone and treats each task's `credits_reward` as an advertised estimate only. See the standings on [/builders](https://example.com/builders).
+The project's real numbers — what it has spent, what it has awarded builders for that spend, what it has paid out and what hosting costs — are on the **[Money](../../modules/hall-ui/public/money.html)** page, which opens for the people who steer the project.
 
-- **Karma** is a *separate* signal that measures **peer trust** — how other builders rate the *way* you work, not how much you ship. It's earned when Metic-and-above builders upvote your confirmed work (tallied weekly), when a proposal of yours is ratified, and when you capture ideas; it can also go *down* if you break things. Karma shows up on your profile (with a 30-day trend) and as a sortable column on the leaderboard, and it feeds your "builder strength" score. **It does not gate rank promotions** — those happen automatically by ship count (Xenos → Thetes after three ships) or by an Archon's deliberate decision. A builder who ships fast but breaks things gains example and loses karma; a builder who ships thoughtfully gains both.
+## How versions organise the work
 
-One more thing worth knowing: builders are **uncapped by default** — your spend is tracked (it's the cost side of the same coin the reward is computed from) but never blocks you. There's no default budget. An Archon *can* set a per-builder **monthly budget cap** as a manual brake on a runaway; if one is set for you, you get a warning at 80% and `/builder-ship` pauses at 100% until it's raised ([ADR 0085](../adr/0085-remove-default-per-builder-spend-cap.md)).
+Every task belongs to a **version** — a named batch of work with a written definition of done. A **planning session** (`/planning-session`) writes a version's **done-when criteria** and seeds its task pool, each task with its dependencies and the rank it needs. The version is **building** while its tasks are claimed and shipped, and it **closes** when every criterion is met: its scope is archived and a guided review comes before the next version takes over. A project runs product versions (what its users get) and platform versions (how it builds) side by side, and `/status` rolls any version up into what is left.
 
 ## How to ask Claude about anything
 
@@ -100,7 +144,7 @@ As you work, Claude writes down durable facts — your standing preferences, a g
 - **The map** (`MEMORY.md`) — a short index loaded at the **start of every session**: one line per memory, just enough to know *what* is known and where the detail lives. Kept deliberately small.
 - **The drawer** — the full notes themselves. They live on your machine, sync to the server (so your memory follows you across machines), and are searchable with `/recall`. They cost nothing until something fetches them.
 
-The map stays light on its own: a session-start guard warns if it's drifting large, and an auto-tidy moves the oldest, least-relevant notes off the map into the drawer when it crosses a threshold — **nothing is deleted**, it's just no longer loaded every session (a `/recall` away when a task needs it). Your standing rules, and anything pinned, always stay on the map. Full picture: [ADR 0074](../adr/0074-memory-map-stays-light.md) and [diagram 4 — the architecture](diagrams/).
+The map stays light on its own: a session-start guard warns if it's drifting large, and an auto-tidy moves the oldest, least-relevant notes off the map into the drawer when it crosses a threshold — **nothing is deleted**, it's just no longer loaded every session (a `/recall` away when a task needs it). Your standing rules, and anything pinned, always stay on the map. Full picture: [ADR 0074](../adr/0074-memory-map-stays-light.md) and the architecture diagram in [Get set up on your machine](#get-set-up-on-your-machine).
 
 ## Where to find more depth
 
@@ -111,23 +155,23 @@ The whole project's source-of-truth index is [`CLAUDE.md`](../../CLAUDE.md). Two
 
 Other depth, in roughly the order you'll need it:
 
-- [`docs/onboarding/example-and-karma.md`](drachmae-and-karma.md) — the full reward economy: how example and karma are earned, the cost-plus session reward, and the monthly budget cap
+- [`docs/onboarding/drachmae-and-karma.md`](drachmae-and-karma.md) — the full credits and karma reference: every formula, the kind table, the budget cap, every karma source, and the code each lives in
 - [`docs/onboarding/slash-commands.md`](slash-commands.md) — which slash commands ship with Claude Code and which are this project's, and what to do about the ones that collide
 - [The Commands page](../../modules/hall-ui/public/commands.html) — every slash command and terminal command this project has, what each does and what it costs
 - [The Repo Atlas](../../modules/hall-ui/public/atlas.html) — a live map of the code: how it is organised and which modules stand on their own
 - [`docs/architecture.md`](../architecture.md) — live system: droplet, stack, schema, API surface
-- [`docs/modules-contract.md`](../modules-contract.md) — the product is built as a small core plus swappable `modules/<key>/` (the game, Discord, art, and more); this is the live roster and how a task lands inside one
+- [`docs/modules-contract.md`](../modules-contract.md) — the product is built as a small core plus swappable `modules/<key>/` (Discord, art, government, and more); this is the live roster and how a task lands inside one
 - [`docs/canonical-permissions.md`](../canonical-permissions.md) — who can do what (rank gates)
 - [`GOVERNMENT.md`](../../GOVERNMENT.md) — how your project's government works and how to change it, in plain words
 - [`docs/file-map.md`](../file-map.md) — where every folder is and what it contains
 - [`docs/recipes/`](../recipes/) — long-form ops gotchas (read before deploying)
-- [`docs/onboarding/diagrams/`](diagrams/) — pan-and-zoom maps of the task lifecycle, rank ladder, the credit economy, the complete architecture (where your work runs and how it reaches production), and versioning
+- [`docs/onboarding/diagrams/`](diagrams/README.md) — the sources of the five diagrams in this primer, regenerated from the live system on every deploy
 
 You don't need to read these now. Bookmark them; come back when something specific is unclear.
 
 ## Get set up on your machine
 
-You don't need to be a programmer to build here. Entry to the project is **approval-gated**: a stranger can't just sign in with GitHub — you first ask for entry on the [builders' hall](https://example.com/builders) and an Archon admits you. Since you're reading this gated primer, you've already been admitted.
+You don't need to be a programmer to build here. How you get in **depends on the project**: some are open, so anyone can sign in with GitHub and start; others are approval-gated, so you first ask for entry on the [builders' hall](https://example.com/builders) and an Archon admits you. Since you're reading this primer, you're already in.
 
 ### Where your work runs — screen, worker, brain
 
@@ -137,7 +181,7 @@ Claude Code is **three pieces that can live in different places**:
 - **The worker** — the part that opens files, runs commands, edits code, runs the project.
 - **The brain** — the AI model itself. **Always on Anthropic's servers**.
 
-Today the worker runs in one place: **your own computer**, working on a clone of the project. The single map that shows the whole picture — your device, the per-builder memory layer, the server (authority *and* production), and how code travels to prod — is [diagram 4, *The complete architecture*](diagrams/).
+Today the worker runs in one place: **your own computer**, working on a clone of the project. The single map that shows the whole picture — your device, the per-builder memory layer, the server (authority *and* production), and how code travels to prod — is the architecture diagram at the top of this chapter.
 
 > **Why a copy of the code at all?** The `/builder-*` commands you'll use every session aren't a separate download — they live *inside* the project's code (in `.claude/skills/`). The moment Claude Code **starts a session on a folder that already holds the code**, all the commands appear automatically. So "get the code" and "get the commands" are the same step — there's no plugin or zip to install. (One wrinkle: if you *clone the code mid-session into a folder that started empty*, the commands won't appear until you start a fresh session on that folder — step 3 handles it.)
 
@@ -187,8 +231,8 @@ npx bongos setup
 
 Run `/builder-start` to see what you can claim — no acknowledgment step needed, the queue is open. New builders see only `newcomer_friendly` tasks — small, well-scoped, easy to finish in one sitting. Pick one that looks interesting, claim it with `/builder-claim N`, do the work, and ship it with `/builder-ship`.
 
-When you ship your **first** task, example land in your column and you're inducted as a citizen of Example. Ship your **third** and you graduate to **Thetes** — the one-claim limit lifts and the whole general queue opens to you. Welcome.
+When you ship your **first** task, credits land in your column and you're inducted as a citizen of Example. Ship your **third** and you graduate to **Thetes** — the one-claim limit lifts and the whole general queue opens to you. Welcome.
 
 ## Previewing your change
 
-Before you ship a change that touches the game, run **`/builder-stage`** to start your own private copy of the game on your computer (at `http://localhost:<port>`) with your current edits in it. Open the link, watch your change running for real, and only then ship it. Nothing you stage there touches the live game or anyone else's work.
+Before you ship a change people will see, run **`/builder-stage`** to start your own private copy of the project on your computer (at `http://localhost:<port>`) with your current edits in it. Open the link, watch your change running for real, and only then ship it. Nothing you stage there touches the live project or anyone else's work.

package/docs/page-inventory.json

@@ -10,10 +10,10 @@
     "An id changes only when the host prefix, the data-page value or the file name changes; that is a rename, and records keyed on the old id move with it."
   ],
   "counts": {
-    "pages": 51,
+    "pages": 48,
     "surfaces": 3,
-    "with_states": 45,
-    "states": 381
+    "with_states": 42,
+    "states": 374
   },
   "surfaces": [
     {
@@ -22,7 +22,7 @@
       "at": "modules/hall-ui/public",
       "answers_at": "host prefix builders.",
       "origin": "https://builders.{apex}",
-      "pages": 39
+      "pages": 36
     },
     {
       "id": "landing",
@@ -363,104 +363,6 @@
         "out"
       ]
     },
-    {
-      "id": "builders:diagrams",
-      "surface": "builders",
-      "module": "hall-ui",
-      "page": "diagrams",
-      "id_from": "data-page",
-      "title": "Diagrams",
-      "document_title": "How the system works — {{worldName}}",
-      "path": "/diagrams",
-      "url": "https://builders.{apex}/diagrams",
-      "files": [
-        "modules/hall-ui/public/diagrams.html",
-        "modules/hall-ui/public/style.css",
-        "modules/hall-ui/public/room.css",
-        "modules/hall-ui/public/diagrams.css",
-        "modules/hall-ui/public/diagram-viewer.css",
-        "modules/hall-ui/public/dom-utils.js",
-        "modules/hall-ui/public/shell-trail.js",
-        "modules/hall-ui/public/craft-mode.js",
-        "modules/hall-ui/public/shell.js",
-        "modules/hall-ui/public/palette.js",
-        "modules/hall-ui/public/diagram-viewer.js",
-        "modules/hall-ui/public/copy-on-click.js"
-      ],
-      "states_files": [
-        "modules/hall-ui/public/diagrams.states.json"
-      ],
-      "states": [
-        "in",
-        "out"
-      ]
-    },
-    {
-      "id": "builders:drachmae",
-      "surface": "builders",
-      "module": "hall-ui",
-      "page": "drachmae",
-      "id_from": "data-page",
-      "title": "Drachmae & karma",
-      "document_title": "Drachmae & karma — {{worldName}}",
-      "path": "/drachmae",
-      "url": "https://builders.{apex}/drachmae",
-      "files": [
-        "modules/hall-ui/public/drachmae.html",
-        "modules/hall-ui/public/style.css",
-        "modules/hall-ui/public/room.css",
-        "modules/hall-ui/public/dom-utils.js",
-        "modules/hall-ui/public/shell-trail.js",
-        "modules/hall-ui/public/craft-mode.js",
-        "modules/hall-ui/public/shell.js",
-        "modules/hall-ui/public/palette.js",
-        "modules/hall-ui/public/md-reader.js",
-        "modules/hall-ui/public/hall-kit.js",
-        "modules/hall-ui/public/drachmae.js",
-        "modules/hall-ui/public/copy-on-click.js"
-      ],
-      "states_files": [
-        "modules/hall-ui/public/drachmae.states.json"
-      ],
-      "states": [
-        "read",
-        "toc-open",
-        "jump",
-        "out"
-      ]
-    },
-    {
-      "id": "builders:fleet",
-      "surface": "builders",
-      "module": "hall-ui",
-      "page": "fleet",
-      "id_from": "data-page",
-      "title": "Fleet costs",
-      "document_title": "Fleet costs — {{worldName}}",
-      "path": "/fleet",
-      "url": "https://builders.{apex}/fleet",
-      "files": [
-        "modules/hall-ui/public/fleet.html",
-        "modules/hall-ui/public/style.css",
-        "modules/hall-ui/public/oversight.css",
-        "modules/hall-ui/public/project-settings.css",
-        "modules/hall-ui/public/dom-utils.js",
-        "modules/hall-ui/public/shell-trail.js",
-        "modules/hall-ui/public/craft-mode.js",
-        "modules/hall-ui/public/shell.js",
-        "modules/hall-ui/public/palette.js",
-        "modules/hall-ui/public/hall-kit.js",
-        "modules/hall-ui/public/fleet-costs.js",
-        "modules/hall-ui/public/fleet.js"
-      ],
-      "states_files": [
-        "modules/hall-ui/public/fleet.states.json"
-      ],
-      "states": [
-        "ledger",
-        "out"
-      ]
-    },
     {
       "id": "builders:gate",
       "surface": "builders",
@@ -893,6 +795,39 @@
         "out"
       ]
     },
+    {
+      "id": "builders:money",
+      "surface": "builders",
+      "module": "hall-ui",
+      "page": "money",
+      "id_from": "data-page",
+      "title": "Money",
+      "document_title": "Money — {{worldName}}",
+      "path": "/money",
+      "url": "https://builders.{apex}/money",
+      "files": [
+        "modules/hall-ui/public/money.html",
+        "modules/hall-ui/public/style.css",
+        "modules/hall-ui/public/oversight.css",
+        "modules/hall-ui/public/project-settings.css",
+        "modules/hall-ui/public/dom-utils.js",
+        "modules/hall-ui/public/shell-trail.js",
+        "modules/hall-ui/public/craft-mode.js",
+        "modules/hall-ui/public/shell.js",
+        "modules/hall-ui/public/palette.js",
+        "modules/hall-ui/public/hall-kit.js",
+        "modules/hall-ui/public/fleet-costs.js",
+        "modules/hall-ui/public/money.js"
+      ],
+      "states_files": [
+        "modules/hall-ui/public/money.states.json"
+      ],
+      "states": [
+        "money",
+        "hosting",
+        "out"
+      ]
+    },
     {
       "id": "builders:my-agents",
       "surface": "builders",
@@ -954,6 +889,7 @@
         "modules/hall-ui/public/shell.js",
         "modules/hall-ui/public/palette.js",
         "modules/hall-ui/public/md-reader.js",
+        "modules/hall-ui/public/primer-live.js",
         "modules/hall-ui/public/primer.js",
         "modules/hall-ui/public/diagram-viewer.js",
         "modules/hall-ui/public/copy-on-click.js"
@@ -964,6 +900,7 @@
       "states": [
         "in",
         "toc-open",
+        "jump",
         "out"
       ]
     },
@@ -1042,37 +979,6 @@
       "states_files": [],
       "states": []
     },
-    {
-      "id": "builders:ranks",
-      "surface": "builders",
-      "module": "hall-ui",
-      "page": "ranks",
-      "id_from": "data-page",
-      "title": "Ranks",
-      "document_title": "Ranks — {{worldName}}",
-      "path": "/ranks",
-      "url": "https://builders.{apex}/ranks",
-      "files": [
-        "modules/hall-ui/public/ranks.html",
-        "modules/hall-ui/public/style.css",
-        "modules/hall-ui/public/dom-utils.js",
-        "modules/hall-ui/public/shell-trail.js",
-        "modules/hall-ui/public/craft-mode.js",
-        "modules/hall-ui/public/shell.js",
-        "modules/hall-ui/public/palette.js",
-        "modules/hall-ui/public/founding-mark.js",
-        "modules/hall-ui/public/ranks.js"
-      ],
-      "states_files": [
-        "modules/hall-ui/public/ranks.states.json",
-        "modules/hall-ui/public/ranks-founding.states.json"
-      ],
-      "states": [
-        "out",
-        "in",
-        "founding"
-      ]
-    },
     {
       "id": "builders:roadmap",
       "surface": "builders",