# PI-STR-0002-V01 · Bridge Landing · 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 isolated landing/abutment interface study; do not set coordinates, transforms or routes while foundation inputs are unresolved.

## Scope basis

Concept shows curved abutment, tiled apron/steps and rail continuity, but card vs aerials differ on road/step treatment and landing locations. Switchback attachment is open.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Curved abutment | Pale sweeping face and stepped plinth. | source_notes | How does abutment align to accepted shore endpoint? |
| Apron/grade transition | Tiled apron and steps in card; aerials read road-level. | source_notes | Are steps retained and how do pedestrian/vehicle paths divide? |
| End post/rail joint | Lit end post and bridge rail continuity. | source_notes | Which rail/lamp components continue and where terminate? |
| Switchback interface | Required creator route is not drawn on landing card. | source_record | Where does it attach and what grade/access envelope governs? |
| Shore/water interface | Must meet a selected shore type and datum. | source_record | Which shoreline type and water datum are accepted? |

## Modeling sequence

1. **Register conflicts** — Record landing discrepancies and card/aerial step ambiguity. Gate: No landing ID or position inferred.
2. **Block abutment parts** — Separate face, apron, steps, rail/post and road edge. Gate: Visual form review without fixed location.
3. **Diagram movement** — Separate road, pedestrian and switchback alternatives. Gate: Route/grade selected before layout.
4. **Test joints** — Show span and shore as detached components. Gate: Endpoint/datum agreed before assembly.
5. **Return evidence** — Plan/elevation/section/joint views; dimensions null. Gate: No placement/collision claim.

## Required review views

- **Landing plan** — Show apron and vehicle/pedestrian/ramp options.
- **Water-facing elevation** — Show curved face, plinth and rail.
- **Landing section** — Show deck/water datum and transition unknowns.
- **Span/shore joint axon** — Show detached interfaces, no coordinates.

## Candidate kits

- CK-KIT-BRIDGE
- CK-KIT-ARRIVAL
- CK-KIT-SHORELINE
- CK-KIT-PROPS

## Proposed dependencies

- PI-STR-0001-V01: Proposed span deck/rail joint; endpoints unresolved. (proposed)
- PI-STR-0003-V01: Candidate shore joint; typology/water datum unresolved. (proposed)

## Decision queue

- Which landing endpoints are canonical? Owner: Legend. Resolution evidence: Accepted map-aligned endpoint list..
- Do steps/apron remain or does vehicle road continue? Owner: Legend + Quik. Resolution evidence: Selected circulation plan and separation review..
- Where do ramps attach and what grade/accessibility applies? Owner: Legend + Quik. Resolution evidence: Approved connection section and measured path..
- Which shoreline/datum meets landing? Owner: Legend + Quik. Resolution evidence: Accepted shore detail and datum..

## Friday: can prepare

- Prepare detached abutment/apron/rail kit with grade and endpoint fields blank.
- Diagram road/steps/ramp alternatives without coordinates.

## Friday: requires decision

- Landing endpoints, step/road choice, ramp path, shoreline type/datum.
- Foundation hold release before geography connection.

## Friday: return evidence

- Editable interface blockout and route alternatives.
- Plan/elevation/section/joint views.
- Endpoint/transform register with unknowns.

## 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 `1579e8aac5867a7b98b104f20321301a40da39860bb0367a363c26f16415c222`
- [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json) · SHA-256 `d6e39153f4d50ff2248805fff9d889a61177a9497b0695cc7fc6927a805c5897`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `636891d2bd437b3e76c290004ffb8422f57111a3580d6ff0eb50d0a6f8326f27`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `2b70c6ce333724a2cba36984c88f0a74a97f59c9e2b9e16dce114e4acc5b354d`
- [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`
