A14. Settlement Layout Canonical Examples

This appendix summarizes how the three classic site-scale layouts—Spine, Ring + Radials, and Mesh—tend to score under the Complex Layout Score (CLS). It explains why they land where they do, the common strengths/weaknesses for each CLS element, and typical mitigations. The final sections cover “classic tropes” that underperform (and why), and why CLS is not tuned for very small (<10,000 m²) or ultra-large (>10,000,000 m²) complexes.

Scope note: CLS evaluates the between-space layout (nodes, links, bulkheads, utility loops, heavy-access), not the interior fit-out of each building node.

Practical use: When reviewing a proposal, identify its canonical base (Spine, Ring, Mesh), then check whether the design includes the mitigations that lift weak elements (loops, cross-ties, sector bulkheads, service alleys, reserved lots, dual/tri utilities). Report both the CLS-100 and the 8-element profile, plus a Future-Space Index (reserves, ROWs, transformability) to avoid local maxima.

Summary at a glance

Indicative scores assume a one/two-storey complex in the 10–120k m² band, default thresholds, and competent execution. Numbers are bands, not absolutes.

Spine

Definition. One dominant link (the spine) with nodes branching from it; may include 1–2 short cross-links (“mini-loops”).

Scoring profile (typical)

Safety & Resilience. Passes gates with care (two egress routes to havens often require at least one cross-link). Vulnerable to single-edge failure until a loop is closed. Fix: close two cross-links to form the first loop; distribute havens along the spine; add sector bulkheads every ~1,000–1,500 m².

Flow & Operations. Short average walks, but F2 (chokepoint) is the limiting factor: peak flows stack on the spine. Fix: periodic bypasses/cross-ties; widen select spine segments; keep bulkhead crossings moderate (≈0.3/trip).

Plan & Envelope. Naturally compact linear envelope; P1 (link-density) often near the sweet spot; good P3–P5 if reserves are platted behind branches.

Mass Efficiency. Low junction variety; few 4-ways; minimal curves → strong M2/M3. Civil works minimal (M4 good) because heavy-access rarely needs bridges/underpasses.

Construction & Maintenance. C7/C8 (heavy-access) are excellent; service clearances easy along a straight trunk. C2 (isolation spacing) easy to satisfy in a linear run.

Expandability. High X1 at branch tips; X3 (transformability) can be weak unless cross-links are pre-stubbed. Fix: reserve cross-tie rights-of-way and install utility stubs/sectionalizers (X5/X6).

Habitability. Predictable wayfinding; ensure H2 (buffering) by not dooring HAB directly to WRK/GAR off the spine.

Environmental & Energy. Single-feed risk unless a counter-rotating utility trunk is added (N2 improves markedly with the first loop).

Bottom line. The spine is quickest to stand up and easiest to service. It climbs into the 60s with a few strategic cross-links and a counter-loop for utilities, then wants to evolve into a Ring.

Ring + Radials

Definition. A closed pedestrian/utility loop (often two concentric rings) with spoke links to interior/exterior nodes; cross-ties relieve spoke hubs.

Scoring profile (typical)

Safety & Resilience. Strong S1/S2 (two disjoint routes are “baked in”). Sector bulkheads size compartments well (S3a), and density is easy to tune (S3b).

Flow & Operations. F1/F3 solid; F2 hinges on spoke-hub capacities and cross-ties. Fix: add inner mini-loop around high-use clusters; keep spoke lengths modest; cross-ties every ~100–120 m.

Plan & Envelope. Good P1 if spokes aren’t overdone; P3–P5 improve when interior reserves are platted off the inner ring and touched by ROWs.

Mass Efficiency. Discipline junctions (prefer T over X); keep curves limited on rings; M4 can slip if inner-ring access relies on many bridges/underpasses. Fix: a service boulevard or planned bridged cuts at intervals.

Construction & Maintenance. Without planning, C7/C8 sag for inner areas; with a boulevard and periodic drives, they recover. SKU standardization is straightforward (C4/C5/C6).

Expandability. Excellent X1 around the outer ring; X2 (live expansion) is high if dual-fed. X3 (mesh-readiness) rises quickly as cross-ties are reserved or added. X5/X6 are easy to satisfy on ring corridors.

Habitability. Placing commons around the loop gives H1 evenness; buffering (H2) is simple with ring-side storages.

Environmental & Energy. Dual loops with cross-ties push N2 high; hot uses can be zoned on spokes (N1).

Bottom line. The ring balances safety, flow, and growth. It tends to land mid-70s and is the natural mid-era topology, ready to Mesh by adding orthogonal cross-ties and a service-alley lattice.

Mesh

Definition. A lattice of links (rectangular or hexagonal cells) with sector bulkheads; nodes at cells/vertices. A dedicated service-alley lattice provides heavy-access to interiors.

Scoring profile (typical)

Safety & Resilience. Best-in-class S1/S2/S6: many short loops; removal of any single edge leaves two egress routes in most places. S3 stays balanced via sector lines.

Flow & Operations. F1/F3 high (short trips, alternative routes). F2 low (few chokepoints). Maintain sensible F4 by not over-sprinkling bulkheads at every link.

Plan & Envelope. P1 can drift high (too many links) if over-meshed; discipline spacing to stay in band. P3–P5 are easiest to satisfy (natural places for internal reserves with ROW contact).

Mass Efficiency. Junctions increase; M2/M3 need active management (favor T-junctions, long straights, minimal curves). Civil works (M4) stay low if the service-alley lattice is platted instead of ad-hoc bridges/underpasses.

Construction & Maintenance. With alleys every 2–3 cells, C7/C8 are excellent; without them, access penalties and the global −5 risk apply. Standardization (C4–C6) remains strong with a grid kit.

Expandability. Outstanding: high X1, high X2 (live add-ons), high X3 (already at target), high X7 (mergeability) because bays recombine along the grid.

Habitability. Commons can be distributed for H1; buffering (H2) is easy with offsetting; daylight proxies (H3) can be routed along select spines.

Environmental & Energy. Dual/tri-loop utilities route on different chases (N2 excellent); hot-use clustering isolates thermal loads (N1).

Bottom line. The mesh is the premium layout for large, long-life settlements—as long as the alley lattice and junction discipline are planned. It typically lands low-80s, with 90+ achievable as utilities and sectoring are perfected.

Classic tropes under CLS (and why they underperform)

1) One large pressure zone (“the giant dome / central domes”)

Fails gates. A single huge compartment exceeds the max sealed size (S3a) and can lack two independent routes to a haven (S2/S1). Dirty↔clean segregation is difficult on all shortest paths (S4).

Other hits. P3–P5 are moot if the whole hull is packed. M1/M2 look “simple,” but one breach = whole habitat.

Verdict. Romantic, but brittle. Even if internally “partitioned” by soft means, without true sector bulkheads it scores near zero or fails.

2) A chain of smaller connected units (“the camp of cans”)

Fails scope if disconnected. CLS requires one internally connected complex; EVA hops between units violate the shirt-sleeves objective.

If hard-connected (later): you inherit many joints/doors (M1), kinks (M2), and bulkhead crossings (F4) with little resilience benefit; flow times balloon (F1), and utility redundancy (N2) is poor unless retro-looped.

Verdict. Good for early sorties, not for civic life. As a city plan it scores poorly.

3) One huge building with internal bulkheads but few distinct nodes/links (“the cruise ship”)

Gates. It can pass S3a with many internal bulkheads and S4 if interlocks are placed carefully.

Weaknesses. S6 (robustness) and F3 (path diversity) are weak because routes share the same volume; C7 (heavy-access) to interiors becomes difficult without major civil works (M4); P3–P5 internal reserves get crowded out.

Verdict. Better than a dome, but still a local maximum: hard to expand into a mesh, expensive to service, and fragile to shared-space failures.

Why CLS isn’t tuned for <10,000 m² or >10,000,000 m²

Below 10,000 m² (outpost scale)

Design intent differs. Short missions, small crews, and EVA logistics dominate; many CLS gates (e.g., sector density, heavy-access lattice) are over-spec.

Metrics are noisy. A handful of nodes makes graph metrics (e.g., algebraic connectivity) and OD travel times unstable; Plan & Envelope bands and reserve lots are less meaningful.

Recommendation. Use CLS qualitatively (“provisional CLS”) or a simplified outpost rubric; switch to full CLS when the complex truly supports civilian-style shirt-sleeves life.

Above 10,000,000 m² (mega-city scale)

Transport regime changes. Walking-based Flow metrics break—internal transit (PRT, trams) replaces corridors; CLS doesn’t model multi-modal networks.

Verticality & layering. Multi-storey, subterranean galleries, and district-level plants change Plan, Mass, and C&M assumptions; “per 1,000 m²” bands no longer capture economics.

System interactions. Power, water, and thermal become regional utilities with separate resilience models; CLS’s N2 proxy is too coarse.

Recommendation. Treat CLS as a district-scale tool inside a larger urban model. Score each district (~0.1–1.0 km²) and manage between-district transit/utilities with city-scale frameworks.