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

Straight Tall

Prepare the Straight Tall envelope, facade-grid, core and typical-floor questions without legacy label or sibling-scale assumptions.

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 Straight Tall with Reception and entrance lobby, Office / workspace sample, Meeting room, 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: OA3 (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-0013-V01P2buildingunset

Prepare now

Open source concept image ↗Straight Tall 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. 01Preserve the quiet straight-tower expressionNo legacy H/LM mapping by name.
  2. 02Establish envelope and facade gridGrid/envelope values stay unset until supported by a source and reviewed.
  3. 03Plan typical floor and service coreRoom clear dimensions are measured after walls, structure, furniture and access are considered.
  4. 04Compare sibling geometry and reuseDo not scale one shell to create the other; footprint/core/opening changes require explicit variant/revision review.
  5. 05Return scope and measurement requestsNo shell approval or placement without measured/reviewed inputs.

Planned review views

Components & scope evidence

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.

ComponentRole and evidenceOpen questions
Straight envelopeThe 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 gridThe 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 coreService core is included in the proposed program.
source_record
  • What core location, access route and stack are supported by source plans?
Typical office/residential floorA 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 variationLobby 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 topNotes 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 & review views
  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.

Shared kits & asset dependencies
Decision queue & Friday return

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