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
Twist Tall
Prepare the Twist Tall variant-specific envelope/core/facade questions and a single typical rotated-floor kit candidate.
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 Twist Tall with Sculptural entrance lobby, Private office, Meeting lounge, furnishings and connected access.
Required spaces
- Sculptural entrance lobby
- Private office
- Meeting 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: 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.
Prepare now
- Preserve the card/render difference between crossing ribbons and parallel deck-like ribbons; list support, termination and walkability questions.
- Prepare a schematic core/facade/typical-floor coordination sheet without reusing one sibling as the other’s scale.

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.
- 01Rotated floor expressionsource record
- 02Stable service coresource record
- 03Facade-to-room fitsource record
- 04Usable corner spacesource record
- 05Typical office/residential floorsource record
- 06Tall spiral ribbons and cylindrical glass bodysource notes
Modeling sequence
- 01Keep braid/deck conflict openLegend review is required before ribbon geometry or walkability is modeled.
- 02Document rotation and coreRotation values and levels remain unset until authored source evidence supports them.
- 03Fit one typical room kitUsable clear dimensions require a sourced plan and reviewed character/camera assumptions.
- 04Prepare variant-specific shell viewsUse views to compare geometry; do not infer measurements from perspective.
- 05Return open decisionsNo shell or room kit is accepted by this prep record.
Planned review views
Components & scope evidence
Scope basis: P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. The register says Tall and Compact are distinct envelopes; proposed program is lobby plus one typical rotated-floor office/residential kit.
| Component | Role and evidence | Open questions |
|---|---|---|
| Rotated floor expression | Tall variant: document the rotation sequence and stable-core relationship across the taller expression; do not infer a floor count from the name. The register requires the floor rotation to be documented. source_record |
|
| Stable service core | The register requires a stable core to be documented alongside the rotation. source_record |
|
| Facade-to-room fit | The register identifies facade-to-room fit as a family-specific test. source_record |
|
| Usable corner space | Corner-space usability is explicitly called out; no room dimensions are supplied. source_record |
|
| Typical office/residential floor | A single reusable typical-floor kit is proposed for review, not approved. source_record |
|
| Tall spiral ribbons and cylindrical glass body | Notes describe a slender cylindrical glass body wrapped by cream spiral ribbons. The card reads as braided/crossing ribbons while the location render reads as parallel decks; ribbon depth, support, front and terminations remain unresolved. source_notes |
|
Modeling sequence & review views
Keep braid/deck conflict open
Use the notes/index to document the crossing-card versus parallel-deck-render readings; prepare a path/termination diagram without choosing geometry.
Gate: Legend review is required before ribbon geometry or walkability is modeled.
Document rotation and core
Create a floor-to-floor relationship diagram for rotation, core continuity, and facade orientation.
Gate: Rotation values and levels remain unset until authored source evidence supports them.
Fit one typical room kit
Place only a schematic office/residential kit against the candidate rotated floor and flag facade/corner conflicts.
Gate: Usable clear dimensions require a sourced plan and reviewed character/camera assumptions.
Prepare variant-specific shell views
Request matching front, top/typical-floor and vertical-section views for this asset and its sibling.
Gate: Use views to compare geometry; do not infer measurements from perspective.
Return open decisions
List envelope, rotation, stable-core and interior-kit questions with evidence needed to resolve each.
Gate: No shell or room kit is accepted by this prep record.
Required review views
Twist Tall front/three-quarter view
Resolve the card’s braided ribbon reading against the render’s parallel spiral-deck reading from selected authority.
- production/assets/buildings/PI-BLD-0004-V01/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0004-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
Typical-floor plan from above
Show the rotated facade, core, room zones and corner usability.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json
Vertical core/facade section
Test whether the core remains stable while the floor/facade expression changes.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json
Typical-room/player-height view
Reveal usable corners, opening placement and camera sightline after the room kit is selected.
Shared kits & asset dependencies
Candidate kits
Proposed dependencies
- PI-BLD-0004-V02: Sibling-family comparison: register requires Tall and Compact to be treated as distinct envelopes; this is not a scale or geometry authority. (proposed)
Decision queue & Friday return
Are the Tall ribbons a crossing braid or stacked spiral decks, and are they walkable around the tower?
Owner: Legend. Resolution evidence: Named reference authority, annotated ribbon path, and selected balcony enterability.
- production/assets/buildings/PI-BLD-0004-V01/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0004-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
Which typical office/residential layout is selected, and which corner zones are usable?
Owner: Legend. Resolution evidence: Representative furnished plan with door, structure, furniture, camera and access checks.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/GUIDE.md
- production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json
Which differences from PI-BLD-0004-V02 require distinct geometry or a separate shell revision?
Owner: Legend. Resolution evidence: Side-by-side reference comparison and an explicit reuse/geometry-change record.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/GUIDE.md
What levels, core vertical connections and openings must be verified before shell approval?
Owner: Quik with design/layout author. Resolution evidence: Measured shell and core/clearance evidence from the actual candidate, reviewed against the accepted dimension contract.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/GUIDE.md
- production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json
Friday: requires decision
- Legend selection of controlling references and the variant geometry differences to preserve.
- Reviewed rotation/core/floor schedule and chosen interior scope before producing a dimensioned shell or room kit.
Friday: return evidence
- Variant comparison showing Twist Tall separately from PI-BLD-0004-V02, with source provenance.
- Dimensioned typical-floor and section proposal with statuses, open items, and candidate camera/player clearance tests.
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-0004-V01/BUILDING_DIMENSIONS.json
- production/assets/buildings/PI-BLD-0004-V01/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0004-V01/VISUAL_NOTES.md
- production/assets/buildings/PI-BLD-0004-V02/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
