# Master Plan Railway — single cross-town execution plan > **Builder entry point:** use the companion [Master Plan Builder Execution > Runbook](MASTER-PLAN-EXECUTION-RUNBOOK.md) for delegation, package order, > acceptance evidence, and stop conditions. This document remains the > reconciliation record; it does not authorize unguarded world edits. Status: **READ-ONLY RECONCILIATION COMPLETE — NO CONTINUOUS CROSS-TOWN PASSENGER RAILWAY YET PROVEN** Evidence cutoff: 2026-08-22 UTC Machine input: [master-plan-railway-report-input.json](master-plan-railway-report-input.json) ## 1. Decision Treat Masterplans 01–13 as one town system, but do not flatten their evidence or authority into one overwrite boundary. Accepted physical evidence controls built status; catalog records describe durable accepted objects; old design documents control intent only where a later current-world plan has not superseded them. The cross-town railway is a proposed delivery program, not an as-built claim. The current evidence proves bounded roads and pedestrian components, one 552-cell passive B09 rail, one bounded maintenance shuttle over indices `9..25`, and sealed Empty Eight future stubs. It does not prove a continuous cross-town passenger railway, public station network, or whole-corridor operation. The controlling subway work sequence is the [Passenger Railway Programme](PASSENGER-RAILWAY-PROGRAM-2026-08-22.md), with the [existing-rail inventory](PASSENGER-RAILWAY-INVENTORY-2026-08-22.md), [network/stop register](2026-08-22-passenger-railway-network-design.md), and [engineering standard](PASSENGER-RAILWAY-ENGINEERING-STANDARD-2026-08-22.md) as its supporting records. It converts the actual B09 guideway only through bounded packages; the restricted shuttle is not public service. Every new or converted passenger segment has a continuous behind-wall **6×6 service corridor** with controlled exits, built and QA-passed before powered passenger trials. ## Circulation correction — required before the next public-realm build Catalog completion and a one-cell normal-walk line do not prove a usable route. The current circulation audits identify three failed bidirectional links (C01 portal→L1, MainStreet portal→warehouse, and Observatory gallery→hub), two legacy one-tread cores (MainStreet H11 and the Ravensreach Library), and several districts whose route width/landing geometry is not current-proof. Every later route package starts with `CIRC-QA-CORE-01`: a fresh-source walkable-cell graph plus width, headroom, rise/run, landing, door, lighting, fluid, and ownership evidence. The companion [Builder Execution Runbook](MASTER-PLAN-EXECUTION-RUNBOOK.md) defines the required circulation classes and the ordered correction packages. The first Ravensreach circulation repair is accepted: the Moot upper spine now has a 7-wide × 6-high envelope, 1:2 flights, seven-deep landings, and a bidirectional normal-walk QA proof. Clerks Hall remains reachable but empty, and Attic Store still has no proven standable floor; those rooms remain a separate architectural package, not a furnishing pass. Conversely, the current Westlight census proves material fabric only; `CIRC-WL-ARRIVAL-01` and `CIRC-WL-ARRIVAL-ROAD-01` must survey route/egress geometry before any repair release is proposed. This plan authorizes no Minecraft, RCON, fleet, service, database, media, or publication mutation. ## 2. Current evidence identity - Latest accepted Combined Zones physical post: `data/worldsnap-r08am-post-20260822T161818Z` - Complete-save SHA-256: `0bcbba4fad530b8a5c22bbef295978cc4864270de652acba18372e445b584699` - Region SHA-256: `30f5c3394c4080d74156a59deb613290366c130e72a859261625117b8276541f` - Current read-only world catalog SHA-256: `bf2b31c121c7d270942f6fa73181f8c71409cfc24c01952d99d8cd35583c8c02` - Rebound R13 bounded-MVP acceptance: [PASS_R13_CONSOLIDATED_MVP_ACCEPTED](../../data/world-review/combined-zones-r13-consolidated-mvp-acceptance-r08al-r08am-doc-rebind-20260822T164000Z/r13-final-acceptance.json) Accepted snapshots remain provenance after a later physical commit. Every new physical package still needs a fresh same-invocation immutable source. ## 3. Whole-town status at a glance | Plan | Area | Current delivery class | Controlling conclusion | |---|---|---|---| | 01 | Cheyenne Mountain Complex | **Partial** | Bounded Cheyenne gallery/contact-route components exist under MP05; the original standalone 15-building program is not accepted as a completed whole. | | 02 | SubTropolis | **Partial** | Deep/service-route context exists; the full pillar-grid, tenant, lobby, climate, and public connection program is not commissioned. | | 03 | Houston Tunnel System | **Partial** | A bounded B07 headhouse and internal circulation exist; the full 24-block CBD/tunnel network and public through-route do not. | | 04 | Combined Complex | **Partial / superseded placement** | Normalized architecture remains design lineage; MP05 controls current-world coordinates and physical truth. | | 05 | Combined Zones | **Bounded MVP built; original broader program partial** | R07–R13 bounded MVP and the R08AL/R08AM Empty Eight round are accepted; major retained interfaces remain closed. | | 06 | Western Approach Road | **Cataloged built; current condition unverified** | Two complete records and the six-point road alignment exist; current route, drainage, clearance, and accessibility need re-survey. | | 07 | MainStreet America | **Accepted built; current condition unverified** | 630 complete records and one removed fence record; no fresh condition claim. | | 08 | Raven Rock | **Catalog/historical only** | 81 complete catalog records and historical dry T2b evidence exist, but no current accepted complex release; wet thresholds, route truth, accessibility, and network legibility remain open. | | 09 | Ravensgate | **Cataloged built; adjacent proposals unbuilt** | Frozen district and 13 records complete; pavilion/water/tunnel/access schedules are not physical acceptance. | | 10 | Ravensreach | **Built; operational configuration partial** | Physical town and MainStreet route accepted; citizen-fleet configuration remains proposed and unapplied. | | 11 | Town Expansion R1 | **Accepted built** | Terminal release, routes, media, catalog, exact interfaces, and rollback accepted. | | 12 | Westlight District | **Cataloged built; current condition unverified** | 59 complete interior records; later Town Expansion chronology and exact overlaps require reconciliation. | | 13 | Westlight Venue | **Accepted/cataloged built; current operations unverified** | Venue and 524-cell focal display accepted; current event, emergency, accessibility, and mode operation are not proven. | No plan is allowed to treat a neighboring plan's bounding box as shared-cell authority. ## 4. Area plans ### MP01 — Cheyenne Mountain Complex Built/accepted: - R10A supplies 594 accepted liner cells, a connected 660-cell secure-gallery route, and a retained 20-cell fail-closed cap. - R10G/H provide the bounded institutional contact sequence and passive route lighting. - R12A/M/O commission only bounded passive internal circulation to explicit holds. Not built or not proven: - The complete standalone 15-building program, Battle Cab visitor sequence, active controls, public access, exterior use, and whole-complex operation. Remaining design: preserve current B03/Z10 state; first survey the obstructed or unsupported `0..187` route indices and every secure/exterior interface. MP01 coordinates are not current-world setout. ### MP02 — SubTropolis Built/accepted: - The combined R03/R04 deep release changed 7,345 cells with an exact inverse. - R07C accepted 5,252 service-tunnel cover cells and 28 route openings after the first attempt compensated safely. Not built or not proven: - The full 200×200 pillar/tenant program, public lobby, vault/climate operation, complete visitor sequence, C3, or an open public rail/shaft link. Remaining design: freeze the exact current occupancy/route envelope, then separate tenant, lobby, climate, utility, C3, and vehicle packages. ### MP03 — Houston Tunnel System Built/accepted: - R07J provides a grounded deck and fail-closed 7×7 B07 headhouse. - R09A-D provides lower lobby/stair circulation only to its upper hold. - R09J/K accepts a 91-surface passive internal inspection component. Not built or not proven: - The full 24-block surface CBD, tower and food-court program, indices `0..20`, lower wet interface, exterior door, lift, smoke, power, drainage, accessibility, and a public through-route. Remaining design: resolve the exact wet and unsupported-gravity interfaces before designing any through-route. Surface towers and B07 circulation retain separate ownership. ### MP04 — Combined Complex Built/accepted: MP04's normalized program informed MP05 R00–R13. Not built or not proven: the original separate-world 1,500×1,500×800 layout, old ravine/skybridge variants, and its independent coordinate system are not current-world authority. Remaining design: use MP04 only for normalized child-program intent. MP05 or a later exact successor controls all physical coordinates and interfaces. ### MP05 — Combined Zones Built/accepted: - Six of six R07–R12 bounded dependencies plus G16–G19. - R08AL's eleven clean, lit, publicly viewable vacant south retail bays and restricted 12-room BOH. - R08AM's secured grand stair, 100-seat theatre, and consensual adults-only, non-explicit restricted private-club annex. - Enumerated R11 max-step-one highway/pedestrian surface components. - R12Q's 552-cell passive B09 rail and R12R's bounded maintenance shuttle. Not built or not proven: - A whole C1 corridor, passenger rail, interchange, hydraulic capacity, drainage, utilities, or public transport. - Empty Eight S06/north public opening, N06, wet/gravity smoke residual, riser, FIRE-EG-B, future stubs, and external systems. - P1-B12, C2, and C3. Remaining design: advance substantial disjoint packages from fresh sources; never enlarge a bounded surface, passive rail, or maintenance shuttle into a whole-system claim. ### MP06 — Western Approach Road Built/cataloged: a seven-block-wide Ravensgate-to-Westlight road through six authored points; two of two catalog records complete. Not proven: current bidirectional travel, vertical clearance, shoulders, drainage, lighting, bridge stairs, and accessibility. Remaining design: read-only reconcile Ravensgate, Westlight, and Town Expansion shared cells, then package only evidenced defects. ### MP07 — MainStreet America Built/accepted: 631 durable records—630 complete and the retired F01 fence removed—plus 96/96 material closure checks and accepted internal connectivity. Not proven: current damage/obstruction state or any new PassageWay, Raven Rock, regional-road, or Town Expansion interface. Remaining design: refresh condition and external-route seams before exact maintenance. Preserve containers, interiors, mountain routes, and the protected property envelope. ### MP08 — Raven Rock / Site R Catalog/historical evidence only: 81/81 durable features, five structures, 28 rooms, RR-Z5, and historical dry T2b evidence at `x=-145..-136`. This is not a current accepted Raven Rock bunker-complex release: S1 was rolled back and the historical T2B scope was superseded. Not built or not proven: any current Raven Rock complex release, the T2b wet edge, C2 wet Cavern C threshold, RR-N6 water interface, complete bidirectional comfort/accessibility, and uniform network signage. Remaining design: route-truth survey first, wet/gravity containment second, vertical-circulation/life-safety work third, legibility rollout last. ### MP09 — Ravensgate Built/cataloged: the frozen `X=-148..-64`, `Z=-562..-420` district, four buildings, seven rooms, and 13/13 complete records. Not built or not proven: adjacent pavilion, pool, monument, surface-water, tunnel, or access schedule proposals and current accessibility/condition. Remaining design: re-census the frozen district and approach-road endpoint; keep underground and hydrology default-deny. ### MP10 — Ravensreach Built/accepted: 63/63 durable features, eleven structures, 46 rooms, and the exact Ravensreach–MainStreet physical route. The first circulation repair is accepted: `CIVIC-RRCH-MOOT-UPPER-SPINE` replaced the old two-wide core with a guarded 7-wide × 6-high Moot vertical spine, two 1:2 flights, and seven-deep landings at `Y=73/80/87`. Independent QA proves a 509-cell bidirectional normal-walk connection; it does not claim the Committee, Meeting, Clerks, or Attic room programme is complete. Not built or not proven: the citizen-fleet configuration patch, fresh town condition, and new Town Expansion/underground interfaces. Remaining design: re-verify the physical route, then review the configuration as a separate nonphysical change. Never infer configuration deployment from a route PASS. ### MP11 — Town Expansion R1 Built/accepted: - 3,665,580 unique target cells and 483,016 exact forward/inverse groups. - 22/22 terminal route checks and 1,178/1,178 media checks. - 340/340 durable records. - 13 exact reviewed interfaces and zero unreviewed interfaces. Not built or not proven: requested program language broader than the imported exact `physicalClaim` records, or any future unreviewed change. Remaining design: preserve the immutable release chain; use new exact packages for future work. The natural-copper exception remains rollback-only. ### MP12 — Westlight District Built/cataloged: 59/59 durable records, including 14 buildings, 34 rooms, and ten stair-based vertical-circulation records. Not proven: current post-Town-Expansion condition, exact shared cells, waterfront/transport operation, and current live route clearance. Remaining design: reconcile the later terminal state and exact interfaces, then design maintenance with enclosure, water, container, and route controls. ### MP13 — Westlight Venue Built/accepted: 26/26 durable records plus the 524-cell reversible infinity screen release and its 48 accepted views. Not proven: current audience circulation, event modes, emergency lighting, accessibility, operations, and exact interface condition. Remaining design: read-only condition/operations survey before any mode or life-safety engineering; keep venue, district, approach road, PassageWay, and Town Expansion owners distinct. ## 5. Cross-Town Railway ### Proven existing pieces - One continuous 552-cell passive B09 rail component over indices `9..560`. - One authenticated bounded maintenance shuttle over indices `9..25`. - Enumerated R11 highway/pedestrian surface components, not a whole corridor. - Eight sealed Empty Eight future stubs. - The cataloged Western Approach Road feeder. - The accepted Ravensreach–MainStreet physical route. - Town Expansion's accepted cross-area routes and 13 exact interfaces. ### Missing before passenger railway construction 1. One exact, source-proven, owned alignment between selected town nodes. 2. Civil profile, foundations, water/drainage/utility treatment, and protected feature clearance. 3. Public stations and max-step-one/accessibility approaches with exact public/private boundaries. 4. Continuous supported passive rails and headroom. 5. Transactional controls, power, signals, vehicles, rescue, and rollback. 6. End-to-end and return-direction commissioning from one immutable post. ### Proposed service concept The proposed Cross-Town Railway would link Westlight, Ravensgate, Ravensreach/MainStreet feeders, Gateway, and the Combined Zones in stages. No exact alignment is selected here. The design freeze must derive one from a fresh terrain/ownership survey; it must not draw a centerline through catalog envelopes or open Empty Eight future stubs by implication. Restricted Cheyenne, BOH/private-club areas, FIRE-EG-B, and sealed future interfaces are not public stations. ## 6. Executable dependency order | Order | Gate | Current status | Required exit | |---:|---|---|---| | 0 | X0 evidence freeze | **Ready, read-only** | Hash-bind all thirteen plans, current catalog census, accepted posts, and supersession rules. | | 1 | X1 ownership/interface graph | **Ready, read-only** | One owner per cell; every seam exact; envelope-only overlaps rejected. | | 2 | X2 route/terrain/hydrology/asset survey | **Needs fresh immutable snapshot** | Exact road/walk truth, rail terrain, fluids, gravity, entities, BEs, utilities, protected features, and station approaches. | | 3 | X3 railway design freeze | **Blocked on X2** | Integer alignment, profiles, cross-sections, stations, reservations, packages, interfaces, and inverse strategy. | | 4 | X4 static enabling works | **Blocked on X3** | Accepted dry foundations, culverts/bridges, retaining, isolation, and closed station shells. | | 5 | X5 passive guideway/approaches | **Blocked on X4** | Continuous supported rail/headroom and safe public approaches to sealed holds. | | 6 | X6 power/control/signaling/rescue | **Blocked on X5** | Transactional mechanisms/BEs, fail-safe behavior, and rescue path. | | 7 | X7 bounded vehicle trials | **Blocked on X6** | Tagged forward/return probes with recovery and rollback. | | 8 | X8 passenger commissioning | **Blocked on X7** | One terminal post proves both service directions, stations, accessibility, evacuation, and preservation. | | 9 | X9 catalog/maps/publication | **Blocked on X8** | Import and publish only hash-bound accepted identities. | X0 and X1 are the next legitimate actions. X2 is the first step requiring a new saved-world capture. X3–X9 cannot be honestly started as construction from the existing evidence. ## 7. Hard execution boundaries For every physical package: 1. capture a fresh immutable same-invocation source; 2. use complete canonical block states and exact source guards; 3. prove one owner per cell and every shared interface; 4. exclude or exactly migrate entities, containers, block entities, mechanisms, fluids, gravity dependencies, utilities, and protected assets; 5. generate exact forward and inverse operations; 6. pass strict-noop parser checks and complete source preflight; 7. execute journaled and fail closed; 8. capture a fresh post, run exact/function/route QA, and prove rollback. Unknown state blocks only its exact package and dependent seam. It does not stop unrelated work. Conversely, a bounded package never authorizes a whole route, public/passenger service, accessibility, hydraulic capacity, utilities, or external opening. Database import, map generation, media capture, and publication follow physical acceptance. They cannot manufacture it.