# PI-BLD-0003-V01 · Terrace Tower · 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 stepped-residential shell and kit brief that tests terrace usability, core continuity, and planting interfaces without assigning dimensions from the concept.

## Scope basis

P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Proposed optional world-life program, with no named story assignment.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Stepped slab sequence | The register identifies stepped slabs as the form-specific coordination issue. | source_record | Which slab/terrace transitions define this variant and which are occupied versus visual? |
| Core continuity | A continuing core through the stepped envelope is explicitly called out. | source_record | How does the core remain continuous across the proposed level changes? |
| Terrace dwelling kit | A typical terrace dwelling kit is proposed; its fit to each edge condition is unverified. | source_record | Which representative unit plan and balcony/terrace condition should anchor the kit? |
| Waterproofing and planting zones | The register requires these interfaces to be resolved, but supplies no technical details. | source_record | Where are planted zones separated from playable unit and circulation areas? |
| Rounded tower and wavy stepped terraces | Notes describe a rounded glass tower beside a lower stepped mass with soft S-curved slab edges. The visible terrace count is a card observation, not a floor schedule; front, smaller glass-volume connection, plan shape and roof use remain open. | source_notes | Are the tower and stepped mass connected, and which side is front?; What authored terrace sequence and tower plan shape control? |

## Modeling sequence

1. **Record the curved terrace signature** — Use the notes/index to preserve the soft S-edge terrace expression and lopsided tower/block relationship; do not convert visible bands into a floor schedule. Gate: No dimensions or floor count are inferred from the concept card.
2. **Draw stepped envelope and core section** — Prepare a section diagram of slab steps, core continuity, dwelling access, and planting/waterproofing interfaces. Gate: All floor heights, terrace depths and core dimensions remain proposed/null until sourced and reviewed.
3. **Plan one representative dwelling kit** — Map usable room zones, doors, furniture clearance and exterior terrace access for a selected typical unit. Gate: Do not assume one scaled unit fits every step or edge.
4. **Review terrace and planting separation** — Mark candidate circulation, shared terrace, planting and service interfaces separately. Gate: Legend selects shared/playable terrace scope before detailed modeling.
5. **Return a blockout evidence plan** — List the named views and measurements required to test core continuity, terrace usability and candidate kit reuse. Gate: No final shell/scale status until measured and reviewed.

## Required review views

- **Tower and stepped-block three-quarter view** — Show the rounded glass tower, lower wavy terrace mass and smaller glass volume; the notes identify only a single concept view.
- **Core and slab section** — Expose floor-to-floor relations, terrace transitions, core continuity and planting interfaces.
- **Typical dwelling/terrace plan** — Show clear usable room areas, openings and access to the selected terrace condition.
- **Shared-terrace access view** — Check whether the selected shared terrace connects to public circulation without crossing private units.

## Candidate kits

- CK-KIT-LOBBY
- CK-KIT-CORE
- CK-KIT-RESIDENCE
- CK-KIT-GARDEN
- CK-KIT-PROPS

## Proposed dependencies

- None proposed.

## Decision queue

- Are the rounded tower and stepped terrace block connected or separate, and which side is front? Owner: Legend. Resolution evidence: Creator-selected orientation and annotated massing plan/elevation..
- What slab/terrace geometry and core path are supported by the controlling source references? Owner: Design/layout author; Legend approves visual intent. Resolution evidence: Dimensioned section with source revision and explicit proposed/approved status..
- Which unit plan is reusable, and where does the stepped shell require a distinct layout? Owner: Legend with layout author. Resolution evidence: Representative furnished unit plan plus a family fit comparison..
- How are planted/wet zones separated from terrace access and the building shell? Owner: Design/layout author; Quik tests later integration. Resolution evidence: Annotated section/plan and subsequent collision/waterproofing interface review..

## Friday: can prepare

- Use the card notes to preserve the wavy curved terrace edges and contrast with the rounded tower; list unseen side and roof questions.
- 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 `fb2f003b80bde44076e00cd3a63872d890d54ea27b2e24f1c356d1ac17292948`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `78c6bede0ef76fd622045e1a4add911b6a41254a5a5645cfd035767c7ebc7482`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `a6a86cf6f4d9a8f5a9e4ad5555aed7e894e88cbbdecafde7d066366acac77fff`
- [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`
