# PI-STR-0005-V01 · Dock Connection · 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 a detached dock-to-shore connection study; do not assign tide, hinge, slope, waterline or endpoints.

## Scope basis

Card shows a trussed gangway between stone head block and timber dock but does not show joint behavior or identify whether it is the creator's switchback ramp. Boat-clearance datum is open.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Inclined gangway | Plank/grated deck between shore block and dock. | source_notes | Is it fixed/tide-following and what slope/landing inputs apply? |
| Truss rails | Thin metal rails with diagonal members. | source_notes | What rail/collision/accessibility treatment is selected? |
| Stone head block | Pale upper block with short rail/lamp. | source_notes | Does upper end attach to seawall, promenade or landing? |
| Dock transition posts | Gold-collared posts at transition/upper block. | source_notes | Are posts supports, bollards or visual markers? |
| Route/clearance role | Card doesn't link gangway to switchbacks or 20 m clearance. | source_record | Is it separate from switchback ramp and does it affect boat envelope? |

## Modeling sequence

1. **Classify route** — Keep gangway distinct from switchback requirement until confirmed. Gate: Owner identifies function/endpoints.
2. **Block joint** — Separate head, gangway, truss, lower end and posts. Gate: Fixed/hinged/tide options named, not selected.
3. **Check grade** — Leave slope/landing fields blank until accessibility inputs exist. Gate: Measured path review follows endpoint selection.
4. **Check clearance** — Show boat relation with datum unresolved. Gate: No 20 m pass until datum selected.
5. **Package interfaces** — Return detached end details and connection schedule. Gate: No tide simulation/collision/placement claim.

## Required review views

- **Gangway plan** — Show deck, rails and both ends without dimensions.
- **Longitudinal section** — Show movement options and datum unresolved.
- **Upper block detail** — Show stone block and shore connection.
- **Dock-end detail** — Show truss and lower attachment.

## Candidate kits

- CK-KIT-DOCK
- CK-KIT-SHORELINE
- CK-KIT-BRIDGE
- CK-KIT-PROPS

## Proposed dependencies

- PI-STR-0003-V01: Candidate upper attachment; type/datum unknown. (proposed)
- PI-STR-0004-V01: Candidate lower attachment; support/deck height unknown. (proposed)

## Decision queue

- Is joint fixed, hinged or tide-following? Owner: Quik. Resolution evidence: Selected detail and operating envelope..
- Is this distinct from switchback ramp? Owner: Legend + Quik. Resolution evidence: Named route/function decision in connection spec..
- Where do ends attach and what accessibility criteria apply? Owner: Legend + Quik. Resolution evidence: Endpoint IDs, datum and measured section..
- Does joint affect 20 m boat clearance? Owner: Legend + Quik. Resolution evidence: Water/boat section with explicit datum..

## Friday: can prepare

- Prepare detached gangway/head-block with fixed/hinged alternatives.
- Draft slope/clearance section with missing inputs blank.

## Friday: requires decision

- Route purpose, endpoints, movement type, datum and accessibility.
- Switchback relationship and 20 m applicability.

## Friday: return evidence

- Editable detached joint and connector spec.
- Plan, longitudinal section and end details without placement.
- Decision record separating observation from route requirement.

## 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 `3fe629a3e373e2f860d0f57d68f5df6905691b4f8d0ffde36b4b9455ce1ac150`
- [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json) · SHA-256 `d43b04dc35a4cf8be8c4a0136c4475b0b3a2c000d73593753a5e97bbd92da62b`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `636891d2bd437b3e76c290004ffb8422f57111a3580d6ff0eb50d0a6f8326f27`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `ffcd2030bd057edc0737915097f1cf48c6053857204efcdb68163bbc49300e41`
- [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`
