# PI-STR-0005-V01 · Dock Connection

EXTERIOR CANDIDATE R01. Editable reusable local geometry, derived views and a proposed dimension/interface contract. All acceptance gates remain false.

## Reference identity

- Sloping timber gangway with open metal truss/handrail sides between shore and floating dock.
- Warm timber, bronze metal and pale dock-edge language continues from the marina kit.

The exact original catalog crop is `catalog-reference.webp`; its immutable source is in `SOURCE_REFERENCE.json`. The catalog is visual evidence, not a survey. Read `CANDIDATE.json` for every editable component and `INTERFACES.json` for route and endpoint datums. Do not infer Crown Key shoreline, bridge count, tide or placement from this candidate.

## Build order for Quik

1. Keep the original source and candidate in separate Blender collections. Use metres, Z up, front −Y, unit object scale.
2. Run the shared `../../../../../../tools/crown_exterior_batch.py` on `CANDIDATE.json`; or import the delivered OBJ/MTL as the exact generated candidate.
3. Review hero/rear/front/plan views and dimensions from this same model before altering the silhouette.
4. Resolve the interface and source gaps below, then attach this local candidate to the reviewed district frame. Endpoint datums are local authoring interfaces, not claimed world coordinates.
5. Check actual structural/support behavior, drainage, collision, route transitions, camera/capsule fit and engine materials. Record real engine tests separately.

## Proposed local interfaces

- floating_end: [0, -5, 0]; finger dock local deck datum; hinge not simulated
- shore_end: [0, 5, 0.4]; proposed shore landing; actual seawall/world datum unresolved

## Route

{
  "polyline_m": [
    [
      0,
      -5,
      0
    ],
    [
      0,
      5,
      0.4
    ]
  ],
  "minimum_clear_width_m": 2.8,
  "candidate_static_slope": 0.04,
  "tide_range_m": null,
  "hinge_motion_tested": false
}

## Source gaps / next decisions

- Actual shore-to-floating elevation/tide range, hinge travel, rollers and collision joints need survey/tests.
- Static 4% pose is proposed; it does not prove usability across tide or dynamic movement.
- Lateral route width and landing length require gameplay/access review.

## Scope boundary

A static local gangway candidate with genuinely sloped deck and rails. No animated or engineered hinge/float behavior is claimed.

No dimension, engineering, access-code or engine compliance is claimed. Local geometry and arithmetic checks only. All cited widths and slopes are proposed and require project-specific review.
