The build standard owns the router model and the line system; one owner per fiber

The routers order reads its model from the build standard (bstd().g, 'keep'
is the old next-model-up rule) and the optical upgrade order its line system
(bstd().sys). The Ops sheet shows "From the build standard: X" with a button
to the sheet. Old saves move a model or line system from an order that was
running into the standard when it has none of its own; a paused order's or
an unhired intern's setting is dropped. opsParam refuses model/sys and points
at bstdSet.

The build standard's order is a generator now: every first job that takes a
fiber dark goes through the optical order's routing test (opsDark, in the
route worker in play), under one shared budget of dark swaps a night (two for
Kevin) and the week-long memory for a failed fiber. A fiber one order worked
on is the other's no more that shift, and decom keeps waves the standard just
upgraded. The plan is checked at every job, since the shift rests between
them: a POP gone or changed by hand meanwhile is skipped. The button still
runs the whole plan at once on the page.
This commit is contained in:
jvanvik 2026-11-07 06:55:01 +01:00
parent 032470f486
commit fbae6fc3ed
22 changed files with 573 additions and 138 deletions

View file

@ -6,16 +6,9 @@ planned or known, not built.
## Promised and not done yet
1. **Router model and line system set in one place only.** The build standard (`S.popStd.g`, `S.popStd.sys`) and two
standing-order settings say the same thing: the `routers` order's `model` (upstream 1e7638c) and the `optup` order's
`sys` (upstream 647e302). Neither ever steps down, so they do not fight, but a player can pick two different targets.
Plan: the Build standard sheet becomes the only place to pick them. The `routers` order reads its model from the
standard, and `optup` its line system (their lists turn into a line "from the build standard: X, change"); sanitize
moves an old `model`/`sys` setting into `S.popStd` when the standard has none.
2. **One owner per fiber for line systems and optics.** `std` (sys/opt targets: a quiet fiber, or a parallel link with
room) and `optup` (one full routing without the fiber, one a night) can each darken a fiber in the same shift. Let `std`
use `optup`'s check (`opsDarkOk`) for line-system swaps, or skip fibers `optup` is working on. Today `std` also holds
any fiber that carries an express with traffic; `opsDarkOk` would handle that case by itself.
1. and 2. are built: the router model and the line system are picked in the Build standard sheet only (the `routers` and
`optup` orders read `bstd().g` / `bstd().sys`; sanitize moves an old setting into `S.popStd`), and `std` takes a fiber
dark on `optup`'s routing test (`opsDark()`), sharing its budget a night, with one owner per fiber a shift (`X.fib`).
## Next features
@ -58,8 +51,14 @@ planned or known, not built.
the server does not verify them; a save over ~60 KB sends only the card when the tab closes; the HUD chip in phone
landscape wider than 760 px was not measured. Behind a reverse proxy, run the server with `--trust-proxy`, or every
player shares one address for the rate limits.
- **Build standard:** the game menu has 8 tiles in a multiplayer game (7 otherwise), so the last row is not full; a wave
the standard just upgraded can still be handed back the same day by `decom` if a bigger parallel link carries it.
- **Build standard:** the game menu has 8 tiles in a multiplayer game (7 otherwise), so the last row is not full. The
sheet's quote and "Bring everything up now" still 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. 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):** red error text on dark tinted cards is about 3.8–4.3:1 (bold, but below AA 4.5); 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; lease-out income