# PI-BLD-0013-V01 · Straight Tall · 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 the Straight Tall envelope, facade-grid, core and typical-floor questions without legacy label or sibling-scale assumptions.

## Scope basis

P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Proposed scope is lobby, typical office/residential floor kit and service core; the register explicitly rejects legacy H/LM mapping by name.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Straight envelope | The register names Tall/Slim as separate variants and requires their envelopes to be established. | source_record | What authored evidence distinguishes this envelope from its sibling? |
| Facade grid | The facade grid is a specific coordination item; no module size is provided. | source_record | What grid controls opening rhythm, room frontage and repeat bay boundaries? |
| Service core | Service core is included in the proposed program. | source_record | What core location, access route and stack are supported by source plans? |
| Typical office/residential floor | A reusable office/residential floor kit is proposed but not yet selected. | source_record | Which room arrangement and entry/core connection should be used as the first sample? |
| Lobby and appearance variation | Lobby is proposed; appearance changes may be separate from geometry only after compatibility review. | proposed_design | Which finishes are cosmetic and which openings/core changes require geometry revision? |
| Straight Tall shaft and shallow stepped top | Notes describe a plain rectangular glass shaft with corner/face fins, shallow top step and larger-looking podium than Slim. Visible card bands are not a floor count. | source_notes | Is the plan square or rectangular?; Are fins structural, and what controls the top? |

## Modeling sequence

1. **Preserve the quiet straight-tower expression** — Use notes to distinguish Tall’s plain shaft and shallow stepped top from Slim’s upper setback; do not derive scale or floors from visible bands. Gate: No legacy H/LM mapping by name.
2. **Establish envelope and facade grid** — Prepare an annotated elevation/plan showing candidate grid, openings, core and shell boundary. Gate: Grid/envelope values stay unset until supported by a source and reviewed.
3. **Plan typical floor and service core** — Identify one reusable office/residential floor candidate and show its service-core connection. Gate: Room clear dimensions are measured after walls, structure, furniture and access are considered.
4. **Compare sibling geometry and reuse** — Compare this variant to its sibling and classify cosmetic versus geometry differences. Gate: Do not scale one shell to create the other; footprint/core/opening changes require explicit variant/revision review.
5. **Return scope and measurement requests** — Provide the selected view/plan/section list and unresolved envelope, grid, core and enterability questions. Gate: No shell approval or placement without measured/reviewed inputs.

## Required review views

- **Straight Tall elevation** — Show shaft, facade fins, shallow stepped top and podium relationship from selected front.
- **Typical-floor plan** — Show a representative office/residential kit, core and usable facade frontage.
- **Core/facade vertical section** — Expose repeated floor relationship and service-core continuity without assigning a floor count.
- **Lobby-to-typical-floor route** — Check entrance, lobby, core and representative room connection once enterability is selected.

## Candidate kits

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

## Proposed dependencies

- PI-BLD-0013-V02: Sibling-variant comparison only; register requires distinct Tall/Slim envelope and facade-grid definition. (proposed)

## Decision queue

- What plan shape and top treatment control Tall, and are its fins structural or applied? Owner: Legend with design/layout author. Resolution evidence: Selected reference authority plus annotated plan/elevation/section..
- Which typical office/residential kit and lobby enterability are selected for the first sample? Owner: Legend. Resolution evidence: Asset brief scope plus a representative plan and room schedule..
- Which differences are cosmetic, and which require a geometry variant or shell revision? Owner: Legend with design/layout author. Resolution evidence: R05 reuse record tied to the actual geometry/opening/core comparison..
- How will legacy H/LM labels be handled without implying identity or scale? Owner: Legend / catalog owner. Resolution evidence: Source-backed crosswalk or explicit unresolved status; no name-only mapping..

## Friday: can prepare

- Compare the plain Tall shaft/shallow top to Slim’s setback and record front, plan-shape and facade-fin questions.
- List facade-grid, opening, core and typical-floor questions plus the first drawing set needed.

## Friday: requires decision

- Legend review of controlling references, selected enterability and the variant geometry boundary.
- Sourced/reviewed envelope and facade grid before shell dimensions or reusable geometry are locked.

## Friday: return evidence

- Variant-specific annotated elevation, floor plan and section with reference provenance and open dimensions.
- R05 reuse comparison recording which parts are genuinely shared and which are asset-specific.

## 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 `b6814b6de0492fd629301aa252784f18bf3ef7e03aa25a562cc1cea50c1c94de`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `78c6bede0ef76fd622045e1a4add911b6a41254a5a5645cfd035767c7ebc7482`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `fb3928c2b5aa7b96748fcf52c06227019ef29b5510589793767e4fdc6aac087d`
- [VISUAL_NOTES.md](../../../PI-BLD-0013-V02/VISUAL_NOTES.md) · SHA-256 `4ba837708785502a42ecafe17398c336e48f9641430c962552599c2554ad2867`
- [BUILD_REGISTER.json](../../../../../districts/D02-CrownKey/planning/BUILD_REGISTER.json) · SHA-256 `bb0a893c54a83f490e9ff59197e593ea1093a393209c7714d57997cd3c06df3e`
- [README.md](../../../../../districts/D02-CrownKey/planning/README.md) · SHA-256 `1367a53f00d00c42b2f39482b9e75693d332fb9394d5582dcea2dd14d65c4b2a`
- [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`
