# PI-STR-0004-V01 · Finger Dock · 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 unplaced dock module and boat/access-envelope study; leave dock count, length, shore positions, datum and support type unresolved.

## Scope basis

Card shows timber deck, gold-collared posts and cleats; aerial dock counts/locations differ. Creator's 20 m boat-clearance direction is retained but datum/applicability need confirmation.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Timber finger deck | Narrow plank deck with pale edge and dark underside blocks. | source_notes | What are deck dimensions/elevation and is deck fixed or floating? |
| Posts/cleats | Gold-collared posts, pale caps and gold cleats. | source_notes | What spacing and mooring use is intended? |
| Support system | Card suggests floating blocks; piles are not established. | source_notes | Is dock floating, pile-supported or another system? |
| Boat envelope | 20 m direction retained; route/datum/applicability open. | source_record | Does it apply and from which water/deck/tide datum? |
| Shore access | Aerial finger counts/locations vary and are not survey evidence. | source_notes | Which segments/count are approved and how connect to promenade? |

## Modeling sequence

1. **Separate evidence** — Record card detail and aerial variation; don't read pixels as dimensions/count. Gate: No dock footprint or quantity inferred.
2. **Block deck/mooring** — Parameterize deck, edge, posts and cleats separately. Gate: Appearance review precedes dimensions.
3. **Select support** — Keep floating/pile options separate until decided. Gate: Structure assumptions are recorded.
4. **Define clearance test** — Show 20 m as a datum-linked blank field. Gate: No pass without measurement method and route.
5. **Connect to shore** — Keep STR-0003/0005 joints detached. Gate: No snap location/tide behavior assumed.

## Required review views

- **Dock plan** — Show deck, posts/cleats and connector with dimensions unset.
- **Side elevation** — Show deck/water relation with datum/support open.
- **Boat-clearance section** — Label direction and datum as unresolved.
- **Shore joint axon** — Show detached dock/gangway/promenade.

## Candidate kits

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

## Proposed dependencies

- PI-STR-0003-V01: Candidate shore joint; datum/edge type must be accepted. (proposed)
- PI-STR-0005-V01: Proposed gangway joint; tide/grade/attachment open. (proposed)

## Decision queue

- Is dock floating or pile-supported? Owner: Quik. Resolution evidence: Selected support detail and assumptions..
- What datum measures 20 m and does it apply here? Owner: Legend + Quik. Resolution evidence: Approved datum, route and measured section..
- How many docks and which segments? Owner: Legend. Resolution evidence: Accepted placement schedule from refreshed master..
- How does gangway attach accessibly? Owner: Quik. Resolution evidence: Joint section and measured route review..

## Friday: can prepare

- Prepare detached deck/post/cleat parts with dimension fields unset.
- Draw boat-clearance section with datum null.

## Friday: requires decision

- Support type, datum/20 m method, dock count and shore endpoints.
- Foundation/shoreline reset before placement.

## Friday: return evidence

- Editable unplaced dock and envelope study.
- Plan, side section, clearance annotation and joint axon.
- Explicitly exclude aerial counts and old bridge-layout figures.

## 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 `c026d6d98f8a8b589fbd679c18bc8589af4d90e5ff6bfe2dc7c5f094e564d44a`
- [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json) · SHA-256 `74bb6ff781b353dddc0da10029c130a56b62de286b1276aa21e03c49d8e6e29b`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `636891d2bd437b3e76c290004ffb8422f57111a3580d6ff0eb50d0a6f8326f27`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `c61b3446152203925c4b38c6845b76c14afc4a29aaf6cc671546bd9fc46881cb`
- [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`
