Lost SoulsCrown Key / preparation

New exterior candidate · R01

Open the model and drawings.

Proposed isolated geometry, four views from the same model, elevations, section and editable sources. Dimensions, shell acceptance, interiors and engine verification remain separate.

Exterior package and downloads →

Draft production prep · R01 · 16 October 2026

Crescent Hotel

Prepare a P1 Tier D hotel candidate with reception/lounge, guest-room kit, public dining, selected terrace and separate service/loading route.

Current R02 scope requires a complete usable asset package. Design and isolated authoring can proceed; proposed dimensions, shell selection, site placement and actual engine checks retain explicit evidence status.

Current production program · R02

Exterior, usable spaces and a complete handoff.

Design a usable Crescent Hotel with Reception and waiting lobby, Furnished guest room, Hospitality / terrace lounge, furnishings and connected access.

Required spaces

Required exterior coverage

Required interior coverage

Delivery state: Scoped — complete design: not yet evidenced; reviewed build packet: not yet evidenced; engine verification: not yet evidenced.

Audited source baseline: Catalog/source preparation and starter records; no dedicated asset design pack, drawings or model identified.

Owner: OA2 (proposed seat assignment) · Independent reviewer: OA1-assigned independent read-only reviewer

Five-seat production plan and kickoff briefs → · Full current scope → · Download all31 programs

R02 supersedes conflicting shell-only or deferred-interior recommendations in the earlier preparation records below. Proposed room uses do not create new story canon; references do not establish completed geometry.

PI-BLD-0009-V01P1buildingunset

Prepare now

Open source concept image ↗Crescent Hotel concept reference
Existing concept reference; appearance evidence, not a measured layout or accepted build reference.

Preparation / not geometry

What Quik will build and review.

Component labels come from this asset’s prep record. This board is a task map, not a dimensional drawing.

Modeling sequence

  1. 01Reconcile reference rolesNo marina image establishes parcel or scale.
  2. 02Trace curveLegend selects curve/endpoints before bay layout.
  3. 03Block arch/balconiesPlan/section reveal arrival and balcony continuity.
  4. 04Lay out hotel routesTier D scope/access decided before dressing.
  5. 05Check roof/quayNo water-edge or engine clearance claim without approved datum.

Planned review views

Components & scope evidence

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.

ComponentRole and evidenceOpen questions
Wavering crescent shellLong 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 bandsCurved edged balconies, glass rails and glazing.
source_notes
  • How do bands change around the curve and which levels are playable?
Sweeping arrival archDrive-through arch over glazed lobby, plus smaller end arches.
source_notes
  • Does arch pass through and how are vehicles/pedestrians separated?
Guest/public roomsReception, guest room, dining and terrace from proposed Tier D program.
source_record
  • Which rooms are playable and how do their routes connect?
Roof pool/pavilionsPool and cabana/round pavilion details differ between views.
source_notes
  • Which roof composition controls and how is access protected?
Service/quay interfaceLoading/laundry route and quay tie are proposed needs.
source_record
  • How does service reach building without inventing placement?
Modeling sequence & review views
  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.

Shared kits & asset dependencies
Decision queue & Friday return

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: 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.
Downloads & source inventory