# PI-BLD-0002-V01 · Split Complex · preparation R01

**DRAFT_PRODUCTION_PREP** · 2026-10-16

Draft preparation only; not an issued reference pack, shell, approval or construction release. Foundation hold remains in force; preparation does not authorize construction or accept dimensions, placement or engine readiness.

Prepare a two-core complex brief that tests the paired-lobby and skybridge relationships before choosing interior scope or shell dimensions.

## Scope basis

P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. The register gives optional everyday-life use and no named story assignment.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Paired lobbies | The proposed program explicitly calls for one lobby at each block. | source_record | How do each lobby and the shared circulation connect to the two cores? |
| Two service cores | The register specifically calls for measuring two cores; their sizes and positions are unset. | source_record | What separation, core continuity, lift/stair content, and service interfaces are required? |
| Skybridge and garden | The register describes a skybridge garden only if selected playable. | source_record | Is the bridge garden enterable, a visual connector, or deferred? What level/egress relationship must be tested? |
| Typical office/residential floor | Reusable office/residential floor is proposed; the balance and precise kit boundary are undecided. | source_record | Which one typical floor is the first candidate kit, and which of its clearances must be proven? |
| Asymmetric blade towers and open-gap bridge | The notes describe two non-mirror towers with an open gap and a bridge; the card reads one slim arched level while the location render notes describe a two-level arrangement with planted upper deck. Card/render massing, podium and planting also conflict. These are concept observations, not dimensions. | source_notes | Which side is front and which source controls the different tower profiles?; Is the bridge one level or two, and how does it meet the two cores? |

## Modeling sequence

1. **Compare visual conflicts** — Use the notes and index to keep the card/render alternatives explicit: non-mirror silhouettes, bridge level count, podium continuity and planting boundary. Do not average conflicting concepts. Gate: Legend selects reference authority and resolves bridge/podium alternatives before geometry interpretation.
2. **Map core and bridge interfaces** — Prepare a dimensionless relationship sketch for both cores, bridge endpoints, public routes and service routes. Gate: No bridge level, span, or clearance is locked without authored dimensions and review.
3. **Choose candidate enterability** — Separate lobby, typical office/residential floor and optional skybridge garden scopes; identify only the representative sample needed for review. Gate: Tier C remains proposed until Legend selects scope.
4. **Prepare floor and section requirements** — List the plans/sections needed to evaluate two-core continuity, shared circulation, bridge access and egress. Gate: Plan dimensions, floor levels and access evidence must be sourced before blockout acceptance.
5. **Return the fit question set** — Deliver open interface questions and a proposed shell/kit review sequence for the designer and Quik. Gate: No shell or placement acceptance from concept prep alone.

## Required review views

- **Open-gap paired-tower elevation** — Show the two different tower profiles, sweeping blade fins and bridge gap from the selected front; notes flag orientation and bridge-level ambiguity.
- **Core and bridge relationship plan** — Locate the two cores, bridge endpoints, lobby entries and candidate public/service paths.
- **Bridge/core vertical section** — Expose candidate bridge level, headroom, attachment, shared circulation and egress questions without assuming values.
- **Lobby and typical-floor plan** — Test whether the proposed reusable office/residential floor can connect to both lobby/core systems.

## Candidate kits

- CK-KIT-LOBBY
- CK-KIT-CORE
- CK-KIT-OFFICE
- CK-KIT-RESIDENCE
- CK-KIT-SERVICE

## Proposed dependencies

- None proposed.

## Decision queue

- Which side is front and which tower/podium profile controls where the card and render disagree? Owner: Legend. Resolution evidence: Named visual authority plus annotated elevation; preserve the bridge-level and planting conflicts until resolved..
- What measured relationship should control the two cores, bridge levels, and bridge clearances? Owner: Legend accepts design scale; design/layout author supplies candidate dimensions. Resolution evidence: Dimensioned plan and section with named source, status, owner, and approval; no pixel-derived values..
- Which typical office/residential kit is the first candidate for this family? Owner: Legend. Resolution evidence: An asset brief selecting program and reuse scope, plus a representative plan..
- How will shared circulation and bridge egress be demonstrated? Owner: Quik with layout author. Resolution evidence: Reviewed access route plus later measured blockout/engine evidence..

## Friday: can prepare

- Review notes for the asymmetric blade towers and record the one-versus-two-level bridge and podium/planting conflicts.
- Create a source-backed reference/variant question list and a non-metric blockout checklist for review.

## Friday: requires decision

- Creator review of controlling visual references, proposed enterability, and any candidate dimensions before shell acceptance or placement.

## Friday: return evidence

- Source paths and revisions, annotated plan/section checklist, unresolved questions with owners, and the exact model/source revision if any candidate blockout is later authorized.

## Controlling records and source inventory

- Dimension contract: [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json).
- Building R05 / District R05 / Spatial Imagery R01; dimensions and approval remain governed by their own records.
- [current-decisions.md](../../../../../../docs/current-decisions.md) · SHA-256 `8001f9a1c613b326b030da3ace10947a3021dc12f9273b7c7fa46d0ade10d382`
- [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json) · SHA-256 `a35e33e05be7ff779653d020f4b6849cc8a14272f780f35926c3e9c1c6fb0c0e`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `dcfbf6674ded41cab605eab4dea8cf520c466504363d8cc30ae29c8bdb9a595f`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `1e3b67375cb121fec292e2949955bd9de3ada2d70a034b99034171bd54cea2d3`
- [BUILD_REGISTER.json](../../../../../districts/D02-CrownKey/planning/BUILD_REGISTER.json) · SHA-256 `bb0a893c54a83f490e9ff59197e593ea1093a393209c7714d57997cd3c06df3e`
- [ASSET_INPUTS_A.json](../../../../../districts/D02-CrownKey/planning/prep/R01/ASSET_INPUTS_A.json) · SHA-256 `8193933c210b0cfaa825428aae1a0d1d2b2fbe8f11d6c7befc0db81d7892d2d4`
- [KIT_CATALOG.json](../../../../../districts/D02-CrownKey/planning/prep/R01/KIT_CATALOG.json) · SHA-256 `52525e0754aee464c84793b3b3cfe2b6ae4c95981fd2bf3e67c2d91c02ada0b9`
- [GUIDE.md](../../../../../protocols/building/R05/GUIDE.md) · SHA-256 `006818490740b4bd9e3994a428da95390f9f4dd987c6fd6f67a8dd1dbbc24509`
- [README.md](../../../../../protocols/building/R05/README.md) · SHA-256 `ecb4c6b0bf144a5da037ba8817528c40cb59ce272bc9ca63b3d187e704dc2715`
- [ASSET_BRIEF_TEMPLATE.json](../../../../../protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json) · SHA-256 `d6f80614e4f7d87f7cd569c7b1320cf6ad58c2021fab1955ff274a157d8df054`
- [BUILDING_DIMENSIONS.json](../../../../../protocols/building/R05/templates/BUILDING_DIMENSIONS.json) · SHA-256 `46fefd72cb9e5bd0b1e98822a1773401f96c35d91ce57fc821d3bbc624e69631`
- [current.json](../../../../../protocols/current.json) · SHA-256 `c7be63113d117523e6b2e608149e6b31620f2f50436f4fbbeebdd1ffb005881a`
- [README.md](../../../../../protocols/district/R05/README.md) · SHA-256 `f95ad3a6c25f181898fd3be47eac800b39b5f1790387f8e93d5450e75ace5a7d`
- [GUIDE.md](../../../../../workflows/spatial-imagery/R01/GUIDE.md) · SHA-256 `288df4dc11896d4e606f8dc49f8b1a6969679d1fad50fad7595f3e2c8b9ad173`
- [SCALE_REGISTER.md](../../../../../world/SCALE_REGISTER.md) · SHA-256 `f56c19d5dbfd1c9b9228c4f34327f908ebee5c9bc9c9d3db2d617fa802accc8e`
