# PI-BLD-0005-V01 · Garden Canyon · preparation R01

**DRAFT_PRODUCTION_PREP** · 2026-10-16

Draft preparation only; not an issued reference pack, shell, approval or construction release. Foundation hold remains in force; preparation does not authorize construction or accept dimensions, placement or engine readiness.

Prepare the Garden Canyon open-space/terrace, bridge, shade and dwelling-kit questions before setting an envelope.

## 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.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Garden court / signature opening | Review the named canyon/opening as this variant’s signature space; the register says to preserve the signature opening. | source_record | Which portions of the opening remain open through the shell, and which routes cross or frame it? |
| Terraces and planting voids | The register calls for a section through terraces and planting voids; geometry is not dimensioned. | source_record | How do planted voids align with occupied floors and accessible terrace edges? |
| Bridge and circulation links | Bridges and circulation are named coordination issues, not approved connections. | source_record | Which bridges are required for access, and where do they meet the core and open space? |
| Lobby and core | A lobby is proposed; the register does not define its location or the core arrangement. | source_record | What entrance, vertical circulation and service path supports the selected kit? |
| Typical dwelling/workspace kit | A reusable dwelling/workspace kit is proposed, with fit to the open-space edge still unresolved. | source_record | Which representative room kit and facade/opening condition should be tested? |
| Slab tower with open canyon slot | Notes describe a straight slab tower with a deep front slot, two glass wings and curved-rail balconies along the slot’s back wall. Slot sky/roof/ground termination and balcony arrangement remain unresolved. | source_notes | Is the slot open to sky, roofed or bridged, and does it reach ground?; Do balconies stay on the back wall or alternate? |

## Modeling sequence

1. **Preserve the slot as the signature** — Use the notes/index to section the straight slab and open slot with back-wall balconies; do not fill the opening with planting or structure without direction. Gate: Slot termination and balcony access remain decisions.
2. **Draw the open-space section** — Diagram the signature opening, terraces, planting voids, shade surfaces and candidate bridge routes. Gate: Keep opening/terrace dimensions unset until they have a source and owner.
3. **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.
4. **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.
5. **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

- **Front slot/canyon elevation** — Show the deep open slot and two wings; notes identify stacked back-wall balconies as must-preserve concept intent.
- **Section through opening and terraces** — Reveal open-to-sky/courtyard voids, planting zones, bridges, shade and circulation relationships.
- **Garden circulation plan** — Trace lobby/core to bridges, garden court, shared terrace and representative dwelling access.
- **Typical dwelling/workspace edge view** — Check room openings and usable room/terrace boundary against the candidate open-space arrangement.

## Candidate kits

- CK-KIT-LOBBY
- CK-KIT-CORE
- CK-KIT-RESIDENCE
- CK-KIT-GARDEN
- CK-KIT-PROPS

## Proposed dependencies

- PI-BLD-0005-V02: Sibling-family comparison: both variants share the register coordination checklist, but each needs its own envelope/open-space review. (proposed)

## Decision queue

- Is the slot open to sky, roofed or bridged, and how does it terminate at ground? Owner: Legend with design/layout author. Resolution evidence: Selected concept interpretation and a dimensioned section; no card-derived dimensions..
- 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..
- 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..
- 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..

## Friday: can prepare

- Use the notes to preserve the open vertical slot and back-wall balconies; list sky/ground termination and balcony-route options.
- List candidate section/plan cuts for opening, bridge, shade, planting and room access.

## Friday: requires decision

- Legend direction on the preserved opening and which terraces/garden routes are shared/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.

## Controlling records and source inventory

- Dimension contract: [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json).
- Building R05 / District R05 / Spatial Imagery R01; dimensions and approval remain governed by their own records.
- [current-decisions.md](../../../../../../docs/current-decisions.md) · SHA-256 `8001f9a1c613b326b030da3ace10947a3021dc12f9273b7c7fa46d0ade10d382`
- [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json) · SHA-256 `63512273997c70d3c42bc92be7ca716dcf49f39311660cb1c98a93057c0243ab`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `78c6bede0ef76fd622045e1a4add911b6a41254a5a5645cfd035767c7ebc7482`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `141d424ca763a3b8050a4251fa1d9071524a3289bdcb36a9816e83d63ce01aaa`
- [VISUAL_NOTES.md](../../../PI-BLD-0005-V02/VISUAL_NOTES.md) · SHA-256 `2ec34c72688d1a1dccf8310855fdceba4a7ab824a728ee2891408b34d3a86e94`
- [BUILD_REGISTER.json](../../../../../districts/D02-CrownKey/planning/BUILD_REGISTER.json) · SHA-256 `bb0a893c54a83f490e9ff59197e593ea1093a393209c7714d57997cd3c06df3e`
- [ASSET_INPUTS_A.json](../../../../../districts/D02-CrownKey/planning/prep/R01/ASSET_INPUTS_A.json) · SHA-256 `8193933c210b0cfaa825428aae1a0d1d2b2fbe8f11d6c7befc0db81d7892d2d4`
- [KIT_CATALOG.json](../../../../../districts/D02-CrownKey/planning/prep/R01/KIT_CATALOG.json) · SHA-256 `52525e0754aee464c84793b3b3cfe2b6ae4c95981fd2bf3e67c2d91c02ada0b9`
- [GUIDE.md](../../../../../protocols/building/R05/GUIDE.md) · SHA-256 `006818490740b4bd9e3994a428da95390f9f4dd987c6fd6f67a8dd1dbbc24509`
- [README.md](../../../../../protocols/building/R05/README.md) · SHA-256 `ecb4c6b0bf144a5da037ba8817528c40cb59ce272bc9ca63b3d187e704dc2715`
- [ASSET_BRIEF_TEMPLATE.json](../../../../../protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json) · SHA-256 `d6f80614e4f7d87f7cd569c7b1320cf6ad58c2021fab1955ff274a157d8df054`
- [BUILDING_DIMENSIONS.json](../../../../../protocols/building/R05/templates/BUILDING_DIMENSIONS.json) · SHA-256 `46fefd72cb9e5bd0b1e98822a1773401f96c35d91ce57fc821d3bbc624e69631`
- [current.json](../../../../../protocols/current.json) · SHA-256 `c7be63113d117523e6b2e608149e6b31620f2f50436f4fbbeebdd1ffb005881a`
- [README.md](../../../../../protocols/district/R05/README.md) · SHA-256 `f95ad3a6c25f181898fd3be47eac800b39b5f1790387f8e93d5450e75ace5a7d`
- [GUIDE.md](../../../../../workflows/spatial-imagery/R01/GUIDE.md) · SHA-256 `288df4dc11896d4e606f8dc49f8b1a6969679d1fad50fad7595f3e2c8b9ad173`
