# PROCITY — Round 22 lane instructions (from Fable, integrator)

Date: 2026-07-16 · **v4.0-beta SHIPPED** (`201a2bb`, tag on origin; matrix 10 towns × 7 gates
green; qa `--strict` GREEN; selfcheck now 161k). R21 review, short: A's cluster bias turned out
to fix a **systemic** stranding (11 of 15 venues under threshold → 0 of 15; Newtown's RSL moved
2,228 m → 29 m from the retail hub), D closed its own finding with the before/after table, B and
C cleared the missed R20 items, E pulled the entire v4.0 town pack forward (**22 towns · 1,192
shops · 298 heroes · all 8 states/territories**, byte-identical re-runs, non-gating as briefed),
and F closed the gate honestly — including recording that the one budget edge got WORSE, and
correcting its own first bad money shot instead of shipping it. **Lane G is merged** at the
boundary as ruled (`dd4489c`); the godverse town passes the sweep (161,264 green).

Round 22 is **v4.0: THE EPOCH CLOSE** — the tri diet first, the pack absorbed, the release tour
on real streets, the Lane G items, docs freeze, the tag. Tag **`v4.0`** at close.

## The ledger

1. **The `venue_night` tri diet (FIRST — the one open gate edge).** F's re-measure: katoomba
   200,965 → **221,935 tris (+11%)**, bendigo ~201k. A's poster cap worked (438→111); **E's
   density widening ate the savings** — more shops = more night geometry at the venue block.
   Two steps, measure-first:
   a. **B diagnoses** (streetscape budget is B's): a layer-by-layer `renderer.info` breakdown at
      katoomba `venue_night` (buildings / posters / furniture / pools / peds / interiors-spill) —
      name the driver with numbers, half a day.
   b. **The named owner fixes** (A if it's plan geometry (lot/poster counts), B if render
      (merge/instance/LOD), E if asset tris), F re-measures. **Must land < 200k** — this is a
      release round; the stress view IS the gate.
2. **A absorbs the pack (the round's spine).** E's 17 new towns + Lane G's `newtown_godverse`:
   feed all through the lift, pin the **36 waiting goldens** (selfcheck prints them), and absorb
   what the meccas surface — **fitzroy is 160 shops, 2× anything absorbed so far**; expect
   overflow/capacity work (your R20 fence, now at scale; drops stay counted by cause). The
   cluster bias + poster cap + junction pipeline all run at 23-town scale for the first time —
   anything that breaks gets the usual treatment: fix or fence, written down. Batch the pins:
   ONE golden commit at the end.
3. **The Lane G items (queued from FABLE_TO_LANE_G):**
   - **B**: per-town bookmarks — resolve bookmark poses against the ACTIVE plan (the
     synthetic-coord teleports land inside OSM geometry; you did this for `poseForVenue` — the
     old set gets the same treatment, plus F's R21 cluster-pose finding below is the right
     primitive to share).
   - **F**: `DBG.enterShop(selector)` grows name/type/id matching (cross-repo QA one-liners).
   - **E**: refresh the stale MODELBEAST notes (trellis_mac proven, the :8777 queue, ultra's
     ⚠️ finish-farm warning folded into pipeline docs verbatim, credited).
   - **Lane G (on ultra, their branch): G2a is GREEN as of the beta tag** — static per-shop
     real-stock atlases behind `?stock=real`, per the ruling. **C + E: the contract review is
     due this round** (atlas per shop · interior budget ceilings are C's · fail-soft to parody).
     Answer in G-progress or LANE_C_PUB; G builds to it next.
4. **The release tour (F).** `tour_shots.py` grows the v4 set → `docs/shots/release_v4/`:
   the Fremantle golden-hour hero (have it), a mecca main street (fitzroy, once A absorbs), a
   thin-tail town (proof the floor holds), the synthetic town (unchanged, the control), and one
   `?classic=1` frame (the covenant, visible). **Use your cluster-pose finding as the tour's
   posing primitive** (project the densest spatial cluster onto its front edge, stand on the
   road) — and publish it as a `dbg.js`-consumable so B's bookmark fix (#3) shares it.
5. **Interiors + citizens at pack scale (C + D, after A).**
   - **C**: sampled door-soak across all 23 towns (your five-town harness, scaled — sample
     ~10 doors/town, every archetype covered town-set-wide). One table.
   - **D**: the fitzroy stress audit (160 shops — the densest citizen field yet: patronage,
     rosters, determinism) + spot-check one thin-tail town (does 12 shops still read alive?).
6. **Docs freeze + the tag (F last, with A).**
   - A: CITY_SPEC v4 amendments final (schema v2, the lift, connectivity rulings, cluster bias,
     poster cap), charter risk-list retired-or-carried line by line.
   - E: provenance table v4-final (22 towns ODbL + the pack's SOURCES.md; the licence spine
     stays complete).
   - F: README v4 section (the towns ARE the product — say it with the selector + tour), notes
     §22, `qa.sh --strict --matrix` green, tag **`v4.0`**, push. **After the tag: Fable writes
     the epoch retro** (not a lane deliverable).

## Laws

Charter laws hold. Golden discipline: A pins the 36 in ONE commit; the tri-diet fix may move
real-town goldens if it's plan-side (amendment law, same commit as the fix); synthetic
`0x3fa36874`, gig `0xb1d48ea1`, fixtures, classic — frozen, as always. The 200k stress edge is a
BLOCKING gate this round (release rounds don't ship known breaches — the R19 precedent).

## THE EXACT RUN ORDER

1. **Start together: B (tri diagnosis, #1a) + A (pack absorb, #2) + E (#3 notes + #6 provenance
   prep).** B's diagnosis is half a day — it lands while A grinds.
2. **When B names the tri driver: the owner fixes (#1b)** — if it's A, fold into the absorb; if
   B/E, parallel commit. **F re-measures immediately.**
3. **When A pins the goldens: start C (#5 soak) + D (#5 audits) + F (#3 enterShop + #4 tour
   build-out).** C+E answer G2a's contract review (#3) in this window too.
4. **When C, D, and the tri re-measure are green: F closes (#6)** — docs, matrix, tag `v4.0`,
   push. Fable retro follows.

Waves: **[B, A, E] → [tri-fix owner] → [C, D, F-prep] → [F close]**.

## Standing

- **John — nothing blocks this round.** FYI: Lane G is merged and their G2a (real stock atlases,
  static half) is green to start on their branch per the standing ruling; the C/E contract
  review happens this round. The tri-diet is blocking for the tag — if the fix turns out to need
  scope you'll hear it loudly, not silently.
- **After v4.0 (the retro decides, do not start):** G2b/G3 design (the economy — both
  integrators + you) · the v4.x backlog (GIG_RANGE chunk lookup · instrument LOD · tram tri diet
  · flag retirement · awning ripple · fabric canopies) · and the next epoch conversation
  (editor vs multiplayer vs the GODVERSE deepening).