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
Terraced Garden
Prepare the Terraced Garden open-space/terrace, bridge, shade and dwelling-kit questions before setting an envelope.
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 Terraced Garden with Garden-facing arrival lobby, Furnished studio sample, Shared garden lounge, furnishings and connected access.
Required spaces
- Garden-facing arrival lobby
- Furnished studio sample
- Shared garden 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
- Compare the stepped/blade concept to the sibling slot concept; list blade, spine and terrace-side questions without assigning levels.
- List candidate section/plan cuts for terraces, blade, spine, shade, planting and room access; bridge links remain unselected.

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 terrace masssource notes
- 02Terraces and planting voidssource record
- 03Bridge and circulation linkssource record
- 04Lobby and coresource record
- 05Typical dwelling/workspace kitsource record
- 06Stepped terrace pyramid and diagonal bladesource notes
Modeling sequence
- 01Preserve the stepped/blade identityVariant envelopes remain distinct.
- 02Draw the terrace and spine sectionTerrace, blade and core dimensions stay unset until sourced and reviewed.
- 03Map access and coreLegend selects which garden/terrace areas are playable or decorative.
- 04Fit a representative room kitNo repeated unit is accepted until a furnished sample is checked against a measured candidate shell.
- 05Return source-backed comparisonA family resemblance does not authorize scaled-copy geometry.
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 proposes a lobby, garden court and typical dwelling/workspace kit, and requires section review of canyon/terraces, planting voids, bridges, shade and circulation.
| Component | Role and evidence | Open questions |
|---|---|---|
| Stepped terrace mass | The variant notes describe rectilinear planted terraces narrowing upward above a broad podium. Preserve this stepped mass rather than importing Garden Canyon’s open slot. source_notes |
|
| Terraces and planting voids | The register calls for a section through terraces and planting voids; geometry is not dimensioned. source_record |
|
| Bridge and circulation links | Bridges and circulation are named coordination issues, not approved connections. source_record |
|
| Lobby and core | A lobby is proposed; the register does not define its location or the core arrangement. source_record |
|
| Typical dwelling/workspace kit | A reusable dwelling/workspace kit is proposed, with fit to the open-space edge still unresolved. source_record |
|
| Stepped terrace pyramid and diagonal blade | Notes describe rectilinear planted terraces narrowing upward, a glass spine and a tall cream diagonal blade with a shorter brace. This differs from Garden Canyon’s open slot; blade endpoints and spine/core relationship remain open. source_notes |
|
Modeling sequence & review views
Preserve the stepped/blade identity
Use the notes to distinguish the stepped terrace stack and diagonal blade from the Canyon slot; map blade/spine questions without transferring sibling geometry.
Gate: Variant envelopes remain distinct.
Draw the terrace and spine section
Diagram the stepped terrace stack, glass spine, diagonal blade, planting zones and shade. Test which family-level garden or bridge circulation proposals are selected for this variant.
Gate: Terrace, blade and core dimensions stay unset until sourced and reviewed.
Map access and core
Show the candidate lobby, vertical circulation, bridge connections and usable terrace circulation.
Gate: Legend selects which garden/terrace areas are playable or decorative.
Fit a representative room kit
Test a schematic dwelling/workspace plan at the open-space edge and flag conflicts with structure, openings and circulation.
Gate: No repeated unit is accepted until a furnished sample is checked against a measured candidate shell.
Return source-backed comparison
Provide the variant comparison, open-space section/view list and unresolved decision queue.
Gate: A family resemblance does not authorize scaled-copy geometry.
Required review views
Stepped mass and diagonal-blade elevation
Show the terrace stack, glass spine and diagonal blade; resolve unseen blade foot and roof conditions.
- production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
Section through terraces, planting and spine
Reveal the terrace-to-spine and planting relationships; distinguish any selected garden/bridge routes from the Canyon sibling’s open slot.
- production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
Garden circulation plan
Trace lobby/core to bridges, garden court, shared terrace and representative dwelling access.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json
Typical dwelling/workspace edge view
Check room openings and usable room/terrace boundary against the candidate open-space arrangement.
Shared kits & asset dependencies
Candidate kits
Proposed dependencies
- PI-BLD-0005-V01: Sibling-family comparison: both variants share the register coordination checklist, but each needs its own envelope/open-space review. (proposed)
Decision queue & Friday return
Where does the diagonal blade land, and how does the glass spine relate to the stepped mass?
Owner: Legend with design/layout author. Resolution evidence: Selected concept interpretation and dimensioned plan/section.
- production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
Which bridge/circulation links and core interfaces are necessary to reach the garden court and representative rooms?
Owner: Legend with design/layout author. Resolution evidence: Dimensioned access plan and section with all unresolved points assigned.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/GUIDE.md
- production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json
How does this variant differ from its sibling in open-space sequence and geometry?
Owner: Legend. Resolution evidence: Source-backed variant comparison; no scaled-copy assumption.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/GUIDE.md
Which dwelling/workspace kit is the first sample, and how will its clear room area be tested?
Owner: Legend; Quik supplies later player/camera evidence. Resolution evidence: Furnished room plan over a reviewed candidate shell with dimension/status provenance.
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/protocols/building/R05/GUIDE.md
- production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json
Friday: requires decision
- Legend direction on the stepped terraces, diagonal blade and which garden routes are shared or playable.
- A dimensioned envelope/core and selected dwelling/workspace kit before room fit can be accepted.
Friday: return evidence
- Variant-specific plan and section proposal, reference provenance, open items and route diagram.
- Later candidate-shell fit views with separate plant, bridge, room and clearance checks.
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-0005-V01/VISUAL_NOTES.md
- production/assets/buildings/PI-BLD-0005-V02/BUILDING_DIMENSIONS.json
- production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv
- production/assets/buildings/PI-BLD-0005-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
