Draft production prep · R01 · 16 October 2026
Terrace Tower
Prepare a stepped-residential shell and kit brief that tests terrace usability, core continuity, and planting interfaces without assigning dimensions from the concept.
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 Terrace Tower with Residential arrival lobby, Furnished studio sample, Residents’ terrace lounge, furnishings and connected access.
Required spaces
- Residential arrival lobby
- Furnished studio sample
- Residents’ terrace lounge
Required exterior coverage
- Full-building hero / silhouette
- Opposite or rear side
- Entrance at player-eye level
- Defining detail / building-to-ground interface
Required interior coverage
- Lobby wide and reverse / exit view
- Selected room 1 wide and reverse
- Selected room 2 wide and reverse, when commissioned
Delivery state: Scoped — complete design: not yet evidenced; reviewed build packet: not yet evidenced; engine verification: not yet evidenced.
Audited source baseline: Existing source research and Concept A; a further full-building concept was generated in this session. Core, setbacks, reverse side and measured connected interior package still need authoring.
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.
Latest Blender delivery · T01
Terrace Tower · T01 Blender build
Executed Blender checkpoint with applied room finishes, 19 modeled prop variants, scenes, GLBs and interior/exterior views.
Proposed furnished candidate · Blender execution reported · Unreal not tested.
Prepare now
- Use the card notes to preserve the wavy curved terrace edges and contrast with the rounded tower; list unseen side and roof questions.
- Create a source-backed reference/variant question list and a non-metric blockout checklist for review.

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.
- 01Stepped slab sequencesource record
- 02Core continuitysource record
- 03Terrace dwelling kitsource record
- 04Waterproofing and planting zonessource record
- 05Rounded tower and wavy stepped terracessource notes
Modeling sequence
- 01Record the curved terrace signatureNo dimensions or floor count are inferred from the concept card.
- 02Draw stepped envelope and core sectionAll floor heights, terrace depths and core dimensions remain proposed/null until sourced and reviewed.
- 03Plan one representative dwelling kitDo not assume one scaled unit fits every step or edge.
- 04Review terrace and planting separationLegend selects shared/playable terrace scope before detailed modeling.
- 05Return a blockout evidence planNo final shell/scale status until measured and reviewed.
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 optional world-life program, with no named story assignment.
| Component | Role and evidence | Open questions |
|---|---|---|
| Stepped slab sequence | The register identifies stepped slabs as the form-specific coordination issue. source_record |
|
| Core continuity | A continuing core through the stepped envelope is explicitly called out. source_record |
|
| Terrace dwelling kit | A typical terrace dwelling kit is proposed; its fit to each edge condition is unverified. source_record |
|
| Waterproofing and planting zones | The register requires these interfaces to be resolved, but supplies no technical details. source_record |
|
| Rounded tower and wavy stepped terraces | Notes describe a rounded glass tower beside a lower stepped mass with soft S-curved slab edges. The visible terrace count is a card observation, not a floor schedule; front, smaller glass-volume connection, plan shape and roof use remain open. source_notes |
|
Modeling sequence & review views
Record the curved terrace signature
Use the notes/index to preserve the soft S-edge terrace expression and lopsided tower/block relationship; do not convert visible bands into a floor schedule.
Gate: No dimensions or floor count are inferred from the concept card.
Draw stepped envelope and core section
Prepare a section diagram of slab steps, core continuity, dwelling access, and planting/waterproofing interfaces.
Gate: All floor heights, terrace depths and core dimensions remain proposed/null until sourced and reviewed.
Plan one representative dwelling kit
Map usable room zones, doors, furniture clearance and exterior terrace access for a selected typical unit.
Gate: Do not assume one scaled unit fits every step or edge.
Review terrace and planting separation
Mark candidate circulation, shared terrace, planting and service interfaces separately.
Gate: Legend selects shared/playable terrace scope before detailed modeling.
Return a blockout evidence plan
List the named views and measurements required to test core continuity, terrace usability and candidate kit reuse.
Gate: No final shell/scale status until measured and reviewed.
Required review views
Tower and stepped-block three-quarter view
Show the rounded glass tower, lower wavy terrace mass and smaller glass volume; the notes identify only a single concept view.
- production/assets/buildings/PI-BLD-0003-V01/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0003-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
Core and slab section
Expose floor-to-floor relations, terrace transitions, core continuity and planting interfaces.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json
Typical dwelling/terrace plan
Show clear usable room areas, openings and access to the selected terrace condition.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json
Shared-terrace access view
Check whether the selected shared terrace connects to public circulation without crossing private units.
Shared kits & asset dependencies
Decision queue & Friday return
Are the rounded tower and stepped terrace block connected or separate, and which side is front?
Owner: Legend. Resolution evidence: Creator-selected orientation and annotated massing plan/elevation.
- production/assets/buildings/PI-BLD-0003-V01/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0003-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
What slab/terrace geometry and core path are supported by the controlling source references?
Owner: Design/layout author; Legend approves visual intent. Resolution evidence: Dimensioned section with source revision and explicit proposed/approved status.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/GUIDE.md
- production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json
Which unit plan is reusable, and where does the stepped shell require a distinct layout?
Owner: Legend with layout author. Resolution evidence: Representative furnished unit plan plus a family fit comparison.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/GUIDE.md
How are planted/wet zones separated from terrace access and the building shell?
Owner: Design/layout author; Quik tests later integration. Resolution evidence: Annotated section/plan and subsequent collision/waterproofing interface review.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/GUIDE.md
Friday: requires decision
- Creator review of controlling visual references, proposed enterability, and any candidate dimensions before shell acceptance or placement.
Friday: return evidence
- Source paths and revisions, annotated plan/section checklist, unresolved questions with owners, and the exact model/source revision if any candidate blockout is later authorized.
Downloads & source inventory
README and JSON retain repository-relative source paths. Use the linked inventory here when reviewing downloaded copies.
Source inventory
- docs/current-decisions.md
- production/assets/buildings/PI-BLD-0003-V01/BUILDING_DIMENSIONS.json
- production/assets/buildings/PI-BLD-0003-V01/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0003-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/districts/D02-CrownKey/planning/prep/R01/ASSET_INPUTS_A.json
- production/districts/D02-CrownKey/planning/prep/R01/KIT_CATALOG.json
- production/protocols/building/R05/GUIDE.md
- production/protocols/building/R05/README.md
- production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json
- production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json
- production/protocols/current.json
- production/protocols/district/R05/README.md
- production/workflows/spatial-imagery/R01/GUIDE.md


