# PI-STR-0006-V01 · Arcade Bay Module · 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 an isolated candidate repeat-bay interface; keep source-card flat canopy/sidewall distinct from BLD-0010 curved/flared arches until fit is decided.

## Scope basis

Card shows pointed arch, flared columns, flat-topped canopy, side wall, glazing and plinth. BLD-0010 notes show curved/flared shells that differ; module reuse is not assumed.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Single arch bay | Pointed opening, flared columns and main/smaller glazed fronts. | source_notes | Does one span repeat and are glazing/doors in this module? |
| Canopy slab/sidewall | Thin overhang and square side wall from card. | source_notes | Is flat slab a repeat feature or end/cap condition? |
| Glazing/lighting | Dark mullions, warm interior and downlights. | source_notes | Which doors/lights are functional? |
| Plinth/rail | Low front plinth/terrace and glass-metal rail. | source_notes | Is terrace module, arcade or promenade scope? |
| Arcade interfaces | BLD-0010 forms conflict with flat top; curved/corner fit unsupported. | proposed_design | What repeat/end-cap and curve/corner contracts are shared? |

## Modeling sequence

1. **Record module authority** — Keep card detail and contextual run distinct; preserve flat/curved discrepancy. Gate: No compatibility inferred from name.
2. **Block one bay** — Separate arch, columns, canopy, wall, glazing, plinth and rail. Gate: Review repeat vs end-cap components.
3. **Define connector fields** — Expose seams, glazing edge and plinth/canopy connectors; dimensions null. Gate: No connector rule before measurement.
4. **Test three relationships** — Overlay with straight, curved and corner arcade without warping straight module. Gate: Each compatibility result is explicit.
5. **Package reuse evidence** — Return module plan/section and seam sketches. Gate: Unresolved kit remains candidate, not production-ready.

## Required review views

- **Module front elevation** — Show arch, flared columns, glazing and flat canopy.
- **Module plan** — Show footprint, wall, plinth and connector edges.
- **Module section** — Show canopy projection, glazing and plinth.
- **Variant seam comparison** — Show straight/curved/corner interfaces and mismatches.

## Candidate kits

- CK-KIT-ARCADE-STRAIGHT
- CK-KIT-ARCADE-CURVED
- CK-KIT-ARCADE-CORNER
- CK-KIT-SHOP-CAFE
- CK-KIT-PROPS

## Proposed dependencies

- PI-BLD-0010-V01: Potential straight interface; flat canopy conflicts with flared building shell. (proposed)
- PI-BLD-0010-V02: No curved deformation evidence; separate interface may be needed. (proposed)
- PI-BLD-0010-V03: No corner turn shown; corner/end cap needs separate review. (proposed)

## Decision queue

- Is flat canopy repeated or end cap? Owner: Legend + Quik. Resolution evidence: Module-role decision and assembly sheet..
- Do doors/glazing/plinth belong to module or building? Owner: Quik. Resolution evidence: Component schedule and kit boundary..
- What fits BLD-0010 V01/V02/V03? Owner: Legend + Quik. Resolution evidence: Measured seam study for each variant..
- What span/height/depth and connector rules apply? Owner: Quik. Resolution evidence: Dimensioned spec from measurement, not pixels..

## Friday: can prepare

- Prepare dimensionless single-bay parts with arch/canopy/wall/glazing/plinth separate.
- Draft three interface sketches; keep curved/corner parts separate.

## Friday: requires decision

- Repeat/end-cap role, kit boundary and fit with all arcade variants.
- Measured span/depth/connectors before reusable production geometry.

## Friday: return evidence

- Editable single-bay candidate, not approved kit.
- Front/plan/section and three-way seam comparison.
- Compatible/incompatible/open interface list.

## 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 `35c21ecc33388a1320068a5995727d120883ccd89c8e19101cdf13f353a1c825`
- [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json) · SHA-256 `05d6e2bfe25dc23c04e20627084c2fd16fb741595559e9cf8ca03bbad9c6b633`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `d42ad5c467c3c0015b176801d5688621d345a944fc935bea80039c732c321f0d`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `e1b79a9cb1db17ca9ebf9c2a03adb8e74edde8967f9fcd5e11bbd382bac254d8`
- [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`
- [CONNECTIONS.json](../../../../../protocols/district/R04/templates/CONNECTIONS.json) · SHA-256 `a8b0be74020bc7b67bdf47eb2bacaa52515f301a02423bbc3bd676b4994387ab`
- [README.md](../../../../../protocols/district/R05/README.md) · SHA-256 `f95ad3a6c25f181898fd3be47eac800b39b5f1790387f8e93d5450e75ace5a7d`
- [GUIDE.md](../../../../../workflows/spatial-imagery/R01/GUIDE.md) · SHA-256 `288df4dc11896d4e606f8dc49f8b1a6969679d1fad50fad7595f3e2c8b9ad173`
