# PI-BLD-0009-V01 · Crescent Hotel · 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 P1 Tier D hotel candidate with reception/lounge, guest-room kit, public dining, selected terrace and separate service/loading route.

## Scope basis

V01 is a long gently wavering S/crescent with layered balconies and sweeping arch; V02 is compact two-tier rectangle and must be tested separately. Marina context is not an approved placement.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Wavering crescent shell | Long curved/S-shaped plan with rounded end; preserve curve rather than forcing simple arc. | source_notes | Is plan an S-curve or arc, and which end faces quay? |
| Guest balcony bands | Curved edged balconies, glass rails and glazing. | source_notes | How do bands change around the curve and which levels are playable? |
| Sweeping arrival arch | Drive-through arch over glazed lobby, plus smaller end arches. | source_notes | Does arch pass through and how are vehicles/pedestrians separated? |
| Guest/public rooms | Reception, guest room, dining and terrace from proposed Tier D program. | source_record | Which rooms are playable and how do their routes connect? |
| Roof pool/pavilions | Pool and cabana/round pavilion details differ between views. | source_notes | Which roof composition controls and how is access protected? |
| Service/quay interface | Loading/laundry route and quay tie are proposed needs. | source_record | How does service reach building without inventing placement? |

## Modeling sequence

1. **Reconcile reference roles** — Keep isolated building card and contextual arrival render distinct; log roof differences. Gate: No marina image establishes parcel or scale.
2. **Trace curve** — Keep editable curve controls; no radius inferred from perspective. Gate: Legend selects curve/endpoints before bay layout.
3. **Block arch/balconies** — Separate arch, lobby glass, guest floors and balcony/roof parts. Gate: Plan/section reveal arrival and balcony continuity.
4. **Lay out hotel routes** — Connect selected public, guest, dining, terrace and service paths separately. Gate: Tier D scope/access decided before dressing.
5. **Check roof/quay** — Show pool/pavilions and shore tie as proposals; datum/placement pending. Gate: No water-edge or engine clearance claim without approved datum.

## Required review views

- **Arrival axon** — Show arch, wavering plan and balcony layers.
- **Curved plan** — Show guest/service circulation and arch pass-through option.
- **Through-arch section** — Show lobby relation and clearance as measured or unresolved.
- **Roof plan** — Show pool/pavilions with source conflict noted.
- **Guest/service route** — Trace selected public, guest and staff paths.

## Candidate kits

- CK-KIT-HOTEL-ROOM
- CK-KIT-HOTEL-PUBLIC
- CK-KIT-SERVICE
- CK-KIT-CORE
- CK-KIT-PROPS

## Proposed dependencies

- PI-BLD-0009-V02: Candidate guest/public kit comparison only after separate fit; curved multi-storey shell differs from compact V02. (proposed)

## Decision queue

- Is plan S-curve or single arc and which side faces quay? Owner: Legend. Resolution evidence: Selected authority and measured plan/orientation..
- Does the arch pass through, and how are paths separated? Owner: Legend + Quik. Resolution evidence: Ground plan and tested clearance after dimensions selected..
- Which roof/pool/pavilion composition controls? Owner: Legend. Resolution evidence: Decision-linked roof plan..
- Which Tier D rooms and service route are playable? Owner: Legend + Quik. Resolution evidence: Selected shot list, room schedule and route evidence..

## Friday: can prepare

- Prepare isolated curve/arch/balcony blockout with dimensions unset.
- Draw guest/public/service route options and roof-conflict sheet.

## Friday: requires decision

- Curve/front, arch pass-through, roof composition and playable scope.
- Measured shell and water datum before room fit or engine route checks.

## Friday: return evidence

- Editable shell and guest-room sample candidate.
- Curved plan, arch section, roof plan and route diagram.
- Separate V01/V02 fit and reuse record.

## 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`
- [ASSET_BRIEF.json](../../ASSET_BRIEF.json) · SHA-256 `f8793c1b88cd6be46f76d8e18ef96b08dd73147f147f80d011089e55677f09b2`
- [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json) · SHA-256 `848ba74b540d64422e191245c79aa00db286269e3a45ced8fdbe5100939518e6`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `0394fa2aac08a133fadf4e40a5d50d7dc1c0d6fd8b386d744ed40f9e83b118d3`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `034eb286c8715bf856ee3f61dec9cc3fca8daa01969e4a4f2eb3f52feb6842a7`
- [BUILD_REGISTER.csv](../../../../../districts/D02-CrownKey/planning/BUILD_REGISTER.csv) · SHA-256 `45be2626767273dce204c95a1233c943cdcdc119fce7a17eda4810c3606a0d52`
- [BUILD_REGISTER.json](../../../../../districts/D02-CrownKey/planning/BUILD_REGISTER.json) · SHA-256 `bb0a893c54a83f490e9ff59197e593ea1093a393209c7714d57997cd3c06df3e`
- [ASSET_INPUTS_B.json](../../../../../districts/D02-CrownKey/planning/prep/R01/ASSET_INPUTS_B.json) · SHA-256 `13b830ec89a557291c006de40e75574fa3be9cb844bb5c021f978e1a021d2698`
- [KIT_CATALOG.json](../../../../../districts/D02-CrownKey/planning/prep/R01/KIT_CATALOG.json) · SHA-256 `52525e0754aee464c84793b3b3cfe2b6ae4c95981fd2bf3e67c2d91c02ada0b9`
- [Building_R05_GUIDE.md](../../../../../handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md) · SHA-256 `006818490740b4bd9e3994a428da95390f9f4dd987c6fd6f67a8dd1dbbc24509`
- [README.md](../../../../../protocols/building/R05/README.md) · SHA-256 `ecb4c6b0bf144a5da037ba8817528c40cb59ce272bc9ca63b3d187e704dc2715`
- [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`
