INIANLAN NextGen
Master Plan

Report 01 · evidence refreshed 28 August 2026

The world, not
just the paperwork.

Use this as the operating map: where to explore, what is actually built, which doors remain closed, and the exact work sequence now moving the city toward a usable passenger subway.

13plans reconciled
30evidence-backed built claims
21unbuilt / unproven claims
29/29evidence bindings passed

Start here

Where you can go,
and what it means.

These are known location anchors for getting your bearings, not a promise that every surrounding room, portal or underground route is public. The state label is the important part.

Built / verify route locally/tp @s -93 ~ -387

Ravensreach civic core

Market, Moot and historic civic fabric. The rebuilt Moot spine is a proven route; the Library still needs its own circulation repair.

Built fabric / access review pending/tp @s -344 ~ -500

Westlight + Ravensgate

The western venue and district cluster sit on the Approach Road. Current material evidence is strong; a fresh public-egress survey comes before changes.

Built / public gateway candidate/tp @s 0 ~ 17

MainStreet + Arrival

The central town surface and visitor edge. Do not use the warehouse, H11, or C01 interior as a passenger shortcut.

Built public gallery / restricted annex separate/tp @s 1661 50 45

Empty Eight retail

Vacant retail shells, public gallery and theatre evidence exist. Sealed rail stubs, BOH and restricted areas are not public routes.

Built maintenance guideway / not passenger rail/tp @s 2048 130 -748

Combined Zones / B09 mountain

B09 is the one proved rail component. Its current cart is restricted maintenance only while its subway conversion is surveyed and released.

Do not treat as public destinationUse Underground Navigation / POI Directory

Raven Rock + deep systems

Raven Rock has catalog/history, not a current accepted public complex. C01, PassageWay, B03 and secure bunker systems remain separately controlled.

Whole-world orientation

Find every
built area.

The Build Index covers the town and the east-side Combined Zones, then explicitly marks systems that sit below ground. The current surface atlas below is a separate, fresh seven-map set; every map is linked directly instead of being hidden behind two preview tiles.

Current 26 August decisions

Held interfaces,
shown plainly.

A separate twelve-map volume brings together the current MP01, MP02–MP05, MP08, MP13 and SYS03 decision evidence. It is deliberately not a construction-completion atlas: ownership, containment, egress, and control holds stay visible on every card.

Read-only current-source evidence

12 maps · 10 held interfaces · 2 civil-only referencesHistorical atlas packages are retained separately; this additive volume does not rewrite their record.

Current design front

Mapped before
it is built.

These maps expose the C01 public-vertical work and the one bounded Cobalt station-pair candidate. They are design evidence only: neither map authorizes a route opening, protected-fabric change, or public commissioning.

Surface mobility amendment

Rail beside a
walkable city.

Roads and paths are now the rights-of-way for a staged above-ground rail-and-promenade system. These maps are exact design and survey evidence. AG-1's three piers and two-deep girder are physically built and post-verified; the loop, station, track, promenade, and old-road conversion are not. Existing routes stay usable until a replacement segment has passed its guarded route and return tests.

Rail + promenade module mapRail + promenade module · 23-block guideway: protected five-wide path, opaque barrier, and separate six-wide service galleryExterior paired-guideway loop mapExterior paired-guideway loop · Eight source-bound survey candidates; fluid and unknown ground remain excluded from build selectionTown anchors and held spurs mapTown anchors and held spurs · Seven normal-walk anchors; existing routes retained while three interfaces require exact contractsFirst finite exterior survey mapFirst finite exterior survey · SL-02-N-AG0-0576: dry pier-bearing survey cell set; no operation, deck, or track authorizationAG-1 as-built support plan mapAG-1 as-built support plan · 1,165 verified support cells: three pier pads and a two-deep girder; rail and promenade remain unbuiltAG-1 as-built support profile mapAG-1 as-built support profile · Continuous pier shafts and the Y82–83 girder verified against the immutable post-state snapshotAG-2 as-built promenade plan mapAG-2 as-built promenade plan · 820 verified civil cells: protected five-wide path, sealed gallery, lighting, and an explicitly empty nine-wide rail reserveAG-2 as-built promenade section mapAG-2 as-built promenade section · Post-verified protected walking route above AG-1 support; rail, power, signals, and service are not builtAG-3 as-built passive rail plan mapAG-3 as-built passive rail plan · Two isolated unpowered tracks, rail-side barrier, and a three-wide maintenance-only recovery path—no station or serviceAG-3 as-built passive rail section mapAG-3 as-built passive rail section · Exact rail support, headroom, separation, and recovery-path evidence from the immutable post-stateAG-4 adjacent continuation hold survey mapAG-4 adjacent continuation hold survey · The immediate continuation is held by water/sand bearing failures and a saved item; the next clean module is disjoint, not a connectionAG-4 water and gravity hold mapAG-4 water and gravity hold · 7,656 observed wet cells escape five measurement faces; no local plug, liner, drain, or bearing replacement is authorized

Latest guarded physical releases

As-built maps,
not inferred status.

These maps bind the newest finite releases to their immutable post state and independent QA. They show exact containment or restricted safety work only; neither card opens a route, endpoint, egress, or public area.

C01 arrival gravity-support as-built plan immutable post-release mapC01 arrival gravity-support as-built plan · 33 polished-deepslate support cells · 219-cell verified halo · arrival-cadence seam and retained gravel preservedC01 arrival gravity-support section immutable post-release mapC01 arrival gravity-support section · Seven protected floor supports · two clear headroom cells · exact reversible liner only, no route commissioningC01 L1 arrival cadence as-built plan immutable post-release mapC01 L1 arrival cadence as-built plan · Three exact sea-lantern inlays · 81-cell verified dry halo · nine prior inlays and two gravel holds retainedC01 L1 arrival cadence clearance section immutable post-release mapC01 L1 arrival cadence clearance section · Three-cell extension · flat walk surface and two clear headroom cells verified · not a route or service commissioningC01 Return-02 as-built plan immutable post-release mapC01 Return-02 as-built plan · 28-station, five-wide × five-clear return · 768 canonical post-state cells · protected switchback excludedC01 Return-02 as-built elevation immutable post-release mapC01 Return-02 as-built elevation · Corrected immutable QA verifies both directions and four exact 5×5 endpoint contracts · no commissioningC01 approach containment 08 immutable post-release mapC01 approach containment 08 · 19-cell finite gravity liner · immutable post state · 121-cell verified dry haloC01 approach containment 07 immutable post-release mapC01 approach containment 07 · 47-cell finite gravity liner · immutable post state · 262-cell verified dry haloC01 approach containment 06 immutable post-release mapC01 approach containment 06 · 99-cell finite gravity liner · immutable post state · 357-cell verified dry haloB07 descent east-wall lighting immutable post-release mapB07 descent east-wall lighting · Five fixed fixtures · dry three-wide core and both controlled door sets retainedB07 ice-edge receiver lighting immutable post-release mapB07 ice-edge receiver lighting · Three sealed-receiver fixtures · dry core and exterior bulkhead retainedB07 descent west-wall lighting immutable post-release mapB07 descent west-wall lighting · Five fixed fixtures · dry stair core and controlled doors retainedC01 approach containment 04 immutable post-release mapC01 approach containment 04 · 42-cell finite gravity liner · immutable post state · 226-cell verified haloC01 approach containment 03 immutable post-release mapC01 approach containment 03 · 116-cell finite gravity liner · immutable post state · 400-cell verified haloB07 central bypass lighting immutable post-release mapB07 central bypass lighting · Six fixed internal fixtures · sealed restricted bypass · no route or egress openingB07 lower-pressure gallery lighting immutable post-release mapB07 lower-pressure gallery lighting · Three sealed-ceiling fixtures · dry segment and pressure closure retained

Build board

The next things
that create a city.

This is the actionable order—not a generic list of blockers. Each card is a bounded release lane, so one bad interface cannot stall unrelated construction.

  1. 01
    Survey captured

    B09-P0 · mountain conversion survey

    Fresh B09 source has been captured. Resolve the exact guideway, 6×6 service-corridor route, exits, fluids, entities and ownership before placing conversion blocks.

  2. 02
    Choose exact alignment

    Cobalt first pair · Westlight ↔ Ravensreach

    Freeze the shortest independently useful western station pair, including two public headhouses and its parallel 6×6 service corridor.

  3. 03
    Blocked on survey

    Access before track

    Build pedestrian routes, exits, vertical access and controlled service doors first. Rail cannot open a station that cannot be walked safely.

  4. 04
    After access QA

    Guideway, controls and closed trial

    Then build passive guideway, service corridor, power and block control; test one cart and one station pair before any passenger opening.

Evidence chapters

The proof that
sits under this plan.

These are parts of the Master Plan workspace: use them for exact maps, screenshots, coordinates, and construction limits. They do not override the register or its hard boundaries below.

Cross-Town Railway

A proposal with a
deliberate starting line.

A staged Cobalt/Amber exploration subway, then Data/Gateway/Empty Eight and mountain extensions, with a separately converted B09 scenic shuttle. No sealed future stub, back-of-house/restricted space, or maintenance route is presented as passenger access.

Accepted ingredients
  • MP05 R12Q: one continuous 552-cell passive B09 rail component over indices 9..560
  • MP05 R12R: one authenticated bounded maintenance shuttle over indices 9..25
  • B09 is the only existing rail component; it remains restricted maintenance infrastructure while its separate subway-conversion lane is surveyed and released
  • MP05 R11: enumerated bounded max-step-one highway/pedestrian surface components; rail and whole corridor remain held
  • MP05 Empty Eight: eight future line stubs remain sealed
  • MP06: cataloged Ravensgate-to-Westlight road feeder
  • MP10: accepted Ravensreach-to-MainStreet physical route
  • MP11: accepted cross-area roads/routes and exact interface contracts
Still required for passenger rail
  1. One exact owned alignment connecting intended town nodes
  2. Complete civil profile, foundations, hydraulic/drainage/utility treatment, and protected-feature clearance
  3. Stations and accessible pedestrian approaches with exact public/private boundaries
  4. Continuous passive rails, controls, power, signaling, vehicle operations, rescue, rollback, and a solid-wall-separated 6x6 service corridor with controlled exits
  5. End-to-end and return-direction commissioning against one immutable terminal post

Alignment. No exact alignment is selected by this reconciliation. The first design freeze must choose a source-proven route from current terrain and exact ownership, not draw a line through catalog envelopes.

Stations. Use accepted public anchors only after landing, accessibility, enclosure, and ownership surveys. Restricted MP01/MP05 areas are not public stations.

Delivery. Survey and access first; civil guideway and the mandatory 6x6 behind-wall service corridor next; active vehicles and public service last. Each bounded package must be independently useful, guarded, journaled, reversible, and post-verified.

MP01—MP13

The complete plan register.

This is the detailed evidence register behind the quick guide above. “Built” is a bounded proven claim, not a blanket declaration that an entire district or every route inside it is finished.

MP01Partial

Cheyenne Mountain Complex

Original standalone design is not accepted as fully built; bounded Cheyenne and institutional-route components are physically accepted through Masterplan 05.

Accepted / built
  • R10A: 594 liner cells, connected 660-cell secure gallery route, retained 20-cell cap
  • R10G/H: accepted institutional contact sequence and passive lighting
  • R12A/M/O: bounded passive internal circulation to fail-closed holds
Unbuilt or unproven
  • The full original 15-building standalone program and Battle Cab visitor sequence are not accepted by MP01 evidence as a completed whole
  • Secure/public access, active controls, direct terminal access, exterior use, and whole-complex operation remain uncommissioned
Proposed remaining design
  • Preserve the accepted B03/Z10 state, then separately survey the uncommissioned indices 0..187 and every secure/exterior interface
  • Only design further rooms or active systems after exact current-source ownership, route, entity, block-entity, and rollback closure
Hard boundaryMP01 coordinates are design lineage, not current-world setout; MP05 placement and accepted release evidence control.
MP02Partial

SubTropolis

The normalized underground shell/service-route context is materially present through MP05, but the full standalone 200×200 pillar grid and tenant program are not commissioned as a complete SubTropolis destination.

Accepted / built
  • R03/R04 combined deep-tunnel release changed 7,345 cells with exact reversal
  • R07C accepted 5,252 service-tunnel cover cells and 28 route openings after a compensated first attempt
Unbuilt or unproven
  • Full tenant grid, public lobby program, climate/vault operations, and complete visitor sequence
  • C3 PassageWay interface and any public shaft/rail connection beyond accepted bounded holds
Proposed remaining design
  • Freeze an exact current-world SubTropolis occupancy and route envelope before tenant fit-out
  • Treat the public lobby, C3, utilities, climate systems, and vehicles as separate releases
Hard boundaryDo not infer that the original standalone footprint or tenant schedule exists from the accepted tunnel shells.
MP03Partial

Houston Tunnel System

Bounded B07 public-core circulation and headhouse components are accepted; the full 24-block Houston surface/tunnel program is not accepted as a completed whole.

Accepted / built
  • R07J accepted a grounded deck and fail-closed 7×7 B07 headhouse
  • R09A-D accepted lower lobby/stair circulation to an upper hold
  • R09J/K accepted only a bounded 91-surface upper inspection component
Unbuilt or unproven
  • Full 24-block CBD, four tower program, four food courts, end-to-end public route, lift, smoke, power, drainage, exterior opening, and accessibility
  • The full through-route across indices 0..20 and wet/gravity interfaces
Proposed remaining design
  • Resolve the exact wet lower interface and unsupported-gravity boundary before considering a through-route
  • Keep surface towers/food courts separate from B07 route engineering and require independent ownership
Hard boundaryR09K is passive internal inspection circulation only; it is not public Houston commissioning.
MP04Partial

Combined Complex normalized architecture

Architectural normalization is accepted as design lineage, while current-world placement and physical truth are superseded by MP05.

Accepted / built
  • Its normalized program informed MP05 R00-R13 geometry and the accepted Combined Zones build
Unbuilt or unproven
  • The original separate-world 1,500×1,500×800 arrangement is not current-world physical authority
  • Old ravine, skybridge, portal, and geological narrative variants are superseded where MP05 differs
Proposed remaining design
  • Use MP04 only for normalized child-program intent; resolve every actual coordinate and interface through MP05 or a later exact successor
Hard boundaryAuthority reconciliation status is RECONCILED_FOR_DETAILED_DESIGN_NOT_AUTHORIZED_FOR_WORLD_EDITS.
MP05Built Partial Original Program

Combined Zones

The bounded MVP and R08AL/R08AM Empty Eight round are accepted; retained caps and broader systems remain explicit local nonclaims.

Accepted / built
  • R07-R12 six of six bounded dependencies and G16-G19 accepted
  • R08AL: eleven clean lit publicly viewable vacant south retail bays plus restricted 12-room BOH
  • R08AM: secured grand stair, 100-seat theatre, and consensual adults-only non-explicit restricted private-club annex
  • R11: enumerated bounded max-step-one highway/pedestrian surfaces
  • R12Q/R12R: one 552-cell passive B09 rail component and a bounded maintenance shuttle over indices 9..25
Unbuilt or unproven
  • Whole C1 corridor, passenger rail, interchange, hydraulic capacity, drainage, utilities, and 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
Proposed remaining design
  • Use the R08AM post only as immutable provenance; capture a fresh source for every later physical package
  • Advance substantial disjoint packages, keeping every local physics/mechanism/interface hold fail-closed
Hard boundaryThe accepted bounded MVP must not be expanded into whole-system commissioning.
MP06Built Cataloged Reverify Current Condition

Western Approach Road

Two durable records are complete; exact current route condition, clearance, drainage, and accessibility were not re-surveyed by the retroactive plan.

Accepted / built
  • Seven-block-wide Ravensgate-to-Westlight road through six authored points; two of two catalog records complete
Unbuilt or unproven
  • Current bidirectional traversal, vertical clearance, shoulders, drainage, lighting inventory, bridge stairs, and accessibility
Proposed remaining design
  • Read-only reconcile exact shared cells with Ravensgate, Westlight, and Town Expansion
  • After route/condition QA, design only evidenced maintenance defects as guarded packages
Hard boundaryNo repair by broad corridor box; shared endpoint cells require a named owner and fresh snapshot.
MP07Built Accepted Reverify Current Condition

MainStreet America

Accepted as-built campus with 630 complete durable records and one intentionally removed fence record; current condition still needs a fresh survey before alteration.

Accepted / built
  • 631 durable records: 630 complete and retired F01 fence removed
  • Physical closure with 96/96 material checks and accepted bidirectional internal connectivity
Unbuilt or unproven
  • Current damage/obstruction state and any new PassageWay, Raven Rock, regional-road, or Town Expansion interface
Proposed remaining design
  • Refresh condition and exact external-route seams before maintenance
  • Preserve the protected property envelope, interior routes, containers, and mountain interfaces
Hard boundaryHistorical site-plan alternatives and property-wide bounds are not overwrite authority.
MP08Partial

Raven Rock / Site R

Catalog and historical evidence document the area, but no current accepted Raven Rock bunker-complex release exists; wet thresholds, route truth, accessibility, and any future complex work remain unproven.

Accepted / built
  • 81 durable catalog features, including five structures, 28 rooms, circulation records, and RR-Z5, are historical/catalog evidence
  • Historical dry T2b evidence exists at x=-145..-136; S1 was rolled back and T2B was superseded
Unbuilt or unproven
  • Any current accepted Raven Rock complex release, T2b wet edge beyond x=-136, C2 wet Cavern C threshold, and RR-N6 water interface
  • Complete bidirectional comfort/accessibility and uniform signage across the network
Proposed remaining design
  • Survey route truth and exact wet/gravity interfaces first
  • Sequence wet-edge containment before vertical-circulation and network-legibility packages
Hard boundaryCatalog completion and historical T2b evidence do not authorize a current Raven Rock complex, tunnel, or public route; wet edges require exact same-snapshot fluid topology and inverse proof.
MP09Built Cataloged With Unbuilt Proposals

Ravensgate

The frozen district and 13 durable features are complete; adjacent pavilion, pool, monument, water, tunnel, and access proposals are not established as built.

Accepted / built
  • Frozen X=-148..-64, Z=-562..-420 district; four buildings and seven rooms; 13/13 catalog records complete
Unbuilt or unproven
  • Neighbor schedule proposals, underground openings, surface-water additions, and current accessibility/condition
Proposed remaining design
  • Re-census the frozen district and approach-road endpoint
  • Design public-realm, accessibility, neighbor interfaces, and hydrology only after default-deny ownership closure
Hard boundaryThe Pavilion East/Ravensgate schedule is a planning reservation, not a build release.
MP10Built Partial Operational Configuration

Ravensreach

The physical town and exact Ravensreach–MainStreet route are accepted; the citizen-fleet configuration patch remains proposed and unapplied.

Accepted / built
  • 63/63 durable features complete, including eleven structures and 46 rooms
  • Accepted exact Ravensreach–MainStreet physical route
  • CIVIC-RRCH-MOOT-UPPER-SPINE: 7-wide × 6-high stair spine with 1:2 flights, seven-deep landings, and post-QA bidirectional walk proof
Unbuilt or unproven
  • Citizen-fleet configuration activation, fresh condition survey, and new Town Expansion/underground interfaces
Proposed remaining design
  • Re-verify route/doorstep/lighting state, then review configuration as a separate nonphysical change
  • Package physical maintenance independently from bot configuration
Hard boundaryPhysical route PASS does not imply the proposed configuration was applied.
MP11Built Accepted

Town Expansion R1

R1 is a completed accepted release and immutable stewardship baseline, not an unbuilt proposal.

Accepted / built
  • 3,665,580 unique target cells; 483,016 forward and inverse groups
  • 22/22 route checks, 1,178/1,178 media checks, 340/340 durable records
  • 13 exact reviewed cross-scope interfaces and zero unreviewed interfaces
Unbuilt or unproven
  • Any program language broader than the exact imported physicalClaim fields
  • Any future change not bound to a new snapshot and exact interface reconciliation
Proposed remaining design
  • Preserve the immutable chain; survey current drift before any maintenance
  • Use new disjoint exact packages rather than modifying historical operations
Hard boundaryNatural copper policy is rollback-only and exact; it never authorizes forward work.
MP12Built Cataloged Reverify Current Condition

Westlight District

The interior district is cataloged as built; chronology and exact overlap with later Town Expansion require a fresh reconciliation before change.

Accepted / built
  • 59/59 durable records complete: one district, 14 buildings, 34 rooms, and ten vertical-circulation records
  • Ten multi-floor structures have stairs and no primary ladders
Unbuilt or unproven
  • Current condition after later Town Expansion, exact shared cells, waterfront/transport operations, and live route clearance
Proposed remaining design
  • Reconcile the later terminal snapshot and exact Westlight/Town Expansion interfaces
  • Design maintenance only after enclosure, water, route, and container preservation checks
Hard boundaryDistrict/scan envelopes and catalog entrances are not work volumes or safe-teleport claims.
MP13Built Accepted Reverify Operations

Westlight Venue

The venue and focal-display release are accepted/cataloged; current event operations, circulation, emergency behavior, and condition remain unverified.

Accepted / built
  • 26/26 durable records complete: bowl, theatre, members club, rooms/circulation, and infinity screen
  • VEN-WL-01 changed 524 exact cells with rollback and 48 accepted screen views
Unbuilt or unproven
  • Current audience circulation, mode controls, emergency lighting, accessibility, event operations, and exact interface condition
Proposed remaining design
  • Run a read-only condition/operations survey before any mode or life-safety engineering
  • Keep venue, Westlight district, approach road, PassageWay, and Town Expansion ownership distinct
Hard boundaryHistorical completion is not a current operational inspection; event activation requires separate evidence and authority.

X0—X9

Evidence first.
Passenger service last.

This is a dependency chain, not a progress bar. Later stages stay closed until the immediately controlling evidence exists.

X0

Evidence freeze

Hash-bind MP01-MP13 sources, current catalog census, accepted posts, and supersession rules.

Ready Read Only
X1

Cross-scope ownership and interface graph

One owner per cell; every shared seam exact; all catalog-envelope-only overlaps rejected as authority.

Ready Read Only
X2

Current route, terrain, hydrology and asset survey

Bidirectional road/walk route truth, candidate rail terrain, fluids, gravity, entities, block entities, utilities, protected features, and station approaches are exact.

Requires Fresh Immutable Snapshot
X3

Cross-Town Railway design freeze

Exact integer alignment, profiles, cross-sections, stations, reservations, interfaces, package boundaries, and inverse strategy approved.

Blocked On X2
X4

Static enabling works

Disjoint dry foundations, culverts/bridges, retaining, drainage isolation, and station shells accepted without active service claims.

Blocked On X3
X5

Continuous passive guideway and public approaches

Continuous supported rail, full headroom, sealed holds, max-step-one pedestrian approaches, and exact rollback accepted.

Blocked On X4
X6

Controls, power, signaling and rescue

Mechanisms and block entities migrate transactionally; fail-safe behavior and rescue path proven.

Blocked On X5
X7

Bounded vehicle trials

Tagged vehicles pass bounded forward/return runtime probes with recovery and rollback evidence.

Blocked On X6
X8

End-to-end passenger commissioning

One immutable post proves all stations, service directions, accessibility, evacuation, operating modes, and off-target preservation.

Blocked On X7
X9

Catalog, maps and publication

Only accepted physical identities are imported and published; every map/media object is hash-bound to X8.

Blocked On X8

Non-negotiable truth boundary

What this report cannot authorize.

01

This plan contains no block operations and authorizes no world, database, service, or publication mutation.

02

A catalog status or planning envelope is never a source guard, target set, route pass, or overwrite right.

03

Use a fresh immutable same-invocation source for every physical release; historical accepted snapshots remain provenance only after later commits.

04

Require complete canonical block states, exact forward/inverse operations, strict-noop parser checks, exact source preflight, live entity clearance, block-entity/container/protected exclusion or exact reviewed migration, journaled execution, fresh post snapshot, post QA, and rollback preflight.

05

Unknown fluid, gravity, entity, container, mechanism, utility, drainage, or protected state fails only the affected package and dependent interface; it does not become a global plan hold.

06

Do not open Empty Eight future stubs, C2, C3, P1-B12, secure Cheyenne, FIRE-EG-B, or any exterior/utility/drainage interface without a separate exact release.

07

Do not claim whole-route, passenger, public, rescue, accessibility, hydraulic, utility, or operational commissioning from a bounded surface, passive rail, or maintenance-shuttle package.

08

Database import, map generation, media capture, and external publication follow accepted physical QA and never manufacture acceptance.

Machine-checked acceptance layer

86 structural checks passed.

The report input, narrative, current catalog, accepted post, and source evidence are hash-bound. The reconciliation made no live call, world edit, database mutation, or passenger-service claim.