# PI-BLD-0004-V01 · Twist 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 Twist Tall variant-specific envelope/core/facade questions and a single typical rotated-floor kit candidate.

## Scope basis

P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. The register says Tall and Compact are distinct envelopes; proposed program is lobby plus one typical rotated-floor office/residential kit.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Rotated floor expression | Tall variant: document the rotation sequence and stable-core relationship across the taller expression; do not infer a floor count from the name. The register requires the floor rotation to be documented. | source_record | What is the rotation sequence and which reference controls each transition? |
| Stable service core | The register requires a stable core to be documented alongside the rotation. | source_record | Does the core remain fixed through the sequence, and how do stairs/lifts/services connect? |
| Facade-to-room fit | The register identifies facade-to-room fit as a family-specific test. | source_record | How do windows/openings align with usable room zones on rotated floors? |
| Usable corner space | Corner-space usability is explicitly called out; no room dimensions are supplied. | source_record | Which corner conditions remain usable after structure, facade and furniture are accounted for? |
| Typical office/residential floor | A single reusable typical-floor kit is proposed for review, not approved. | source_record | Which use and room arrangement anchors the first kit? |
| Tall spiral ribbons and cylindrical glass body | Notes describe a slender cylindrical glass body wrapped by cream spiral ribbons. The card reads as braided/crossing ribbons while the location render reads as parallel decks; ribbon depth, support, front and terminations remain unresolved. | source_notes | Are ribbons crossing or parallel, and which reference controls?; Are they walkable balconies, and where do they start/end? |

## Modeling sequence

1. **Keep braid/deck conflict open** — Use the notes/index to document the crossing-card versus parallel-deck-render readings; prepare a path/termination diagram without choosing geometry. Gate: Legend review is required before ribbon geometry or walkability is modeled.
2. **Document rotation and core** — Create a floor-to-floor relationship diagram for rotation, core continuity, and facade orientation. Gate: Rotation values and levels remain unset until authored source evidence supports them.
3. **Fit one typical room kit** — Place only a schematic office/residential kit against the candidate rotated floor and flag facade/corner conflicts. Gate: Usable clear dimensions require a sourced plan and reviewed character/camera assumptions.
4. **Prepare variant-specific shell views** — Request matching front, top/typical-floor and vertical-section views for this asset and its sibling. Gate: Use views to compare geometry; do not infer measurements from perspective.
5. **Return open decisions** — List envelope, rotation, stable-core and interior-kit questions with evidence needed to resolve each. Gate: No shell or room kit is accepted by this prep record.

## Required review views

- **Twist Tall front/three-quarter view** — Resolve the card’s braided ribbon reading against the render’s parallel spiral-deck reading from selected authority.
- **Typical-floor plan from above** — Show the rotated facade, core, room zones and corner usability.
- **Vertical core/facade section** — Test whether the core remains stable while the floor/facade expression changes.
- **Typical-room/player-height view** — Reveal usable corners, opening placement and camera sightline after the room kit is selected.

## Candidate kits

- CK-KIT-LOBBY
- CK-KIT-CORE
- CK-KIT-TWIST
- CK-KIT-OFFICE
- CK-KIT-RESIDENCE

## Proposed dependencies

- PI-BLD-0004-V02: Sibling-family comparison: register requires Tall and Compact to be treated as distinct envelopes; this is not a scale or geometry authority. (proposed)

## Decision queue

- Are the Tall ribbons a crossing braid or stacked spiral decks, and are they walkable around the tower? Owner: Legend. Resolution evidence: Named reference authority, annotated ribbon path, and selected balcony enterability..
- Which typical office/residential layout is selected, and which corner zones are usable? Owner: Legend. Resolution evidence: Representative furnished plan with door, structure, furniture, camera and access checks..
- Which differences from PI-BLD-0004-V02 require distinct geometry or a separate shell revision? Owner: Legend. Resolution evidence: Side-by-side reference comparison and an explicit reuse/geometry-change record..
- What levels, core vertical connections and openings must be verified before shell approval? Owner: Quik with design/layout author. Resolution evidence: Measured shell and core/clearance evidence from the actual candidate, reviewed against the accepted dimension contract..

## Friday: can prepare

- Preserve the card/render difference between crossing ribbons and parallel deck-like ribbons; list support, termination and walkability questions.
- Prepare a schematic core/facade/typical-floor coordination sheet without reusing one sibling as the other’s scale.

## Friday: requires decision

- Legend selection of controlling references and the variant geometry differences to preserve.
- Reviewed rotation/core/floor schedule and chosen interior scope before producing a dimensioned shell or room kit.

## Friday: return evidence

- Variant comparison showing Twist Tall separately from PI-BLD-0004-V02, with source provenance.
- Dimensioned typical-floor and section proposal with statuses, open items, and candidate camera/player clearance tests.

## 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 `b0e4822b93058bc7aad5c5f08dc1ff32cd8caf880e71618efa76c025edb7075c`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `fb34a233fc6efec653042b7f88675292fb0f5893669d10abd0c3e4618553348d`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `61a31ab2b7f86dd26cc560cba326140e3f96d28732b76999e618b76669894348`
- [VISUAL_NOTES.md](../../../PI-BLD-0004-V02/VISUAL_NOTES.md) · SHA-256 `63de53b318b7f38078a8001595557383d7813877933944f221c76c60e9a505cf`
- [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`
