# PI-BLD-0007-V01 · Courtyard Offices · 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 P1 Tier C office sample with reception, representative office/meeting and service route; retain the courtyard-ring shell as V01-specific.

## Scope basis

Register proposes office/meeting use and courtyard access. Visual notes describe a rounded open ring, warm glazed base and uneven roofline, but show no street-to-court route or measured sides. V02 is a solid glass block, not a scaled version.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Courtyard ring | Rounded office wings around an open-to-sky court; keep void distinct. | source_notes | Which sides/levels enclose the court, and what do hidden elevations show? |
| Court threshold | Candidate passage/lobby threshold; access is not visible in the concept. | proposed_design | Is access through a ground passage, lobby or controlled opening? |
| Office/meeting bay | One candidate reusable office/meeting kit within the shell. | source_record | Which rooms are selected, and which levels if any repeat? |
| Glazed ground/service | Warm glazed base with candidate toilet/service zones from proposed program. | source_record | Where are accessible entry, service and delivery routes? |
| Uneven roofline | Wing heights, parapets, roof boxes and planting are visual cues only. | source_notes | Which roof boxes are rooms, plant or appearance-only? |

## Modeling sequence

1. **Resolve source roles** — Log front/access uncertainty; leave dimensions null and do not scale from card pixels. Gate: Owner review distinguishes observations from missing decisions.
2. **Block ring** — Keep court void, wings, base and roof parts separate and parameterized. Gate: Same-model axon and plan show the open court and wing hierarchy.
3. **Diagram access** — Lay out public, controlled and service route options without inventing an entrance. Gate: Route is selected before committed office layout.
4. **Fit one office kit** — Place a parameterized sample only after measured shell/core inputs arrive. Gate: Dimensioned plan and named unknowns precede furnishing.

## Required review views

- **Front/courtyard axon** — Show court, ring, glazed base and uneven wings.
- **Roof plan** — Show court void, wing footprints, roof boxes and candidate planting.
- **Courtyard section** — Show enclosure and ground route, with unmeasured heights left open.
- **Street-to-court route** — Separate public, controlled and service access.

## Candidate kits

- CK-KIT-OFFICE
- CK-KIT-CORE
- CK-KIT-LOBBY
- CK-KIT-SERVICE
- CK-KIT-PROPS

## Proposed dependencies

- PI-BLD-0007-V02: Candidate office kit only after both shells are measured; courtyard and its route remain V01-specific. (proposed)

## Decision queue

- Which face is front and where is the main entrance? Owner: Legend. Resolution evidence: Selected reference and dimensioned entry plan..
- Is the court enclosed on all four sides, and how is it reached? Owner: Legend. Resolution evidence: Approved court/access sketch keyed to levels..
- Which wings/roof boxes are occupied or plant? Owner: Legend + Quik. Resolution evidence: Elevation/section and component schedule..
- Which office parts may be reused in V02 after fit checks? Owner: Quik. Resolution evidence: Measured plans for both shells and a kit-fit record..

## Friday: can prepare

- Prepare an unscaled ring study with separate court, wings, base and roof parts.
- Diagram public/controlled/service routes and expose all dimensions as parameters.

## Friday: requires decision

- Front and entry, courtyard access, wing hierarchy and staff route.
- Measured envelope/core before fit or clearance claims.

## Friday: return evidence

- Editable candidate with dimension fields unset.
- Plan, section, axon and route diagram.
- Decision list separating observations, proposals and measurements.

## 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`
- [ASSET_BRIEF.json](../../ASSET_BRIEF.json) · SHA-256 `b086f62749fb60a488c369c08519da4000e42f63bf8eddbb7326e27055d11d24`
- [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json) · SHA-256 `e5f2e9166a582d7662218bfc58f680914269b78dbf9b98c894112b12f8060d0a`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `51ab3b2c699cbcce34af5f1c2bbb1c437f0b48ac16286f28b9d99ea22be63994`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `8aef735dd6b9a23e2f59a3480e4f64e5e8910b21113786b995aa758ad41d5838`
- [BUILD_REGISTER.csv](../../../../../districts/D02-CrownKey/planning/BUILD_REGISTER.csv) · SHA-256 `45be2626767273dce204c95a1233c943cdcdc119fce7a17eda4810c3606a0d52`
- [BUILD_REGISTER.json](../../../../../districts/D02-CrownKey/planning/BUILD_REGISTER.json) · SHA-256 `bb0a893c54a83f490e9ff59197e593ea1093a393209c7714d57997cd3c06df3e`
- [ASSET_INPUTS_B.json](../../../../../districts/D02-CrownKey/planning/prep/R01/ASSET_INPUTS_B.json) · SHA-256 `13b830ec89a557291c006de40e75574fa3be9cb844bb5c021f978e1a021d2698`
- [KIT_CATALOG.json](../../../../../districts/D02-CrownKey/planning/prep/R01/KIT_CATALOG.json) · SHA-256 `52525e0754aee464c84793b3b3cfe2b6ae4c95981fd2bf3e67c2d91c02ada0b9`
- [Building_R05_GUIDE.md](../../../../../handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md) · SHA-256 `006818490740b4bd9e3994a428da95390f9f4dd987c6fd6f67a8dd1dbbc24509`
- [README.md](../../../../../protocols/building/R05/README.md) · SHA-256 `ecb4c6b0bf144a5da037ba8817528c40cb59ce272bc9ca63b3d187e704dc2715`
- [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`
