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

Frame Compact

Prepare the Frame Compact frame/core/floor-kit coordination record and identify which shared parts can be tested across the height family.

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 Frame Compact with Lobby revealing the exoframe / core, Private office, 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-0006-V03P2buildingunset

Prepare now

Open source concept image ↗Frame Compact 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 roof-level frame expressionDo not extend frame members above roof without source/design direction.
  2. 02Diagram exoframe and coreEvery numeric value requires a source, status, owner and reviewer.
  3. 03Check one office/meeting kitClear dimensions and circulation are candidates until the shell is measured and furnished-player reviewed.
  4. 04Compare variant reuse boundariesDo not turn a cosmetic/material reuse candidate into geometry reuse without compatible interfaces.
  5. 05Return variant evidence planNo shell or engine acceptance is implied.

Planned review views

Components & scope evidence

Scope basis: P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Register program is lobby, typical office kit and selected shared meeting room; each height variant requires its own exoframe, intrusion, clear-height and service-core check.

ComponentRole and evidenceOpen questions
Exoframe bayThe register requires the structural bay to be coordinated, but gives no span or module dimensions.
source_record
  • Which source reference controls bay rhythm and where does it join slabs/façade?
Structural intrusions and clear floorThe register calls out intrusions and clear floor height as explicit fit checks.
source_record
  • Which structure zones reduce usable room/circulation clearance in this variant?
Service coreA service core is in the proposed program and must be coordinated with the frame.
source_record
  • What core location/continuity is supported by the controlling references?
Office / meeting room kitTypical office and selected shared meeting room are proposed, not selected/approved.
source_record
  • Which representative meeting space is needed and how does it connect to the core?
Variant envelopeCheck the compact variant’s exoframe intrusions and clear-floor relationship without shrinking another variant.
proposed_design
  • What dimensions distinguish this variant, and which parts are genuinely reusable across siblings?
Compact low-wide body and roof-level frameNotes describe a low wide box with diagonals across its upper face; unlike the taller variants, the frame stays near roof height. The broad podium/pool-or-planter and terrace connection remain open.
source_notes
  • Does the frame rise above the roof?
  • Is the podium feature water or a planter?
Modeling sequence & review views
  1. Preserve roof-level frame expression

    Use the note/index comparison to distinguish Compact’s low-wide frame from its taller siblings; keep the roof line and podium-water interpretation open.

    Gate: Do not extend frame members above roof without source/design direction.

  2. Diagram exoframe and core

    Prepare a section/elevation with frame bays, floor lines, core zones and known structural intrusions; leave values blank where no source exists.

    Gate: Every numeric value requires a source, status, owner and reviewer.

  3. Check one office/meeting kit

    Place a schematic typical office and selected meeting-room zone against the frame/core diagram.

    Gate: Clear dimensions and circulation are candidates until the shell is measured and furnished-player reviewed.

  4. Compare variant reuse boundaries

    Classify candidate repeat parts versus variant-specific frame/envelope/core geometry.

    Gate: Do not turn a cosmetic/material reuse candidate into geometry reuse without compatible interfaces.

  5. Return variant evidence plan

    List each required plan/section and return measurement, route, collision and player-camera evidence needed later.

    Gate: No shell or engine acceptance is implied.

Required review views

Frame Compact front/three-quarter view

Show the low-wide body, upper-face frame and broad podium as distinct from tower-like siblings.

Typical floor/core plan

Show the office kit, service core and structural intrusions relative to the candidate clear room zone.

Frame/core vertical section

Show level relationships, clear-height questions, frame continuity and service-core stack.

Meeting-room sample view

Test one selected shared meeting room against the frame and player/camera envelope after scope is chosen.

Shared kits & asset dependencies
Decision queue & Friday return

Does the frame rise above the roof, and is the podium feature a pool or planter?

Owner: Legend. Resolution evidence: Selected concept interpretation and building/landscape section.

What clear floor height and structural intrusion zones must the office kit preserve?

Owner: Legend with design/layout author. Resolution evidence: Measured section and furnished clear-room plan, followed by candidate-shell fit evidence.

What is the service-core arrangement and how does it connect to the lobby and typical floors?

Owner: Legend; Quik provides later measured engine evidence. Resolution evidence: Reviewed core/access plan and shell continuity evidence.

Which frame parts can actually be reused across Tall, Mid and Compact without changing geometry?

Owner: Legend with design/layout author. Resolution evidence: Side-by-side variant interface comparison and an R05 reuse record.

Friday: requires decision

  • Legend review of each variant envelope and the proposed shared meeting-room scope.
  • Approved/sourced frame, core and clear-height dimensions before a shell can be accepted.

Friday: return evidence

  • Independent Frame Compact plan/section plus comparison against PI-BLD-0006-V01, PI-BLD-0006-V02 with all source revisions named.
  • Later shell-fit and player/camera evidence for frame intrusion, clear floor, core continuity and the selected meeting room.
Downloads & source inventory