You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d950d46
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: specs/flow-routes.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,8 +109,12 @@ The city builder streams node annotations in two passes over per-origin compress
109
109
110
110
CA catalog publication uses at most eight concurrent uploads, consuming origin encoding and SQLite destination reads on the caller thread. Only eight catalog payloads can remain queued; the ordered result map and deterministic compressed objects match serial publication byte-for-byte. Routing/checkpoint computation remains serial. Separate topology/publication timings and stage logs expose the post-routing work.
111
111
112
+
Build the full rollout under `routes-city-candidate/v1`, then run `check-city -k routes-city-candidate/v1` and `promote-city` in the same remote task. The checker uses eight bounded catalog reads while preserving origin/destination iteration and floating-point aggregation order on the caller thread. Its small report binds acceptance to the exact candidate index MD5. Promotion refuses capped catalogs or a changed index, server-side copies only indexed CA objects with source size/hash checks and conditional copies, and publishes the production `index.json` last. It copies no checkpoints and downloads no catalog bodies to the laptop. Server-side copy and source ETag conditions are supported by R2's [S3 API compatibility table][r2-copy].
113
+
112
114
The existing 2024 census is a sizing baseline, not a current-population guarantee. Refresh `routes-census.yml` for `202510-202609` before the full build; September remains provisional. Catalogs retain the immutable census object key, so a later census refresh does not invalidate an older build's audit. New or rare pairs outside the chosen population continue to use explicit fallback arcs/straight animation paths. The full JC/Hoboken catalog still overrides the city/sample namespace for its covered pairs.
113
115
114
116
`ctbk flow-routes system -d YYYYMM` streams the month's immutable animation days, verifies hashes/counts, excludes carry-in and round trips, and assigns actual monthly directed-pair counts to route alternatives. It publishes `flows/v1` with exact encoded/routed/fallback/roundtrip accounting, source object hashes, provisional status, the route context and graph key, and expected signed street volumes. Missing routes are reported as uncovered volume rather than invented street traffic. `.github/workflows/routes-system.yml` runs this remotely for one month with a serialized writer; monthly automatic extension and time-mode interpolation remain follow-up work.
115
117
116
118
`/stations?m=2506&network=1` shows the opt-in whole-network layer with direction chevrons and opposing lanes when no station is pinned. It loads one monthly volume object and one shared graph, without downloading every origin catalog. The legend reports the actual non-roundtrip routed share and explicitly names an unbuilt month. Selections continue to use lazy origin/destination catalogs; a missing city index keeps today's NJ/sample behavior. Unit tests cover exact directional expected volumes and floors; a complete hermetic two-origin build/audit tests both indexes and checkpoint resume; the monthly fixture proves carry/roundtrip exclusion and uncovered-pair accounting. Browser checks cover network opt-in/reload/view preservation and an unbuilt month. Chrome CIC could not connect because the installed browser runtime references a missing service module; automated Chromium rendering was checked instead, without claiming HCCSx verification.
0 commit comments