# What is left (as of 2026-11-09) Work in this fork, pushed to the `vanvik` Forgejo remote (never to `origin`). `main` is at 3e30621. Nothing below is switched on or built unless it says so. ## Built so far On top of upstream, merged up to 3.3.0 (61e31c5 "Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0)"; earlier merges 032470f and 4b922ab): - **Build standard**: 2b48a6a "A build standard for the whole network, kept by the intern", and fbae6fc "The build standard owns the router model and the line system; one owner per fiber" (the router model and line system are picked in the sheet only; the `routers` and `optup` orders read them from there). - **Multiplayer phase 1** for self-hosted copies: 95aa9b6 "Multiplayer for self-hosted copies: sessions, server-side saves, a leaderboard" (`docs/MULTIPLAYER.md`). - **Dark mode (#80)**: 2cd6b71 "Dark mode: Light, Dark or Auto under Settings › Theme". - **IPv4 address space (#150)**: eac0604 "IPv4 address space: scarce, bought, leased, leased out; IPv6 is free", and 69328ce "IPv6-only broadband: 464XLAT city by city, a NAT64 pool next to CGNAT". - **Express fiber (#58)**: 8e1f2d6 "Express fiber: light a wave through a city without its router". - **Satellite teleports (#83)**: e1ae8e0 "Satellite teleports: GEO and MEO circuits for islands and remote towns". - A fix after the 3.1.0 merge: e8808f6 "The connections list no longer breaks on a 400G fabric port". - **Server-run play, parts 1 and 2** (merged, not switched on): T1 is d1e127d "Server-run play, part 1: game prerequisites and shared contracts". T2 is 065c922 "Server-run play, part 2: the engine" with its fixes c5c7ea9, 72f31e8, 3b8c331, 9597d89, 77f4035 and 3e30621. The design, its status and what building T2 changed in it are in `docs/plans/server-run.md`. ## The user's answers (2026-11-09) The four questions of the server-run design: 1. A player who joins an old session starts on the **session's date**: one shared calendar. The game's day-0 rules then have to count from each network's own start (`server-run.md`, "What Q1 changes"). 2. Single player in a multiplayer build runs **on the server** by default; "this device" stays an option. 3. An empty session that wakes runs at **1×**. 4. Phase-1 sessions **start fresh**: nothing is migrated. ## On hold until the user says go - **#97 co-op companies** (several players run one network, with roles, budgets and approvals). - **Multiplayer phase 2** (players as carriers in each other's simulations: transit, peering, PNIs, shared fiber): design in `docs/plans/multiplayer-phase2.md`. When it restarts, that design needs rework for the shared server clock: it assumes each player's own clock, and tenders and notice timed in real minutes. - **#144 directional traffic**, last and on its own: keep the totals, split them by traffic profile, utilization is the busier direction. It comes after #58 because both touch link capacity (express channels count too). ## Open questions waiting for the user Asked on 2026-11-09, not answered yet: 1. **Late joiners' prices and beginner grace.** With one calendar, a friend who joins an old session meets its economy from day one: at day 1868, hardware about 18% dearer and customer prices about 34% lower, with the 180-day beginner grace long over. Keep that, or give a grace or extra starting cash counted from the joiner's own start? 2. **Other players' POPs on the map.** Draw other players' POPs and links on your map (from their cards) as part of the server-run work, or wait for phase 2? 3. **The other modes in a multiplayer build.** Sandbox, scenarios, puzzles and the weekly keep running on the device. Fine, or should sandbox (or all of them) also run on the server? 4. **Dark mode and the build standard upstream.** Upstream contributors have said they will open pull requests for a dark mode (#80) and a bulk redundancy kit (#317), and a three-tier router standard sits on another contributor's branch (#315). Offer the fork's dark mode and build standard upstream before those land, or keep them fork-only and settle the clash at the next merge? 5. **#58 whole-fiber splicing.** Is the express lightpath enough, or should a whole fiber pair also splice through a city (one dark fiber A–C through B, with no ROADM at B)? The issue asks for "waves and/or entire fibers". 6. **#83 WISP zones and a rented LEO tier.** Add island demand pools served remotely on top of the existing island cities, and a tier between MEO and Pie in the Sky that rents LEO capacity from a partner network? Or are teleports with GEO and MEO circuits enough? 7. **Investors' cut of IPv4 lease income.** Should investors on a revenue-share loan take their cut of the income from leasing out IPv4 blocks too? Today they do not (dark fiber sold to customers is in their share). 8. **Founding an exchange on a basic router.** Founding your own exchange gives a 400G port even where the POP's router only takes 100G, though the shop would not sell that port. Document it as a limitation, block founding until the router takes 400G, or found at the router's largest port size? (`tests/server-sim-prereqs.test.js` asserts today's behaviour.) 9. **The six old wip worktrees.** They hold nothing `main` lacks. Delete them and their branches? ## Next - **In progress** (another builder is on these right now): - the build standard's "Bring everything up now" and the intern follow one rule for fibers that carry sold alien or managed waves (today the button can take such a fiber dark for a day, while the intern refuses any fiber with a customer, leased pairs and IRUs included, which a line-system swap cannot hurt); - dark mode: the capacity market's hot and cool tags, and red `--bad` text that is below AA contrast on dark cards; - IPv4 notices in the notification log get their "Address space" button; - the "no subsea cable lands here" hint (#321) mentions a satellite circuit where a teleport can reach the city; - express fiber: a regen site added later charges for the express channels on its fiber, and loss incidents on a fiber reach the expresses on it; - selective peers react to peering that rides a GEO link; - the intern's two small standing-orders fixes in `opsRun()` (the shift's log keeps an uncapped list of broken orders, and the week's tally makes an empty list of places for a job that names none); `opsTidy()` stays after the shift until `tests/canonical-state.test.js` passes without it; - IPv6-only broadband in the build standard: a "Broadband: IPv6-only" row, with the intern's `std` order rolling it out busiest CGNAT cities first (`ip6Go`/`ip6Stop` are in `src/game/90-actions/55-ipv6-only.js`, the panel and day logic in `src/game/60-features/34-ipv6-only.js`; the row goes into `BSTD` and `bstdPlan` in `src/game/60-features/96-pop-standard.js`). - **After the user's go:** T3 (host and protocol), T4 (the browser client) and the integration of server-run play, as `docs/plans/server-run.md` describes them, with the corrections at its top. That includes the Q1 work: the game's `S.day0` and day-0 rules, a start day for a new network on the server, and `CLOCK.off` taken out of the contract. ## Known limitations of what shipped - **Multiplayer (phase 1):** each browser runs its own clock, so the players' worlds drift apart (server-run play fixes this for new sessions only); other players' POPs are not drawn on the map (open question 2); cards are what each browser reports, and the server does not check them; a save over ~60 KB sends only the card when the tab closes, and the save goes with that device's next push; a session network still makes its save on the page, so it misses 3.3.0's smoother saves in the worker; the capacity market and path moves are each player's own, with no market shared between players; the HUD chip in phone landscape wider than 760 px has not been checked by eye (worth doing when T4 changes the chip). Behind a reverse proxy, run the server with `--trust-proxy`, or every player shares one address's rate limits. - **Server-run engine (merged, not switched on):** a checkpoint is over its size budget, and so are a snapshot, a big realm's memory and a small network's day; a checkpoint written before c5c7ea9 restores close to exact, not exact; the engine has no per-call deadline of its own; a worker of its own whose session's loads all fail stays idle until the next unload; the path window would read routes the page never gets (`server-run.md`, "Corrections from building T2"). - **Build standard:** the game menu's last row of tiles is not full (7 tiles, or 8 in a multiplayer game, in rows of 3). The sheet's quote and "Bring everything up now" judge a line-system swap without routing (`bstdDarkOk()`: a quiet fiber, under 10% of its capacity, or a parallel link with room; any express with traffic holds its fibers, `bstdXpBusy()`), so the quote is the bill; only the intern routes to test. A quiet fiber with no way around can still go dark from the button for a day. An old save's `routers.model` moved into the standard (only from a running order with an intern hired; a paused one's is dropped) also becomes what new POPs get. A model or line system in the standard is a ceiling for the `routers` and `optup` orders (their next-one-up rule only applies with "keep"), as an order's own model was before; `optup` has no per-POP exceptions, so it moves fiber at POPs excepted from `std` too. - **Dark mode (#80):** the share card PNG and the web manifest stay light; the WebGL map was checked by tests only, not by eye in a real GPU browser. - **IPv4 (#150):** the intern does not manage addresses (optional in the issue); transfers are instant (real ones take weeks); lease-out income is not in the investor revenue share (open question 7); blocks granted to old saves can be sold after two years (a one-off windfall); CGNAT annoyance costs refunds but does not slow broadband growth. - **IPv6-only broadband:** no one-off grumble while a city's home routers are swapped; a new home in an IPv6-only city pays its router even when cash is short (a running cost, so a finished city never looks like a stopped swap). - **Express fiber (#58):** a whole fiber pair does not splice through a city (every fiber end is a POP; expresses cover the need; open question 5). - **Satellites (#83):** no WISP zones and no rented LEO tier (open question 6); the rented GEO and MEO circuits never fail (no rain fade or sun outage; Pie in the Sky has its own); no island volcano or Caribbean and Pacific hurricane events; no "Island Hopper" scenario; no footprints on the map; no satellite tab in the drag-to-link window (ordering is from the city panel); GEO/MEO losses and prices are design numbers; well-cabled islands (Wellington, Hobart) also count as "can be served"; MEO needs 5° elevation (10° would drop 416 pairs); Pitcairn's $120k satellite grant stays Pie-only. ## Housekeeping - `npm run perf -- --browser` runs with `PERF_CHROME=/usr/bin/chromium`. - The phase-1 playtest on port 8090 runs from its own checkout outside the repo, with its data in `mp-data/playtest`: leave it alone unless the user asks. Its one session can go once a server-run build replaces it (answer 4). - The six old wip worktrees under `.claude/worktrees/` wait for the user's answer (open question 9).