# PI-BLD-0006-V01 · Frame Tall · 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 Frame Tall frame/core/floor-kit coordination record and identify which shared parts can be tested across the height family.

## Scope basis

P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Register program is lobby, typical office kit and selected shared meeting room; each height variant requires its own exoframe, intrusion, clear-height and service-core check.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Exoframe bay | The register requires the structural bay to be coordinated, but gives no span or module dimensions. | source_record | Which source reference controls bay rhythm and where does it join slabs/façade? |
| Structural intrusions and clear floor | The register calls out intrusions and clear floor height as explicit fit checks. | source_record | Which structure zones reduce usable room/circulation clearance in this variant? |
| Service core | A service core is in the proposed program and must be coordinated with the frame. | source_record | What core location/continuity is supported by the controlling references? |
| Office / meeting room kit | Typical office and selected shared meeting room are proposed, not selected/approved. | source_record | Which representative meeting space is needed and how does it connect to the core? |
| Variant envelope | Check the tall variant’s exoframe/core/clear-floor relationships independently across its proposed stack. | proposed_design | What dimensions distinguish this variant, and which parts are genuinely reusable across siblings? |
| Tall taper and crossing exoframe | Notes describe a tapered glass body and large crossing diagonals. The card shows several members while the close render reads as one dominant A; the apparent taper also differs. These remain concept conflicts. | source_notes | Which frame layout and faces control?; Is the taper genuine or a perspective effect? |

## Modeling sequence

1. **Record A-frame/taper conflicts** — Use the notes/index to list the multiple-diagonal versus dominant-A reading and taper question without resolving geometry. Gate: Legend chooses authority before frame geometry is modeled.
2. **Diagram exoframe and core** — Prepare a section/elevation with frame bays, floor lines, core zones and known structural intrusions; leave values blank where no source exists. Gate: Every numeric value requires a source, status, owner and reviewer.
3. **Check one office/meeting kit** — Place a schematic typical office and selected meeting-room zone against the frame/core diagram. Gate: Clear dimensions and circulation are candidates until the shell is measured and furnished-player reviewed.
4. **Compare variant reuse boundaries** — Classify candidate repeat parts versus variant-specific frame/envelope/core geometry. Gate: Do not turn a cosmetic/material reuse candidate into geometry reuse without compatible interfaces.
5. **Return variant evidence plan** — List each required plan/section and return measurement, route, collision and player-camera evidence needed later. Gate: No shell or engine acceptance is implied.

## Required review views

- **Frame Tall front/three-quarter view** — Show the tapered body and frame pattern against selected authority; notes flag a card/render disagreement.
- **Typical floor/core plan** — Show the office kit, service core and structural intrusions relative to the candidate clear room zone.
- **Frame/core vertical section** — Show level relationships, clear-height questions, frame continuity and service-core stack.
- **Meeting-room sample view** — Test one selected shared meeting room against the frame and player/camera envelope after scope is chosen.

## Candidate kits

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

## Proposed dependencies

- PI-BLD-0006-V02: Sibling-height comparison only; the register requires verifying each height variant and does not authorize scaled copies. (proposed)
- PI-BLD-0006-V03: Sibling-height comparison only; the register requires verifying each height variant and does not authorize scaled copies. (proposed)

## Decision queue

- Which frame pattern controls, and is the glass body actually tapered? Owner: Legend. Resolution evidence: Named authority, annotated elevation and candidate plan/section; perspective alone does not resolve taper..
- What clear floor height and structural intrusion zones must the office kit preserve? Owner: Legend with design/layout author. Resolution evidence: Measured section and furnished clear-room plan, followed by candidate-shell fit evidence..
- What is the service-core arrangement and how does it connect to the lobby and typical floors? Owner: Legend; Quik provides later measured engine evidence. Resolution evidence: Reviewed core/access plan and shell continuity evidence..
- Which frame parts can actually be reused across Tall, Mid and Compact without changing geometry? Owner: Legend with design/layout author. Resolution evidence: Side-by-side variant interface comparison and an R05 reuse record..

## Friday: can prepare

- Keep the multiple-diagonal/card versus dominant-A/render and taper conflicts open; request frame-foot, balcony and roof-end sections.
- Identify candidate office/meeting kit interfaces and mark the frame, intrusion and clear-height values still missing.

## Friday: requires decision

- Legend review of each variant envelope and the proposed shared meeting-room scope.
- Approved/sourced frame, core and clear-height dimensions before a shell can be accepted.

## Friday: return evidence

- Independent Frame Tall plan/section plus comparison against PI-BLD-0006-V02, PI-BLD-0006-V03 with all source revisions named.
- Later shell-fit and player/camera evidence for frame intrusion, clear floor, core continuity and the selected meeting room.

## 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 `fc585237d87e6420f0f0f35c65f1b87fe68fe62006007723ad4c282910590b6b`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `c478394e09200e4b0c23cd6c109759c72d8f918ed0fe241cd0a89964712a8a1e`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `6859eaca6cf97390bc18378e5333738830b616e3ce6d6d80b5cb7fbfba278b66`
- [VISUAL_NOTES.md](../../../PI-BLD-0006-V02/VISUAL_NOTES.md) · SHA-256 `a5b5e07f5df5c81b3fa8977b41d57f0f0ba759ce3b66dce3d3359f484a06d4a2`
- [VISUAL_NOTES.md](../../../PI-BLD-0006-V03/VISUAL_NOTES.md) · SHA-256 `ea05171ae8cf8a9787d1188fccd9be977473563410415c0a2341207fa1ef69f1`
- [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`
