Prague Tram Peak Fleet.html (project root), artifact https://claude.ai/artifact/5Dt65EJ7F8YJnMbJugLGTi. Since 2026-09-28 it is generated by pipeline/praha (python scripts/run.py --state 2026-09-27); its README lists sources, steps and every manual decision. Olomouc uses the same scripts: olomouc-tram-peak-fleet. Shared rules are in pipeline/README.md (written by the Brno session). Older context: simutrans-city-sheet-rules.

User rules given 2026-09-28 (apply to every city):

• Designed trams: if the real records have too few trams, design the additions (cars from the line's recent history, free that day), marked "designed, not recorded".
• Splits: branches get separate Simutrans lines, sized by cycle_need (from pipeline/brno), by course range where the numbers show the branch, otherwise as a stated choice.
• Shared pools are OK and preferred for 5/6. Mark them everywhere, and design the timing as one circulation (pool_need).
• Verification: always ask the Brno session (simutrans-timetable-c6) to verify, and tell the Ostrava session (simutrans-timetable-10) about it.
• Display: no abbreviations; every vehicle cell is 3 lines (numbers · depot / full types · length / pak core).
• Pak sync: go through simutrans-custom-czech-pak128-77.
• Loop termini: −1 min (watch the phrase "no loop").

Change sheets (13 Oct 2026): for a network change the user rebuilds in game, they want a change sheet, not a fresh roster: keep the trams already in the game, move as few as possible, show what changed per line, new lines in full, only the trams that must change visible, everything else folded. Done as state 2026-10-12 (closure Nákladové nádraží Žižkov – Ohrada, 11 Oct – 18 Dec; 9/10 as two circles, 16 cancelled, new 30 and 37, 27 tram actions) via 04b_rebase.py + assets/page_changes.html; recipe in the README. The artifact now shows this change sheet; when the closure ends (18 Dec), make the reverse change sheet against 2026-10-12. Brno verification of it is still pending.

Why: the user coordinates several city sessions; Brno is the reference for the method. How to apply: for a new timetable, add a state file and rerun (recipe in the README). Before publishing a split, pool or design, send it to Brno for verification.